seo-site-health-audit-c751de — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited seo-site-health-audit-c751de (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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.
seo-traffic-diagnosis)seo-onpage)seo-technical)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.
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:
A fix on Tier 1 is worth 10x a fix on Tier 3 in most cases.
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.
Some issues are 5-minute fixes. Some are multi-sprint projects.
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.
references/issue-impact-table.md.seo-audit-orchestration.These patterns commonly produce outsized impact when fixed:
When you spot one of these, prioritize even if individual issues look small. The cluster impact is large.
A site health triage document with:
Length: 5-12 pages plus a backlog spreadsheet.
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.
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.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.