Hreflang and Canonicals: Checking That Signals Agree

Hreflang and canonical tags solve different problems, but a mismatch between them can make an international site hard to interpret. Canonicals express the preferred URL for duplicate or very similar content; hreflang identifies localized alternates. Before changing either, decide which URL should be indexed for each language or region and whether the pages truly offer a distinct localized experience.

Build a URL-pair table

List each live regional page, its language and region, intended canonical, hreflang alternates, status code and indexability. Start with a small template such as the homepage, a service page and a product page. Check what the rendered page actually outputs, not only the CMS fields. Include mobile and desktop renderings if they differ. A spreadsheet makes contradictions visible before a deployment changes hundreds of URLs.

Google’s localized-version guidance says each language version should list itself and the other versions. Its canonical guidance says hreflang pages should point to a canonical in the same language where one exists. A canonical is a signal, not a command; Google may choose another representative URL.

Test a three-page example

Illustrative URLs, not a Megvi implementation: /en-ae/service/, /en-gb/service/, and /ar-ae/service/. Each returns 200, contains useful localized content, and has a self-referencing canonical. Each page’s hreflang annotations list all three alternates, including itself, with reciprocal target URLs. The Arabic page must contain Arabic main content; translating only the navigation does not create a meaningful localized page.

Now imagine /ar-ae/service/ canonicals to /en-ae/service/ while hreflang presents it as the Arabic alternate. The signals disagree about whether the Arabic URL should stand on its own. Investigate why that canonical was set; do not simply add more hreflang tags. Likewise, a regional page that redirects or is marked noindex should not be treated as an ordinary indexable alternate.

A compact audit checklist

• Resolve every alternate URL and record status, redirect destination and canonical.
• Check that each page names itself and the other intended alternates consistently.
• Confirm the language and regional content is genuinely useful to that audience.
• Check that the canonical target is in the same language when possible.
• Inspect a sample in Search Console to compare declared and Google-selected canonicals.
• Repeat after templates, translation processes or URL structures change.

Do not assume that a clean tag audit guarantees the right page will rank in each country. The content, internal links and site structure still matter. The broader website translation for SEO guide helps plan distinct localized content.

Megvi’s international SEO service can review a URL sample, template output and Search Console evidence. Bring your current language map and the URLs that appear in the wrong market.

Google Search Central guidance reviewed 19 October 2026. URLs in the example are hypothetical.