New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

SEO Site Health Audit

by rampstackco in rampstackco/claude-skills

Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity.

MITAuto-check passedData & Analytics

Install SEO Site Health Audit

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rampstackco/claude-skills seo-site-health-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-site-health-audit .claude/skills/seo-site-health-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
seo-site-health-audit
GitHub stars
945
Token cost
~2.5k tokens
SKILL.md length
1,378 words
Files
3 (incl. references)
Skills in repo
103
Repo updated
First seen
Licence
MIT

At a glance

Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity.

  • Works in 10 steps: Pull the crawl results. Ahrefs Site… → Tier the URLs. Use organic traffic data.… → Categorize each issue by mechanism. Look… → …
  • Reviewing crawl results
  • SKILL.md covers When to use, When NOT to use, Required inputs and The framework: triage by SEO…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

SEO Site Health Audit is an agent skill from rampstackco/claude-skills. 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.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `README.md` and `references/issue-impact-table.md`).

It sits in Data & Analytics, covering Web scraping, Technical SEO and SEO audit. It works with Ahrefs. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.

When your agent uses it

  • Reviewing crawl results
  • Prioritizing technical fixes
  • Scoping a technical SEO sprint
  • After running any site-wide crawl

Example prompts

  • “/seo-site-health-audit”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  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.

What it can do on your machine

Read from SKILL.md and the folder at commit 482c9bf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

SEO Site Health Audit loads about 2.5k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 133 tokens; SKILL.md has 1,378 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~133
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 1,378 words, ~2,500 tokens.

Download SKILL.mdSave it as .claude/skills/seo-site-health-audit/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
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 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.

TierMechanismEffortPriority
Tier 1HIGHSP0 (do this week)
Tier 1HIGHMP1 (do this sprint)
Tier 1HIGHLP2 (plan as project)
Tier 1MEDIUMSP1
Tier 1MEDIUMMP2
Tier 1MEDIUMLP3
Tier 1LOWSP3 (batch when convenient)
Tier 1LOWM-LPark unless evidence emerges
Tier 2HIGHSP1
Tier 2HIGHM-LP2
Tier 2MEDIUMSP2
Tier 2MEDIUMM-LP3
Tier 3HIGHSP3
Tier 3Anything elseAnythingPark

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.
Show full SKILL.md (545 more words)Show less

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 - 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. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/seo-site-health-audit of rampstackco/claude-skills.

  • SKILL.md
  • README.md
  • references/issue-impact-table.md

Open the folder on GitHubat commit 482c9bf

Compare with similar skills

SEO Site Health Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

SEO Site Health Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
SEO Site Health Audit this skillrampstackco/claude-skills945—~2.5kAutomated safety check: PassMIT
Docs Managementxiaoyuge886/aigc198—~7.8kAutomated safety check: NotesMIT
Crawl4AI SEO Site Crawlerartwist-polyakov/polyakov-claude-skills208—~1.7kAutomated safety check: PassMIT
SEO Site Auditspronta/crawlie114—~966Automated safety check: PassCustom licence
Site Content Cataloggooseworks-ai/goose-skills1.2k1 repos~1.9kAutomated safety check: PassMIT
SEO Content Auditgooseworks-ai/goose-skills1.2k1 repos~2.8kAutomated safety check: PassMIT

Similar skills

  • Docs Management

    xiaoyuge886/aigc

    Single source of truth and librarian for ALL Claude official documentation.

    198 GitHub stars~7.8k tokensUpdated 2 mo ago
    Data & AnalyticsAuto-check: notes

  • Crawl4AI SEO Site Crawler

    artwist-polyakov/polyakov-claude-skills

    Crawls a site with Crawl4AI to audit titles, meta tags, H1s, canonicals, navigation and internal links, and to compare landing pages and competitor sites.

    208 GitHub stars~1.7k tokensUpdated 3 days ago
    Marketing & SEOAuto-check passed

  • SEO Site Audit

    spronta/crawlie

    Run a complete technical SEO + AI-search audit of a website with crawlie.

    114 GitHub stars~966 tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed

  • Site Content Catalog

    gooseworks-ai/goose-skills

    Crawl a website's sitemap and blog index to build a complete content inventory.

    1.2k GitHub starsUsed in 1 repo~1.9k tokens
    Writing & ContentAuto-check passed

  • SEO Content Audit

    gooseworks-ai/goose-skills

    Comprehensive SEO footprint analysis. An agent skill from gooseworks-ai/goose-skills.

    1.2k GitHub starsUsed in 1 repo~2.8k tokens
    Marketing & SEOAuto-check passed

  • Robots Txt

    kostja94/marketing-skills

    When the user wants to configure, audit, or optimize robots.txt.

    1k GitHub stars~1.9k tokensUpdated 5 days ago
    Data & AnalyticsAuto-check passed

More from rampstackco/claude-skills

All 103 skills in this repo

  • After Action Report

    rampstackco/claude-skills

    Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.

    945 GitHub stars~2.5k tokensUpdated 4 days ago
    Auto-check passed

  • Analytics Strategy

    rampstackco/claude-skills

    Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.

    945 GitHub stars~2.4k tokensUpdated 4 days ago
    Auto-check passed

  • Brand Style Guide

    rampstackco/claude-skills

    Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.

    945 GitHub stars~2.1k tokensUpdated 4 days ago
    Auto-check passed

  • Brand Voice

    rampstackco/claude-skills

    Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.

    945 GitHub stars~2.2k tokensUpdated 4 days ago
    Auto-check passed

  • Content And Copy

    rampstackco/claude-skills

    Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.

    945 GitHub stars~2.1k tokensUpdated 4 days ago
    Auto-check passed

  • Content Strategy

    rampstackco/claude-skills

    Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.

    945 GitHub stars~2.6k tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about SEO Site Health Audit

What does SEO Site Health Audit do?

Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity. SEO Site Health Audit is an agent skill from rampstackco/claude-skills. Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity.

When should I use SEO Site Health Audit?

SEO Site Health Audit fits situations like: reviewing crawl results; prioritizing technical fixes; scoping a technical SEO sprint; after running any site-wide crawl.

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`. Or copy the skill folder (skills/seo-site-health-audit in rampstackco/claude-skills) into .claude/skills/seo-site-health-audit in your project. Claude Code loads it when a task matches its description.

How do I install SEO Site Health Audit in Codex?

Run `npx skills add rampstackco/claude-skills --skill seo-site-health-audit -a codex`. Or copy the skill folder (skills/seo-site-health-audit in rampstackco/claude-skills) into .agents/skills/seo-site-health-audit in your project. Codex loads it when a task matches its description.

Can I use SEO Site Health Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rampstackco/claude-skills --skill seo-site-health-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-site-health-audit, .gemini/skills/seo-site-health-audit, .github/skills/seo-site-health-audit and .opencode/skills/seo-site-health-audit in your project.

What does SEO Site Health Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: SEO Site Health Audit is instructions for the agent only.

Does SEO Site Health Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is SEO Site Health Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does SEO Site Health Audit use?

SEO Site Health Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does SEO Site Health Audit use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to SEO Site Health Audit?

Skills that share tags, products or a category with SEO Site Health Audit: Docs Management (xiaoyuge886/aigc, 198 stars), Crawl4AI SEO Site Crawler (artwist-polyakov/polyakov-claude-skills, 208 stars), SEO Site Audit (spronta/crawlie, 114 stars) and Site Content Catalog (gooseworks-ai/goose-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SEO Site Health Audit?

rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 945 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.

Source: rampstackco/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.