Stop guessing whether your pages are indexed. The URL Inspection tool in Google Search Console gives you the ground truth. This guide shows you exactly how to use it, interpret every status, and fix the most common blocking issues.
Third-party index checkers are unreliable. They sample, they guess, they cache. The Google Search Console URL Inspection tool reads live data from Google's own index. When you paste a URL and hit Enter, you get the exact answer Google uses for ranking decisions. No approximation.
A common situation we see: an SEO runs a site: search, sees the page, assumes it's indexed. Then the URL Inspection shows 'Crawled but not indexed'. The difference? The site: operator shows stale data. The Inspection tool shows the last crawl verdict. That gap costs weeks of wasted effort if you chase the wrong signal.
If you want to understand why Google might block indexing entirely, read Google's official documentation on blocking indexing with robots.txt and meta tags. It's the authoritative source for the technical mechanisms underneath.
You need a verified property in Search Console. That's non-negotiable. Once you have it, the workflow is short but dense.
Step 1: Open Google Search Console and select the correct property (URL prefix or Domain).
Step 2: Paste the full URL you want to check into the search bar at the top. Include the protocol (https://).
Step 3: Press Enter. The tool runs a live test. This takes 10-30 seconds.
Step 4: Read the 'Coverage' result. You'll see one of: 'URL is on Google', 'Indexed', 'Not indexed', 'Excluded', 'Error', or 'Pending'.
Step 5: If the status is anything other than 'URL is on Google', click 'View details' to see the root cause. This is where the real work begins.
For pages that are not indexed, the next step is often a deep diagnostic. Our guide on pages not indexed diagnostic walks through the exact filters and log analysis you need when the basic inspection shows 'Crawled but not indexed'.
Must be exact. Include trailing slash if used in sitemap.
Look for 'URL is on Google' – anything else needs details.
Read the 'Why is this URL not indexed?' field. It gives the exact reason.
Remove noindex tag, fix robots.txt block, or improve page quality.
Click the 'Request Indexing' button. One request per URL per week max.
Some changes take days. Re-check to confirm indexing.
| Status Label | What It Actually Means | Most Common Cause | Hidden Failure Mode |
|---|---|---|---|
| URL is on Google | Page is indexed and can appear in search results | Normal, healthy page | Might still have index bloat – too many low-value pages indexed |
| Indexed | Same as 'URL is on Google' but older UI naming | Normal state | Check the indexing date – if old, Google might not be re-crawling |
| Not indexed | Google knows the URL but chose not to index it | Crawled but not indexed – often thin content or duplicate | Page might have good content but low authority; fix with internal links |
| Excluded | URL was excluded via noindex tag, robots.txt, or canonical directive | noindex meta tag left on accidentally | Canonical tag pointing to a different URL – Google respects it even if you don't |
| Error | Google tried to crawl but hit a technical failure | 5xx server error or DNS resolution failure | Soft 404s (200 status but empty page) are often missed by crawlers |
| Pending | URL is in the crawl queue but hasn't been processed yet | Brand new page or after a sitemap submission | If pending for more than 2 weeks, the page might be stuck due to crawl budget |
Let's run a real inspection. URL: https://example.com/blog/seo-tips-2025. I paste it into Search Console. The result: 'Excluded – Blocked by robots.txt'.
I click 'View details'. The tool shows: 'Blocking directive: robots.txt'. It also shows the exact line: Disallow: /blog/. That's the culprit. The entire blog section is blocked.
I open the robots.txt file at https://example.com/robots.txt. There it is, line 12: Disallow: /blog/. A developer added it six months ago during a staging migration and never removed it.
The fix: delete that line, save the file, and test it with the robots.txt Tester in Search Console. Then I click 'Request Indexing'. After 72 hours, the inspection shows 'URL is on Google'. Traffic from organic search to that blog post goes from zero to 140 clicks per week within 10 days.
For a broader look at crawl errors that can block indexing even when the robots.txt is clean, check out our deep dive on Google crawl errors – it covers soft 404s, DNS timeouts, and redirect loops that the URL Inspection tool flags.
The URL Inspection tool is accurate, but it has blind spots. Here are three edge cases we've seen burn teams.
1. JavaScript rendering mismatch. The tool renders the page twice: once as Googlebot (no JS) and once as Googlebot Smartphone (with JS). If your page depends on client-side rendering, the inspection might show 'Crawled but not indexed' because the no-JS version is empty. The fix: use server-side rendering or dynamic rendering. The Inspection tool shows you both versions in the 'Screenshot' tab. Compare them.
2. Cross-property confusion. You have a Domain property and a URL prefix property. The inspection only checks the property you're in. If the URL is indexed under the other property, you'll see 'Not indexed' incorrectly. Solution: always verify both properties and check both if in doubt.
3. Soft 404s that look like 200. The tool might show 'Indexed' but the page is a thin, auto-generated tag page with 20 words. It's indexed, but it's weak. The Inspection tool won't tell you that. You need manual quality review. Google's documentation on blocking indexing explains how to use noindex on such pages to avoid index bloat.
If you're managing a large site and need to automate index checks, the Python Google Indexing API setup guide shows you how to submit URLs and check status programmatically – useful for bulk workflows that the manual tool can't handle.
Verify you are in the correct Search Console property (Domain vs URL prefix)
Make sure you have Owner or Full User permissions – Restricted users cannot see details
Check that the URL includes the exact protocol (https vs http) and trailing slash
Clear your browser cache before running the live test. Stale cache can show old results
If the URL is new, wait at least 24 hours after publishing before expecting a result
Run the inspection on both Googlebot and Googlebot Smartphone to catch rendering issues
This is rare but serious. Check if your homepage has a noindex tag accidentally applied. Also check robots.txt for a Disallow on the root. If both are clean, the page might be blocked by a canonical tag pointing elsewhere. Use the 'View details' link in the inspection report to see the exact blocking reason.
The manual tool only checks one URL at a time. For bulk, use the Indexing API (quota: 200 URLs per day per property). Our guide on the Python Google Indexing API setup shows how to script it. Alternatively, export your sitemap and check a sample of 50 URLs manually to spot patterns.
An 'Error' status means Googlebot could not access the URL during the last crawl. Common causes: 5xx server error, DNS timeout, or a redirect loop. Check your server logs for the crawl IP range. If the error persists for more than 48 hours, the page might be dropped from the crawl queue. Fix the server issue, then request indexing again.
'Crawled but not indexed' means Googlebot fetched the page but chose not to index it – often due to thin content, low authority, or duplication. 'Discovered but not indexed' means Google found the page via a link or sitemap but hasn't crawled it yet, usually due to crawl budget limits. The URL Inspection tool shows both as 'Not indexed' but the details tab tells you which one.
Yes, and you should. After a guest post goes live, run the URL Inspection to confirm it's indexed. If it shows 'Not indexed' or 'Excluded', the guest post has no SEO value. Common reasons: the host site used a nofollow or noindex tag. Check the page source yourself. If the host refuses to fix it, consider moving the post to a different site.
A brand-new site with no crawl history will show 'Pending' or 'Not indexed' for weeks. This is normal. Submit your sitemap via Search Console and request indexing for the most important pages. Do not over-request indexing – Google limits requests per URL to once per week. Focus on building internal links and getting one or two external links to kickstart crawling.
First, identify the exact reason in the 'Coverage' details. Common fixes: remove noindex tag, unblock the page in robots.txt, fix the canonical tag to self, improve page content if it's thin, or fix server errors. After the fix, click 'Request Indexing'. Wait 24-48 hours, then re-inspect. If it still fails, check for a redirect chain that ends at a blocked URL.
Yes, it is completely free. There is no per-user, per-property, or per-URL charge. However, the Indexing API (for bulk submission) has a daily quota of 200 URLs per property. For agencies managing dozens of client sites, you need one Search Console property per client. The manual Inspection tool has no hard limit, but Google may temporarily throttle excessive requests.
Quick calculator. Put in the expected monthly value of a page or link batch and the natural waiting time.