Skip to content

rampstackco/claude-skills / skills/seo-audit-orchestration

seo-audit-orchestration

Verified

Master orchestrator for a full SEO audit suite powered by the Ahrefs MCP. Use this skill when running a comprehensive SEO audit, scoping a quarterly health check, doing pre-acquisition SEO due diligence, or post-migration verification. Triggers on full SEO audit, comprehensive SEO review, SEO health check, audit my site, SEO due diligence, audit suite, comprehensive audit, end-to-end SEO. Also triggers when a stakeholder wants the complete picture rather than a single-dimension audit.

FileKindSize
README.mdmarkdown364 B
SKILL.mdskill md8.2 KB
references/audit-rollup-template.mdmarkdown5.6 KB

references/audit-rollup-template.md

View on GitHub
# Audit rollup template

A template for the final SEO audit deliverable. Adapt sections to fit the audit goal and stakeholder appetite.

---

## Document structure

```
1. Executive summary           (1 page)
2. Audit charter               (1 page)
3. Themes and recommendations  (1 page each, count by audit type)
4. 90-day roadmap              (1-2 pages)
5. Sub-audit appendix          (linked or attached)
6. Methodology notes           (1 page)
```

Total length and theme count depend on the audit type: see "Common length targets by audit type" below. Executive summary always readable in 5 minutes.

---

## 1. Executive summary template

```
# [Property] SEO Audit

**Audit date:** [date]
**Period covered:** [date range]
**Auditor:** [name or team]

## Headline

[One sentence. The state of SEO at this property.]

## Top 3 themes

1. **[Theme name].** [One sentence. Why it matters.]
2. **[Theme name].** [One sentence. Why it matters.]
3. **[Theme name].** [One sentence. Why it matters.]

## Top 3 quick wins

1. **[Action].** Estimated impact: [target metric movement]. Effort: [size].
2. **[Action].** Estimated impact: [target metric movement]. Effort: [size].
3. **[Action].** Estimated impact: [target metric movement]. Effort: [size].

## Recommended next 90 days

[3-5 bullets describing the proposed plan.]

## What is going well

[2-4 bullets. Avoid an audit that reads as 100% negative.]
```

---

## 2. Audit charter template

```
## Scope

- Properties in scope: [list]
- Languages: [list]
- Subdomains: [list]
- Out of scope: [list]

## Goal

[Baseline / fix plan / growth roadmap / due diligence]

## Stakeholders

| Name | Role | Priority |
| --- | --- | --- |
| [name] | [role] | [their main concern] |

## Methodology

- Data sources: [Ahrefs, Search Console, Analytics, logs]
- Pull dates: [dates]
- Sub-audits run: [list]

## Limitations

[Anything that limits confidence: data gaps, access restrictions, time constraints.]
```

---

## 3. Theme template

Use one page per theme. For the number of themes, see "Common length targets by audit type" below: 3-4 for a quarterly health check, 5-7 for a full annual audit, 6-10 for due diligence, 3-5 for post-migration verification.

```
## Theme [N]: [Name]

**What is happening**

[2-3 sentences describing the pattern.]

**Why it matters**

[2-3 sentences linking the pattern to a business outcome.]

**Size of prize**

[Quantified opportunity. E.g., "+12,000 monthly clicks" or "+$80k annual revenue at current conversion."]

**Evidence**

- [Data point with source]
- [Data point with source]
- [Data point with source]

**Recommendation**

[The proposed fix or action. 1 paragraph.]

**Effort and timeline**

[Effort: S/M/L. Timeline: weeks or sprints. Dependencies: list.]

**Owners**

[Who needs to do what.]
```

---

## 4. 90-day roadmap template

Sequence the work. Tie to themes. Assign owners.

```
## Days 1-30

| Action | Theme | Owner | Effort | Target |
| --- | --- | --- | --- | --- |
| [Action] | [Theme #] | [Name] | [S/M/L] | [Metric target] |

## Days 31-60

| Action | Theme | Owner | Effort | Target |
| --- | --- | --- | --- | --- |
| [Action] | [Theme #] | [Name] | [S/M/L] | [Metric target] |

## Days 61-90

| Action | Theme | Owner | Effort | Target |
| --- | --- | --- | --- | --- |
| [Action] | [Theme #] | [Name] | [S/M/L] | [Metric target] |

## Review cadence

[Weekly, biweekly, monthly. Who attends. What is reviewed.]
```

---

## 5. Sub-audit appendix

Link or attach the output from each child skill:

- Site health audit: [link or attachment]
- Backlink audit: [link or attachment]
- Keyword gap audit: [link or attachment]
- Content gap audit: [link or attachment]
- Page-level audits (top pages): [link or attachment]
- AI search readiness: [link or attachment]

Do not paste full sub-audits into the rollup. Reference them. Stakeholders who want detail can drill in.

---

## 6. Methodology notes

```
## Data sources and freshness

| Source | Pull date | Coverage | Notes |
| --- | --- | --- | --- |
| Ahrefs Site Explorer | [date] | [scope] | [caveats] |
| Ahrefs Site Audit | [date] | [scope] | [caveats] |
| Search Console | [date range] | [scope] | [caveats] |
| Analytics | [date range] | [scope] | [caveats] |

## Caveats

- Ahrefs metrics are estimates, not ground truth.
- Search Console data is sampled and capped.
- Analytics may have tagging gaps.
- Server log data was [available / unavailable] for this audit.

## Repeatability

To rerun this audit:

- [Steps to reproduce data pulls]
- [Saved Ahrefs reports or filters]
- [Companion data pull instructions]
```

---

## Style guidance

- Lead with the "so what." Stakeholders skim.
- Quantify wherever possible. Vague impact claims get ignored.
- Pair every problem with a proposed fix. Audits without recommendations are reports.
- Keep technical jargon out of the executive summary.
- Use tables and bullets. Avoid wall-of-text.

---

## Common length targets by audit type

| Audit type | Total length | Executive summary | Themes |
| --- | --- | --- | --- |
| Quarterly health check | 10-15 pages | 1 page | 3-4 themes |
| Full annual audit | 25-40 pages | 1-2 pages | 5-7 themes |
| Pre-acquisition due diligence | 30-50 pages | 2 pages | 6-10 themes |
| Post-migration verification | 10-20 pages | 1 page | 3-5 themes |

---

## Pre-delivery checklist

- [ ] Executive summary readable in 5 minutes
- [ ] Every theme tied to a quantified impact
- [ ] Every recommendation tied to an owner
- [ ] Quick wins called out separately
- [ ] 90-day roadmap is sequenced and resourced
- [ ] Methodology and caveats are documented
- [ ] Internal review completed before stakeholder readout
- [ ] Next audit date scheduled
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall