How can you find out which URL Google has really indexed on your site?

What exactly does the URL Inspection tool reveal?

The URL Inspection tool (formerly known as the “URL Testing Tool”) gives you access to how Googlebot sees a specific URL of your site. The Coverage section displays four crucial pieces of information: the discovery source (sitemap, internal link, backlink, etc.), the date of the last crawl, the user agent used (desktop or mobile), and most importantly, the canonical URL chosen by Google.

If Google preferred another version of the page — say /product?color=red instead of /product — the tool will clearly indicate this. Many discover here that their rel canonical tag has been ignored or that URL parameters have created unmanaged duplicates.

Why would Google choose a different canonical URL than the one declared?

Canonicalization is a process where Google decides which version of a page to index when multiple variants exist. You can suggest a canonical URL via the <link rel="canonical"> tag, but it’s Google that makes the final decision. The algorithm takes into account multiple signals: internal links, backlinks, 301 redirects, declarations in the sitemap, and content consistency.

In practice? If you declare /page-a as canonical but 90% of your internal links point to /page-a/ (with a trailing slash), Google may ignore your tag and choose the latter instead. Similarly, if a mobile version displays radically different content, Googlebot might find it more relevant and index it instead of the desktop version.

In what scenarios does this information change the game for an SEO?

When a page disappears from the index without apparent reason, it’s often because an unexpected variant was chosen as canonical. You optimize /product, but Google indexes /product?utm_source=email. The result: your meta-data, enriched content, and on-page optimizations become useless.

The URL Inspection tool allows you to diagnose these types of discrepancies in seconds. You type in the URL that should rank, see that Google has chosen another, and you can trace back: check internal links, tracking parameters, cascading redirects, and conflicting canonical tags.

• Quick identification of the indexed version when multiple variants coexist
• Detection of duplicates created by URL parameters or trailing slashes
• Verification of Google's compliance with your canonical tags by Googlebot
• Understanding the discovery source: sitemap, crawl, external backlink
• Visibility on the user agent used, crucial for sites with divergent desktop/mobile versions

Does this statement align with observed practices in the field?

Yes, but with a significant nuance: Google doesn’t tell you *why* it chose this URL over another. You see the result, not the reasoning. In practice, the tool often reveals inconsistencies in site architecture: a canonical tag pointing to a page that redirects, unfiltered tracking parameters in Search Console, AMP or mobile-first versions indexed instead of the desktop.

On e-commerce sites with product filters, it is common to see Google canonicalizing towards facet URLs (color, size, price) instead of the main product page — because these facets receive more internal links or backlinks. The URL Inspection tool can help spot these discrepancies, but you then need to cross-check with server logs and Analytics data to understand the “why”.

What nuances should be added to this claim?

Google refers to a

What should you do concretely to master canonicalization?

First, systematically audit all strategic pages of your site using the URL Inspection tool. If Google chooses a different URL than expected, trace back: check the canonical tag, redirects, internal linking, and URL parameters. Just one misconfigured internal link can distort the entire signal.

Next, align your canonicalization signals: the rel="canonical" tag, the URLs in the XML sitemap, and internal links should all point to the same version. If you declare /page as canonical but your sitemap contains /page/, you create ambiguity that Google will resolve according to its own algorithm — not necessarily the way you want.

What mistakes should you avoid to maintain control over canonicalization?

Do not multiply unnecessary URL variants. Each tracking parameter (?utm_source, ?ref, ?sessionid) creates a distinct URL that Google has to process. Use the URL Parameter feature in Search Console to indicate which parameters to ignore or implement a dynamic canonical on the server-side to clean up the variants.

Avoid chains of redirects leading to a canonical URL. Google can lose track and choose an intermediate URL. Lastly, do not change the canonical URL without redirecting old versions — otherwise, you create a signal warfare scenario where Google may index the old URL for weeks.

How can I verify that my site is compliant and that Google respects my choices?

Use the bulk URL Inspection through the Search Console API to scan all your strategic pages. Compare the crawled URL with the one declared in your CMS or your canonical file. Any discrepancies reveal architectural inconsistencies or conflicting signals.

Implement a regular monitoring: a script that extracts the canonical URLs weekly via the API and alerts you in case of unexpected changes. On a medium-sized e-commerce site, a drift in canonicalization can lead to thousands of organic visits lost within days — it’s better to catch it early.

• Audit strategic pages using URL Inspection and identify discrepancies between the expected URL and the canonical URL chosen by Google
• Align all signals: canonical tag, XML sitemap, internal links, 301 redirects
• Filter out unnecessary URL parameters via Search Console or a dynamic canonical on the server-side
• Avoid chains of redirects and always redirect old URLs to the new canonical URL
• Automate monitoring via the Search Console API to detect canonicalization drifts
• Cross-check URL Inspection data with server logs to ensure crawl consistency at scale