How to read a URL Inspection result
Search Console's URL Inspection tool shows what Google knows about one page. Read it from top to bottom: the verdict, the reason, then Discovery, Crawl, and Indexing. Each guide explains one message and the fix.
Read it from top to bottom
The default view shows Google's last visit, not the live page. Check the Last crawl date before you trust a line: a fix you made after it won't show yet.
- 1
The verdict
Top of the result
The line at the top sums up the result: URL is on Google, URL is on Google, but has issues, or URL is not on Google. Everything below it explains why.
- URL is on GoogleGoogle has the page in its index, and it can show it in search. That does not promise it shows up for the words you search.
- URL is on Google, but has issuesThe page is in Google's index. Something extra on it, such as structured data, has a problem. The page itself can still show in search.
- URL is not on GoogleGoogle did not add the page to its index, so it can't appear in search. The reason is in the Page indexing section, right below the verdict.
- 2
Page indexing
The heading of the Page indexing section
It says Page is indexed, or Page is not indexed followed by a reason, such as "Crawled - currently not indexed". That reason is the same one the Page indexing report uses. If it says "URL is unknown to Google", Google has never seen the address.
- 3
Discovery
Page indexing > Discovery
How Google found the page: the sitemaps that list it, and a page that links to it.
- 4
Crawl
Page indexing > Crawl
When Google last visited, with which crawler, and whether the visit worked. Google's help says that when a page is not on Google, the reason is usually here.
- Last crawl: N/AGoogle has no successful visit to this page on record. So it has nothing indexed to show yet.
- Crawled as: Googlebot smartphoneGoogle visited the page with its mobile crawler. That is normal. For most sites, Google indexes the mobile version of each page.
- Crawl allowed? No: blocked by robots.txtA rule in your robots.txt file tells Google not to visit this page. Google follows it, so it can't read the page.
- Page fetch: FailedGoogle tried to get the page from your server and could not. The words after "Failed:" say why.
- Page fetch: Failed: Redirect errorGoogle followed the page's redirects and gave up. The redirects go in a circle, run too long, or lead to a bad address.
- Server connection errorGoogle could not connect to your server at all. That is a problem for the whole site, not just this page.
- Page fetch: Successful, but not indexedGoogle got the page without trouble and still left it out. The reason is about the page or a duplicate, not your server.
- 5
Indexing
Page indexing > Indexing
Whether the page allows indexing, and which address counts as the main one: the one you named, and the one Google picked.
- Indexing allowed? No: 'noindex' detectedYour page tells Google not to index it, with a noindex rule in a meta tag or an HTTP header. Google follows it.
- User-declared canonical: NoneYour page does not name a main address. For a page with no copies, that is fine.
- Google-selected canonicalThis is the address Google treats as the main version of the page. Inspected URL means this page. Another address means Google sees this page as a copy.
- 6
Enhancements & Experience
Below Page indexing
Extras Google found on the page, such as structured data, AMP, and HTTPS. A problem here does not keep the page off Google. It turns the verdict into URL is on Google, but has issues.
After a fix: the live test and Request indexing
Fix the page first. Then click Test live URL to check the fix, and Request indexing to ask Google to visit again.
The live test
The live test checks the page as it is now. Use it after a fix. It checks less than the indexed result, so a pass is not a promise.
Request indexing
The messages you can get when you ask Google to crawl one page again.
- Indexing requestedGoogle added the page to its crawl queue. It will visit, then decide whether to index it. The request does not promise indexing.
- Quota exceededYou hit Search Console's daily limit for Request indexing. Google does not publish the number. Try again the next day, and let your sitemap handle the rest.
- Indexing request rejectedGoogle ran a quick live test before it queued the page, and the test found a problem. Fix it, then ask again.
Fixed many pages at once?
URL Inspection works one page at a time. For a whole group of pages with the same reason, use Validate fix in the Page indexing report. See what each validation state means, and why validation fails. Google makes the final call on what it indexes.
Check your whole site, not one page at a time
Sign in with Google. CrawlCoach checks up to 500 pages for free, sorts the missing ones by reason, and shows the fix for each.
Get my free reportFree for up to 500 pages. No card needed. Sign in with the Google account you use for Search Console.