LEYUN · SITE LAUNCH CHECKLIST独立站上线自查清单库

hreflang Configuration Review for Multilingual Sites

Sections: Crawl & Indexing · Reviewed: 2026-11-21 · 12 items

Key takeawayThe most common indexing problem on multilingual sites is not thin content but language versions that fail to reference each other, leaving the system to guess which version belongs to which region. This sheet checks code format, reciprocity, canonical alignment and validation.

Industries and use cases

  • Adding a second or further language version
  • After switching multilingual plugins or templates
  • When one language version is not indexed or indexed incorrectly
  • Before running ads in multiple regions and needing the right landing version

Checklist

Checklist: hreflang configuration review
Check itemPass criteriaRisk levelFix hint
Language and region code formatISO 639-1 language codes with ISO 3166-1 region codes such as en-US, de-DE or zh-CNHighUse uppercase region codes consistently and never mix en-us with en-US.
Reciprocal referencesPage A lists page B and page B lists page A, forming a closed loopHighCheck page by page against the language matrix; a missing return link voids the whole set.
x-defaultEach set names one default version, usually an international or English pageHighPoint x-default at a region-neutral page, not a country-specific landing page.
Self referenceEach page includes an entry pointing to itselfMediumSelf references are frequently forgotten; include the current page in template output.
Reachable targetsEvery annotated URL returns 200 and none points to a 301, 302 or 404HighAnnotate the final URL; redirects lose the signal in transit.
Canonical alignmentEach language version canonicals to itself and never across languagesHighCross-language canonicals cancel each other out, so keep every page self-canonical.
One primary methodhead tags, HTTP headers or sitemap declarations are used as the primary method without conflicting duplicatesMediumLarge sites should declare in the sitemap to reduce template work.
Currency and region fitPrices, units and contact details on a regional version match its target marketMediumTranslating text while keeping the original currency makes the region annotation meaningless.
Switcher consistencyLanguage switcher links and hreflang entries point to the same set of URLsMediumGenerate both from one language configuration instead of maintaining two lists.
Full coverageEvery live language version is included with no omissionsMediumAfter adding a language, update all older versions rather than only the new one.
No untranslated pagesPages without finished translation are excluded from hreflangLowDo not publish unchecked machine translation, which distorts overall language signals.
ValidationSearch Console international targeting or a third-party validator reports no errorsMediumCheck within a week of launch and sample one language group monthly afterwards.

Common misjudgements

  • Believing finer language codes are better: city-level codes have no support and only add maintenance cost.
  • Declaring older languages only from the new page and leaving old pages untouched, which looks efficient but breaks the loop.
  • Treating hreflang as a translation switch: it selects a version, it does not make content localised.

How to use this checklist

  • Pair with the duplicate content sheet: confirm each version is unique first, then handle language targeting.
  • Re-run fully whenever a language is added and sample the main language groups quarterly.
  • Link with the sitemap sheet so both annotation methods share one URL table.

FAQ

Is hreflang needed when only English and Chinese exist?
It is recommended, especially when the two versions target different regions, as it reduces version mismatches.
Does hreflang improve rankings?
It does not raise rankings directly; it helps show the right language version to the right user.
Can a language code be used without a region code?
Yes, but for a specific market the language plus region pair is more precise.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.

If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.

Note: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.