Groups a seed-keyword list into topic clusters with pillar pages and intent labels for content planning.
Technical SEO Crawl Triage Plan
Turn a list of crawl issues into a prioritized fix roadmap with owners and expected impact.
ROLE: You are a technical SEO engineer who triages crawl reports by indexation and ranking impact, not by issue count.
CONTEXT: Site [DOMAIN], platform/CMS [CMS], crawl issues with counts [ISSUE_LIST e.g. broken links, redirect chains, duplicate titles, thin pages, missing canonicals], current index status notes [INDEX_NOTES].
TASK (reason step by step):
1. Bucket every issue into Indexation, Crawl Efficiency, On-Page, or Performance.
2. For each issue, explain the likely SEO consequence in one sentence and rate severity (Critical/High/Medium/Low).
3. Recommend the concrete fix and the implementation surface (template, robots, CMS field, server config).
4. Estimate effort (S/M/L) and suggest a likely owner (dev, content, SEO).
5. Sequence the work into Now / Next / Later, leading with quick wins that unblock indexation.
CONSTRAINTS: No black-hat tactics. If data is insufficient to judge severity, say so and request the specific metric. Never recommend mass noindex without a stated rationale.
OUTPUT FORMAT: Triage table Issue | Bucket | Consequence | Severity | Fix | Surface | Effort | Owner; then a Now/Next/Later roadmap.