Using URL Inspection in Google Search Console: A Founder Guide

Why URL Inspection Matters (And Why You're Probably Not Using It)

You shipped your product. Traffic is coming in. But organic search? Silent.

The brutal truth: you don't know if Google even sees your pages. You assume they're indexed. You hope the crawler found them. You're flying blind.

URL Inspection is the tool that kills that guessing game. It's a 30-second audit of any single page—what Google crawled, what it indexed, whether it's rendering correctly, and why it might be invisible. It's buried in Google Search Console, and most founders never touch it.

This guide walks you through it step-by-step. You'll learn how to diagnose why a page isn't showing up in search, request indexing on demand, and fix the problems that are tanking your organic visibility.

Let's ship some SEO wins.

Prerequisites: What You Need Before You Start

Before you can use URL Inspection, you need three things in place:

1. A Google Search Console Account

You need GSC set up and your domain verified. If you haven't done this yet, follow the step-by-step setup guide to get running in 10 minutes. Verification takes 5 minutes—use the DNS method if you control your domain registrar, or the HTML file method if you can't touch DNS.

2. Your Domain Actually Verified

URL Inspection only works on domains you own and have verified in GSC. If you're looking at a domain you don't control, the tool won't let you inspect it. Here's the complete guide to verifying your domain using every method available—DNS, HTML file, meta tag, or Analytics.

3. The Page Must Be Public

Google can't inspect pages behind a login, paywall, or robots.txt block. If you're testing staging URLs or password-protected content, URL Inspection will fail. Make sure the page is live and publicly accessible before you inspect it.

If you have all three, you're ready to go.

Step 1: Access URL Inspection in Google Search Console

Open Google Search Console. You're at https://search.google.com/search-console.

Select your property (the domain you want to inspect).

Look at the top of the left sidebar. You'll see a search box with a magnifying glass icon. That's URL Inspection.

Click on it. The search box expands.

Paste in the full URL you want to inspect. Include the protocol (https:// or http://), the domain, and the full path. Don't just paste the domain—paste the exact URL.

Examples:

• https://seoable.dev/insights/url-inspection-tool-search-console-feature-founders-underuse
• https://myproduct.com/pricing
• https://myproduct.com/blog/post-title-here

Hit Enter or click the search icon.

Google processes the request. This takes 10-30 seconds. You'll see a loading state. Wait for it to finish.

Step 2: Read the Indexing Status

Once URL Inspection loads, the first thing you see is the indexing status. It's a large colored box at the top. There are three possible statuses:

URL is on Google

Green box. This means Google crawled, rendered, and indexed the page. It's in the search index. This is what you want. The page is eligible to show up in search results.

If you see this, your page is indexed. The problems you're having with visibility are likely ranking issues (keyword strategy, competition, content quality), not indexing issues. Read the Performance Report guide to understand why an indexed page isn't ranking.

URL is on Google but has issues

Yellow/orange box. This means Google indexed the page, but something's wrong. Common issues: missing meta tags, mobile usability problems, AMP errors, or structured data issues. The page is indexed, but Google flagged something that might hurt ranking or display.

Scroll down to the "Enhancements" section to see what's broken. Fix those issues and re-test.

Discovered - not indexed

Red box. Google found the page (via sitemap, internal links, or crawling), but didn't index it. This is the problem status. Your page is invisible in search.

Scroll down to see why. Common reasons: robots.txt blocks it, noindex tag, redirect, duplicate content, or Google just hasn't crawled it yet. Check the Coverage Issues guide for a plain-English breakdown of every exclusion reason.

Not found (404)

Gray box. The page doesn't exist or returns a 404 error. Google can't index something that's not there.

If you see this, the URL is wrong, the page was deleted, or there's a server error. Double-check the URL. Make sure the page is live and returns a 200 status code.

The status box is the headline. It tells you immediately whether indexing is the problem or not.

Step 3: Inspect the Crawl, Index, and Serving Details

Below the status box, you'll see three tabs: Crawl, Index, and Serving. Each one tells you something different about what Google did with your page.

Crawl Tab

This shows whether Google's crawler could access the page. Look for:

Last crawl date: When did Google last crawl this URL? If it's old (weeks or months), Google isn't visiting often. Check if you need to submit a sitemap or request indexing.

User-agent: What Googlebot version crawled it? Usually "Googlebot" or "Googlebot-Image". Ignore this unless you're debugging mobile-specific crawl issues.

HTTP status code: Did the page return a 200 (success)? Or a 3xx (redirect), 4xx (error), 5xx (server error)? If it's not 200, Google can't index it.

If the crawl tab shows an error, the problem is at the server level. Check your server logs. Make sure the page returns a 200 status code. If it's a redirect, make sure it's a 301 (permanent) not a 302 (temporary).

Index Tab

This shows whether Google indexed the page after crawling it. Look for:

Indexing allowed: Is the page blocked by robots.txt, noindex, or redirect? If "No", Google crawled it but didn't index it. Check why.

Canonical URL: What URL does Google think is the canonical version? If it points to a different URL, Google is indexing that version instead. Read the canonical domain guide to understand how to enforce the right version.

Mobile-friendly: Is the page mobile-optimized? This doesn't block indexing, but it affects ranking on mobile search.

If indexing is blocked, the reason appears here. Common blocks: noindex meta tag, robots.txt rule, or redirect. Fix the block and re-test.

Serving Tab

This shows how Google renders the page. Look for:

Page resources: Can Google load CSS, JavaScript, images? If resources fail to load, rendering might break.

Rendering issues: Did JavaScript execute correctly? Are there console errors? If the page uses heavy JavaScript, rendering might fail and hurt indexing.

Indexed content: What text did Google actually see? If it's blank or missing key content, JavaScript rendering failed.

If you see rendering errors, your page has JavaScript issues. Test with Google's Rich Results Test to see if structured data is breaking. Or simplify your JavaScript and use server-side rendering instead.

Step 4: Test the Live URL (Optional but Useful)

URL Inspection has a "Test live URL" button. This runs a fresh crawl and render of your page right now, without waiting for Google to naturally crawl it again.

Click "Test live URL".

Google crawls and renders the page. This takes 30-60 seconds.

You'll see a new set of results. This is what Google sees right now, not what it saw last time it crawled.

Use this when:

• You just published a new page and want to check if it's crawlable
• You fixed an indexing issue and want to verify the fix
• You changed the page content and want to see if Google can render it

The live test is useful for quick verification. It doesn't guarantee indexing—Google still needs to actually crawl and index the page in its normal crawl schedule. But it tells you if there are obvious blockers.

Step 5: Check Enhancements (Rich Results, AMP, Breadcrumbs)

Scroll down past the tabs. You'll see an "Enhancements" section if Google found any special features on your page.

Common enhancements:

Rich results: Did Google find structured data (schema markup)? Is it valid? If you have product reviews, FAQs, or recipes, structured data can earn rich result snippets in search.

AMP: If you have an AMP version of the page, does it validate? AMP errors can prevent indexing of the AMP version.

Mobile usability: Are there mobile issues? Viewport problems, clickable elements too close, text too small?

If an enhancement shows errors, fix them. Use Google's Rich Results Test to validate schema markup.

Enhancement errors don't usually block indexing, but they hurt ranking and click-through rate. Fix them if you want to compete.

Step 6: Request Indexing (If the Page Isn't Indexed)

If the status is "Discovered - not indexed" and you've fixed the blocking issue (removed noindex, fixed robots.txt, etc.), you can request indexing.

At the top right of the URL Inspection panel, click "Request indexing".

Google adds the page to its crawl queue. It doesn't guarantee immediate indexing, but it prioritizes the page for crawling.

Important: You get a limited quota for indexing requests. Google doesn't publish the exact number, but it's roughly 50-200 requests per day depending on your site's crawl budget. Read the indexing request guide for the full details and when to actually use this feature.

Don't spam indexing requests. Only request indexing for:

• New pages you just published
• Pages you fixed after they were blocked
• High-priority pages (homepage, top products, key landing pages)

For everything else, submit a sitemap and let Google crawl naturally.

Common Indexing Problems and How to Fix Them

URL Inspection shows you the problem. Here's how to fix the most common ones.

Problem 1: Discovered - Not Indexed (No Reason Given)

Google found the page but hasn't indexed it yet. This usually means:

Crawl budget issue: Google doesn't crawl your site often. If you have thousands of pages, Google prioritizes the important ones. Low-traffic pages might not get crawled.

Fix: Submit a sitemap to tell Google which pages matter. Link to the page from your homepage or a high-authority page to signal importance.

Page is new: If you published the page less than a week ago, Google might not have crawled it yet.

Fix: Request indexing. Wait 3-7 days. Check again.

Problem 2: Blocked by robots.txt

Your robots.txt file is blocking Google from crawling the page.

Fix: Open your robots.txt file. Find the rule blocking the page. Remove it or make it more specific. Here's the robots.txt template and guide.

Example:

If your robots.txt says:

User-agent: *
Disallow: /

It's blocking everything. Change it to:

User-agent: *
Disallow: /admin/
Disallow: /private/

Now Google can crawl everything except /admin/ and /private/.

After you fix robots.txt, request indexing again.

Problem 3: Noindex Meta Tag

Your page has a <meta name="robots" content="noindex"> tag. Google won't index it.

Fix: Remove the noindex tag from the page. Or use the correct tag if you want to allow indexing:

<meta name="robots" content="index, follow">

Or just delete the noindex tag entirely. If there's no robots meta tag, Google indexes by default.

After you remove it, request indexing.

Problem 4: Redirect Loop or Redirect Chain

The page redirects to another URL, which redirects to another, which redirects again. Google can't follow the chain.

Fix: Check your redirect rules. Make sure redirects are 301 (permanent) and point directly to the final destination, not to another redirect.

If you're migrating domains, follow the domain migration guide for proper 301 setup.

Problem 5: Rendering Issues / JavaScript Errors

Google crawled the page but couldn't render it properly. JavaScript failed or resources didn't load.

Fix: Check your browser console for errors. Make sure external CSS and JavaScript load correctly. Consider server-side rendering instead of client-side JavaScript.

Test the page with Google's Rich Results Test to see exactly what Google sees.

Problem 6: Duplicate Content

Google found a canonical tag pointing to a different URL. Google is indexing the canonical version instead.

Fix: This isn't always a problem. If you have multiple versions of the same content (www vs non-www, http vs https), canonical tags are correct. Read the canonical domain guide for the right setup.

If the canonical points to the wrong page, remove or fix it.

Using URL Inspection for Different Scenarios

Scenario 1: You Just Published a New Page

You shipped a new blog post, landing page, or product page. You want to make sure Google indexes it.

Step 1: Wait 24 hours for Google to discover it naturally (via sitemap or internal links).

Step 2: Open URL Inspection. Paste the URL.

Step 3: If it says "URL is on Google", you're done. It's indexed.

Step 4: If it says "Discovered - not indexed", click "Request indexing". Google will crawl it sooner.

Step 5: Wait 24-48 hours. Check again with URL Inspection.

Scenario 2: A Page Disappeared from Search Results

Your page was ranking. Now it's gone. Traffic dropped.

Step 1: Open URL Inspection. Paste the URL.

Step 2: Check the status. If it's still indexed, the problem is ranking, not indexing. Check your Performance Report to see if clicks and impressions dropped.

Step 3: If it's "Discovered - not indexed", something broke. Check the Index tab for the reason. Did you accidentally add a noindex tag? Did robots.txt change?

Step 4: Fix the issue. Request indexing.

Scenario 3: You Fixed a Broken Page and Want to Re-Index It

You had a 404 error, noindex tag, or robots.txt block. You fixed it. Now you want Google to re-crawl and re-index.

Step 1: Open URL Inspection. Paste the URL.

Step 2: Click "Test live URL". Google crawls the page right now. This shows you if your fix worked.

Step 3: Once the live test passes, click "Request indexing".

Step 4: Wait 24-48 hours. Check again.

Scenario 4: You're Auditing Your Top Pages

You want to make sure your most important pages are indexed and have no issues.

Step 1: Make a list of your top 10-20 pages (homepage, top products, main landing pages).

Step 2: For each page, open URL Inspection and paste the URL.

Step 3: Document the status. Note any errors or warnings.

Step 4: Fix issues in bulk. If multiple pages have the same problem (e.g., missing meta descriptions), fix the template or theme once.

Step 5: Request indexing for any pages that aren't indexed.

This 30-minute audit catches most of your indexing problems.

Pro Tips: Advanced URL Inspection Workflows

Tip 1: Check Canonicals Before Publishing

Before you publish a new page, use URL Inspection's live test to check if Google can crawl and render it. This catches rendering issues before they hurt your SEO.

Tip 2: Monitor Crawl Frequency

If the "Last crawl date" is weeks old, Google isn't visiting often. This means low crawl budget. Submit a sitemap to prioritize which pages Google should crawl.

Tip 3: Use URL Inspection to Debug Redirects

If you're setting up redirects for a domain migration, use URL Inspection to verify the redirect works. Test the old URL. Check that the canonical points to the new URL.

Tip 4: Test Mobile Rendering

URL Inspection shows how Google renders the page on desktop. But Google also crawls mobile versions. If your site has separate mobile URLs or responsive design, test both.

Tip 5: Batch Test With a Spreadsheet

For large audits, create a spreadsheet with URLs in one column. Use URL Inspection for each URL. Document the status in the next column. This gives you a clear audit trail and makes it easy to track fixes.

When URL Inspection Isn't the Right Tool

URL Inspection is perfect for single-page diagnosis. But it's not the right tool for everything.

Use URL Inspection for: Checking if a specific page is indexed, diagnosing why a single page isn't ranking, testing a new page before publishing, fixing indexing issues.

Don't use URL Inspection for: Auditing your entire site (use Coverage Issues instead), checking keyword rankings (use a rank tracker), analyzing traffic (use Performance Reports), bulk indexing requests (use a sitemap).

URL Inspection is for precision diagnosis. For site-wide health, use other GSC reports.

The Workflow: From Diagnosis to Fix to Verification

Here's the complete workflow that works:

1. Identify the problem: A page isn't showing up in search. You don't know why.

2. Inspect the URL: Open URL Inspection. Paste the URL. Check the status.

3. Read the diagnosis: Look at Crawl, Index, and Serving tabs. Find the blocker.

4. Fix it: Remove noindex. Fix robots.txt. Resolve redirect loops. Check the Coverage Issues guide for specific fixes.

5. Verify with live test: Click "Test live URL". Make sure your fix works.

6. Request indexing: Click "Request indexing" if the page was blocked.

7. Wait and check: After 24-48 hours, open URL Inspection again. Verify the status changed to "URL is on Google".

8. Monitor ranking: Use Performance Reports to track clicks and impressions. If the page is indexed but not ranking, the problem is keyword strategy or content quality, not indexing.

That's the full loop. Diagnosis → Fix → Verification → Monitoring.

Connecting URL Inspection to Broader SEO Strategy

URL Inspection is one tool in the larger SEO toolkit. It's part of a complete workflow:

Domain audit: Start with a full domain audit to understand your baseline. What pages are indexed? What's broken? What's missing?

Keyword strategy: Decide which pages should rank for which keywords. Use a keyword roadmap to prioritize.

Content creation: Publish content targeting those keywords.

Indexing verification: Use URL Inspection to verify each page is indexed.

Ranking monitoring: Use Performance Reports to track how each page ranks.

Optimization: If a page is indexed but not ranking, improve the content, links, or keyword targeting.

URL Inspection is the verification step. It ensures your content is discoverable before you spend time optimizing for ranking.

Key Takeaways

URL Inspection is a 30-second audit that saves you weeks of guessing.

Remember:

1. Access it: Search box at the top of Google Search Console.
2. Read the status: Green (indexed), yellow (indexed with issues), red (not indexed), gray (404).
3. Inspect the tabs: Crawl (can Google access it?), Index (did Google index it?), Serving (can Google render it?).
4. Test live: Click "Test live URL" to verify a fix works.
5. Request indexing: Only for new pages or fixed pages. Don't spam.
6. Fix and verify: Remove blockers, request indexing, check again after 24-48 hours.
7. Use it for diagnosis: Single-page problems. For site-wide audits, use Coverage Issues.

URL Inspection tells you immediately whether a page is visible to Google. Use it before you publish. Use it when ranking drops. Use it to verify fixes.

It's the fastest way to kill the guessing game and ship SEO that actually works.

Need a complete audit of your site's indexing health? Start with a full domain audit and brand positioning strategy to understand your baseline, then use URL Inspection to verify and fix individual pages. Most founders skip this step and wonder why their organic traffic stays flat. Don't be that founder. Inspect, fix, and ship.