Reference guide · search-console · Published 2026-08-16 · 3 min read
URL Inspection versus the live test in Search Console
URL Inspection versus the live test in Search Console: what each shows, why the live version can differ, and how to request indexing.
- ·Two views, one tool
- ·When they diverge
- ·Request indexing
Two views inside one tool
The URL Inspection tool is a single text box, but it returns two different answers depending on what you are testing. The "URL is on Google" screen shows what Google has already stored for that page, its latest indexed snapshot, with the indexed time and the last crawl. The same tool also offers a "Test live URL" action that ignores the stored copy and fetches the page fresh to see what a crawler would encounter right now.
This distinction is the whole point of the tool. The URL Inspection reference covers the full interface; this page is specifically about knowing which of the two answers you are looking at and why they can disagree.
What each view actually shows
| View | Source of truth | Good for | Limit |
|---|---|---|---|
| Indexed view | Google's stored page | What Google thinks your page is | Can be days or weeks old |
| Live test | A fresh fetch right now | Whether rendering, robots, or the page itself changed | A snapshot, not an ongoing state |
The indexed view is confirmation of a past state. The live test is a probe of the current one. When you are debugging "Google shows the old title", the two views give different clues: the indexed view proves Google is serving the old snapshot, while the live test proves whether the current page would even be different if re-crawled.
When they diverge
The two views disagree in predictable situations:
- The page changed but has not been re-crawled. The indexed view is stale and the live test shows the new content. This is normal and usually resolves on the next crawl.
- The live test hits a different state than a crawler would. A paywall, a bot check, or a geo-served variant can make a live fetch from where the fetch runs differ from what Google's own crawler saw, so a "matched" live test does not guarantee the indexed copy is current.
- Robots.txt or a noindex has appeared. The live test flags "URL is not on Google" and the reason it gives is where you look first, because a
noindexor arobots.txtrule is often the cause of a page dropping out. - Rendering differs. Client-side content that needs JavaScript renders fully in the live test but may be absent from the indexed snapshot if the renderer has not re-visited.
Request indexing, the honest way
The live test includes a "Request indexing" button. That request is worthwhile only when the indexed view is genuinely behind the live copy you have confirmed. The reliable sequence:
- Open the URL Inspection tool and confirm the indexed view is stale.
- Run the live test and confirm the current page is clean (no
noindex, no crawl-block, title and content correct). - Request indexing for that specific URL.
- Re-check in a day or two to see whether the indexed snapshot caught up with the indexing progress.
The how to request indexing article warns that the request is a nudge, not a guarantee. The URL Inspection tool tells you whether the nudge was worth sending, which is the difference between guessing and knowing.