Playbook: Triage the GSC Page Indexing report in priority order
The report dumps 15 statuses. Here's the sequence that finds real problems fastest.
Setup:
— Open Why pages aren't indexed, sort by affected count
— Triage in THIS order:
— Server error (5xx) and Redirect error first (technical, you broke something)
— Blocked by robots.txt next (check if intentional)
— Excluded by noindex tag (verify it's deliberate)
— Duplicate without user-selected canonical (consolidation needed)
— SKIP Crawled/Discovered - not indexed last (quality, not a bug)
What it does well: groups by cause and gives sample URLs + a validate button per group. Free.
Where it falls short: counts lag 2-4 days, samples cap at ~1,000 URLs so big issues are under-sampled, and 'quality' buckets give no specifics.
Pros:
— Cause-grouped, batchable
— Validate-fix built in
Cons:
— 2-4 day data lag
— Sample caps hide scale
Best for: monthly indexation health checks. NOT for real-time debugging of a single URL.
Index or Bust
@IndexOrBust
Playbook: Triage the GSC Page Indexing report in priority order
Этот пост опубликован в Telegram-канале Index or Bust. Подписаться можно по ссылке: @IndexOrBust.