Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity.
SkillScore91Maintained
Automatic
◆Marketing & Content pack
Last verified 8/20/2026
What it changes
Passed 20 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill91%
Checks it passed that the model alone missed
Mark the low-tier minor crawler notices as Parked or P3.
Assign P1 priority to medium-impact small-effort issues on Tier 1 pages.
Include a dedicated measurement plan section outlining validation protocols for fixes.
and 4 more in the full report
5 fixed15 passed either way2 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+69%
Agent turns
0%
Response time
-19%
Model gemini-3.6-flashMeasured 8/20/2026v220 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
Our technical crawler flagged minor HTML formatting notices on legacy archive pages that receive zero organic traffic. What remediation action or priority band should be applied?
What was checked, without and with the skill
Checked
Without skill
With skill
Mark the low-tier minor crawler notices as Parked or P3.
Missed
Passed
case-12 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md175 lines2 files
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)
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.
Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not triggering or not loading the right context, when you are auditing a skill that is underperforming, or when you want to publish a skill for others. Also triggers when someone asks