Hreflang Pro

Your hreflang can look perfect on the page and still be completely ignored by Google. Here's why. Hreflang isn't a page-level tag. It's a handshake. If your /de/ page points at /fr/ but /fr/ doesn't point back, Google throws that pairing away. Nothing errors. Nothing 404s. Your tags look flawless in view-source. You just quietly stop showing up in that market. Which is the problem with checking one page at a time: you're inspecting one half of a conversation and hoping the other half agrees. It usually doesn't. Hreflang Pro checks the whole conversation. ONE CLICK, WHOLE CLUSTER Open any page in the set, click the icon, done. It reads your hreflang from the HTML, from HTTP Link headers, and from your XML sitemaps (including sitemap indexes it finds through robots.txt). Then it goes and fetches every alternate URL and checks them all against each other. No crawl to configure. No spreadsheet of pairs. No firing up a desktop crawler to check one template. THE MATRIX IS THE WHOLE POINT Every page down the side. Every language across the top. One dot per pair. Green means confirmed in both directions, red means broken, gold means self-referencing. You'll find the gap in about two seconds. So will your client, when you drop the PNG into the deck. That's the bit users keep telling me they love, and it's the bit a single-page checker physically cannot give you. IT FINDS THE STUFF THAT HIDES Search Console tells you that you have return tag errors. It won't tell you which pages, or what to change. And since it retired the International Targeting report, hreflang is pretty much the only lever you've got left. Worth knowing it actually works. Over 25 checks, including the ones people get caught by: • Missing return tags and missing self-references, mapped page by page • Invalid codes, validated properly against ISO 639-1, ISO 15924 scripts (zh-Hans, sr-Latn) and ISO 3166-1 regions. It knows es-419 isn't supported, that EU gets ignored, and that "se" is Northern Sami before it accuses you of a typo • Alternates blocked in robots.txt. They load fine for you. Googlebot never sees them • Redirects that fire on browser language. It refetches with a matching Accept-Language to prove whether a crawler gets bounced, instead of guessing • Pages that disagree with each other about which URL serves which language • Sitemap and HTML declaring different hreflang for the same page • Canonicals quietly undermining the whole set • noindex conflicts, including X-Robots-Tag headers that never appear in the source • x-default missing, redirecting, or pointing outside the cluster • Relative URLs, #fragments, tracking parameters, tags sitting outside the head • html lang and Content-Language mismatches (that second one matters for Bing, which ignores hreflang entirely) • Hreflang injected by JavaScript, flagged as an FYI rather than an error WHAT YOU WALK AWAY WITH • A 0 to 100 cluster health score, so you can show progress rather than describe it • Issues ranked by impact, in plain English, with the exact tag to paste in • The cluster matrix, exportable as a PNG • CSV for the dev ticket, JSON for your pipeline, Markdown for pasting straight into an LLM or a client report • Safe mode for Shopify and anything else that rate-limits you, with throttled requests and automatic retries HOW IT WORKS Click the icon. That's it. Everything runs locally in your browser. No account, no sign-up, no tracking, nothing sent to us. It injects nothing into your pages either. Built by Chris Lever SEO at Glass Atlas.