Skip to main content
skill CX Codex

seo-site-health-audit — Claude Code skill

The seo-site-health-audit skill reranks crawler results (Ahrefs, similar tools) by actual impact on rankings instead of issue count. It helps you decide which technical fixes to tackle first when dev time is limited.

MIT 291 installs ★ 1,107 updated 2026-10-19

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add rampstackco/claude-skills --skill seo-site-health-audit -a claude-code
Open on GitHub

What seo-site-health-audit does

After running a site-wide crawl, you face hundreds of issues labeled "critical" or "warning". But a critical error on a page with zero traffic often matters less than a warning on a top traffic page. The skill prioritises along three axes: organic traffic on affected pages (Tier 1–3), the actual ranking mechanism (HIGH, MEDIUM, LOW severity), and fix effort (S, M, L). Output is a priority matrix with four levels—P0 for urgent, P3 for routine maintenance, Park for deferral.

It includes a reference that pre-grades every issue type: indexability, crawlability, Core Web Vitals, structured data, links, hreflang and others. The skill hunts for high-leverage clusters—chains of redirects, accidental noindex on a template, stale sitemap pipeline. One code change often resolves thousands of related issues at once.

You get a ranked backlog with effort estimates, fix descriptions and success metrics. Fits quarterly health audits, pre-launch checks and post-migration verification.

What it helps with

  • choose which technical issues to fix first from hundreds of findings
  • measure actual organic traffic impact on affected pages
  • identify fixes with outsized ranking impact
  • group similar fixes to ship in one sprint
  • build a technical backlog ranked by business value

Example prompts for the agent

  • Here's our Ahrefs Site Audit report. How do I prioritize these issues by ranking impact?
  • We have 400 redirect chain errors. Which ones move traffic most and which should we fix first?
  • Post-migration crawl just finished. Build a dev backlog—what's critical vs. what can wait.

How to install seo-site-health-audit

1Skills CLI (Vercel)

npx skills add rampstackco/claude-skills --skill seo-site-health-audit -a claude-code

2Manually: put the files in place

~/.claude/skills/seo-site-health-audit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/seo-site-health-audit/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about seo-site-health-audit

How do I install seo-site-health-audit in Claude Code?

Run npx skills add rampstackco/claude-skills --skill seo-site-health-audit -a claude-code. Then open ~/.claude/skills/seo-site-health-audit/SKILL.md to configure.

What does seo-site-health-audit do?

The skill takes crawler output (Ahrefs Site Audit, Screaming Frog or equivalent), combines it with traffic data, and ranks technical issues across three dimensions: which pages are affected, how much each issue moves rankings, and fix effort. Result is a prioritized backlog for your dev team.

What inputs does it need?

Crawl results from a site auditor, Search Console coverage data, Core Web Vitals, your organic traffic profile, and dev capacity. If you connect the Ahrefs MCP, it can pull the crawl directly; otherwise, supply an export from any equivalent crawler.

Source text

SKILL.md · MIT
---
name: seo-site-health-audit
description: "Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity. Use this skill when reviewing crawl results, prioritizing technical fixes, scoping a technical SEO sprint, or after running any site-wide crawl. Triggers on site audit results, technical fix list, crawl errors, technical SEO triage, prioritize technical issues, what should we fix first, broken links, redirect chains. Also triggers when a long list of crawler issues is creating decision paralysis."
category: seo-audit-suite
catalog_summary: "Triage Ahrefs Site Audit findings by SEO impact, not severity"
display_order: 6
---

# 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, only when the crawl is being pulled through Ahrefs. A supplied export from any equivalent crawler satisfies the first input on its own.

---

## 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 page that drives meaningful organic traffic, or one that does not?

A "critical" issue on a tag archive with zero traffic is lower priority than a "warning" on a top-10-traffic landing page.

Tier the affected URLs:

- **Tier 1:** Top 10% of pages by organic traffic
- **Tier 2:** Pages that rank but do not yet drive significant traffic (page 2-3 results)
- **Tier 3:** Pages that exist but do not rank meaningfully

A fix on Tier 1 is worth 10x a fix on Tier 3 in most cases.

### Axis 2: Mechanism of impact

Does the issue actually move rankings or traffic? Some "critical" issues are aesthetic or theoretical.

Grade every issue HIGH, MEDIUM, or LOW. [`references/issue-impact-table.md`](references/issue-impact-table.md) owns the grade for each issue type and the definition of each grade. Look the issue up there instead of judging it fresh, and use the grade it gives.

The issue families the reference covers, in lookup order: indexability, crawlability, renderability, Core Web Vitals, structured data, internal link integrity, hreflang, on-page elements, images, security and trust. It also carries a park-or-skip list for the findings that rarely deserve dedicated work.

Grades vary inside a family. Indexability rows are mostly HIGH; internal link integrity runs MEDIUM down to LOW row by row. Grade by row, never by family.

Fix HIGH-grade issues on Tier 1 URLs first.

### Axis 3: Effort

Some issues are 5-minute fixes. Some are multi-sprint projects.

- **S (small):** Configuration change, single template edit, sitemap regeneration
- **M (medium):** Theme or component change, redirect map work, template-level fixes
- **L (large):** Architecture change, re-platform, framework migration, schema overhaul

---

## The triage matrix

Combine the three axes into a priority score.

Mechanism here is the HIGH / MEDIUM / LOW grade the issue-impact table gives the issue. All three grades have rows: the reference grades a large share of its issue types MEDIUM, and a MEDIUM issue on a Tier 1 page still needs a band.

| Tier | Mechanism | Effort | Priority |
| --- | --- | --- | --- |
| Tier 1 | HIGH | S | P0 (do this week) |
| Tier 1 | HIGH | M | P1 (do this sprint) |
| Tier 1 | HIGH | L | P2 (plan as project) |
| Tier 1 | MEDIUM | S | P1 |
| Tier 1 | MEDIUM | M | P2 |
| Tier 1 | MEDIUM | L | P3 |
| Tier 1 | LOW | S | P3 (batch when convenient) |
| Tier 1 | LOW | M-L | Park unless evidence emerges |
| Tier 2 | HIGH | S | P1 |
| Tier 2 | HIGH | M-L | P2 |
| Tier 2 | MEDIUM | S | P2 |
| Tier 2 | MEDIUM | M-L | P3 |
| Tier 3 | HIGH | S | P3 |
| Tier 3 | Anything else | Anything | Park |

The MEDIUM rows follow one rule: a MEDIUM issue sits one band below the HIGH issue at the same tier and effort. Rows the reference grades LOW-MEDIUM take the MEDIUM row when the URL is Tier 1 and the LOW row otherwise.

P0-P1 work earns the team's attention. P2 goes on the roadmap. P3 batches into routine maintenance. Park is honest about deprioritization.

---

## Workflow

1. **Pull the crawl results.** Ahrefs Site Audit + Search Console + Core Web Vitals.
2. **Tier the URLs.** Use organic traffic data. Tag every affected URL as Tier 1, 2, or 3.
3. **Categorize each issue by mechanism.** Look up the HIGH, MEDIUM, or LOW grade in `references/issue-impact-table.md`.
4. **Estimate effort per fix type.** Group similar fixes into one effort estimate.
5. **Apply the triage matrix.** Assign P0-P3 or Park.
6. **Cluster the fixes.** Group fixes that share an effort: one template change can resolve hundreds of issues.
7. **Build the backlog.** P0 first, P1 next, etc. Add fix descriptions, owners, expected impact.
8. **Add measurement.** What metric will confirm the fix worked? Define before shipping.
9. **Hand off.** Output feeds the development backlog and `seo-audit-orchestration`.
10. **Re-crawl after fixes.** Confirm resolution. Update the backlog.

---

## High-leverage clusters worth looking for

These patterns commonly produce outsized impact when fixed:

- **Wholesale redirect chain cleanup.** One sitemap update plus internal link updates can resolve thousands of "redirect chain" issues at once.
- **Accidental noindex on a template.** A single line of code change can re-index hundreds or thousands of pages.
- **Sitemap freshness pipeline.** A broken sitemap regeneration job affects every issue that depends on Search Console seeing the right URLs.
- **Canonical inconsistencies on faceted navigation.** A template-level canonical fix can resolve duplicate content issues across an entire ecommerce category tree.
- **Robots.txt restored.** A reverted production robots.txt can recover a sitewide drop in days.
- **Hreflang block fix.** One template change resolves hreflang issues across the whole multilingual site.
- **Image optimization at the asset pipeline.** Fixing the build process resolves thousands of individual asset issues.

When you spot one of these, prioritize even if individual issues look small. The cluster impact is large.

---

## Failure patterns

- **Severity worship.** Treating every "critical" label as truly critical. Many are not. Triage by mechanism and traffic impact.
- **Counting issues.** Reporting "we fixed 1,200 issues" without showing traffic or ranking impact wastes engineering credibility.
- **Skipping the tiering.** Fixing 100 Tier-3 issues before 5 Tier-1 issues is busy work.
- **Single-issue fixes.** Most issues come in clusters. Fixing one redirect chain when 800 share the same root cause is the wrong unit of work.
- **No re-crawl.** "Fixed" without verification leaves doubt. Always re-crawl after major fixes.
- **Ignoring Search Console.** Ahrefs sees what its crawler finds. Search Console reflects what Google actually sees and indexes. Use both.
- **Treating Core Web Vitals like a checklist.** CWV is field data, not lab data. Optimize for real-user experience, not synthetic scores.
- **Fixing low-mechanism issues for show.** A clean technical report with no traffic gain helps no one.
- **Not measuring.** Define the metric that proves the fix worked before fixing.

---

## Output format

A site health triage document with:

1. **Summary.** Total issues, top 3 fix clusters, expected impact, or state the gap per the data-availability rule.
2. **URL tiering.** How URLs were classified and counts per tier.
3. **Issue categorization.** Counts by mechanism category, by tier, by priority band.
4. **Prioritized backlog.** P0-P3 ordered. Each item has: issue, affected URLs, fix description, effort, expected impact, owner.
5. **Fix clusters.** Groups of issues that share a fix. Highest leverage at the top.
6. **Measurement plan.** Per fix or cluster, what proves it worked.
7. **Methodology.** Crawler used, date, scope, caveats.

Length: 5-12 pages plus a backlog spreadsheet.

---

## If required data is unavailable

This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.

---

## Reference files

- [`references/issue-impact-table.md`](references/issue-impact-table.md) - Mapping table of common crawler issues to mechanism grade and typical fix effort, plus cluster signals and the park-or-skip list. This file is the source of truth for every issue grade; the triage matrix above turns a grade plus a tier plus an effort into a priority band.

© rampstackco · MIT · rampstackco/claude-skills

Similar skills

All skills for SEO and GEO →
site-audit James Dickerson (@boringmarketer) The site-audit skill for Claude Code performs a technical SEO check of a website. It identifies indexation issues, crawler accessibility problems, and broken links. CX Codex +1 ★ 778repo stars seo-audit sickn33 seo-audit audits your site for indexation problems, performance issues, mobile readiness, and content gaps. Identifies what blocks organic visibility and helps prioritize fixes. CX Codex +1 1,000installs SEO Web Analysis MCP — Site Audit & Tech Stack nexgendata-apify SEO Web Analysis MCP — Site Audit & Tech Stack is an MCP server for Claude Code that reveals a site's tech stack, DNS records, SSL status, and WHOIS data. It supports competitive research and security audits. CX Codex +1 9,357installs technical-seo-stinger Legion Code Inc. technical-seo-stinger is a Claude Code skill that audits technical SEO across 100 pages, checking crawlability, indexability, sitemaps, robots.txt, canonicalization, and crawl-budget use to assess an external site's technical health. CX Codex +1 ★ 96repo stars website-audit-tools Legion Code Inc. website-audit-tools — a plugin for comprehensive public-site audits: crawl, SEO, accessibility, conversion, security. Outputs a scorecard with findings and reports. CX Codex ★ 96repo stars firecrawl-seo-audit firecrawl firecrawl-seo-audit inspects metadata, headings, internal links and canonical declarations using Firecrawl CLI. Generates prioritized SEO fixes backed by raw page source. CX Codex +1 32,400installs

From the same set102

The whole set →
after-action-report after-action-report runs a structured review of an incident, launch, or finished project, then turns the findings into causes, lessons, and owned actions. CX Codex +1 292installs content-brief-authoring The content-brief-authoring skill helps shape a brief for one piece of content, from search intent and audience to outline and success criteria. Use it to guide a writer or review an existing brief. CX Codex +1 292installs jtbd-framing jtbd-framing is a Claude Code skill that applies Jobs-to-be-Done to product work. It activates for JTBD analysis, prioritization, and product positioning. CX Codex +1 291installs email-sequences The email-sequences skill plans and drafts email campaigns, from onboarding flows and newsletters to transactional messages and win-back sequences. CX Codex +1 291installs seo-traffic-diagnosis seo-traffic-diagnosis diagnoses drops, stalls, or sudden spikes in organic search traffic using Ahrefs MCP, Search Console, and site analytics. CX Codex +1 290installs lead-magnet-design lead-magnet-design — a growth methodology skill to structure gated offers, checklists, and templates that qualify audience interest before collecting emails. CX Codex +1 289installs programmatic-seo Architect durable programmatic SEO systems from structured data without triggering search engine thin-content penalties. CX Codex +1 289installs seo-backlink-audit seo-backlink-audit reviews backlink quality via Ahrefs MCP: whether your profile is healthy, which links are risky, what you've lost, and how you stack against rivals. CX Codex +1 288installs

Project sponsors

Companies that keep this analytics open