Triage Discovered / Crawled — Not Indexed URLs by template
Group unindexed URLs by directory and reason, then propose a fix per group instead of per URL.
The prompt
Copy this and paste it into Claude, Cursor, or any AI client connected to your GenieSeo MCP URL.
For my main Search Console property, run a full indexing triage:
1. Pull every URL currently in any "not indexed" state. Group by reason (Discovered – not indexed, Crawled – not indexed, Page with redirect, Duplicate, Excluded by noindex, Soft 404, Blocked by robots, Server error).
2. Within each reason, group URLs by their second-level path segment (e.g., /blog/, /products/). Show counts.
3. Pick ONE representative URL per group and run URL Inspection. Report: indexability verdict, canonical, robots directives, last crawl, mobile usability.
4. For each group with ≥10 URLs, write a Jira-ready ticket: title, severity (P1 ≥500 URLs, P2 ≥100 URLs, P3 otherwise), description with reproduction steps, suggested fix.
Output: one section per group, table summary at the top.When to use it
Whenever the Search Console Pages report shows a spike in 'Discovered – not indexed' or 'Crawled – not indexed'. Always start with grouping; never triage URL-by-URL.
What you get back
- Table of unindexed URLs grouped by second-level path segment and reason, with counts.
- Spot-inspection of one representative URL per group (indexability, canonical, robots, mobile usability).
- Jira-ready ticket per group: title, severity (P1/P2/P3 by URL volume), one-line fix.
How this runs
GenieSeo doesn't execute prompts — your AI client does. Make sure your MCP URL is connected to Claude, Cursor, Codex, or Antigravity. New here? Read the 60-second setup guide.
Tags
- indexing
- triage
- templates
Frequently asked questions
How do I run the "Triage Discovered / Crawled — Not Indexed URLs by template" prompt?+
Sign up for GenieSeo, connect Google OAuth, paste your MCP URL into Claude or Cursor, then copy the prompt from this page into a new chat. The model will call the relevant Search Console or GA4 tools automatically.
Does this recipe change my Google data?+
No. This recipe only uses read-only Search Console and GA4 scopes. It will not submit sitemaps or modify properties unless you use a separate write-enabled recipe.
What is a GenieSeo recipe?+
A recipe is a copy-paste prompt you run inside Claude, Cursor, or Codex after connecting your GenieSeo MCP URL. It tells the model which Search Console or GA4 tools to call and how to format the answer.
Do I need GenieSeo connected before using a recipe?+
Yes. Sign up at GenieSeo, approve Google OAuth, paste your personal MCP URL into your AI client, then paste the recipe prompt. Without MCP, the model cannot reach live Google data.