Does the URL inspection tool really show you how Google discovers your pages?

What exactly does this new information reveal?

The URL inspection tool no longer just tells you whether a page is indexed. It now indicates the discovery method used by Googlebot: either an XML sitemap file or a specifically identified referring page.

Concretely, you know whether Google found your page because you actively submitted it via sitemap, or because it discovered it by following a link from another page on your site (or an external one). This distinction is far from trivial.

Why does this granularity change the game?

Until now, diagnosing why certain pages weren't being crawled was often a matter of trial and error. You had hypotheses: excessive click depth, orphaned links, crawl budget issues.

Now, you have factual evidence. If a strategic page only appears via sitemap and never through natural discovery, it's suffering from internal linking problems. Conversely, if Google finds it through discovery but not via sitemap, your XML file deserves an audit.

What's the practical difference between sitemap and referring page?

Sitemaps are a suggestion — not an order. Google consults them but doesn't guarantee crawling all listed URLs, especially if your crawl budget is tight.

Discovery via referring page indicates that Googlebot actively followed a link from an already-known page. It's a signal that your internal linking works and that the page benefits from a certain crawl authority transmitted by the source page.

• The tool displays the precise source: sitemap URL or exact referring page URL
• This allows you to trace Googlebot's discovery path through your site structure
• Useful for identifying orphaned pages only discovered via sitemap
• Helps prioritize internal linking to poorly discovered strategic pages
• Enables detection of inconsistencies between your sitemap and your actual link structure

Is this transparency really new?

Let's be honest: Google has always known how it discovered your pages. What's new is that it's finally sharing this data through Search Console in an accessible way.

Previously, server logs allowed you to reconstruct this information by cross-referencing Googlebot requests with your sitemaps and link structure. But it was time-consuming and limited to sites with solid analytics infrastructure. Now it's democratized.

What limitations should you anticipate with this tool?

First point: the inspection tool displays the source of the most recent known discovery. If Googlebot discovered your page via sitemap six months ago and then re-crawled it via an internal link yesterday, the complete history isn't necessarily visible. [To verify] whether Google keeps a history of different discovery methods or only the most recent one.

Second nuance: this information says nothing about the quality or priority given to the page. Discovery via referring page isn't automatically synonymous with quick indexing or good rankings — it only confirms that a crawl path exists.

Does this data challenge current practices?

Not really. The fundamentals remain: coherent internal linking, clean XML sitemap, flat architecture, optimized crawl budget. What this tool does is make visible what was previously opaque.

But it offers a valuable diagnostic lever. If you notice that your strategic pages are only discovered via sitemap, it's a clear warning sign: your internal linking isn't doing its job. Conversely, if secondary or unnecessary pages are massively crawled through natural discovery, you're wasting crawl budget — and you need to review your nofollow or robots.txt.

What should you audit first with this information?

Start with your strategic pages: flagship product sheets, SEO landing pages, pillar content. Inspect them one by one and note the discovery source displayed.

If they only appear via sitemap, it means Google isn't finding them naturally by browsing your site. This indicates they're either too deep in your architecture, poorly linked, or completely orphaned despite their sitemap presence.

How do you fix a failing discovery problem?

If a critical page is only discovered via sitemap, strengthen its internal linking. Add links from the homepage, from main category pages, from related blog articles.

Also check click depth: ideally, no important page should be more than 3 clicks from the root. If it is, revise your architecture.

Conversely, if parasite pages (date archives, unnecessary tags, auto-generated facets) are massively discovered via referring pages, ask yourself if they deserve to be crawled. Add noindex, add nofollow to links toward these sections, or block them in robots.txt if relevant.

What errors should you avoid when interpreting this data?

Don't jump to conclusions based on a single page. Inspect a representative sample: 20-30 URLs distributed among strategic content, transactional pages, editorial content.

Also don't overlook crawl delays. A recently published page might appear as discovered via sitemap simply because Googlebot hasn't found it through natural navigation yet. Wait a few weeks before panicking.

• Audit the discovery source of 20-30 strategic pages via the inspection tool
• Identify orphaned pages only discovered via sitemap
• Strengthen internal linking to these isolated pages
• Check click depth and real accessibility from the homepage
• Detect secondary sections over-crawled through referring pages
• Clean up unnecessary links or add nofollow/noindex if relevant
• Cross-reference this data with server logs for a complete view of Googlebot behavior
• Reassess regularly: discovery source can evolve after optimizations