What does the orchestrator do?

It runs a complete SEO audit by sequencing the sibling audit skills in a defined order and synthesizing their findings into a single rollup report across backlinks, keywords, content, traffic, technical health, and rankings. The child skills (site health, backlinks, keyword gap, content gap, on-page, and AI search) do the actual analysis; this skill defines the scope, gathers the data, sequences the sub-audits, integrates their outputs, and turns the combined picture into themes and a roadmap.

What are the six phases?

Scope and baseline (a one-page charter defining what is in and out of scope and the goal), data gather (the Ahrefs pulls plus Search Console, analytics, and logs, with freshness documented), run the sub-audits (each child skill producing its own findings), synthesize (5 to 7 themes, because a list of 200 issues is not an audit), prioritize (an impact-effort matrix that surfaces quick wins), and deliver (the rollup report and a 90-day roadmap). The phases run in order, because skipping one produces gaps and reordering produces rework.

Why synthesize into themes instead of listing findings?

Because a list of 200 issues is data, not an audit, and 'here are 47 things to fix' gets nothing fixed. Combine the sub-audit findings into 5 to 7 themes, each answering what is happening, why it matters, the size of the prize, and the fix. Then prioritize the themes on an impact-effort matrix so quick wins surface to the top, and tie each theme to a measurable target like organic clicks or ranked keywords in a target band. Themes are what stakeholders can act on; raw findings are what they ignore.

When should I run a single audit instead?

Reach for a child skill directly when the question is narrower: a single dimension (use the specific audit like seo-onpage or seo-backlink-audit), a specific traffic drop (use seo-traffic-diagnosis), a tactical keyword question (use seo-keyword-gap-audit), or routine monitoring (use seo-rank-tracking). The orchestrator is for the complete picture: a full quarterly or annual audit, pre-acquisition due diligence, post-migration verification, onboarding a new property, or a baseline before a major SEO investment.

What makes an audit shelfware?

No goal going in, and no roadmap coming out. An audit without a charter produces a 60-page document nobody reads, and one without a 90-day roadmap afterward is shelfware. Charter the audit first, synthesize ruthlessly into themes, prioritize so the team knows what to do this quarter, walk stakeholders through it to get commitment, and standardize the structure audit to audit so trends are visible. And do not treat Ahrefs as the only source: Search Console, analytics, and logs add the ground truth that keeps conclusions honest.

Skill · SEO audit orchestration

SEO audit orchestration.

Run the full audit by sequencing the child skills, then synthesize the themes.

Run a complete SEO audit by sequencing the sibling audit skills in a defined order and synthesizing their outputs into a single rollup report. Six phases carry it: scope and baseline, data gather, run the sub-audits, synthesize, prioritize, and deliver. The child skills do the analysis; this skill coordinates them and integrates the results.

It is the master orchestrator, for the complete picture rather than a single dimension. The discipline is themes over findings: a list of 200 issues is data, while five to seven themes are an audit.

Audience: SEO leads running a quarterly or annual health check, scoping due diligence, verifying a migration, or building a baseline before a major investment.

View the skill on GitHub Browse the full catalog

The framework

Six phases, in order.

A complete audit moves through six phases in order. Skipping phases produces gaps; reordering them produces rework.

01Scope and baseline: define what is in and out of scope, the goal (baseline, fix plan, growth roadmap, due diligence), and the stakeholders. Output a one-page charter.
02Data gather: pull the raw data from Ahrefs (Site Explorer, Site Audit, Keywords Explorer, Content Explorer, Rank Tracker) plus Search Console, analytics, and server logs, documenting freshness for every pull.
03Run the sub-audits: run each child audit, each producing its own findings doc, while this skill sequences them and integrates the outputs.
04Synthesize: combine findings into 5 to 7 themes, because a list of 200 issues is not an audit. Each theme names what is happening, why it matters, the size of the prize, and the fix.
05Prioritize: rank the themes on a simple impact-effort matrix (quick wins, strategic plays, maintenance, avoid), each tied to a measurable target.
06Deliver: produce the rollup report, walk stakeholders through it, and get commitment to the next 90 days of work.

What it sequences

Six child audits, integrated into one.

The orchestrator runs each of these child skills and integrates their outputs. The child skills do the analysis; this skill sequences them and synthesizes the rollup.

Run by the orchestrator

seo-site-health-audit
A prioritized technical fix backlog from the crawl, triaged by impact.
seo-backlink-audit
Profile health, the toxic list, the reclamation list, and the competitive gap.
seo-keyword-gap-audit
The prioritized keyword opportunity list against the competitor set.
seo-content-gap-audit
The create, update, and merge content roadmap across the catalog.
seo-onpage
Per-page audits on the top pages by organic traffic.
seo-aeo-geo
AI search readiness gaps across the five AEO and GEO layers.

The SEO-intelligence stack the suite runs on.

The suite is powered by the Ahrefs MCP: every phase pulls from Site Explorer, Site Audit, Keywords Explorer, Content Explorer, and Rank Tracker, cross-checked with Search Console, analytics, and server logs. The content sub-audit it runs also draws on Similarweb (traffic-driving page gaps) and Semrush (SERP-feature gaps).

Reference files

The reference that goes alongside the SKILL.md.

references/audit-rollup-template.md
The template for the rollup report, including the executive summary, the theme structure, and the roadmap format.

Browse all reference files on GitHub

Open source under MIT

Read the SKILL.md on GitHub.

The skill source lives in the rampstackco/claude-skills repository alongside dozens of other skills covering the full lifecycle of brand and product work. This page is a structured overview; the SKILL.md is the source. MIT licensed.

View SKILL.md Browse the full catalog

Frequently asked questions.

What does the orchestrator do?: It runs a complete SEO audit by sequencing the sibling audit skills in a defined order and synthesizing their findings into a single rollup report across backlinks, keywords, content, traffic, technical health, and rankings. The child skills (site health, backlinks, keyword gap, content gap, on-page, and AI search) do the actual analysis; this skill defines the scope, gathers the data, sequences the sub-audits, integrates their outputs, and turns the combined picture into themes and a roadmap.
What are the six phases?: Scope and baseline (a one-page charter defining what is in and out of scope and the goal), data gather (the Ahrefs pulls plus Search Console, analytics, and logs, with freshness documented), run the sub-audits (each child skill producing its own findings), synthesize (5 to 7 themes, because a list of 200 issues is not an audit), prioritize (an impact-effort matrix that surfaces quick wins), and deliver (the rollup report and a 90-day roadmap). The phases run in order, because skipping one produces gaps and reordering produces rework.
Why synthesize into themes instead of listing findings?: Because a list of 200 issues is data, not an audit, and 'here are 47 things to fix' gets nothing fixed. Combine the sub-audit findings into 5 to 7 themes, each answering what is happening, why it matters, the size of the prize, and the fix. Then prioritize the themes on an impact-effort matrix so quick wins surface to the top, and tie each theme to a measurable target like organic clicks or ranked keywords in a target band. Themes are what stakeholders can act on; raw findings are what they ignore.
When should I run a single audit instead?: Reach for a child skill directly when the question is narrower: a single dimension (use the specific audit like seo-onpage or seo-backlink-audit), a specific traffic drop (use seo-traffic-diagnosis), a tactical keyword question (use seo-keyword-gap-audit), or routine monitoring (use seo-rank-tracking). The orchestrator is for the complete picture: a full quarterly or annual audit, pre-acquisition due diligence, post-migration verification, onboarding a new property, or a baseline before a major SEO investment.
What makes an audit shelfware?: No goal going in, and no roadmap coming out. An audit without a charter produces a 60-page document nobody reads, and one without a 90-day roadmap afterward is shelfware. Charter the audit first, synthesize ruthlessly into themes, prioritize so the team knows what to do this quarter, walk stakeholders through it to get commitment, and standardize the structure audit to audit so trends are visible. And do not treat Ahrefs as the only source: Search Console, analytics, and logs add the ground truth that keeps conclusions honest.