The URL Inspection tool is the single most useful diagnostic in Google Search Console. Paste any URL from your verified property into the search bar at the top of GSC, and you get a complete picture of how Google sees that specific page — indexed or not, crawled or not, what canonical Google chose, what schema it detected, and what the page looks like to Googlebot when rendered.
Most people use it for one thing (requesting indexing). It can do considerably more.
How to Open It
At the top of every GSC page is a search bar that says "Inspect any URL in [property name]." Paste a URL from your verified property and hit Enter. You can also click any URL from any GSC report — Performance, Page Indexing, etc. — and it opens the URL Inspection view for that specific URL.
Note: the URL must be from a verified property. You can't inspect competitor URLs or URLs from sites you don't have GSC access to.
The Two Views: Indexed vs Live Test
After inspecting a URL, you'll see Google's last cached information about it. The key sections:
- Coverage: Indexed or not, last crawled date, sitemap inclusion, referring page that helped Google discover the URL
- Enhancements: Detected structured data (Article, FAQ, Product, etc.) and any errors in the schema
- Mobile usability: Page experience flags from Core Web Vitals
- HTTPS status: Certificate validity
The data shown is from Google's last crawl, which can be days or weeks old. To see the current state of the page, click "Test live URL" in the top right. This makes Google crawl the page right now and report back — typically in 10-60 seconds.
What the Live Test Shows
The live test result has its own set of tabs:
HTML
Shows the raw HTML Googlebot received from your server. Critically: this is the HTML before JavaScript execution. If your site is JavaScript-heavy (React, Vue, Angular), this is what Googlebot's initial fetch returns — and it may not be what users see in their browsers.
Screenshot
A rendered screenshot of the page as Googlebot sees it after JavaScript execution. Compare this to what you see in your browser. If they differ significantly, Google may not be indexing the content you think you're publishing.
More Info
Includes HTTP response code, request status, page resources loaded, JavaScript console messages, and any errors encountered during rendering. This is where you find the diagnostic details that explain why a page isn't indexing correctly.
The Top 5 Things to Use It For
1. Diagnosing Why a Page Isn't Indexed
Open the URL Inspection for the page. Read the Coverage section. The status will be one of:
- "URL is on Google" — indexed and fine
- "URL is on Google, but has issues" — indexed but problems noted (check the issues list)
- "URL is not on Google" — not indexed, with a reason
If not indexed, scroll to the Indexing section and read the specific reason. The most common ones (and what to do about them) are covered in detail in our post on the Page Indexing report.
2. Requesting Indexing After Publishing or Updating
After publishing a new page or making significant updates to an existing one, you can nudge Google to recrawl it. In the URL Inspection view, click "Request indexing." Google will queue the URL for fresh crawling.
Two important caveats:
- Request indexing has a daily quota (around 10-12 requests per day per property). Use it for important pages, not bulk updates.
- Requesting indexing doesn't guarantee indexing — Google still applies its quality and value criteria. Forcing a recrawl of a low-quality page just gets that page re-evaluated, not promoted.
3. Verifying JavaScript Rendering
Run the live test on a content-heavy page from a JavaScript-rendered site. Switch to the screenshot tab. If the rendered screenshot shows your actual content (paragraphs, images, navigation), JavaScript rendering is working correctly. If the screenshot shows a blank or partially-rendered page, Google isn't seeing your content the way users do — which prevents indexing or ranking.
Also check the HTML tab. The pre-render HTML should at minimum contain meta tags, structured data, and ideally enough textual content to express the page's topic. If the pre-render HTML is essentially empty, you're relying entirely on Googlebot's rendering engine to discover your content — which works but adds risk and delay.
4. Verifying Structured Data Implementation
The Enhancements section shows which structured data types Google detected on the page. If you implemented Article schema but the inspection shows none detected:
- The schema is malformed (validation errors)
- The schema is in a part of the page Google can't access
- The schema implementation is correct but Google hasn't recrawled since you added it
For detailed schema validation, also use Google's Rich Results Test — it provides more diagnostic detail than the URL Inspection tool's Enhancements section.
5. Confirming Canonical URL Selection
For pages where multiple URLs could be considered duplicates (with/without trailing slash, with/without www, with/without query parameters), the inspection tool shows which URL Google chose as canonical.
If "User-declared canonical" differs from "Google-selected canonical," Google disagreed with your canonical tag. This is the diagnostic signal that you have a canonical configuration problem — usually fixable by ensuring consistent canonical tags across the duplicate URLs, ensuring internal links point only to the canonical version, and verifying the canonical URL is at least as accessible to crawlers as the duplicates.
Common Misuses
Things people use the URL Inspection tool for that don't really work:
- Bulk indexing requests: Too rate-limited. Use sitemaps and good internal linking instead.
- Diagnosing ranking issues: The tool confirms whether a page is indexed and how Google sees it; it doesn't explain why it ranks where it ranks.
- Checking how your site performs in search: That's the Performance report's job. URL Inspection is per-URL diagnostics, not site-wide performance.
The Programmatic Version
For automation, the URL Inspection API (separate from the Search Analytics API) lets you check the indexing status of URLs programmatically. Quota: 2,000 URL inspections per day per property. Useful for:
- Automated indexation monitoring at scale
- Verifying that newly-published URLs got indexed within a target time window
- Building internal dashboards that combine indexing status with other site data
Google's URL Inspection API documentation covers the request structure and response format.
A Diagnostic Worth Building Into Your Workflow
After publishing or significantly updating any important page, run a live test 24 hours later. Check that the rendered HTML contains your content, the structured data was detected, the canonical is what you intended, and the page is eligible for indexing. This 30-second check catches the surprising number of cases where a page looks fine in browsers but has a subtle issue that prevents Google from indexing it correctly.
Most of the indexing problems I've encountered across multiple sites were diagnosable within the URL Inspection tool in under five minutes. The information is all there; the question is whether you read it before assuming you have a more complex problem.