Technical SEO Crawl Triage: Prioritized Fix Plan for the Next Sprint

Turn a crawl export and Search Console data into a scored, sprint-ready technical SEO fix list. It separates facts from assumptions and flags what needs verification before developers start work.

You get: Decision summary, issue table and sprint plan

More like this

The prompt

technical-seo-crawl-triage-prioritized-fix-plan-for-the-next-sprint.md
Role: You are a senior technical SEO consultant who writes tickets developers can act on.

Context: I must decide which technical SEO issues to fix in the next {sprint_length} for {site}. Business goal: {goal}. The decision this answer supports: which 5-10 fixes go into the sprint, which wait, and which need verification first.

Task: Triage the crawl and Search Console data I provide into a prioritized fix plan.

Constraints:
- Use only the data I provide. Do not invent traffic, rankings, crawl counts, or issues.
- Keep Facts (from my data), Assumptions, and Recommendations in separate sections.
- No guaranteed outcomes. Describe expected impact as low, medium, or high with reasoning.
- If you cannot open files, work from the pasted rows and do not extrapolate to the whole site without saying so.

Inputs:
- Site type and CMS: {site_type_cms}
- Crawl data (summary or pasted rows by issue type): {crawl_data}
- Search Console data (indexing, performance, Core Web Vitals notes): {gsc_data}
- Priority sections or templates: {priority_sections}
- Dev capacity per sprint: {dev_capacity}
- Known constraints (migrations, freezes, platform limits): {constraints}
Before any analysis, list missing inputs under Missing information. Then continue with clearly labeled assumptions.

Workflow:
1. Restate the job-to-be-done and the decision in two sentences.
2. Group issues by type: indexability, canonicals, status codes and redirects, internal linking, structured data, rendering, performance, duplicate or thin templates.
3. For each group, score Impact (1-5), Confidence (1-5), and Effort (1-5). Priority = (Impact x Confidence) / Effort. Show the reasoning in one line.
4. Mark items that need verification first, for example URL Inspection, server logs, or template review, and say what to check.
5. Build the sprint plan within {dev_capacity}, with owners by role and dependencies.

Tool-specific notes:
- ChatGPT with data analysis: count rows per issue type from the uploaded CSV before interpreting, and show the counts.
- Claude: read the data inside <crawl_data> and <gsc_data> tags, and quote the row patterns you rely on.
- Gemini or other chat tools: ask me for the top 50 rows per issue type if the data is too large.

Output format:
1. Decision summary (max 5 lines)
2. Missing information and assumptions (bulleted)
3. Issue table: Issue | Evidence from data | Affected template or URL pattern | Impact | Confidence | Effort | Priority | Verify first?
4. Sprint plan: ticket title, acceptance test, owner role, dependency
5. Deferred backlog with reasons
6. Risks (e.g., redirect chains after fix, noindex mistakes) and next 3 actions

Acceptance criteria:
- Every recommendation cites evidence from my inputs or is labeled as an assumption.
- The sprint plan fits {dev_capacity}.
- Each ticket has a testable done-condition.
- Items with low confidence are marked for verification, not scheduled as certain wins.

Quality checks:
- No invented numbers or URLs.
- Scores are consistent with the stated reasoning.
- Facts, assumptions, and recommendations are not mixed.
- Risks are specific to this site, not generic SEO advice.

Example output

AI-written example

1. Decision summary

  • Site: Ridgeline Outdoor Supply (Shopify). Sprint: 2 weeks, 12 dev-days. Goal: improve indexed product coverage before the autumn peak.
  • Schedule 4 fixes (10 dev-days). Two need a quick check first. Defer 2.
  • All counts come from pasted rows (up to 50 per issue type), not the whole site.

2. Missing information and assumptions

  • Missing: server logs, full crawl totals, CWV field data by template.
  • Fac
Generated from this prompt by AI. Your results will vary.

Tips and common edits

Paste real crawl rows (Screaming Frog, Sitebulb, or similar) and Search Console exports, not just summaries, for the strongest results. Re-run after fixes ship to compare. Treat Priority scores as a ranking aid and validate high-impact items in your own tools before committing dev time.

Questions about this prompt

More in SEO

AI Visibility Audit: Brand Mention and Citation Test Plan for AI Answer Engines

Design and analyze a repeatable prompt test set that checks how AI answer engines mention and cite your brand. It turns results into a citation table, evidence-based gap findings, and prioritized page and entity fixes.

AI Visibility Prompt Tracker List: 25 Buyer Prompts by Funnel Stage

Produces 25 realistic buyer prompts grouped by funnel stage, ready to run monthly to track whether AI assistants mention your brand.

Decaying Content Refresh Plan: Outdated Facts, Gaps and a New Intro

Audits an old article for outdated facts and missing subtopics, proposes new sections and rewrites the intro for your target keyword.

FAQ Block for Rich Results: 8 Customer Questions and FAQPage JSON-LD

Extracts 8 genuine customer questions with standalone answers from your page and outputs matching FAQPage JSON-LD.

GEO Page Audit: Citation Likelihood Score and Rewrites for AI Answers

Get a scored estimate of how citable your page is to ChatGPT, Gemini and Perplexity, plus a summary box, question headings, fact prompts and an FAQ.

Keyword List to Content Plan: Intent Groups, Page Types and Titles

Turns a raw keyword list into intent-based page groups, each with a recommended page type, title and build order.

Meta Title and Description Variants: 5 Click-Angle Pairs Within Limits

Writes 5 meta title and description pairs within character limits, each using a different angle to earn the click.

SERP-Based Content Brief with Search Intent Analysis for a Single Keyword

Create a writer-ready content brief from SERP observations you supply. It covers intent, required sections, evidence gaps, and a go or no-go call on whether the page is worth producing.

Topic Cluster Map: Pillar and Supporting Pages Ranked by Build Order

Build a topic cluster from a keyword list and existing content, then rank which cluster and pages to create first. It includes a keyword-to-page mapping table, internal link rules, and cannibalization risks.

Brain Dump to Weekly Plan with Top 3 Outcomes

Turns a messy brain dump into a realistic weekly plan with three outcomes, time blocks and a drop or delegate list.

SEO-Friendly Etsy or Gumroad Listing with 13 Tags and FAQ

Produces a complete Etsy or Gumroad listing for a digital or handmade product, with title, 13 tags, description, and FAQ.

UX Flow Audit from Screenshots with Prioritized Fix Plan

Audits a user flow from screenshots or descriptions and returns an evidence-labeled issue table plus a fix-now, next, defer plan for a sprint decision.