Why it matters
- hreflang links tell Google which page to show to which reader: the Arabic page to someone searching in Arabic, the English one to someone searching in English, the Saudi one in Saudi Arabia.
- Google's guide is strict: "If two pages don't both point to each other, the tags will be ignored", and "If page X links to page Y, page Y must link back to page X". A version that does not return the link breaks the set for both.
- A version that redirects, answers an error, says
noindexor names another canonical cannot be shown as itself, so its hreflang link points nowhere useful.
How to fix
Write the same full set of hreflang links on every version, each version naming itself and all the others:
html
<link rel="alternate" hreflang="ar" href="https://www.example.com/" />
<link rel="alternate" hreflang="en" href="https://www.example.com/en/" />- Use each version's final address: the one that answers 200 and names itself as canonical.
- A store with Arabic and English pages often has the links on one language only; add them to the other.
How we detect
- We read the page's hreflang links:
<link rel="alternate" hreflang>in<head>, andLinkheaders. hreflang in sitemaps is judged byhreflang-sitemap-invalid. - We ask for each version, the first ten that are not the page itself, once, with GET, without following a redirect, where its site's robots.txt lets ArablyzerBot.
- We report a version that answers a redirect, an error or
noindex, that names another canonical, or whose own hreflang links do not name this page or its canonical address. A slash at the end of a path is not counted as a difference. Versions that refuse a bot (401, 403, 429, 503), or did not answer, are not judged.