Guides
Search Console URL Inspection: Check If Google Indexed a Page
URL Inspection answers one question precisely: what does Google currently know about this URL? Most misreadings come from confusing the live test with the indexed version.
Run a fresh DomainLens audit and use the report as your priority list.
What the URL Inspection tool reports
Read the reason under the verdict before acting on it. "Discovered — currently not indexed" and "Excluded by noindex tag" both describe a page missing from search, but the first is Google prioritising elsewhere and the second is your own directive being obeyed. The fixes have nothing in common.
| Verdict | Meaning | Common misreading |
|---|---|---|
| URL is on Google | Indexed and eligible to appear | Assuming it ranks — eligibility is not position |
| URL is on Google, but has issues | Indexed despite enhancement problems | Treating it as an indexing failure |
| URL is not on Google | Not indexed, for the stated reason | Assuming a penalty rather than reading the reason |
| URL is not on Google: indexing errors | Blocked, failed, or excluded outright | Requesting indexing without removing the block |
| URL is unknown to Google | Never discovered | Reading absence as rejection |
Using URL Inspection as a Google index checker
The panel is the authoritative index checker for a property you own, and it reports the fields in the order Google evaluated them. Read them in that order — a failure early on makes everything below it irrelevant.
- Discovery — the sitemaps listing the URL and a referring page. No referring page usually means the URL is orphaned and reachable only via the sitemap.
- Last crawl — the timestamp behind the indexed version. Anything changed after it is not reflected yet.
- Crawled as — Googlebot smartphone or desktop. Mobile is the default for almost every site, so debug the mobile response.
- Crawl allowed — whether robots.txt permitted the fetch at all.
- Page fetch — whether the server actually returned the page. A failure here is a status code or timeout problem, not an SEO configuration one.
- Indexing allowed — whether a noindex directive was present at crawl time.
- User-declared canonical — the canonical you specified.
- Google-selected canonical — the URL Google actually consolidated on.
When the Google-selected canonical disagrees with yours
A mismatch between the declared and selected canonical is the single most useful signal in the panel. It means Google found stronger evidence pointing at a different URL: duplicate content, internal links favouring the other address, or a sitemap listing it instead.
Re-declaring the same canonical will not change the outcome. The declaration is a hint, and Google has already weighed it against the rest of the evidence and preferred something else. Change the evidence — consolidate the duplicates, or repoint the internal links — and the selection follows.
- Check whether both URLs return 200 and serve near-identical content.
- Count internal links to each. The version you want indexed should be the one you link to.
- Confirm only the preferred URL appears in the sitemap.
- Verify the canonical survives rendering — a client-side script can overwrite it after load.
Live test versus indexed version
The panel opens on the indexed version, which is a record of a past crawl. "Test live URL" fetches the page right now. They answer different questions, and reading one as the other causes most of the confusion around this tool.
A live test that passes while the indexed version shows an error means you already fixed the problem and Google has not recrawled yet. A live test that fails while the indexed version is healthy means you have just broken something that is still live in search — the more urgent of the two.
| Indexed version | Live test | Interpretation |
|---|---|---|
| Error | Pass | Already fixed; waiting on recrawl |
| Healthy | Error | Newly broken — investigate the current deploy |
| Error | Error | Still broken; the reason field is current |
| Healthy | Pass | Nothing to do here |
Reading the rendered HTML Google saw
View crawled page and View tested page expose the HTML Google held after rendering, a screenshot, the resources it fetched, and JavaScript console messages. For a client-rendered site this is the fastest way to prove whether content exists after render or only in a real browser.
Check three things: whether the main content is present, whether the canonical and robots directives survived rendering, and whether any resource failed to load. A blocked script that builds the page body produces an indexed shell with no content — which indexes perfectly and ranks for nothing.
<!-- Is the body actually there, or just the app root? -->
<div id="app"></div>
<!-- Did the directives survive rendering? -->
<meta name="robots" content="noindex">
<link rel="canonical" href="https://example.com/other-page">
<!-- Failed fetches are listed under "Page resources" -->When to request indexing for a page
When many URLs sit unindexed, the pattern matters more than any single page. Sample a few, look for a shared cause, and cross-check against crawl error reports and your server logs.
- 1Confirm the live test passes. Requesting indexing for a page that still fails changes nothing and spends the quota.
- 2Remove the blocking cause first — a noindex, a disallow, a wrong canonical, or a non-200 status.
- 3Request indexing once per meaningful change. Repeat submissions add no priority.
- 4Expect days rather than hours. The queue has no guaranteed turnaround and no visible position.
- 5For more than a handful of URLs, fix discovery instead: sitemap accuracy and internal links scale, manual requests do not.
How DomainLens contributes
URL Inspection reports Google's conclusion one URL at a time. DomainLens checks the inputs behind that conclusion across a page in one pass — status code, robots directives, canonical, rendered content, and structured data — so you reach the inspection panel already knowing what to look for. The Search Console audit guide covers the surrounding reports, and the Search Console API guide covers automating this check.
- Why does the live test pass but the page is still not indexed?
- A passing live test only proves the page is crawlable and indexable right now. Google still decides whether the page is worth indexing, and "Discovered — currently not indexed" is that decision rather than an error.
- What does "Google-selected canonical: Inspected URL" mean?
- Google agreed with your declared canonical, or found no competing duplicate. That is the healthy outcome and needs no action.
- How many URLs can I request indexing for per day?
- Google enforces an undisclosed daily quota per property, low enough that manual requests cannot serve as a bulk indexing strategy.
- Can I inspect a URL on a site I do not own?
- No. Inspection requires a verified Search Console property covering that URL, which is why third-party index checkers rely on site: queries instead.