Article No. 42

How to Use the Google Search Console URL Inspection Tool

Abstract

The URL Inspection tool in Search Console shows what Google actually knows about one specific URL: whether it's indexed, what Google saw the last time it crawled the page, and...

Editorial Staff Published Read 6 min read

On this page

The URL Inspection tool in Search Console shows what Google actually knows about one specific URL: whether it’s indexed, what Google saw the last time it crawled the page, and whether the live version passes basic indexability checks right now. It’s a per-URL diagnostic, not a site-wide report. For patterns across many URLs at once, the Page Indexing report is the right tool; URL Inspection is where a site owner goes when a specific page needs answers.

This guide covers the tool’s UI and workflow only: what each field means, the distinction that causes most of the confusion around it, and how Request Indexing actually behaves. It doesn’t cover Googlebot’s crawling mechanics generally, or the full exclusion-reason taxonomy in the Page Indexing report; those live elsewhere.

Accessing the Tool

A URL can be inspected two ways: typing the fully-qualified URL into the inspection bar at the top of any Search Console screen, or clicking an “Inspect” link next to a URL inside another report (Page Indexing, Sitemaps, and others surface this link contextually). Inspection is scoped to whichever property is currently selected, and works for any URL within that property, indexed or not.

Indexed Version vs. Test Live URL: The Core Distinction

This is the single most important thing to understand about the tool, and the source of most user confusion. When a URL is inspected, Search Console first shows the Google index view: a snapshot of what Google saw and recorded the last time it crawled that URL, which could be hours or weeks old depending on how often the page gets crawled. Separately, clicking Test Live URL sends a fresh, real-time fetch and evaluates the page as it exists right now.

These two views can disagree, and often do. A page that was fixed an hour ago might still show as blocked or non-indexable in the Google index view, because that view reflects the last crawl, not the current state. A page that’s currently broken might still show as indexed and healthy in the Google index view, because Google hasn’t recrawled it since the problem started. Testing the live URL is the only way to confirm whether a recent fix actually resolved an issue; checking only the indexed version after making a change will often just show the old, pre-fix state.

Reading the Report: Field by Field

Field What it shows
Coverage status Whether the URL is indexed, and if not, which exclusion reason applies (points to the Page Indexing report's taxonomy for the full list)
Sitemaps Which submitted sitemap(s), if any, reference this URL
Referring page A page Google discovered this URL through, when available
User-declared canonical The canonical URL specified in the page's own markup
Google-selected canonical The canonical URL Google actually chose to index, which can differ from the user-declared one if Google judged another URL to be the better representative
Crawled as Whether Googlebot Smartphone or Googlebot Desktop performed the crawl (effectively always Smartphone today)
Page fetch Whether the most recent crawl attempt succeeded, and if not, why

The gap between user-declared and Google-selected canonical is worth watching closely. When they differ, it usually means Google judged the page to be a near-duplicate of another URL and picked the version it considered more authoritative, sometimes correctly, sometimes not. A pattern of Google overriding a site’s declared canonicals across many URLs is a signal worth investigating rather than a one-off quirk.

The Page fetch field is where most crawl-side surprises show up. A status of “Failed: Not found (404)” or “Failed: Server error (5xx)” here explains, in plain terms, why a page might be missing from the index even when everything else about it looks fine. “Failed: Blocked by robots.txt” points back to a robots.txt rule as the actual cause, which is a faster diagnosis than working backward from the Page Indexing report alone for a single URL a site owner already has in mind.

Testing a Brand-New Page

For a URL that hasn’t been crawled yet at all, inspecting it returns a straightforward “URL is not on Google” result with no historical data to show, since there’s no prior crawl to report on. Running Test Live URL in this case still returns useful information: whether the page is currently reachable, whether it would pass basic indexability checks (no unintended noindex tag, no accidental robots.txt block), and a rendered screenshot of what Googlebot currently sees. This is the right moment to catch a launch-time mistake, an accidentally-inherited staging noindex tag being the most common one, before requesting indexing and waiting on a full crawl cycle to discover the same problem days later.

Using Request Indexing Correctly

The Request Indexing button submits a URL into Google’s crawl queue with elevated priority; it is not an instant re-crawl and it does not bypass normal processing. In practice, expect the live test itself to complete in something like seconds to a couple of minutes, but the actual crawl and indexing of the URL afterward can still take anywhere from under a day to well over a week, depending on the site’s overall crawl demand and the URL’s history.

Google has acknowledged that Request Indexing is subject to a daily quota per property, but has not published an exact number in its current official documentation. Any claim online of a specific figure like “10 to 50 requests per property” is an unofficial estimate based on user reports, not a Google-confirmed limit. The accurate framing: Google enforces an undisclosed daily quota on manual indexing requests, and once it’s hit, the Request Indexing option becomes unavailable until it resets, typically after about 24 hours.

Request Indexing is appropriate for a handful of specific, already-fixed URLs, not as a substitute for solving an underlying crawl or content problem across many pages. Submitting the same broken URL repeatedly without fixing the underlying issue does nothing, since Google will simply re-observe the same problem on the next crawl.

Common Statuses and What They Mean

  • URL is on Google: the page is indexed and, as far as the tool can tell, eligible to appear in search results.
  • URL is not on Google: the page isn’t indexed, and the specific exclusion reason (Discovered – currently not indexed, Crawled – currently not indexed, blocked by robots.txt, and others) determines the next step.
  • URL is on Google, but has issues: the page is indexed, but something (a mobile usability problem, for instance) is flagged.

When to Escalate Beyond the Tool

URL Inspection is built for one URL at a time. When the same issue shows up across many URLs, or when the goal is understanding a site-wide pattern rather than a single page’s status, the Page Indexing report is the better starting point; it groups affected URLs by exclusion reason and shows trend data over time, which the single-URL tool doesn’t provide.

Used correctly, the tool’s real value is narrow but genuinely useful: confirming, with a live test, that a specific fix actually worked, rather than relying on Google’s last crawl of the page to tell that story.

Related:

  1. Google Search Console Indexing Issues: A Guide to the Page Indexing Report The Page Indexing report (Search Console's central indexing dashboard, sometimes still called the Coverage report from its earlier name) groups every URL Google knows about into an indexed or excluded......
  2. URL Structure Best Practices: How to Build URLs Google and Users Can Actually Read This post covers how to construct a new URL: length, word choice, separators, folder depth, and consistency rules. It does not cover what to do when two URLs serve the......
  3. Rich Results Types: What’s Actually Live in Google Search (2026) Rich result eligibility changes often enough that a "which types are worth implementing" page goes stale fast, and the date on this heading is load-bearing, not decorative. This is a......
  4. URL Parameters & Canonical Strategy: Handling Tracking, Filter & Session Duplicate URLs Query parameters create URL variants of the same underlying content. A product page reached through ?utm_source=newsletter, a filtered collection view at ?color=black&size=medium, an old-style session ID appended as ?sid=8f3e2a1 all......
  5. On-Page SEO Mechanics Checklist: Title Tags, Headers, URL Slugs, Keyword Placement & Alt Text This post covers one thing: the mechanical, page-level elements you control directly in your HTML and content structure. Title tags. Heading hierarchy. URL slugs. Where keywords belong on the page.......
  6. Google Analytics 4: Setup and Configuration Guide This is a setup and configuration guide for Google Analytics 4 as it exists today, not a Universal Analytics migration walkthrough. If you're reading this in 2026, you're almost certainly......
  7. Google Tag Manager Performance: How Tags Slow Pages Down and How to Fix It Google Tag Manager itself is lightweight. The container script that loads GTM is small, and its job is simply to load and manage other tags, not to do heavy work......
  8. How to Read Search Volume Data (And When It’s Lying to You) You already have a keyword with a number next to it. Maybe it's 2,400, maybe it's 90, maybe it's a range. The question this guide answers isn't where to find......
  9. Victorious: New York City SEO Services from a National Agency Victorious is an SEO-only marketing agency founded in 2013 by Michael Transon, who remains the company's CEO. The agency did not start out SEO-exclusive: for its first few years it......
  10. 15 Strategic SEO Content Ideas for Acupuncture Clinics in Georgia Georgia licenses acupuncturists through the Georgia Composite Medical Board under a specific statute (O.C.G.A. 43-34-64), Medicare covers acupuncture for exactly one condition, and Georgia Medicaid generally does not cover it......
  11. 18 Strategic SEO Content Ideas for Air Conditioning Services in Georgia Georgia is not one HVAC market, it is at least three. A condenser unit twelve miles from the Savannah coast fights salt air and near-constant humidity. A unit in a......
  12. 16 Strategic SEO Content Ideas for Antique Stores in Georgia Georgia's antiquing scene doesn't sit in one neighborhood. It's split across a handful of real, distinct regional clusters: the dealer-dense districts inside metro Atlanta, the historic squares of Savannah, the......
  13. Crawl Budget: When It Actually Matters and How to Fix It Most sites reading a "crawl budget optimization" guide don't actually need one. That's not a hook, it's Google's own position: its crawl budget documentation opens by telling most readers to......
  14. Webpack Optimization for SEO: Bundle Size, Code-Splitting, and Loading Performance JavaScript bundle weight and structure connect directly to two of the three Core Web Vitals. A large, poorly split bundle can delay Largest Contentful Paint by blocking rendering while it......
  15. Canonical Tag Complete Guide: What rel=canonical Does and How to Implement It A canonical tag tells Google which URL, among a group of URLs that show the same or very similar content, should be treated as the primary one for indexing and......
Call Now Button