URL Inspection Tool
What Is the URL Inspection Tool?
The URL Inspection tool is a diagnostic tool in Google Search Console where you enter a single URL to see how Google views that page. Google’s official documentation says the tool “provides information about Google’s indexed version of a specific page, and also allows you to test whether a URL might be indexable.” Google (official) You run it by pasting a URL into the search bar at the top of Search Console, or by clicking the inspect link in any report.
If the Page indexing report, which gathers indexing status for the whole site, is the map, the URL Inspection tool is a magnifying glass for one specific address. In fact, the official Page indexing report documentation also says, “To see the indexing status of a specific URL, use the URL Inspection tool.” GSC Help Center The two tools are designed to be used as a pair.
Look First at the Verdict at the Top
When you inspect a URL, an overall verdict appears at the top of the results. Google’s official documentation lists these four verdicts. Google (official)
| Verdict | Meaning |
|---|---|
| URL is on Google | The page is indexed and can appear in search results. However, the official documentation makes clear that appearing is not guaranteed. |
| URL is on Google, but has issues | The page is indexed, but some enhancements, such as structured data, may not appear in search results. |
| URL is not on Google | The page is not indexed and cannot appear in search results. Check the details below for the reason. |
| URL is an alternate version | The page is an alternate version of another canonical page, such as an AMP page. |
The first verdict is the one newcomers misunderstand most. “On Google” means the page has entered the arena of search, not that it ranks at the top. Indexing is the admission ticket; ranking is a separate matter that comes after.
The Order to Read the Details
Expand the Page indexing section below the verdict to see the details. Reading them in this order makes the picture clear.
- Last crawl – The official documentation describes it as “the last time this page was crawled by Google.” Google (official) Anything you changed after this time is not yet reflected in the results.
- Crawled as – Shows whether the desktop or the mobile (smartphone) crawler visited.
- The two canonical lines – “User-declared canonical” is the representative address you declared on the page yourself; “Google-selected canonical” is the address Google actually chose as representative. If the two differ, Google has chosen a different page as canonical.
- Indexing allowed? – Checks whether the page was caught by a blocking signal such as robots.txt or noindex.
Indexed Version vs Live Test
This is a common point of confusion in the URL Inspection tool. About the default inspection results, the official documentation states, “The information shown is for the most recently indexed version of the page, not the live version on the web.” Google (official) In other words, the default screen is the record from your last checkup, and the live test is a blood pressure reading taken right now.
| Aspect | Indexed version inspection (default) | Live test |
|---|---|---|
| What it looks at | The copy Google most recently indexed | The page as it exists on the web right now |
| Question it answers | What are Google’s search results currently based on? | Can the current page be indexed? |
| Main use | Checking index status, canonical URL and crawl history | Checking right away whether a fix solved the problem |
The official documentation explains that the live test “fetches the URL in real time” to check “whether the current page can be indexed.” Google (official) Click View tested page to see the page “rendered as Google-InspectionTool sees it,” along with a screenshot. This is useful for checking whether content drawn by JavaScript is properly visible to Google. For developers, the URL Inspection API, which retrieves the same information programmatically, has also been available since its launch in January 2022. Google (official)
Passing the Live Test Doesn’t Mean the Page Is Indexed
Here is the gap practitioners run into most often. It is not unusual for a page to get a green light in the live test and still not actually be indexed. That’s because the environment in which the live test renders the page is not exactly the same as the real indexing crawler’s environment. Putting Google’s official explanation side by side with field advice makes the criteria clear.
| Google’s official position | If the live test passes, the tool marks the URL as indexable. But the official documentation also makes clear that indexing is not guaranteed. Google (official) |
|---|---|
| Expert field advice | In practice, pages that pass the live test often still don’t get indexed. The more JavaScript a page has, the more the actual indexing result differs because of rendering timeouts and resource budgets. Onely analysis |
The difference lies in rendering conditions. The live test renders the page with less time and fewer resources so it can give people a quick answer, while actual indexing fetches the resources it needs more generously before rendering. So in practice, it is safer to read a passed live test not as “indexing done” but as “no obvious block preventing indexing,” and to recheck with the default inspection a few days later whether the page was actually indexed. Onely also advises: “Don’t rely solely on what you see in the live test. Its rendering environment may differ from the one used for indexing.” Onely analysis
Request Indexing: Lower Your Expectations
From the inspection results, you can request a crawl with the Request indexing button. However, Google’s official documentation states firmly, “There’s a quota for submitting individual URLs, and requesting a recrawl multiple times for the same URL won’t get it crawled any faster,” and notes that “crawling can take anywhere from a few days to a few weeks.” Google (official) Industry guides agree that a request doesn’t guarantee indexing; Semrush explains that “it can speed up recrawling, but indexing isn’t guaranteed.” Semrush guide
When It’s Not a Problem
The following situations are not errors, so no action is needed.
- The last crawl was weeks ago – Google revisits each page on a different schedule, and per the official documentation, crawling can take days to weeks. An old timestamp is not a problem in itself.
- The default inspection shows old content – The default inspection is meant to show the most recently indexed copy. It’s normal that it isn’t live.
- The default inspection and live test results differ – If you fixed the page and it hasn’t been recrawled yet, this is natural. The two results will line up after the next crawl.
- It says “on Google” but doesn’t show up in search – The official documentation itself says appearing in search results is not guaranteed. Google (official) In this case the issue is ranking or queries, not indexing, so check it separately in the Performance report.
References
- URL Inspection tool – Google Search Console Help
- Page indexing report – Google Search Console Help
- Ask Google to recrawl your URLs – Google Search Central
- Introducing the new Search Console URL Inspection API – Google Search Central Blog
- Google Search Console: The Ultimate Guide – Semrush
- How To Fix “Discovered ‐ Currently Not Indexed” in GSC – Onely
Jul.2026By Studio JT