Auditing hreflang after a regional site migration

Audit hreflang after migrating regional URLs. Compare declared alternates, redirects, reciprocal references and the final pages customers receive.

A world map with colored pins sits beside a globe and a site migration checklist.

A migration can leave every translated page online and still make its language annotations disagree. Customers then land on a regional version that looks plausible but quotes the wrong currency or talks about the wrong service area.

Start with one product family

List the intended equivalent URLs from the publishing system, including any general fallback. Inspect the alternates that each page declares. Verify each referenced destination resolves to its intended final page and that reciprocal references exist where expected. A similar title alone is poor evidence that two pages are equivalents. Google Search on multilingual and multi-regional sites.

Separate markup from delivery

Check whether the links still describe the same pages when opened from the target markets. With XtremeProxy, a release team can investigate country-sensitive redirects on its own sites without assuming that an annotation itself triggers the redirect. Report the source URL, declared alternate, observed destination and intended replacement in one row. This gives engineering a concrete repair list before the migration rolls out further.

For example, replacing a product slug in one language can leave its peers pointing to a redirect. The new page might still work when opened directly. A table of declared destination versus final destination exposes stale references in the other locales that a single-language launch review would miss.

One alternate still points to the retired path

A product family has Canadian English, Canadian French and US English pages. After a migration, the French page declares the two new English URLs but one English page links back to the retired French URL. Draw each declaration as an arrow and check final destinations and response codes. A temporary redirect may make the old page appear to work in a browser while preserving a stale annotation. Correct the shared publishing template and retest all three directions on the released pages.

Compare the declarations in both directions

An alternate may resolve correctly while naming a translated category page instead of the matching product. Record the intended equivalence group from the CMS and inspect each declared destination within that group. Retain the final canonical reference separately so a reciprocal link does not hide another conflicting signal.

Inspect the actual URL named in each alternate annotation, including its host and path. Redirects that repair a visitor’s old bookmark can conceal obsolete annotations from a casual browser test. Extracting the declarations directly from each released language version makes that discrepancy visible.

Inspect the generic fallback

Alongside the language-specific pages, the site may declare a neutral selector as a default destination. Confirm that this page actually helps an unmatched visitor choose a region and that its links resolve after migration. A default selector can be correct for an unmatched audience yet incorrect as the supposed French equivalent of an individual product.

Check every delivery surface your publishing system actually uses for language alternates. A migration can update annotations in the HTML template while a sitemap generator continues to emit the retired host. Select a small translation family from the CMS and compare its declared URLs across those outputs, including any separate deployment dates. If the sources disagree, identify the generator responsible for each declaration. Repairing a redirect on the retired URL alone leaves the site publishing contradictory instructions about the same translation family.

Set aside a small migration sample containing one discontinued page, one regional translation that moved, and one page with no equivalent in another market. Inspect the final HTTP destination of each alternate link before comparing the returned language annotations. A link can land on a valid regional homepage and still be the wrong equivalent for a product article. Record the old address, final address and intended content identifier. This evidence gives the migration team a concrete link to fix without adding a misleading language alternate for a page that never had a translation.

After repairing an alternate, test the equivalent page in every direction and identify which signals still point to a retired URL. Reciprocal language alternates is a practical model for reciprocal declarations. If the search result itself is correct and the customer still lands in another market, investigate the navigation path with Diagnosing a search result that lands on the wrong country store. Compare XtremeProxy network types.

Frequently asked questions

Does a successful country redirect prove that alternate annotations are correct?

Read the annotations on each intended regional page and inspect what they point to. Redirect behavior and search-engine interpretation involve different signals. Record the actual declarations and give indexing changes time to appear in the site's reporting.

Related articles