URL Inspection tool: how to debug one page in Search Console
The URL Inspection tool shows what Google actually crawled, rendered, and chose as canonical. Here is how to read it and when a live test helps.
Most indexing problems come down to one question: what does Google see when it visits this page? The URL Inspection tool in Search Console answers it for a single URL. It is free, and it is the closest thing you get to looking over Googlebot's shoulder.
What the tool actually shows
Paste a URL from your property into the search bar at the top of Search Console. The first view is the indexed version. That is the copy Google stored the last time it crawled the page, not the page as it exists right now.
This matters more than it sounds. If you fixed a problem an hour ago, the indexed view will still show the old state. The report is a record of the past crawl.
Four details are worth reading first:
- Index status: whether the page is on Google, and if not, the reason given.
- Last crawl: the date and the crawler type, desktop or smartphone.
- Canonical: the URL you declared next to the one Google selected.
- Page indexing and enhancements: sitemap source, referring page, and any detected structured data or mobile issues.
Check the two canonicals
The tool lists a user-declared canonical and a Google-selected canonical. When they match, good. When they differ, Google has overruled your tag, and the page you care about may not be the one in the index.
Common causes are near-duplicate pages, a canonical that points to a redirected or noindexed URL, and internal links that all use a different version. Fix the signals that disagree. Do not just add the tag again.
Live test versus indexed version
The Test live URL button fetches the page now. It tells you whether Google can reach it today, whether robots.txt allows it, and whether a noindex tag is present. Use it after a fix to confirm the fix works before you wait for a recrawl.
A live test does not put the page in the index. It only tests. A page can pass the live test and still be left out, because passing means the page is eligible, not that Google will choose to keep it.
Read the rendered HTML
After a live test, open View tested page. You get the rendered HTML, a screenshot, and a list of resources that failed to load, plus JavaScript console messages. This is the fastest way to find out if your content depends on a script that Google could not fetch.
Search the rendered HTML for a sentence from your main content. If it is missing, Google is not seeing it, and a client-side rendering issue is the likely cause. Our guide on JavaScript SEO covers the fixes.
What Request indexing does and does not do
After a successful live test you can click Request indexing. This adds the URL to a priority crawl queue. It is not a guarantee. Google still decides whether the page deserves a spot, and the number of requests you can make is limited.
Treat it as a nudge for new or freshly fixed pages that matter, not as a routine. Submitting the same URL repeatedly does not speed anything up. If a page stays out after a request, the problem is almost always quality or duplication, not discovery.
Limits to keep in mind
- It inspects one URL at a time. For patterns across many pages, use the Page indexing report.
- It only works for URLs inside a property you have verified.
- It reflects Google only. Bing and AI crawlers have their own view, and their fetch results can differ.
- A URL Inspection API exists for checking many URLs by script, with daily quotas. It reports status but does not submit pages for indexing.
The indexed version tells you what happened. The live test tells you what would happen now.
A simple routine to follow
- Inspect the URL and read the index status and the reason given.
- Compare the declared canonical with the Google-selected one.
- Run a live test and confirm the page is reachable and not blocked.
- Open the rendered HTML and check your main content is present.
- Fix whatever differs, then run the live test again.
- Request indexing once, and recheck the indexed version in a few days.
Next time a page will not rank or will not appear, inspect it before you change anything. Five minutes in this tool usually tells you which problem you really have.