URL Inspection tool

The Google Search Console URL Inspection tool, field by field

What each line of a URL inspection means, when to run a live test, how Request indexing really works, and how to inspect more than a few URLs.

Explore the live demo →

5 days free · no card needed · ends on its own

Updated

The URL Inspection tool in Google Search Console shows what Google knows about one URL on your site: whether it’s indexed, when Googlebot last crawled it, how Google found it, which canonical URL Google chose, and whether anything blocks indexing. Paste a full URL into the search bar at the top of Search Console to see the indexed version, use Test live URL to check the page as it is now, and click Request indexing after you’ve changed it.

Limits to know: you can only inspect URLs in a property you have access to. Request indexing has a daily limit Google doesn’t publish (in practice about 10 to 12 URLs a day). The URL Inspection API allows 2,000 inspections per site per day, so checking a whole site takes planning.

How to open it

  1. In Search Console, pick the property, then paste the full URL (with https://) into the Inspect any URL bar at the top and press Enter. You can also click a URL in most reports and choose Inspect URL.
  2. The URL must belong to the property you are in. For a URL-prefix property such as https://www.example.com/, an http:// or non-www URL belongs to a different property. A Domain property covers every subdomain and protocol.
  3. The first screen is the indexed result: what Google stored from its last crawl. Expand Page indexing for the details.

What the verdicts mean

VerdictWhat it means
URL is on GoogleThe page is indexed and eligible to appear in search results. Eligible, not guaranteed: it still has to rank.
URL is on Google, but has issuesIndexed, but an enhancement such as structured data has problems that may stop it showing with rich results.
URL is not on GoogleNot indexed. The Page indexing section gives the reason.
URL is available to Google (live test)Google could fetch the page now and found nothing that blocks indexing. It doesn’t mean Google will index it.
URL is not available to Google (live test)A critical issue, such as a noindex, a block or a fetch error, would stop indexing.

Wording from Google’s URL Inspection tool help.

Every field in the result, explained

FieldWhat it tells youWhat to look for
Page indexing (status)The page’s coverage state, the same reasons as the Page indexing report: “Page is indexed”, “Crawled - currently not indexed”, “URL is unknown to Google” and so on.The reason links to the fix. See the page indexing issues guide.
Discovery: SitemapsSitemaps submitted in the Sitemaps report that list this URL.“No referring sitemaps detected” on a page you expected in one. Sitemaps found only through robots.txt aren’t listed here.
Discovery: Referring pageA page Google possibly used to discover this URL.Blank or a deep page for an important URL means weak internal links. It can be blank even when links exist.
Crawl: Last crawlWhen Google last crawled the page, in your local time. Everything else comes from this crawl.An old date on a page you changed: Google hasn’t seen the change yet.
Crawl: Crawled asThe user agent used: Googlebot smartphone or desktop.Almost always smartphone. Make sure the mobile page has the full content.
Crawl: Crawl allowed?Whether robots.txt allowed the crawl.“No: blocked by robots.txt” on a page you want indexed. See blocked by robots.txt.
Crawl: Page fetchWhether Google actually got the page from your server.Failed: Not found (404), Soft 404, Server error (5xx), Redirect error.
Indexing: Indexing allowed?Whether the page blocks indexing, for example with a noindex tag or header.“No: ‘noindex’ detected”. See excluded by noindex. If robots.txt blocks the crawl this shows Yes, because Google can’t read the noindex.
Indexing: User-declared canonicalThe canonical URL your page declares, if any.“None” is fine for a page that isn’t a duplicate.
Indexing: Google-selected canonicalThe URL Google chose as canonical among similar pages.A different URL from yours means Google indexes that one instead. See Google chose different canonical.
EnhancementsRich result types Google detected (such as breadcrumbs or products), video indexing and AMP, with errors and warnings.Errors that stop rich results. Not every rich result type is covered.

Indexed result vs live test

The default view is the indexed version: what Google saw on its last crawl, which is what search results use. Test live URL fetches the page now with Google’s inspection crawler and tells you whether it could be indexed as it stands. Use the live test after you fix something, before you request indexing.

The live test is narrower than the indexed result. Google lists what it doesn’t check: sitemaps, referring pages, duplicate and canonical selection, manual actions, quality and security issues, content removals and temporary blocks. So a page can pass the live test and still not be indexed, most often because Google judged it a duplicate or not valuable enough (crawled, currently not indexed).

Both views let you open the page as Google saw it (View crawled page or View tested page), with the HTML Google read and the HTTP response. On JavaScript-heavy listing pages, check that the business name, description and reviews are in that HTML.

Request indexing: how it works and its limits

  1. Inspect the URL and run Test live URL. If the live test says the URL is not available to Google, fix that first; Search Console won’t accept a request for a page it can’t index.
  2. Click Request indexing. Google runs a quick check and adds the URL to a priority crawl queue.
  3. Wait. Google says crawling can take a few days to a few weeks, and that requesting the same URL several times won’t get it crawled faster.

There is a daily limit per property. Google doesn’t publish the number; in practice Search Console starts refusing after about 10 to 12 requests a day. For more than a handful of URLs Google recommends a sitemap. A request also only helps when something changed: requesting an unchanged page that Google already passed on usually gets the same answer.

Common results and what to do

You seeIt meansDo this
URL is unknown to GoogleNo link or sitemap has led Google to the URL yetLink to it from an indexed page, add it to the sitemap, then request indexing
Discovered - currently not indexedKnown, not crawled yetImprove internal links and cut URL waste
Crawled - currently not indexedRead and passed onImprove or consolidate the page
Page with redirectThe URL redirects elsewhereInspect the destination instead. See page with redirect
Page fetch: Not found (404)The server returned 404Fix, redirect or leave it
Google-selected canonical differsGoogle indexes another URL as the main versionMake signals agree: canonical, internal links, sitemap
Last crawl: N/ANever crawledSame as unknown or discovered: links first

The URL Inspection API and its limits

Search Console’s URL Inspection API returns the indexed result for a URL in a property you have access to: the verdict, coverage state, robots.txt state, indexing state, page fetch state, last crawl time, crawled-as user agent, both canonicals, the sitemaps that list it and referring URLs, plus rich result and AMP details. It needs only read-only access. It can’t run a live test and it can’t request indexing; those stay in the Search Console interface.

LimitValue
Per site (property), per day2,000 inspections
Per site, per minute600 inspections
Per Google Cloud project, per day10,000,000
Per Google Cloud project, per minute15,000

Source: Google’s Search Console API usage limits, checked 16 November 2026.

How to inspect thousands of URLs

At 2,000 a day, checking a 40,000-page directory one URL at a time takes 20 days, and the result is out of date before you finish. Three habits make it workable:

That is what our bulk index checker does, using the API rather than site: searches.

On directory websites

Inspect one URL of each template before you inspect thousands. A listing that is indexed next to one that isn’t tells you most of what you need: compare the Referring page (is the stuck listing linked from its city page?), the Google-selected canonical (has Google folded it into another listing?) and the content in the crawled HTML. Then fix the template and check a sample again a few weeks later.

How DirectoryLens helps

DirectoryLens runs the URL Inspection API for you, within Google’s quota (it uses up to 1,800 of the 2,000 daily inspections per site). Every day it inspects your priority URLs, including paid and featured listings, then new sitemap URLs, then a sample of each page type, and shows the estimated indexed share per page type in Google indexing > Summary.

Google indexing summary for a sample directory: estimated share indexed for listing, guide, city and category pages with coverage states, then priority URLs not indexed with the days each has been out.
Index estimates by page type from daily URL inspections, then priority pages that aren’t indexed. Sample directory from the live demo.

In Individual pages you can start a run on a page type, a pasted list of up to 5,000 URLs, a sitemap, URLs last seen not indexed, or URLs not inspected in a number of days. Each URL keeps its inspection history, and gets flags such as Google picked another canonical, Weak internal links, Not in a sitemap and Not crawled in 60 days. The request indexing queue ranks not-indexed URLs by value and links each straight to Search Console. You can see it on sample data in the live demo.

Questions

What is URL inspection in Google Search Console?

A tool that shows Google’s indexed information for one URL on your site: whether it’s indexed, the last crawl, how Google found it, the canonical Google chose, and anything blocking indexing. It also tests the live page and lets you request indexing.

What does the URL Inspection tool in Search Console provide?

The indexing status, discovery details (sitemaps and referring page), crawl details (last crawl, user agent, whether robots.txt allowed it, page fetch), indexing details (noindex, user-declared and Google-selected canonical) and detected enhancements.

What is crawling in Google Search?

Crawling is the first stage of Google Search: automated programs called crawlers, such as Googlebot, download text, images and videos from pages Google has found. Indexing and serving results come after it.

How many URLs can I inspect per day?

Through the URL Inspection API, 2,000 per site per day and 600 per minute. The Search Console interface also has a daily per-property limit that Google doesn’t publish.

How many times can I request indexing per day?

Google doesn’t publish the limit. In practice Search Console stops accepting requests at about 10 to 12 a day per property, so use them for your most important changed pages.

Why does the live test pass but the page still isn’t indexed?

The live test only checks that Google can fetch and index the page. It doesn’t check duplicate and canonical selection or quality, which are the usual reasons a crawlable page is left out.

Can I inspect a URL on a site I don’t own?

No. The URL must be in a Search Console property you have access to. For other sites, only public tools such as Google’s Rich Results Test work.

Inspect every page type, every day.

Connect Search Console and DirectoryLens runs URL inspections within Google’s quota and shows which templates Google is leaving out.

Explore the live demo →

5 days free · no card needed · ends on its own