What hreflang does
Hreflang tells Google which language or regional alternatives belong together. It helps the search system choose an appropriate version for a user. It does not translate content, guarantee a ranking or replace a canonical. Begin with a list of real equivalent pages, not a list of countries you would like to target.
A useful example is a product offered in English for Ireland and German for Germany. Each page needs accurate local information and a working URL. If the product is not sold in Germany, creating a German alternate solely for search coverage is not a sound implementation plan.
Choose actual equivalents
Build an inventory by page purpose. A category should reference corresponding categories; it should not point every language alternative to a homepage. Include the page itself and all relevant alternatives in each group. Record missing equivalents before adding annotations so incomplete groups are intentional rather than accidental.
Language and country are separate concepts. Use supported language codes and, where justified, a region code. An English page can serve more than one country. Region-specific pages need meaningful operating differences or a clear reason to exist, not merely a different flag.
Keep canonicals and return annotations consistent
Distinct localised pages normally use self-referencing canonicals. A German alternate canonicalised to the English page sends conflicting signals about which URL should be indexed. Check that every listed page is accessible and that alternatives point back to the relevant group.
Implementation can use HTML link elements, HTTP headers or a sitemap. Choose a maintainable method for the platform. If more than one method is used, the groups must agree. A crawler export, source inspection and an independent URL sample help identify template-level errors before release.
Use x-default only for a genuine fallback
An x-default annotation can identify a fallback page for users whose language or region is not explicitly covered. It may be a selector or a broadly suitable page. It is not a required extra country and should not be added to every group without deciding what the fallback actually does.
Visitors must still be able to choose another version. Automatic location or language redirects can interfere with access and crawling. Avoid forcing every user or crawler through a selector before reaching the content. Use crawlable links so alternatives remain discoverable.
Validate the release
Check final status codes, canonical values, annotations, language content and internal links. Redirected or blocked URLs should not remain in the alternate group. Test representative pages from each template, then inspect the full inventory for missing return links and inconsistent country codes.
Monitor the intended pages in Search Console after release. Indexation and the version shown to users may take time to change. A valid annotation does not establish that Google has indexed every alternate. Separate implementation validation from observed search performance.
Plan ownership before adding languages
Assign an editorial owner, implementation owner and review process for every market. Product changes, discontinued pages and new launches must update alternate groups as well as the visible content. International SEO becomes difficult to maintain when localisation and development operate from different URL lists.
Our aviation case documents a 14-market programme using localised subfolders and a hreflang matrix. It provides an existing project context, not a universal architecture prescription. Review its scope alongside your own platform and operating requirements.
Sources and next steps
Primary documentation: official crawler or localisation guidance. Platform rules can change; verify the current documentation before implementation.


