seo-site-health-auditlisted

# SEO Site Health Audit Triage technical SEO findings from Ahrefs Site Audit (or any equivalent crawler) by impact on rankings and traffic, not by raw issue count or severity label. Stack-agnostic. Produces a prioritized backlog of fixes mapped to business impact. --- ## When to use - After running an Ahrefs Site Audit or other site-wide crawl - Reviewing a long list of technical issues and needing to prioritize - Scoping a technical SEO sprint - Pre-launch or post-migration technical verification - Quarterly technical health check - When developer time is limited and you must pick the highest-leverage fixes ## When NOT to use - Running the crawl itself (use the crawler tool directly) - Diagnosing specific traffic drops (use `seo-traffic-diagnosis`) - Single-page audits (use `seo-onpage`) - Pure technical strategy or schema design (use `seo-technical`) --- ## Required inputs - Crawl results from Ahrefs Site Audit (or equivalent) - Search Console coverage and Core Web Vitals data - Property's organic traffic profile (which pages drive traffic) - Stakeholder time and developer capacity available - Confirmation Ahrefs MCP is connected --- ## The framework: triage by SEO impact, not severity Crawlers label issues "critical", "warning", "notice". These labels are useful but not sufficient. Two issues both labeled "critical" can have wildly different actual impact on the property. Triage on three axes. ### Axis 1: Page-level traffic impact Does the issue affect a pag