Search Console Triage (Coverage Issue to Action Plan)
This prompt analyzes Search Console patterns and converts them into a triage plan covering which pages to improve, merge, noindex, redirect, or leave alone. It is designed for messy real-world sites where not every issue deserves the same amount of work.
GPT / Claude / Gemini5 variables
Prompt
Analyze these Search Console issues and create a triage plan.
SITE TYPE: {SITE_TYPE}
MAIN PAGE TYPES: {PAGE_TYPES}
ISSUES OBSERVED: {SEARCH_CONSOLE_ISSUES}
SAMPLE URLS: {URL_EXAMPLES}
KNOWN CONTEXT: {CONTEXT}
Rules:
- Group by likely root cause
- Prioritize business value and page quality
- Distinguish improve vs merge vs noindex vs ignore
- Focus on practical actions, not generic SEO advice
Output format:
1) Core diagnosis
2) Issue categories
3) URL groups and recommended action
4) Template-level fixes
5) Reindexing priority list
6) 14-day action planQuick brief
Purpose
Turn Search Console coverage and performance problems into prioritized actions instead of vague SEO anxiety.
Expected output
A triage plan containing: issue categories, likely causes, which pages to improve versus prune, what templates need attention, what should be submitted for reindexing, and a practical order of operations.
Customize before copying
Replace these placeholders with your own context before you run the prompt.
{SITE_TYPE}{PAGE_TYPES}{SEARCH_CONSOLE_ISSUES}{URL_EXAMPLES}{CONTEXT}
Works well with
GPT
Claude
Gemini
Variations
Make the plan specific for an AI tools directory.
Add a section for tag and taxonomy pages.
Focus only on coverage issues, not performance.
Focus only on the highest-impact 20 percent of URLs.
How to get better results
Fill in the placeholders with specifics instead of generic labels.
Tell the model what a strong answer looks like before you ask for the output.
After the first run, paste the response back in and ask for one focused revision.
What this prompt helps you do
This prompt analyzes Search Console patterns and converts them into a triage plan covering which pages to improve, merge, noindex, redirect, or leave alone. It is designed for messy real-world sites where not every issue deserves the same amount of work.
When to use it
Use this when Search Console shows coverage issues like Crawled - currently not indexed, when clicks are flat despite impressions, when indexing changes after a content migration, or when you need to prioritize SEO tasks for limited time.
Decision context
Search Console reports are signals, not instructions. Some pages should be improved, others should be merged, and some should never have been indexed in the first place. This prompt helps separate high-value opportunities from low-value cleanup.
How it works
The prompt groups pages by likely root cause, such as thin content, duplicate intent, weak internal links, stale content, or low search value. It then assigns an action type and priority so you can move through the backlog systematically instead of randomly.
Best practices
Provide examples of affected URLs, page type, impressions, clicks, and a short note on content quality. Ask for actions grouped by impact and effort. Use the output to drive batches of fixes rather than reacting to each URL one by one.
Common mistakes
Trying to force every page into the index. Treating all coverage issues as technical. Spending hours on pages with no real value. Ignoring internal linking and site structure. Looking only at affected URLs without grouping them by template or type.
What you should expect back
A triage plan containing: issue categories, likely causes, which pages to improve versus prune, what templates need attention, what should be submitted for reindexing, and a practical order of operations.
Limitations
The prompt cannot see the live site or SERP by itself. It depends on the quality of the examples and notes you provide. Final decisions still need judgment about business value and content quality.
Model notes
Works well with all major models. Best results come when you include Search Console notes, sample URLs, and a short explanation of what each page type is trying to do.
Real-world applications
Solo site owners use this to prioritize cleanup. Agencies use it to turn audit data into a plan. Editorial teams use it after publishing sprints to understand what templates are underperforming. Product content sites use it to decide whether thin taxonomy pages should remain indexable.
How to tell if it worked
Successful triage means fewer low-value URLs competing for crawl budget, clearer page priorities, and a sharper roadmap for improving the pages that actually matter. You should end up with fewer random SEO tasks and more template-level fixes.
Where to go next
Use SEO Content Refresh Brief for the pages marked improve. Pair with Topical Authority Cluster Planner when the issue is weak site structure rather than isolated pages. Follow with redirect planning for pages marked merge or remove.
Related prompts
Product Review Brief (Balanced + Credible)
Write reviews that don't sound like paid ads.
Landing Page Copy Audit (Fix Confusing Text)
Improve website copy so users understand it in 5 seconds instead of leaving.
SEO Content Refresh Brief (Traffic Decay to Update Plan)
Turn aging pages into clear refresh plans that improve usefulness, depth, and ranking potential.
Topical Authority Cluster Planner (Pillar + Support Pages)
Turn a broad topic into a practical cluster strategy with pillar pages, support content, and internal-link logic.