Check your hreflang tags before localized pages compete with each other

SiteCurl reviews hreflang tags on the page and flags pages that do not declare them correctly. This is useful for sites with multiple language or regional versions that risk showing the wrong page to the wrong audience.

The check looks for <link rel='alternate' hreflang='...'> tags in the page head and validates the language and region codes used. It also checks whether the page includes a self-referencing hreflang tag, which is required for the hreflang set to be complete.

SiteCurl flags pages where hreflang tags are present but incomplete, such as when a page declares alternates for three locales but is missing the return tag for one of them. Incomplete hreflang sets are treated as errors by most search engines.

Hreflang is a signal that tells search engines which version of a page to show based on the searcher's language and location. A user searching in French from Canada should see the French-Canadian version, not the US English version. Without hreflang, the search engine guesses based on content signals, which often leads to the wrong version ranking in the wrong market.

The hreflang specification requires reciprocal links. If page A declares page B as an alternate, page B must also declare page A. If the return link is missing, search engines may ignore the entire hreflang set for those pages. This reciprocal requirement is the most common source of hreflang errors because it requires coordination across every localized version of every page.

Hreflang tags can be implemented in three places: HTML link tags in the page head, HTTP headers, or the XML sitemap. HTML tags are the most common approach. Sitemap-based hreflang is useful for sites where modifying the HTML head is difficult, but the relationships still need to be complete and reciprocal.

The x-default hreflang value is a special code that designates a fallback page for users whose language or region does not match any declared alternate. It is optional but recommended for sites with a clear default version, such as an English-language page that serves all markets without a specific localization.

Without hreflang, search engines may rank the wrong regional page or split signals across language variants. Visitors then land on the wrong currency, wrong spelling, or wrong legal copy, which hurts trust and conversion.

International SEO without hreflang is confusing. Google may decide to show your UK English page to US searchers, your French page to Belgian users searching in Dutch, or your Australian pricing page to users in Germany. Each mismatch is a lost opportunity: the user sees irrelevant content and either bounces or converts at a lower rate.

Ranking signal consolidation is another benefit. Without hreflang, each localized version of a page competes independently in search. Links earned by the US version do not help the UK version. With hreflang, search engines understand these are the same page in different markets and can consolidate signals accordingly, improving rankings for all versions.

Global e-commerce sites are the primary audience. A store selling in the US, UK, and EU needs hreflang to show the correct currency, shipping options, and legal notices for each market. A British shopper who lands on the US version sees prices in dollars and shipping estimates that do not apply, which kills trust.

SaaS companies with localized marketing sites need hreflang to prevent their English-language pages from outranking localized versions in non-English markets. Without it, the English version often wins because it has more links, even though the local version is more relevant to the searcher.

Content publishers with translated articles need hreflang to avoid duplicate-content confusion. If the same article exists in English, Spanish, and Portuguese, search engines need hreflang to understand these are translations, not copies. Without it, they may index only one version and ignore the rest.

Step 1: Add self-referencing and alternate hreflang tags to every localized page. Each page must declare itself with its own language code and list every other localized version as an alternate. If you have English, French, and German versions, each page needs three hreflang tags (one for each language including itself).

Step 2: Use valid language and region codes. Language codes follow ISO 639-1 (e.g., en, fr, de). Region codes follow ISO 3166-1 Alpha 2 (e.g., en-US, en-GB, fr-CA). Invalid codes are ignored by search engines.

Step 3: Align canonical tags with hreflang. Each localized page should have a self-referencing canonical that matches the URL used in its hreflang tag. A page should not canonicalize to a different locale unless that locale is the preferred version.

Step 4: Verify reciprocal links. Check every alternate page to confirm it links back. If the US English page declares a UK English alternate, the UK English page must also declare the US English page. Missing return links invalidate the entire hreflang set for those pages.

Missing return tags. Hreflang must be reciprocal. If page A lists page B as an alternate but page B does not list page A, search engines may ignore the entire set. This is the single most common hreflang error.

Mixing canonicals and hreflang incorrectly. A page should not canonicalize to another locale unless that locale is genuinely the preferred version. If the French page canonicalizes to the English page, it tells search engines the French page should not be indexed independently.

Using hreflang on sites that do not have true alternates. Hreflang only helps when equivalent content exists in each declared language or region. A page that lists five language alternates but only has real content in two of them creates broken expectations for crawlers and users.

Forgetting x-default. Without an x-default fallback, searchers in unlisted regions may see an arbitrary version. Adding a default page ensures everyone has a reasonable starting point.

Run another scan and confirm the hreflang warning clears. Then inspect the page source on each alternate version to make sure the hreflang set is complete and consistent.

For a thorough check, visit each localized version and view the page source. Count the hreflang tags: every page should have the same number of tags (one per locale plus x-default if used). If the counts differ between pages, at least one version is missing a return link. Use Google Search Console's International Targeting report to see how Google interprets your hreflang setup.