What is the URL Inspection Tool?
The URL Inspection Tool is the part of Google Search Console that answers the question "what does Google think of this page?" for one URL at a time. Paste an address and it reports whether the page is in Google's index, when Googlebot last fetched it, how it was discovered (sitemap, link or neither), whether the page's own canonical tag matches the one Google selected, whether it is allowed by robots.txt, whether it is mobile friendly, and which rich result types its structured data qualifies for, with any errors.
It also offers a live test, which fetches the page as Googlebot would right now and shows the rendered HTML, a screenshot and any resources that failed to load. And it includes a request-indexing button, which asks Google to recrawl the page sooner than it otherwise might.
Why it matters
Why the URL Inspection Tool matters
It turns guessing into looking. When a page is not ranking, the usual explanations are that it was never crawled, that it was crawled and not indexed, that Google chose a different canonical, that robots.txt blocked it, or that it rendered without its content. The tool tells you which. That saves days of speculation and it ends arguments, because the report shows exactly what the crawler saw rather than what a developer believes it should have seen.
It is also the quickest route to getting a change noticed. A corrected page, a new entry or a fixed error can wait weeks for a natural recrawl; a request through the tool usually shortens that to days.
In practice
How the URL Inspection Tool works in practice
- 01
It is used in three situations. The first is diagnosis: a page is missing or misbehaving in search, so it is inspected, the index status and canonical are read, and the live test is run to compare what Google renders with what the browser shows. Differences point at JavaScript that fails for the crawler, resources blocked by robots.txt or a server that behaves differently for bots.
- 02
The second is verification after a fix: the page is inspected again to confirm the error is gone, and indexing is requested. The third is launch: a new page is inspected, tested live and submitted, so it enters the index on the team's schedule rather than Google's. The daily quota on indexing requests is small, so the tool is for priorities, not for bulk submission, which is what the sitemap is for.
Watch out
What people get wrong about the URL Inspection Tool
Treating the index request as a ranking lever. It asks for a crawl; it does not improve the page, and submitting the same URL repeatedly does nothing extra. The other mistake is reading the indexed status as the end of the story: a page can be indexed and still rank nowhere because the content is thin or duplicated. And many people never run the live test, which is the only part that shows whether the page actually renders for Googlebot, the single most common hidden cause of a page that will not index.
