スキル一覧に戻る

seo-audit-orchestration

rampstackco
更新日 2 days ago
4 閲覧
239
27
239
GitHubで表示
その他mcpdesign

について

このスキルは、専門的な監査ツールを連携させて包括的なSEO監査を調整し、統合レポートを生成します。フルサイトレビュー、デューデリジェンス、またはステークホルダーが全体像を必要とするヘルスチェック時に起動されます。このスキルは技術スタックに依存せず、Ahrefs MCPを活用してバックリンク、キーワード、コンテンツ、トラフィック、技術的健康状態、ランキングを分析します。

クイックインストール

Claude Code

推奨
メイン
npx skills add rampstackco/claude-skills -a claude-code
プラグインコマンド代替
/plugin add https://github.com/rampstackco/claude-skills
Git クローン代替
git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/seo-audit-orchestration

このコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします

ドキュメント

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 list of 5-7 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 (5-7 themes, 1 page each)
  • 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. 5-7 themes max. Each 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 (1 page).
  2. Audit charter (scope, goal, methodology).
  3. Themes and recommendations (5-7 themes, each 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: 15-30 pages including appendices. Executive summary readable in 5 minutes.


Reference files

GitHub リポジトリ

rampstackco/claude-skills
パス: skills/seo-audit-orchestration
0
agent-skillsai-agentsanthropicclaudeclaude-aiclaude-code

関連スキル

seo-site-health-audit

その他

このスキルは、Ahrefsなどのクローラーが検出する技術的SEOの問題を、深刻度ラベルだけでなく、実際の順位やトラフィックへの影響に基づいて優先順位付けします。監査結果のレビューやSEOスプリントの範囲策定時に、開発者が優先的な修正バックログを作成するのに役立ちます。長大なクロールエラーリストによる意思決定の麻痺を解消し、高インパクトなアクションに集中するためにご活用ください。

スキルを見る

seo-keyword-gap-audit

その他

このスキルはAhrefs MCPを介して競合のSEOデータを分析し、対象サイトが順位を獲得していないキーワードを特定・優先順位付けします。新規市場参入時やシェア減少時のコンテンツ企画、即効性のある施策の発見、競合分析を目的として設計されています。出力は、新規または改善コンテンツのための優先順位付けされ、クラスタリングされたキーワード機会のリストです。

スキルを見る

seo-traffic-diagnosis

その他

このスキルは、AhrefsとSearch Consoleのデータを使用して、5層の根本原因分析により有機トラフィックの変動を診断します。急激なトラフィックの減少、アルゴリズムのアップデート、移行後の損失などの問題をトリガーとして、原因を特定します。出力は明確な診断と、開発者がSEOパフォーマンスの問題を解決するための実行可能な計画を提供します。

スキルを見る

seo-rank-tracking

その他

このスキルは、Ahrefs MCPを使用したSEO順位追跡の設定と管理を開発者が行う際に役立ちます。キーワードの選択、セグメント化、ベースラインの確立、アラートの閾値設定を順を追ってガイドします。新たな追跡プロジェクトを開始する際や、ステークホルダー向けの定期的な報告体制を確立する際にご利用ください。

スキルを見る