Check your hreflang tags before localized pages compete with each other

SiteCurl reads hreflang tags on each page and flags pages that do not set them right. This helps sites with more than one language or region version avoid showing the wrong page to the wrong crowd.

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

SiteCurl flags pages where hreflang tags exist but are partial. For instance, a page may list alternates for three locales but miss the return tag for one. Partial hreflang sets are treated as errors by most search tools.

Hreflang tells Google which version of a page to show based on language and location. A user searching in French from Canada should see the French-Canadian page, not the US English one. Without hreflang, Google guesses from content cues, which often leads to the wrong version ranking in the wrong market.

The hreflang spec requires return links. If page A lists page B as an alternate, page B must also list page A. If the return link is missing, Google may ignore the full hreflang set for those pages. This return-link rule is the top source of hreflang errors because it needs sync across each locale of each page.

Hreflang tags can go in three places: HTML link tags in the page head, HTTP headers, or the XML sitemap. HTML tags are the most common. Sitemap-based hreflang works for sites where changing the HTML head is hard, but the links still need to be full and paired.

The x-default hreflang value is a special code that names a fallback page for users whose language or region does not match any listed alternate. It is not required but is a good idea for sites with a clear default version, such as an English page that serves all markets with no local version.

Without hreflang, Google may rank the wrong regional page or split signals across language forms. Users then land on the wrong currency, wrong spelling, or wrong legal text. That hurts trust and sales.

Global SEO without hreflang is a mess. Google may show your UK page to US users, your French page to Dutch-speaking Belgians, or your Aussie pricing page to users in Germany. Each mismatch is a lost chance: the user sees the wrong content and either leaves or buys at a lower rate.

Signal merging is a bonus too. Without hreflang, each locale version of a page fights on its own in search. Links earned by the US version do not help the UK version. With hreflang, Google knows these are the same page in new markets and can merge signals, lifting rankings for all versions.

Global online stores are the main crowd. A store selling in the US, UK, and EU needs hreflang to show the right currency, shipping, and legal notices for each market. A British shopper who lands on the US version sees dollar prices and wrong shipping. That kills trust.

SaaS firms with local marketing sites need hreflang to stop the English pages from outranking local versions in non-English markets. Without it, the English version often wins because it has more links, even though the local version is a better fit for the user.

Content sites with translated articles need hreflang to avoid same-content confusion. If one article exists in English, Spanish, and Portuguese, Google needs hreflang to know these are translations, not copies. Without it, Google may index only one version and skip the rest.

Step 1: Add self and alternate hreflang tags to each locale page. Each page must list itself with its own language code and list all other locale versions. If you have English, French, and German, each page needs three hreflang tags (one per language, itself included).

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

Step 3: Line up canonical tags with hreflang. Each locale page should have a self-set canonical that matches the URL in its hreflang tag. A page should not point its canonical to a new locale unless that locale is the main version.

Step 4: Check return links. Open each alternate page and confirm it links back. If the US English page lists a UK English alternate, the UK page must also list the US page. Missing return links void the full hreflang set for those pages.

Missing return tags. Hreflang must go both ways. If page A lists page B but page B does not list page A, Google may ignore the full set. This is the top hreflang error.

Mixing canonicals and hreflang the wrong way. A page should not point its canonical to a new locale unless that locale is the main version. If the French page points its canonical to the English page, it tells Google the French page should not be indexed on its own.

Using hreflang on sites with no real alternates. Hreflang only helps when equal content exists in each listed language or region. A page that lists five language forms but only has real content in two of them sets up false hopes for crawlers and users.

Skipping x-default. Without an x-default fallback, users in unlisted regions may see a random version. Adding a default page gives each user a good starting point.

Run a new scan and check that the hreflang warning clears. Then view the page source on each alternate to make sure the hreflang set is full and consistent.

For a deep check, visit each locale version and view page source. Count the hreflang tags: each page should have the same count (one per locale plus x-default if used). If the counts differ, at least one version is missing a return link. Use Search Console's global targeting report to see how Google reads your hreflang setup.