The Google URL Inspection Tool is a page-level diagnostic tool that shows how Google sees a specific URL. It helps you check whether a page is indexed, review crawl and indexing details, test the current live page and request another crawl after an important change.
The tool sits inside Google Search Console and works one URL at a time, giving you more detail than a basic website index checker.
What the URL Inspection Tool Does
URL Inspection combines the main page-level indexing checks in one report.
Check Index Status and Search Eligibility
Use URL Inspection as a Google index checker for one exact page. It shows whether Google currently has that URL in its index and whether it may be eligible to appear in Search.
For anyone looking for a Google indexing checker, this is the page-level tool Google provides through Search Console. The result confirms indexing status, not rankings.
Diagnose Crawl and Indexing Issues
The report shows discovery, crawl, fetch, indexing and canonical information. These fields help you separate different problems instead of treating every missing page as the same issue.
That makes the Google URL Inspection Tool more useful than a simple URL index checker that only returns yes or no.
Test Changes and Request Another Crawl
The indexed report shows information Google already has. Test Live URL checks the current published page, while Request Indexing asks Google to crawl the URL again.
Use them after a meaningful update or after fixing an indexing problem.
How to Inspect a URL in Search Console
Google Search Console indexing data for one page starts with URL Inspection.
Two Ways to Open the Tool
Enter a URL in the inspection field at the top of Search Console, or use the inspect option beside a URL in another report when it is available.
The URL must belong to the Search Console property you are viewing.
Enter the Complete URL
Inspect the exact version you want to diagnose, including the protocol, hostname and full path.
Different URL versions can return different results, so checking the wrong protocol, subdomain or path can lead you to diagnose the wrong page.
Read the First Screen
The first screen shows the main verdict and expandable page indexing details. From there, you can review crawl, canonical and discovery information.
You can also access Test Live URL and, when appropriate, Request Indexing.
Caption:
Key areas to review first in Google Search Console URL Inspection, including index status, page indexing, live testing and Request Indexing.
Read the Indexed URL Status
The headline verdict shows Google’s current indexed status for the inspected URL.
Status | What it means |
|---|---|
URL is on Google | The URL is indexed and may be eligible to appear in Search. |
URL is on Google, but has issues | The URL is indexed, but a supported search enhancement has an issue. |
URL is not on Google | The URL is not currently indexed. Review the reported reason. |
URL is an alternate version | Google treats the URL as an alternate of another canonical page. |
URL Is on Google
URL is on Google means Google has indexed the inspected URL and it may be eligible to appear in Search.
It does not prove rankings or traffic. If you are troubleshooting, check the last crawl, fetch result and Google-selected canonical below the verdict.
URL Is on Google, but Has Issues
This status means the page is indexed, but Google detected an issue with a supported enhancement or structured data feature.
The problem affects the enhancement rather than basic index inclusion, so review the reported issue before deciding what to fix.
URL Is Not on Google
This means the inspected URL is not currently indexed. The important part is the reason shown in the page indexing details.
The cause may involve discovery, crawl access, fetching, a noindex directive, redirects, canonical selection or an HTTP error.
Caption:
Example of a URL that is not indexed in Google, with the Page Indexing reason highlighted before requesting another crawl.
URL Is an Alternate Version
Google may treat the URL as an alternate version of another page rather than as the main canonical URL.
This can be expected when alternate versions are intentional. Check the canonical information before trying to index the inspected URL separately.
Understand Crawl, Indexing and Canonical Details
Read the Crawl Details
Last crawl shows when Google visited the page. Crawled as identifies the crawler. Crawl allowed shows whether crawling was permitted, while Page fetch shows whether Google successfully retrieved the URL.
Together, these fields show whether Google could reach and fetch the page.
Why “Indexing Allowed” Can Mislead You
Read Crawl allowed before relying on Indexing allowed.
If robots.txt blocks Google from crawling the page, Google cannot read a page-level noindex directive. The indexing field can therefore appear allowed simply because Google could not access the page to see the directive.
Compare User-Declared and Google-Selected Canonicals
The user-declared canonical is the URL your site identifies as preferred. The Google-selected canonical is the version Google chose.
If they differ, investigate why before assuming the inspected URL should be indexed separately. Live testing cannot predict Google’s final canonical choice.
See also: Product Page SEO: Complete Optimisation Checklist
Check Sitemaps, Referring Pages and Last Crawl
See How Google Discovered the URL
URL Inspection can show a sitemap associated with the page and a referring page Google may have used to discover it.
Treat these fields as discovery clues, not a complete history of every source Google used.
Interpret Missing Discovery Data
If no sitemap or referring page is shown, do not assume Google has no discovery path.
For an important page, confirm that it belongs in the appropriate sitemap and has crawlable internal links from relevant pages.
See also: Shopify SEO Checklist: Easy Fixes to Improve Store Rankings
Use Last Crawl to Judge Data Freshness
The indexed report is based on Google’s previous processing of the URL.
If you changed or fixed the page after the Last crawl date, the stored report may still show the old state. Use a live test to check the current page.
Run and Interpret a Live URL Test
When to Use Test Live URL
Use Test Live URL after publishing a new page, making a meaningful update or fixing a crawl or indexing problem.
The test checks the page that is currently available, which is useful when the indexed report may still reflect an older version.
Watch Out for Redirects
A live test can follow a redirect without clearly showing the redirect path or final URL tested.
If the inspected URL redirects, verify the destination separately so you know which page Google can actually access.
What a Successful Live Test Actually Means
A successful live test means the current page passes the checks included in that test.
It does not mean the page is indexed. Google still needs to crawl and process the URL before the indexed status can change.
View the Rendered Page and Structured Data
View the Rendered Screenshot
After a successful live test, use View Tested Page to see how Google rendered the current URL.
The screenshot helps confirm that important visible content appears, especially when the page depends on scripts or external resources.
Check Loaded Resources and JavaScript Output
Review failed resources or JavaScript output when they affect important content.
If a required script or resource does not load, the rendered page may be incomplete even when the URL itself is accessible.
Review Structured Data
URL Inspection can show supported structured data and search enhancement information detected on the page.
Use these results to identify markup problems. Valid structured data can make a page eligible for supported enhancements, but it does not guarantee a rich result.
Request Indexing or Reindexing
When to Request Indexing
If you need to request indexing in Google Search Console, use it for an important new page, a meaningful update or a page where you have fixed an indexing problem.
Minor edits usually do not need a manual request.
How to Request Indexing in Google Search Console
Inspect the URL first and run a live test if you have just made a fix.
If the live test considers the page non-indexable, Request Indexing is unavailable until the issue is resolved. Once the page is indexable, use Request Indexing to ask Google to crawl it again.
What Happens Next
Request Indexing adds the URL to Google’s recrawl process. It does not force immediate indexing, and repeating the request does not make crawling faster.
For many new or updated pages, use an XML sitemap with an accurate <lastmod> value instead of requesting each URL individually.
What the Tool Does Not Test
It Does Not Check Discovery in a Live Test
The live test checks the current page, not how Google originally discovered it.
It does not provide the same sitemap or referring-page information shown in the indexed report.
It Does Not Make Canonical or Duplicate Decisions
A live test cannot confirm the final canonical Google will choose or reproduce every duplicate-content decision made during indexing.
A page can pass the live test and still be treated as an alternate or remain unindexed after processing.
It Does Not Check Penalties or Rankings
URL Inspection is not a ranking or penalty checker. It does not show keyword positions, traffic, manual actions, security issues or removal requests.
URL is on Google confirms index eligibility, not search performance.
See also: SEO Services Australia
Troubleshoot a Missing Page and FAQ
Troubleshoot One Missing URL
Inspect the exact URL and read the reported indexing reason before making changes.
If the report is based on an old crawl, run a live test. Fix crawl access, fetching, noindex, redirects or canonical issues first, then request indexing after the page is ready.
Use the Page Indexing Report for Site-Wide Problems
URL Inspection is best for one page. If many URLs show the same issue, use the Page Indexing report to identify the wider pattern, then inspect representative URLs individually.
See also: SEO Audit Services Australia
How do I check if a page is indexed by Google?
Enter the exact URL into the Google URL Inspection Tool. If the report shows URL is on Google, the page is indexed and may be eligible to appear in Search.
Use the details below the verdict to diagnose crawl, canonical or enhancement issues.
Does Request Indexing guarantee Google will index the page?
No. Request Indexing asks Google to crawl the URL again, but Google still decides whether the page should be added to the index.
Fix any crawl or indexability issue before sending the request.
Why does a URL pass the live test but stay unindexed?
Because the live test checks whether Google can access the current page. It does not complete the full indexing process.
The page may still need to be recrawled and processed, and Google may make a separate canonical or indexing decision.
Can I use a site: search as a Google index checker?
Yes, but only as a quick check. A site: search can help you see whether a page appears in Google, but it is not a complete index report.
Use URL Inspection when you need page-level diagnosis.