URL Inspection Tool: The Complete Guide (2026)

The URL Inspection tool in Google Search Console tells you whether a specific URL is indexed, why it is or isn’t, and lets you test the live page and request indexing. Its catch: it only works on URLs inside a property you’ve verified, and only one URL at a time. So for auditing hundreds of pages — or backlinks that live on sites you don’t own — you need a bulk approach instead.

This guide covers everything the tool does, how to read each part of the report, its real limits, and what to use when one-URL-at-a-time stops being practical.

What the URL Inspection tool is

URL Inspection shows you Google’s indexed version of a page and lets you test whether the current version could be indexed. You open it two ways:

• Type a fully-qualified URL into the inspection bar at the top of Search Console.
• Click the Inspect link next to a URL in most Search Console reports.

The URL must belong to the property you currently have open. That single requirement drives most of its limitations, which we’ll get to.

How to inspect a URL

1. Open the correct property in Search Console.
2. Paste the full URL (including https://) into the inspection bar.
3. Read the indexed status (data from Google’s last crawl).
4. If you’ve changed the page recently, click Test Live URL to check the current version.
5. Fixed an issue? Click Request Indexing.

Reading the index status

The headline result falls into one of four states:

• URL is on Google — indexed and eligible to appear (eligible ≠ guaranteed to rank).
• URL is on Google, but has issues — indexed, but enhancements or AMP problems exist.
• URL is not on Google — not indexed; the report shows the reason.
• URL is an alternate version — e.g. an AMP page treated as alternate to the canonical.

The coverage details that actually matter

Under the status, Google explains how it handled the page. The fields worth reading:

Field	What it tells you
Discovery / Referring page	How Google found the URL (sitemap, a linking page)
Last crawl	When Google last fetched it — old date = stale data
Crawled as	Googlebot desktop or smartphone
Crawl allowed	Whether robots.txt permits crawling
Page fetch	Whether Google could retrieve the page
Indexing allowed	Whether a noindex directive is blocking it
User-declared canonical	The canonical you set
Google-selected canonical	The canonical Google actually chose — the key field for duplicate issues

If “User-declared” and “Google-selected” canonical don’t match, you’re likely looking at a duplicate/canonical problem.

Indexed status vs Live Test (the part people get wrong)

These are two different things, and confusing them wastes hours:

• Indexed status = what Google stored at the last crawl. If you fixed a problem yesterday but Google last crawled three weeks ago, this still shows the old, broken state.
• Test Live URL = the page’s current state, fetched in real time, bypassing the index. Fixed the issue? The live test reflects it immediately.

Rule of thumb: use the indexed status to see what Google currently believes; use the live test to confirm a fix before you request indexing.

Requesting indexing (and its limits)

After a live test passes, click Request Indexing to add the URL to Google’s crawl queue. Keep expectations realistic:

• Indexing can take anywhere from a day to one–two weeks.
• There’s a daily per-property limit (a soft cap widely observed around 10–12 manual requests per day).
• Requesting indexing does not guarantee indexing — a thin or low-value page still won’t be indexed.
• Spamming “Request Indexing” without changing the page does nothing.

For many pages at once, submitting a sitemap with accurate <lastmod> dates is a better discovery signal than clicking request repeatedly.

Viewing the crawled and rendered page

Both the indexed result and the live test can show you what Googlebot saw:

• Raw HTML returned
• HTTP response headers
• JavaScript console output and loaded page resources
• A screenshot of the rendered page — live test only, and only when the fetch succeeds

This is where you catch rendering problems: content that depends on JavaScript, blocked resources, or a page that looks fine to you but renders empty for Googlebot.

What the tool does NOT do

Knowing the blind spots saves you from wrong conclusions:

• It doesn’t check quality/security guideline compliance or manual actions.
• The live test doesn’t confirm whether duplicates are truly indexed, or check sitemap/referring pages.
• It only works on properties you’ve verified — you can’t inspect a competitor’s page or a backlink on someone else’s site.
• It’s one URL at a time, with a daily inspection limit per property.

When one URL at a time isn’t enough

This is the real ceiling for anyone working at scale. Two common cases the URL Inspection tool simply can’t handle:

• Hundreds or thousands of your own URLs — inspecting each by hand is impossible, and the daily limit stops you fast.
• Backlinks on sites you don’t own — you can never verify those properties, so the tool won’t touch them at all.

For both cases you need a checker that works outside Search Console and handles lists. A bulk index checker lets you paste or import thousands of URLs and get Indexed / Not indexed in one pass — including third-party backlink URLs the URL Inspection tool can’t see.

The URL Inspection API (for automating your own site)

Google offers a URL Inspection API to automate checks within your verified properties. The practical limits:

• 2,000 requests per day and 600 per minute, per property.
• Project-level ceilings are much higher, but the per-property 2,000/day is the real bottleneck.
• Still property-only — it won’t inspect URLs you don’t own.

Great for monitoring your own site’s indexation programmatically; not a solution for large backlink lists.

FAQ

Can the URL Inspection tool check my backlinks?

No. If a link sits on a site you haven’t verified in Search Console, the tool can’t inspect it. Use a bulk index checker that doesn’t require GSC for those.

Why does the tool say “indexed” but the Page Indexing report says otherwise?

Usually reporting lag. URL Inspection is closer to real time, so trust it over the aggregate report for a single URL.

How long after Request Indexing until a page is indexed?

Anywhere from a day to a couple of weeks — and only if the page is worth indexing.

What’s the difference between the live test and the indexed result?

The live test is the page’s current state, fetched now; the indexed result is what Google stored at its last crawl.