International SEO
A practical hreflang checklist for multilingual websites
Hreflang does not translate a page, detect its language, or guarantee ranking. It maps genuine language or regional alternatives so a search engine can serve a more appropriate URL. The mapping works only when the documents and URLs remain consistent.
Think in document groups, not isolated tags
Every translated document needs a stable identity and a complete set of alternates. Each version lists itself and all counterparts with absolute URLs. The references must be reciprocal, indexable, and aligned with each page’s same-language canonical. x-default is optional and should have an intentional destination.
1. Define the language and URL model first
Give every language its own crawlable URL rather than changing the same URL from cookies or Accept-Language alone. Decide whether you target languages, language-region combinations, or both. Use valid codes and only create regional variants when their main experience genuinely differs.
- Keep a stable internal content key separate from translated slugs so alternates are generated from one source of truth.
- Use visible native-language content; search engines determine language from the page, not from hreflang or the html lang attribute alone.
- Offer a clear language switcher and avoid forcing visitors through IP-based redirects they cannot override.
2. Publish one complete reciprocal group
For English, Romanian, and Hungarian versions, each page should list all three URLs plus itself. If English is the general fallback, an x-default link can point there; a dedicated selector is another option. Absolute URLs reduce ambiguity across hosts and protocols.
- If page A names page B as an alternate, page B must name page A back or the relationship may be ignored.
- Do not mix unrelated articles because their slugs or templates look similar; alternates must represent the same underlying document.
- Keep each genuine translation self-canonical instead of canonicalizing every language to the default version.
3. Choose a maintainable delivery method
Google supports HTML, HTTP headers, and XML sitemaps for hreflang. A site can use more than one, but every implementation must remain identical. HTML is visible near the document, while sitemap groups can be easier to generate and audit across a content registry. Maintenance reliability matters more than duplication.
- Generate HTML language-switcher targets and sitemap alternates from the same registry to prevent drift.
- Keep alternate targets out of redirect chains and ensure they return stable indexable content.
- Update or remove the entire group when a translation is renamed, retired, merged, or temporarily unavailable.
4. Test URLs, reciprocity, and rendered language
Validate more than syntax. Crawl every group, resolve each alternate, compare canonical and language, and verify that the switcher reaches the equivalent document. Include localized slugs, trailing-slash redirects, query handling, and wrong-language slug behavior in automated tests.
- Assert one self-canonical, one alternate per supported language, and one intentional x-default on every indexable version.
- Reject or redirect duplicate locale roots and outdated slugs before publishing their replacements in the sitemap.
- Monitor Search Console and real landing behavior after release; correct markup cannot compensate for untranslated or low-value content.
Hreflang release checklist
- 01 Assign one stable content identity and a distinct crawlable URL to each genuine language version.
- 02 Use valid language or language-region codes and absolute final URLs.
- 03 List every counterpart, including the current page, and make every relationship reciprocal.
- 04 Keep each translation self-canonical and ensure all alternates return indexable 200 responses.
- 05 Choose an intentional x-default destination and keep the visible language switcher equivalent.
- 06 Generate and test HTML and sitemap mappings from one registry whenever both are published.
A complete mapping is a content promise
Hreflang succeeds when the same document truly exists at stable, useful URLs in every declared language. Model that relationship once, generate every consumer from it, and test reciprocity whenever content changes. The tag is the final expression of the translation system, not a repair for a missing one.
Primary references
Continue with a related guide
These checks influence one another. Follow the next guide to verify the surrounding signals, not only one tag or score.