URL Inspection Tool: How to Diagnose Any Page Fast

By Emily Redmond, Data Analyst at Emilytics · April 2026

TL;DR: The URL Inspection tool shows you what Google sees when it visits your page—indexing status, crawl errors, rendering issues, Core Web Vitals. Paste any URL, get instant diagnostics, request reindexing. Your fastest way to debug a page.

The URL Inspection tool is the Swiss Army knife of GSC. One tool, instant diagnostics. Is your page indexed? Can Google access it? Are there mobile issues? Rendering errors? Just inspect the URL and you'll know in seconds.

This is your go-to when something feels off.

How to Use URL Inspection

Step 1: Open the Tool

At the top of any GSC page, you'll see a search bar. Click it and paste your full URL:

https://yoursite.com/your-page-slug

Include the full URL, including http/https. Partial URLs won't work.

Step 2: Wait for the Report

GSC will crawl that page and show you a report. Usually takes 5–30 seconds depending on Google's queue.

Step 3: Read the Result

You'll see:

• URL is on Google (green check) = Page is indexed, can rank
• URL is not on Google (red X) = Page is not indexed
• Page crawled successfully or Crawl blocked = Google could/couldn't access it

Below that, you'll see details:

• Crawl status
• Last crawl date
• Screenshots of how Google sees the page
• Core Web Vitals
• Mobile usability issues (if any)
• AMP status (if applicable)

Understanding the Statuses

If you see anything other than "Indexed," investigate. It's usually fixable.

💡 Emily's take: I use URL Inspection on every new page I publish before declaring victory. Takes 30 seconds and saves you from publishing a page that won't rank because it's got a noindex tag or a rendering issue. Small habit, big payoff.

Common Findings and Fixes

Issue: "Crawl denied"

Cause: Google's crawler can't access the page.

Why:

• robots.txt is blocking it
• Server is returning 5xx errors
• Page requires login
• Redirect loop

Fix:

1. Check your robots.txt file (at yoursite.com/robots.txt)
2. Make sure it's not blocking the page
3. Check your redirects—no loops
4. Test the URL in your browser. Does it load?
5. Check server logs for 5xx errors

Re-run the inspection after fixing.

Issue: "Discovered, not indexed"

Cause: Google found your page but decided not to index it.

Why:

• Low-quality content
• Duplicate content
• Noindex tag
• Too similar to other pages
• Content doesn't load properly

Fix:

1. Check if the page has a noindex tag (look at page source, search for "noindex")
2. Remove noindex if it's there
3. Check content quality. Is it substantial? >300 words?
4. Check if it's a duplicate of another page. Remove if so.
5. Re-submit for indexing

Issue: "URL marked as duplicate"

Cause: Google thinks this page is a duplicate of another.

Why:

• You have the same content on multiple URLs
• You haven't set a canonical tag
• www vs non-www versions exist

Fix:

1. Identify which version should rank (usually the preferred domain)
2. Add a canonical tag to the non-preferred version pointing to the preferred one: <link rel="canonical" href="https://yoursite.com/preferred-url">
3. Or redirect non-preferred → preferred using a 301 redirect
4. Re-inspect

Issue: Core Web Vitals Failing

Cause: Page is slow or has stability issues.

Why:

• Large images
• Slow server
• Render-blocking CSS/JavaScript
• Ads loading after content

Fix:

1. Go to PageSpeed Insights for that URL
2. See the specific recommendations
3. Ask a developer to implement
4. Re-test in a few days

Learn more in the Core Web Vitals article.

Issue: Mobile Usability Errors

Cause: Page is broken on mobile.

Why:

• Text too small
• Buttons too close together
• Viewport not set correctly
• Content wider than screen

Fix:

1. Open the page on a phone (or use Chrome dev tools, F12, toggle device toolbar)
2. See what's broken
3. Fix it
4. Re-inspect

Requesting Reindexing

If the page isn't indexed but should be, click "Request indexing" button in the inspection report.

This tells Google to re-crawl the page and consider it for indexing. Usually takes 24–48 hours.

Only use this for important pages. Google crawls regularly anyway; you're just prioritizing.

Checking Rendering Issues

GSC shows you two versions of your page:

• Desktop version: How it appears on desktop
• Mobile version: How it appears on mobile

If they look different (mobile is broken), you have a rendering issue.

Common problem: Client-side rendering. Content loads via JavaScript after the page initially loads. Sometimes Google doesn't execute JavaScript properly, so it sees a blank page.

If this happens:

1. Check if your CMS or framework uses client-side rendering
2. Consider server-side rendering (technical change)
3. Or ensure critical content loads without JavaScript

Using Inspection for Content Updates

Updated an old article with new information?

1. Inspect the URL
2. If it's indexed, click "Request indexing"
3. Google will re-crawl and re-rank based on the new content

Takes 24–48 hours. Your updated content should show new ranking position after that.

Bulk Inspection (for Many Pages)

You can only inspect one URL at a time in GSC. If you need to check many pages:

1. Submit them in your sitemap (if not already submitted)
2. Check the Coverage report to see which have indexing issues
3. Inspect individual problem pages

Sitemap + Coverage report is faster than inspecting 50 pages individually.

Frequently Asked Questions

Q: How often can I inspect a URL? A: As many times as you want. No limit.

Q: What if inspection shows "Indexed" but I don't see it ranking? A: Being indexed doesn't guarantee ranking. You still need content quality, backlinks, and relevance. Inspect just tells you Google found it.

Q: Can I inspect URLs from competitors' sites? A: Only if you have a GSC property for that domain. You can't inspect competitors' sites.

Q: How fast is the inspection? A: Usually 5–30 seconds. Sometimes slower if Google's queue is full.

Q: Should I inspect every page I publish? A: Yes, especially new or important pages. Takes 30 seconds and prevents indexing surprises.

Next Steps

Next time you publish a page, inspect it immediately. If it shows "Indexed" with no errors, you're done. If you see issues, fix them and re-inspect.

Use URL Inspection as your diagnostic tool when something feels off with a page's rankings or visibility.

Emily Redmond is a data analyst at Emilytics — the AI analytics agent that watches your GA4, Search Console, and Bing data around the clock. 8 years of experience. Say hi →