Technical SEO Triage
Use this when
The user has crawl results, Search Console evidence, URL samples, rendering problems, or a suspected indexing issue.
Process
- Establish the symptom, affected templates or URLs, first-known date, and expected behavior.
- Gather evidence from representative URLs and distinguish site-wide issues from isolated examples.
- Check discovery, robots rules, status codes, redirects, canonicals, renderability, indexability, sitemaps, structured data, internal links, and performance only where relevant.
- Identify the most likely cause and list plausible alternatives when evidence is incomplete.
- Rank each finding as blocker, high, medium, or low based on reach and business impact.
- Define a fix owner and a verification step that can prove the issue is resolved.
Output
For every finding provide: evidence, affected scope, severity, likely cause, recommended fix, risk, owner, and verification.
Guardrails
Do not claim a crawl or index state without evidence. Avoid dumping generic audit checks that are unrelated to the reported symptom.
1---2name: technical-seo-triage3description: Turn crawl and indexing evidence into reproducible, severity-ranked technical findings.4---56# Technical SEO Triage78## Use this when910The user has crawl results, Search Console evidence, URL samples, rendering problems, or a suspected indexing issue.1112## Process13141. Establish the symptom, affected templates or URLs, first-known date, and expected behavior.152. Gather evidence from representative URLs and distinguish site-wide issues from isolated examples.163. Check discovery, robots rules, status codes, redirects, canonicals, renderability, indexability, sitemaps, structured data, internal links, and performance only where relevant.174. Identify the most likely cause and list plausible alternatives when evidence is incomplete.185. Rank each finding as blocker, high, medium, or low based on reach and business impact.196. Define a fix owner and a verification step that can prove the issue is resolved.2021## Output2223For every finding provide: evidence, affected scope, severity, likely cause, recommended fix, risk, owner, and verification.2425## Guardrails2627Do not claim a crawl or index state without evidence. Avoid dumping generic audit checks that are unrelated to the reported symptom.