Hreflang tells Google which version of a page to show depending on the user's language or country. It is one of the most fragile parts of technical SEO: every page has to link to all its translations, and every translation has to link back.
AD2SPIDER reads hreflang in the HTML, in the HTTP header and in sitemaps, and checks that codes are valid, that every link has a return link, that there is a self-reference and an x-default, and that targets return 200, are indexable and are the canonical version.
Hreflang warnings
Real problems worth fixing.
Invalid hreflang code
- Why it matters
- The code does not follow language[-region] (ISO 639-1 / ISO 3166-1) nor is x-default: it is ignored.
- How to fix it
- Use codes like es, es-ES, en-GB or x-default.
Hreflang without self-reference
- Why it matters
- The page declares alternates but does not include itself in the set.
- How to fix it
- Add an hreflang pointing to this URL with its language.
Hreflang points to a non-200 URL
- Why it matters
- The alternate redirects or errors: the annotation is useless.
- How to fix it
- Point each hreflang at the final URL returning 200.
Repeated hreflang code with different targets
- Why it matters
- The same language/region points to several URLs: the signal is ambiguous.
- How to fix it
- Keep one URL per code.
Hreflang without return link
- Why it matters
- The alternate does not link back to this page: Google may ignore the pair.
- How to fix it
- Add an hreflang on the alternate page pointing back here.
Hreflang outside <head>
- Why it matters
- The hreflang annotation is in the <body> (or the <head> closed early because of an invalid element): Google ignores it.
- How to fix it
- Move the <link rel="alternate" hreflang> tags into <head> and check that no invalid element closes it early.
Hreflang to a non-canonical URL
- Why it matters
- The declared alternate has a canonical pointing elsewhere: the signals conflict and Google may ignore the annotation.
- How to fix it
- Point hreflang to the canonical URL of each language version.
Hreflang to a noindex URL
- Why it matters
- The declared alternate is noindex: it cannot appear in results and the annotation is useless.
- How to fix it
- Remove noindex from the language version or drop it from the hreflang annotations.
Hreflang on a canonicalised page
- Why it matters
- The page has hreflang annotations but its canonical points to another URL: hreflang should be declared on (and point to) canonical URLs.
- How to fix it
- Declare hreflang on the canonical URL, or make the page self-canonical.
Inconsistent language and region return links
- Why it matters
- This page annotates the alternate with a different code from the one the alternate uses for itself: Google may ignore the pair.
- How to fix it
- Use the same language and region code for each URL across all annotations.
Unlinked hreflang URL
- Why it matters
- The URL only appears in hreflang annotations: no internal page links to it, so it gets little authority and is hard to discover.
- How to fix it
- Link to the language versions across the site (for example, with a language switcher).
Hreflang opportunities
Improvements with impact, usually based on configurable thresholds.
Missing x-default
- Why it matters
- The page declares language alternates but no x-default: Google does not know which version to show users of other languages or regions.
- How to fix it
- Add an hreflang="x-default" pointing to the default version (for example, the language selector or the English version).