Seo Audit Orchestration logo

Seo Audit Orchestration

OrganizationPopular
rampstackco
seo-audit-orchestration

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.

Overview

Publisherrampstackco
Repositoryclaude-skills
Skill nameseo-audit-orchestration
Stars
1K
Forks
134
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by rampstackco on GitHub. Read the source before you install it.

Installation

Install the Seo Audit Orchestration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/rampstackco/claude-skills/tree/main/skills/seo-audit-orchestration
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/rampstackco/claude-skills.git /tmp/claude-skills
mkdir -p .claude/skills
cp -r /tmp/claude-skills/skills/seo-audit-orchestration .claude/skills/seo-audit-orchestration
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Seo Audit Orchestration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Seo Audit Orchestration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Seo Audit Orchestration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

SEO Audit Orchestration

Run a complete SEO audit by sequencing the sibling audit skills in a defined order. Stack-agnostic. Assumes the Ahrefs MCP is connected. Produces a single rollup report that synthesizes findings across backlinks, keywords, content, traffic, technical health, and rankings.


When to use

  • Running a full SEO audit (quarterly, biannual, annual)
  • Pre-acquisition SEO due diligence
  • Post-migration verification (after content move, replatform, or domain change)
  • Onboarding a new client or new property
  • Building a baseline before a major SEO investment
  • Diagnosing chronic underperformance

When NOT to use

  • Single-dimension audits (use the specific child skill: seo-onpage, seo-backlink-audit, etc.)
  • Investigating a specific traffic drop (use seo-traffic-diagnosis)
  • Tactical questions like "which keywords should we target" (use seo-keyword-gap-audit)
  • Routine monitoring (use seo-rank-tracking)

Required inputs

  • The site or properties in scope
  • Target market and primary languages
  • Competitor set (3-5 properties)
  • Goal of the audit (baseline, due diligence, fix plan, growth roadmap)
  • Time and reporting constraints
  • Confirmation that the Ahrefs MCP is connected and the workspace has access to the target property

The framework: 6 phases of an end-to-end audit

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

Phase 1: Scope and baseline

Define the audit before running it.

  • What is in scope (subdomains, paths, languages)
  • What is out of scope
  • Goal of the audit (baseline, fix plan, growth roadmap, due diligence)
  • Stakeholders and their priorities
  • Reporting format and length expectations

Output: a 1-page audit charter.

Phase 2: Data gather

Pull the raw data from Ahrefs and any companion sources.

Required pulls:

  • Site Explorer: organic keywords, organic traffic, top pages, top countries, referring domains, backlinks, anchor text profile
  • Site Audit: full crawl results
  • Keywords Explorer: target keyword universe and competitor keyword overlap
  • Content Explorer: top performing content in target topics
  • Rank Tracker: current tracked positions if set up

Companion pulls (not Ahrefs-native):

  • Search Console: query and page data, coverage issues
  • Analytics: traffic, conversions, segment by source
  • Server logs (if available): bot crawl behavior

Document data freshness for every pull. Stale data yields wrong conclusions.

Phase 3: Run the sub-audits

Run each child audit. Each produces its own findings doc.

Sub-auditSkillWhat it produces
Site healthseo-site-health-auditPrioritized technical fix backlog
Backlinksseo-backlink-auditProfile health, toxic list, reclamation list
Keywordsseo-keyword-gap-auditPrioritized opportunity list
Contentseo-content-gap-auditCreate/update/merge roadmap
Page-levelseo-onpagePer-page audit on top pages
AI searchseo-aeo-geoAI search readiness gaps

The child skills do the analysis. This skill sequences them and integrates the outputs.

Phase 4: Synthesize

Combine findings into themes. A list of 200 issues is not an audit. A short list of themes is.

Themes typically emerge in categories like:

  • Technical foundation gaps that cap upside
  • Content depth gaps in priority topics
  • Backlink profile concentration risks
  • Keyword opportunities the site is leaving on the table
  • Cannibalization or thin coverage
  • AI search readiness

Each theme should answer: what is happening, why it matters, what is the size of prize, what is the fix.

Phase 5: Prioritize

Rank the themes. Use a simple impact/effort matrix.

  • Quick wins: high impact, low effort. Do now.
  • Strategic plays: high impact, high effort. Plan and resource.
  • Maintenance: low impact, low effort. Backlog.
  • Avoid: low impact, high effort. Drop.

Tie each theme to a measurable target (organic clicks, ranked keywords in target band, conversions from organic).

Phase 6: Deliver

Produce the rollup report. See references/audit-rollup-template.md.

Structure:

  • Executive summary (1 page)
  • Themes and recommendations (1 page each; count per audit type, from the template's length-targets table)
  • Sub-audit findings (linked or appended)
  • Roadmap (next 90 days)

Walk stakeholders through it. Get commitment to the next 90 days of work.


Workflow

  1. Charter the audit. 1-page scope, goal, stakeholders, format.
  2. Confirm Ahrefs MCP access. Verify the workspace has the target property and recent data.
  3. Pull all data. Run the gather list in phase 2. Document freshness.
  4. Run each sub-audit. Use the child skills. Each produces its own findings doc.
  5. Synthesize themes. Hold to the theme count the template's length-targets table gives for this audit type. Each theme ties to an impact and a fix.
  6. Prioritize. Impact/effort matrix. Quick wins surface to the top.
  7. Draft the rollup. Use the template. Executive summary first.
  8. Review with the team. Pressure-test conclusions before stakeholder readout.
  9. Deliver. Walk stakeholders through. Get commitment to next 90 days.
  10. Schedule the next one. Audits decay. Rerun on a cadence.

Failure patterns

  • Audit without a goal. Produces a 60-page document nobody reads. Charter the audit first.
  • All findings, no themes. A list of 200 issues is data, not an audit. Synthesize into themes.
  • Skipping the sub-audits. Running one big audit instead of six focused ones produces shallow analysis everywhere.
  • No prioritization. "Here are 47 things to fix" gets nothing fixed. Rank them.
  • Stale data. Ahrefs index updates on a delay. Note freshness. Do not draw conclusions from week-old movement.
  • Tool worship. Ahrefs is one source. Search Console, analytics, and logs add ground truth. Triangulate.
  • Audit-to-audit drift. Running every audit differently makes trends impossible to spot. Standardize the structure.
  • No 90-day roadmap. Without a plan after the audit, the audit is shelfware.
  • Solo audit. Audits done alone miss context. Pull in the people who own the work.

Output format

A rollup audit report with:

  1. Executive summary.
  2. Audit charter (scope, goal, methodology).
  3. Themes and recommendations (each theme with what, why, size of prize, fix).
  4. Sub-audit appendix (linked outputs from each child skill).
  5. 90-day roadmap (sequenced work with owners and targets).
  6. Methodology notes (data sources, pull dates, caveats).

Total length, executive summary length, and theme count all vary by audit type: a quarterly health check is not a due-diligence audit. The length-targets table in references/audit-rollup-template.md owns those numbers per type. Whatever the type, the executive summary stays readable in 5 minutes.


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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Seo Audit Orchestration AI skill do?

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.

Why use Seo Audit Orchestration on TypingMind?

Because you install it once and use it with any model. Seo Audit Orchestration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Seo Audit Orchestration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/rampstackco/claude-skills/tree/main/skills/seo-audit-orchestration. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Seo Audit Orchestration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Seo Audit Orchestration?

As many as you like. As long as a model supports skills, you can use Seo Audit Orchestration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Seo Audit Orchestration AI skill free?

Yes. It is published on GitHub by rampstackco under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇