Auditing hreflang: crawler vs Search Console vs log files

Auditing hreflang: crawler vs Search Console vs log files

Three diagnostic tools, three different truths. Relying on one gives a partial and sometimes misleading picture.

What each actually tells you:

— Crawlers (Screaming Frog, Sitebulb) excel at reciprocity and syntax: missing return tags, invalid codes, non-canonical conflicts, at scale. Their blind spot — they crawl what they can reach. JavaScript-injected or geo-served hreflang may not appear as Google sees it.
— Search Console's International Targeting / hreflang reports show what Google actually parsed and where it found errors. This is ground truth for Google's view, but it is sampled, lagged by days, and notoriously vague on which specific URL failed.
— Log files reveal whether Googlebot even fetched the alternate URLs. We have diagnosed 'phantom' hreflang errors that were really crawl-budget starvation — Google never saw the return tag because it never crawled that locale.

The data suggests no single tool is sufficient. Crawlers find syntax errors fast; Search Console confirms Google's interpretation; logs explain why a syntactically perfect tag still fails.

Our workflow: crawl first to fix the obvious, cross-check Search Console for what Google parsed, reach for logs only when the first two disagree. Limitation — Search Console hreflang reporting has degraded over time and should be treated as directional, not exhaustive.