Why does Search Console hide your international hreflang pages?

What does it mean to "report only on canonical URLs"?

Search Console aggregates data at the level of the declared canonical URL. If your site offers example.com/fr/, example.com/de/, and example.com/en/ with hreflang, Google selects one version as the reference — usually what it considers the main version.

The impressions, clicks, and positions of alternative variants do not come up individually. You see the consolidated overall performance, but it’s impossible to tell if your clicks are mainly coming from the German or French version. It’s like flying a multi-engine plane with a single gauge for all engines.

How does this impact multilingual sites?

An e-commerce site active in 15 countries ends up with analytic black holes. You know the Spanish version exists, that it is indexed, but its specific metrics? Untraceable in the standard interface.

Local SEO teams lose their autonomy to operate. The SEO manager for Germany cannot prove to their management that their optimizations are working, as their KPIs are drowned in a global aggregate. And this is where the issue lies — editorial decentralization requires a reporting granularity that Google refuses to provide.

Why does Google maintain this limitation?

Technical simplicity above all. Processing and displaying data for each hreflang variant would exponentially increase server load and interface complexity. Google chose to simplify its infrastructure at the expense of granularity.

But let’s be honest: this justification really doesn’t hold anymore. Third-party tools like Analytics 4 handle multilingual segmentation perfectly well. Google could technically offer a detailed view as an option, but that’s clearly not a product priority.

• Search Console consolidates data at the level of the canonical URL chosen by Google
• Alternative hreflang pages disappear from performance reports even when they are serving traffic
• This limitation is a design choice, not an insurmountable technical constraint
• International sites lose the necessary granularity to operate by market
• No public roadmap mentions a planned improvement

Does this limitation reflect the reality of crawling and indexing?

Not really. Google does crawl, index, and serve your hreflang variants to the appropriate users. Server logs prove it: Googlebot regularly visits all language versions. The issue lies solely at the reporting level in Search Console.

It’s a frustrating divergence between the actual functioning of the engine (which manages hreflang very well) and the operating tool (which refuses to report on it). It’s like your accountant saying, "your business is making money in several countries, but I will only show you the global total.".

What specific data is missing for practitioners?

The language-specific queries, first. A term searched in German has a different intent than in English, even when translated. You can't optimize without knowing which keywords perform in which region.

The click-through rates by market, next. A low CTR can be normal in Germany but catastrophic in the UK — impossible to detect with aggregated data. And what about average positions? They become a weighted average, statistically absurd.

[To verify]: some observe that alternative variants sometimes appear in the Coverage report, but with ambiguous statuses ("Excluded by the canonical tag"). This inconsistency between reports further complicates diagnosis.

Are there workable workarounds?

Yes, but all introduce friction and costs. Creating a Search Console property by language/country works… if you force Google to treat them as distinct sites (sub-domains or national domains). But then you lose the benefits of hreflang grouping.

The Search Console API allows for extracting data more finely, but it requires custom development and does not solve the fundamental problem: Google simply does not expose granular metrics. Some third-party tools claim to fill the gap — [To verify] their reliability remains questionable, as they interpolate rather than measure.

How do you audit the actual state of your hreflang pages?

Cross-reference several sources: server logs, Google Analytics segmented by language/country, and a crawler like Screaming Frog or Oncrawl configured to track hreflang annotations. The logs show you what Googlebot actually visits, while Analytics shows what users see.

Set up an automated monitoring of hreflang tags via a script that checks their presence and reciprocity daily. Search Console won’t alert you if a tag breaks — you'll only find out weeks later when international traffic has already dropped.

What alternative metrics should you track?

Switch to Google Analytics 4 with language and geographic source segments. Set specific conversion goals by market to measure the real business impact, not just clicks.

The Core Web Vitals by region via CrUX API can reveal performance gaps between language versions. And don’t forget third-party position trackers (SEMrush, Ahrefs) configured by country: they partially fill the Search Console gap on local rankings.

What to do if Search Console reports are insufficient?

Document the hreflang architecture in an external dashboard: which page points to which variants, with what x-default. This becomes your source of truth when Search Console remains silent.

For large sites, investing in a data warehouse solution that centralizes logs, Analytics, and Search Console API may be worthwhile. But let’s be realistic: it’s a project that requires technical resources and budget — such optimizations can be complex to implement without specialized internal skills. Working with an international SEO agency experienced in multilingual architectures can expedite diagnosis and avoid costly mistakes.

• Set up GA4 with segmentation by language/country to fill the gaps in Search Console
• Implement automated monitoring of hreflang tags (reciprocity, presence, syntax)
• Cross-reference server logs + Analytics to validate that all variants receive crawl and traffic
• Use position trackers by country to track local rankings that Search Console blinds
• Document the architecture in an external repository to maintain visibility on hreflang links
• Regularly test with VPNs or local proxies to ensure Google serves the correct version based on geolocation