Loading tutorials…
Loading tutorials…
URL Inspection is the most-misused tool in GSC. People use it on the wrong URLs, hit the daily quota, and wonder why nothing gets indexed. Here's the correct workflow — and when to use it vs trust the sitemap.
Who this is forSite owners launching new pages, updating high-priority content, or recovering from accidental noindex. Not a daily-use tool — used selectively for high-priority URLs.
What you'll need
Step 1
Use it for: new high-priority pages, content updates on top pages, and recovery from accidental noindex. Not for: bulk indexing or routine new content.
Good use cases: launched a new pillar page, updated a top-ranking page with new content, recovered a page from accidental noindex, fixed a Soft 404 error.
Bad use cases: routine blog posts (let sitemap handle), every product page in a 10K-product catalog (use sitemap + IndexNow), pages that haven't changed (Google has nothing new to see).
Daily quota: ~10 URL submissions/day per property. Burning quota on routine pages means you can't push priority URLs when needed.
Mental model: URL Inspection is for "please look again now," not "please discover this for the first time." Sitemap handles discovery; URL Inspection handles re-evaluation.
Step 2
The URL Inspection bar is at the top of every GSC page. Paste the full URL.
In GSC, the URL Inspection bar is at the very top — "Inspect any URL in [property]."
Paste the full URL including https:// — e.g., https://yoursite.com/blog/your-post.
The URL must be within the property you've opened. Cross-property URLs return errors.
Press Enter or click search. GSC fetches Google's current index info for that URL.
Step 3
Four key facts: indexing status, mobile usability, page experience, last crawl date.
"URL is on Google" — indexed. Good. Click "Test live URL" if you want to see what Google currently sees.
"URL is on Google, but has issues" — indexed but with mobile usability, structured data, or other issues. Click into each issue.
"URL is not on Google" — not indexed. Look at the "Discovery" and "Crawl" sections for why.
"Excluded" reasons: most common are noindex tag, robots.txt block, canonical points elsewhere, soft 404, Crawled-not-indexed, Discovered-not-indexed.
Note the "Last crawl" date — if it's months old, Google hasn't re-crawled despite changes. That's when Request Indexing makes sense.
Step 4
Compare what Google has indexed against what's currently live. If they're the same, indexing won't change anything.
Click "Test live URL" in the top right.
GSC fetches the page in real-time as Googlebot would.
If the live test shows the same status as the indexed version, requesting indexing won't help — there's no new info for Google to evaluate.
If the live test shows different content (e.g., you fixed the noindex tag), requesting indexing will trigger a re-crawl.
Live test also surfaces: rendered HTML, page resources blocked, screenshot of how Google sees the page.
Step 5
The actual submission. Takes about 60 seconds to process.
In the URL Inspection results, click "Request Indexing."
GSC runs a quick crawl to confirm the page is fetchable. Takes 30-60 seconds.
If successful: "Indexing requested." The URL enters a priority crawl queue.
Timeline: high-authority sites see indexing in hours. Lower-authority sites in 1-7 days. Sometimes never — Request Indexing is not a guarantee.
Daily quota: roughly 10 submissions per day per property. Hitting the quota gives a "quota exceeded" message; wait 24 hours.
Step 6
URL Inspection is for one-off URLs. Bulk needs different tooling.
IndexNow is a free protocol supported by Bing, Yandex, and indirectly some Google signals. Submits URLs in bulk via a simple API call.
Most CMSs have an IndexNow plugin (RankMath, Yoast Premium, IndexNow Plugin for WordPress).
For Google specifically: rely on sitemap + good internal linking. New URLs linked from high-authority pages get crawled within days.
If you have 1,000+ new URLs (e.g., a new product category launch), submit a fresh sitemap rather than 1,000 individual URL Inspections.
Don't try to game URL Inspection quota by switching between properties — Google catches this and devalues your indexing requests.
Step 7
Don't re-request indexing if the first one didn't work in 24 hours. Google decides; persistence doesn't change the decision.
Wait at least 7 days before re-inspecting. If GSC still shows "Crawled - currently not indexed," the issue isn't request quantity — it's content quality or crawl budget.
Re-requesting the same URL daily doesn't change the outcome. It just burns your quota.
If the page is still not indexed after 14 days: check for noindex, canonical issues, content quality. Fix the underlying issue.
Once indexed: confirm in URL Inspection (status = URL is on Google) and check that it appears for at least one site:yoursite.com/your-url search.
Common mistakes
Using Request Indexing on every new blog post
What goes wrong: You burn the daily quota on routine new content. When a major launch happens, you can't push your priority URLs. The blog posts would have been indexed via sitemap anyway in 3-7 days — no acceleration gained.
How to avoid: Trust sitemap + internal linking for routine new content. Save URL Inspection for top-priority launches and re-indexing of updated pages.
Requesting indexing without checking blockers
What goes wrong: The page has a noindex tag, blocked robots.txt, or broken canonical. Request Indexing succeeds (Google fetches), but the page still isn't indexed because of the underlying block. You think the tool is broken; the page is broken.
How to avoid: Always run "Test live URL" first. Read the Coverage / Indexing section. Fix any blockers BEFORE requesting indexing.
Re-requesting the same URL multiple times
What goes wrong: Wastes daily quota. Doesn't change Google's evaluation. Sometimes causes Google to deprioritize the URL because repeat requests look like spam signals.
How to avoid: Request once, wait 7 days, evaluate. If not indexed, fix underlying issues — don't just resubmit.
Submitting URLs from a different property
What goes wrong: You try to inspect a URL outside the property scope. Returns an error or inspects in the wrong property. Confusion follows.
How to avoid: Confirm you're in the right property before inspecting. Domain property covers all subdomains; URL-prefix property covers only one URL pattern.
Expecting Request Indexing to fix Crawled-not-indexed
What goes wrong: Google already decided this URL isn't worth indexing. Re-requesting doesn't change that decision. You waste hours believing the tool will eventually "work."
How to avoid: Crawled-not-indexed is a content-quality verdict. Improve the page substantially (content, internal links, E-E-A-T signals) before re-requesting.
Recap
Done — what's next
How to submit a sitemap to Google Search Console (and keep it healthy)
Read the next tutorial
Hand it off
Indexing strategy for a 100-page site is one workflow. Indexing strategy for a 10K-page ecommerce store with daily new SKUs is a different beast — requires sitemap segmentation, IndexNow integration, and ongoing monitoring. A technical SEO specialist runs this for $400-800/mo at $14-16/hr.
See specialist rates
On high-authority sites: hours to a day. On smaller sites: 1-7 days. Sometimes never — Google decides. If you've waited 7+ days without indexing, the issue isn't speed, it's a structural reason Google chose not to index.
Per property. If you own multiple properties, you have separate quotas for each. Don't try to abuse this with split properties — Google tracks patterns and downweights the property.
Sitemap is for ongoing discovery — Google crawls it on its own schedule. Request Indexing is a one-off priority signal — "look at this specific URL now." Both can exist for the same URL.
Three usual causes: (1) the URL is blocked (noindex, robots.txt, canonical points elsewhere); (2) Google evaluated and decided it's not worth indexing; (3) you've hit your daily quota and the request silently failed.
Don't try. Google rate-limits per property and detects automation patterns. For bulk: use sitemap with frequent updates, IndexNow protocol for instant pings, and good internal linking from high-authority pages.
Google Search Console
Submitting a sitemap is one click. Submitting the right sitemap, in the right format, with the right URLs is what separates indexed sites from invisible ones. Here's how to get this right and how to diagnose the most common errors.
Google Search Console
GSC's Indexing report shows you what's broken — in language that often hides what to actually do about it. This is the field-tested decoder: every error type, what causes it, and the specific fix that works.
Google Search Console
Most owners pick the wrong property type on day one and spend the next year staring at split data. Here's the setup the way SEO specialists actually do it — including the domain-property workflow that captures every subdomain and protocol.
Google Search Console
DIY SEO works longer than DIY ads — you can run on momentum for 12+ months. But there's a point where you're losing more in opportunity than you'd pay a specialist. Here's how to tell which side you're on.