Agent skill · Security

seo-site-health-audit

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.

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill seo-site-health-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/seo-site-health-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 se

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: triage by SEO impact, not severity
  5. Axis 1: Page-level traffic impact
  6. Axis 2: Mechanism of impact
  7. Axis 3: Effort
  8. The triage matrix
  9. Workflow
  10. High-leverage clusters worth looking for
  11. Failure patterns
  12. Output format
  13. Reference files
Ships with 1 file
  • references/issue-impact-table.md
More from claude-skills
All skills →
About this skill
What does the seo-site-health-audit skill do?

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.

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill seo-site-health-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going