GSC URL Inspection or Page Indexing: Which Check?
URL Inspection diagnoses one address; the Page indexing report shows sitewide indexing buckets. Pick the right Search Console check before you request indexing again.
A single post refuses to show as indexed, so you hammer Request indexing. Meanwhile the Page indexing report shows hundreds of URLs in mixed buckets. Those are different instruments. URL Inspection answers questions about one URL. Page indexing answers questions about the site’s indexing health in aggregate.
This page is a check router. It is not URL Inspection before request indexing (the inspect-then-request workflow). It is not Page indexing report basics. It is not Page indexing vs Sitemaps. It is not a canonical clone.
Early owners:
- URL Inspection before request indexing
- GSC Page indexing report basics
- GSC Page indexing vs Sitemaps
- Why Google isn’t indexing your pages
One URL mystery or post-publish verify → URL Inspection. Sitewide patterns and reason codes → Page indexing. Then fix causes—don’t spam requests.
Official (confirm live): Inspect a URL in Search Console · Page indexing report · Performance report overview (traffic—not indexing).
Table of contents
- Scale of the question
- What URL Inspection is for
- What Page indexing is for
- A practical order for small blogs
- When both tools disagree
- Scenario: ten new posts, one stuck
- Mistakes that waste crawl budget attention
- FAQ
- Choose one check, then fix
Microscope versus ledger
| Tool | Scope | Typical output |
|---|---|---|
| Page indexing | Property-wide buckets | Counts by reason: indexed, crawled not indexed, blocked, not found |
| URL Inspection | One pasted URL | Live test: fetch, indexability, canonical, enhancements where shown |
Page indexing tells you which problem class grew. Inspection tells you whether this exact URL still carries that problem after your fix.
Mechanism: Google aggregates known URLs into buckets on a schedule; Inspection fetches now (subject to quotas) and returns current signals. Aggregates lag; live tests cost attention. Using only one tool wastes either pattern recognition or proof.
Scale of the question
Ask: “Is this about one address I can paste, or about the whole property?” Pasteable address → Inspection. Whole property → Page indexing first, then sample URLs with Inspection.
If I were debugging a client property, I would forbid mass “Request indexing” until Page indexing reasons were read once.
What URL Inspection is for
- Live index status and last crawl clues for a URL you care about
- Checking whether Google can fetch the page
- Requesting indexing after you understand the result (see the inspect-before-request owner)
Inspection will not list every soft-404 on the site.
What Page indexing is for
- Counts of indexed vs not indexed
- Reason groupings and example URLs
- Spotting template-level problems (noindex, soft 404, crawled–not indexed patterns)
Read Page indexing basics before you redesign the site from one scary chart.
A practical order for small blogs
| Situation | First check |
|---|---|
| Just published an important URL | URL Inspection |
| Sudden drop in indexed pages | Page indexing |
| Sitemap confusion | Page indexing vs Sitemaps router |
| Chronic “nothing ranks” | Why Google isn’t indexing + Page indexing |
When both tools disagree
Inspection can show a URL indexed while Page indexing still updates slowly, or examples can lag. Re-check after a day or two; prefer fixes over panic. Dotted recent Performance days are unrelated—do not confuse Performance lag with indexing tools.
Scenario: ten new posts, one stuck
Nine posts appear under Indexed examples over time; one money URL shows “URL is not on Google” with a clear blockage. Open Inspection on that URL, fix the template issue (noindex, login wall, canonical to elsewhere), re-inspect, then request if appropriate. Do not request indexing on all ten blindly.
Scenario: migration week
After a host move, Page indexing shows not found (404) or redirect error buckets climbing—a ledger signal that many URLs misrouted.
Wrong response: Inspect the homepage repeatedly without fixing maps.
Better response: Export example URLs from the spike bucket, repair redirects and internal links, run Inspection on one old and one new URL to confirm 200 responses and sensible canonicals, then watch bucket counts fall over crawl cycles. Deeper recovery paths live on why Google isn’t indexing your pages when redirects are messy.
Small-blog loop using both tools
- Page indexing: note the top not indexed reason by business importance, not only raw count.
- Sample: open example URLs; discard intentional exclusions (deliberate noindex, deleted posts).
- Inspection: paste the money URL; read indexability and canonical lines per Inspect help.
- Fix once at template level when the sample shows a class bug.
- Re-inspect the same URL; expect bucket trends to move over days, not minutes.
- Performance only after important URLs are indexed for sensible reasons.
Mistakes that waste crawl budget attention
- Requesting indexing as a daily ritual without reading Inspection results.
- Ignoring Page indexing reason codes while rewriting titles.
- Treating this as another canonical essay—canonical waste queries are a different trap (Step 2h discipline).
FAQ
Frontmatter covers schema Q&A for this router.
Choose one check, then fix
URL Inspection for the address in your clipboard. Page indexing for property-wide buckets. Workflow detail → inspect before request. Report literacy → Page indexing basics. Confirm live Search Console docs when UI labels change.
Keep learning
More guides in the same topic lane.
Word to PPTX or Compress Word: Which Job?
Turn a Word doc into slides or shrink the DOCX for email? Route Word to PPTX versus Compress Word by deliverable format versus attachment size.
Split PDF or PDF to Word: Which Job?
Page ranges as separate PDFs or an editable Word file? Route Split PDF versus PDF to Word by what the client must open and change—not by habit.
Merge Word or Word to Excel: Which Job?
Stack several DOCX files into one document or turn one Word file into a spreadsheet? Pick Merge Word versus Word to Excel from file count and the next app.