How can you find out which canonical Google has actually retained for your pages?

Quick SEO Quiz

Test your SEO knowledge in 3 questions

Less than 30 seconds. Find out how much you really know about Google search.

🕒 ~30s 🎯 3 questions 📚 SEO Google

Official statement

The URL Inspection tool in Search Console can be used to check if there is confusion regarding the canonical tag retained by Google, particularly in cases of mobile-first indexing or conflicting canonicals.

9:06

🎥 Source video

Extracted from a Google Search Central video

⏱ 39:51 💬 EN 📅 17/06/2020 ✂ 51 statements

Watch on YouTube (9:06) →

✂ Other statements from this video 50 ▾

📅

Official statement from June 17, 2020 (5 years ago)

⚠ A more recent statement exists on this topic Should you use the noindex directive in your robots.txt file? John Mueller · March 26, 2024 View statement →

TL;DR

Google confirms that the URL Inspection tool in Search Console displays the canonical tag that is actually considered by the algorithm, especially in mobile-first configurations or when multiple canonicals conflict. For an SEO, this is the only reliable source to audit canonicalization errors from Google's side. But beware: what you declare and what Google retains can diverge, and this divergence often reveals critical structural inconsistencies.

What you need to understand

Why is the URL Inspection the only reliable source for knowing the retained canonical?

The canonical tag you declare in your code is merely a suggestion, not an absolute directive. Google reserves the right to ignore your choice if other signals contradict your intent. And this is precisely where the URL Inspection tool becomes essential.

Unlike a third-party crawler that simply reads your HTML, this tool shows the effective canonical—the one that the Google index has retained after analysis. If you declared a canonical A but Google chose a B, you will know immediately.

In what situations does Google ignore your declared canonical?

Mobile-first indexing creates situations where the mobile and desktop versions of a page have different canonicals. If your two versions are not perfectly aligned, Google may arbitrate differently than you expected.

Conflicting canonicals are another typical case: a tag in the <head>, another in the XML sitemap, a third in the HTTP headers. Google decides—and that choice is not always predictable.

What does this announcement concretely mean for technical SEO auditing?

You can no longer rely solely on a Screaming Frog or OnCrawl crawl to validate your canonicals. These tools tell you what you declare, not what Google retains. The gap between the two can be costly in terms of visibility.

The URL Inspection becomes a mandatory post-crawl validation tool, especially for strategic pages: products with high variation, paginated content, AMP pages, localized versions with hreflang.

The URL Inspection shows the effective canonical from Google's side, not the one you declare
Google can ignore your canonical if other signals (redirects, internal links, sitemaps) contradict your intent
Mobile-first configurations and multiple canonicals (HTML + HTTP headers + sitemap) increase the risk of divergence
A complete technical SEO audit must now cross-reference manual crawls and verification via URL Inspection on a representative sample

SEO Expert opinion

Is this statement consistent with field observations?

Yes, and it's even a public admission of what SEOs have observed for years: Google does not blindly follow your directives. The canonical is a suggestion, and Google acts as an arbiter that decides based on multiple contradictory signals.

What’s interesting is that Martin Splitt implicitly acknowledges that confusions are frequent. If Google takes the time to communicate about this tool, it’s because many sites are losing traffic due to misunderstood canonicals. And this is indeed what we observe.

What nuances should be added to this assertion?

The URL Inspection does not tell you why Google chose one canonical over another. You see the result, not the underlying algorithmic logic. It remains a partial black box. [To verify]: does the tool also indicate the candidate canonicals that were discarded and the reasons for the choice?

Another limitation: the tool works page by page. It’s impossible to launch a bulk check on 10,000 URLs. You need to manually identify the critical pages to audit, which already requires expertise to spot risky areas.

In what cases is this tool not enough to solve the problem?

If Google has indexed the wrong canonical for months, fixing your code will not be sufficient. You will need to force a re-crawl and wait for the index to update. The URL Inspection will tell you if the correction has been taken into account, but it won't magically speed up the process.

Finally, certain complex architectures — especially sites with dynamic facets, multiple localized versions, or JS-generated content — present canonical problems that the tool detects but does not resolve. It reveals the symptom; you have to diagnose the root cause.

Warning: If the URL Inspection displays a different canonical than the one declared, do not blindly correct your code without understanding why Google diverged. Sometimes, Google is right—your architecture is sending contradictory signals that you had not detected.

Practical impact and recommendations

What should you concretely do to audit your canonicals?

First step: identify your site’s strategic pages — those that generate traffic or conversions. List them in a spreadsheet and run them one by one through the URL Inspection. Note the canonical displayed by Google and compare it with the one declared in your code.

If you notice discrepancies, do not panic immediately. Sometimes Google intelligently consolidates stray variations that you may have left lingering. But if the retained canonical points to a less relevant or less optimized page, then it’s a red flag.

What mistakes should be avoided when configuring canonicals?

Never declare multiple different canonicals for the same URL (one in HTML, another in the HTTP header, a third in the sitemap). Google will choose, and it may not be the one you wanted. Unify your signals.

Avoid chains of canonicals: a page A that points to B, which in turn points to C. Google may lose track or arbitrate differently than your intention. A canonical should point directly to the master final URL.

How do you check that your site is compliant after correction?

After you have corrected your canonicals in your code, use the “Request Indexing” option in the URL Inspection to force a quick re-crawl. Check back 48-72 hours later to see if the displayed canonical has indeed been updated.

Cross-check this verification with a server log audit to confirm that Googlebot is crawling the correct versions. If you see massive crawls on URLs that you have canonicalized, it means Google has not yet taken your directive into account.

Crawl your site to extract all declared canonicals (HTML, HTTP headers, XML sitemap)
Run a representative sample of pages through the URL Inspection and compare with your declarations
Correct the detected inconsistencies by unifying signals (remove redundant or contradictory canonicals)
Request re-indexing via URL Inspection to accelerate consideration
Verify in the server logs that Googlebot is now crawling the correct canonical URLs
Repeat the audit every quarter, especially after migrations or structural redesigns

The URL Inspection has become a critical tool to validate that your SEO intentions are well understood by Google. However, auditing thousands of pages, interpreting discrepancies, and correcting complex architectures requires sharp expertise and time. If your site exhibits significant variations between declared and retained canonicals, it may be wise to engage a specialized SEO agency for an in-depth diagnosis and a tailored action plan.

❓ Frequently Asked Questions

L'URL Inspection remplace-t-il un crawler SEO classique pour auditer les canonicals ?

Non, il le complète. Un crawler vous dit ce que vous déclarez, l'URL Inspection ce que Google retient. Il faut croiser les deux pour détecter les écarts.

Si Google affiche une canonical différente de celle que je déclare, dois-je toujours corriger mon code ?

Pas forcément. Parfois Google consolide intelligemment des variations parasites. Analysez d'abord pourquoi Google a divergé avant de corriger aveuglément.

Peut-on vérifier en masse les canonicals retenues par Google via l'URL Inspection ?

Non, l'outil fonctionne URL par URL. Vous devez identifier manuellement les pages critiques à auditer, impossible de lancer une analyse en masse.

Combien de temps faut-il pour que Google prenne en compte une canonical corrigée ?

Ça dépend de la fréquence de crawl de votre site. Utilisez « Demander une indexation » pour accélérer, puis vérifiez 48-72h plus tard via URL Inspection.

Les canonicals déclarées en HTTP header ont-elles plus de poids que celles en HTML ?

Non, elles ont théoriquement le même poids. Le problème survient quand elles sont contradictoires — Google arbitre, et le résultat n'est pas toujours prévisible.

🏷 Related Topics

canonical indexation Search Console mobile-first URL Inspection audit technique crawl budget duplicate content

Crawl & Indexing Mobile SEO Domain Name Search Console

🎥 From the same video 50

Other SEO insights extracted from this same Google Search Central video · duration 39 min · published on 17/06/2020

🎥 Watch the full video on YouTube →

Related statements

« Previous

Missing screenshot is not an indexing issue...

Unloaded resources in Search Console are not alway...

« Back to results