Seo Audit

作者 agricidaniel4b99de2f7de7MIT18K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫3 天前更新

Run a full-site SEO audit and return a scored, prioritized report. Use only for site-wide checks; use seo-page for one URL or seo-technical for a technical-only review.

僅含說明Marketing & Sales
AI 產生的概覽

執行全站 SEO 稽核,回傳含評分與優先順序的報告,可選輸出 PDF。

功能
爬取站內連結(最多 500 頁,遵守 robots.txt),渲染首頁,並將檢查分派給多個專項子代理,涵蓋技術 SEO、內容、結構化資料、網站地圖、效能、視覺、AI 搜尋就緒度、本地、反向連結、聚類與電子商務。它依加權類別彙總為 0-100 的 SEO 健康分數,並將稽核產物寫入以網域命名的資料夾。產出包括完整稽核報告、優先順序行動計畫、結構化 JSON 資料、各分類發現、螢幕截圖,以及可選的 PDF 或 HTML 報告。
適用情境
適用於全站 SEO 稽核,而非單一頁面或純技術審查。當你需要針對整個網站搜尋健康狀況的評分與優先順序全貌,並可選結合分析、反向連結與搜尋控制台資料時使用。
執行需求
僅為說明文件,技能本身不附帶指令碼。它引用外部 claude-seo 外掛執行器與子代理,並可選整合 DataForSEO MCP、Google API(CrUX、GSC、GA4)、Matomo、Moz 或 Bing 反向連結 API,以及用於截圖的 Playwright。爬取網站需要網路存取;憑證為可選,僅用於資料增強。

Full Website SEO Audit

Process

  1. Render homepage: use "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run render_page.py <url> --mode auto --json to capture raw HTML, rendered HTML, extracted text, SPA status, and accessibility data when needed
  2. Detect business type: analyze homepage signals per seo orchestrator
  3. Crawl site: follow internal links up to 500 pages, respect robots.txt
  4. Delegate to subagents (if available, otherwise run inline sequentially):
    • seo-technical -- robots.txt, sitemaps, canonicals, Core Web Vitals, security headers
    • seo-content -- E-E-A-T, readability, thin content, AI citation readiness
    • seo-schema -- detection, validation, generation recommendations
    • seo-sitemap -- structure analysis, quality gates, missing pages
    • seo-performance -- LCP, INP, CLS measurements
    • seo-visual -- screenshots, mobile testing, above-fold analysis
    • seo-geo -- AI crawler access, llms.txt, citability, brand mention signals
    • seo-agentic -- Lighthouse Agentic Browsing fraction (X/N), accessibility tree for agents, AI agent access policy, Markdown and discovery files, WebMCP (always include in full audits; its findings feed AI Search Readiness)
    • seo-local -- GBP signals, NAP consistency, reviews, local schema, industry-specific local factors (spawn when Local Service industry detected: brick-and-mortar, SAB, or hybrid business type)
    • seo-maps -- Geo-grid rank tracking, GBP audit, review intelligence, competitor radius mapping (spawn when Local Service detected AND DataForSEO MCP available)
    • seo-google -- CWV field data (CrUX), URL indexation (GSC), organic traffic (GA4) (spawn when Google API credentials detected via "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run google_auth.py --check)
    • seo-matomo -- Matomo Reporting API: organic traffic, landing pages, device / country splits, referrer analysis (spawn when Matomo credentials detected via "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run matomo_auth.py --check; runs alongside seo-google when both are configured, or as a GA4 alternative when GA4 is not)
    • seo-backlinks -- Backlink profile data: DA/PA, referring domains, anchor text, toxic links (spawn when Moz or Bing API credentials detected via "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run backlinks_auth.py --check, or always include Common Crawl domain-level metrics)
    • seo-cluster -- Semantic clustering analysis (spawn when content strategy signals detected: blog, pillar pages, topic clusters)
    • seo-sxo -- Search experience analysis: page-type mismatch, user stories, persona scoring (always include in full audits)
    • seo-drift -- Drift analysis: compare against stored baseline (spawn when drift baseline exists for the URL via "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run drift_history.py <url>)
    • seo-ecommerce -- Product schema, marketplace intelligence (spawn when E-commerce industry detected)
  5. Score -- aggregate into SEO Health Score (0-100)
  6. Persist audit artifacts -- write all outputs under {domain}-audit/
  7. Report -- generate prioritized action plan and optional PDF/HTML report

Crawl Configuration

Max pages: 500Respect robots.txt: YesFollow redirects: Yes (max 3 hops)Timeout per page: 30 secondsConcurrent requests: 5Delay between requests: 1 second

Output Files

  • {domain}-audit/FULL-AUDIT-REPORT.md: Comprehensive findings
  • {domain}-audit/ACTION-PLAN.md: Prioritized recommendations (Critical > High > Medium > Low)
  • {domain}-audit/audit-data.json: Structured audit envelope for report generation
  • {domain}-audit/findings/*.md: Per-category specialist findings (technical.md, content.md, schema.md, performance.md, visual.md, etc.)
  • {domain}-audit/screenshots/: Desktop + mobile captures (if Playwright available)
  • PDF Report (recommended): Generate a professional A4 PDF using "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run google_report.py --type full --data {domain}-audit/audit-data.json --domain <domain> --output-dir {domain}-audit/. This produces a white-cover enterprise report with TOC, executive summary, charts (Lighthouse gauges, query bars, index donut), metric cards, threshold tables, prioritized recommendations with effort estimates, and implementation roadmap. Always offer PDF generation after completing an audit.

Structured Audit Data Envelope

Write {domain}-audit/audit-data.json with this shape so "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run google_report.py --type full --data {domain}-audit/audit-data.json --domain <domain> --output-dir {domain}-audit/ can generate a report even when Google API data is unavailable:

json
{  "summary": {    "health_score": 0,    "business_type": "detected type",    "top_findings": [],    "quick_wins": []  },  "categories": [    {      "name": "Technical SEO",      "score": 0,      "what_works": [],      "findings": [        {          "title": "Finding title",          "severity": "Critical|High|Medium|Low|Info",          "description": "Evidence-backed detail",          "recommendation": "Specific fix"        }      ]    }  ],  "action_plan": {    "phases": [      {"name": "Phase 1: Critical Fixes", "timeframe": "Week 1", "items": []},      {"name": "Phase 2: High-Impact Improvements", "timeframe": "Weeks 2-3", "items": []},      {"name": "Phase 3: Content & Authority", "timeframe": "Month 2", "items": []},      {"name": "Phase 4: Monitoring & Iteration", "timeframe": "Ongoing", "items": []}    ]  },  "artifacts": {    "findings_dir": "findings/",    "screenshots_dir": "screenshots/"  }}

Scoring Weights

CategoryWeight
Technical SEO22%
Content Quality23%
On-Page SEO20%
Schema / Structured Data10%
Performance (CWV)10%
AI Search Readiness10%
Images5%

Report Structure

Executive Summary

  • Overall SEO Health Score (0-100)
  • Business type detected
  • Top 5 critical issues
  • Top 5 quick wins

Technical SEO

  • Crawlability issues
  • Indexability problems
  • Security concerns
  • Core Web Vitals status

Content Quality

  • E-E-A-T assessment
  • Thin content pages
  • Duplicate content issues
  • Readability scores

On-Page SEO

  • Title tag issues
  • Meta description problems
  • Heading structure
  • Internal linking gaps

Schema & Structured Data

  • Current implementation
  • Validation errors
  • Missing opportunities

Performance

  • LCP, INP, CLS scores
  • Resource optimization needs
  • Third-party script impact

Images

  • Missing alt text
  • Oversized images
  • Format recommendations

AI Search Readiness

  • Citability score
  • Structural improvements
  • Authority signals

Priority Definitions

  • Critical: Blocks indexing or causes penalties (fix immediately)
  • High: Significantly impacts rankings (fix within 1 week)
  • Medium: Optimization opportunity (fix within 1 month)
  • Low: Nice to have (backlog)

DataForSEO Integration (Optional)

If DataForSEO MCP tools are available, spawn the seo-dataforseo agent alongside existing subagents to enrich the audit with live data: real SERP positions, backlink profiles with spam scores, on-page analysis (Lighthouse), business listings, and AI visibility checks (ChatGPT scraper, LLM mentions).

Google API Integration (Optional)

If Google API credentials are configured ("${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run google_auth.py --check), spawn the seo-google agent to enrich the audit with real Google field data: CrUX Core Web Vitals (replaces lab-only estimates), GSC URL indexation status, search performance (clicks, impressions, CTR), and GA4 organic traffic trends. The Performance (CWV) category score benefits most from field data.

Matomo Integration (Optional)

If Matomo credentials are configured ("${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run matomo_auth.py --check), spawn the seo-matomo agent to enrich the audit with self-hosted analytics: organic visits trend, top landing pages, device and country breakdowns, channel / search-engine split, and organic keywords. Works as a GA4 alternative (when only Matomo is configured) or as a complement (when both GA4 and Matomo are present). Matomo numbers will not match GA4 exactly because of segmentation differences (referrerType==search vs sessionDefaultChannelGroup == "Organic Search") and attribution-window rules.

Google Update Correlation

Before attributing a traffic or ranking change to anything, list the confirmed Google updates in that window from the primary-source ledger:

bash
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run seo_updates.py --since <yyyy-mm> --json

Every entry cites a Google-owned URL. If freshness.stale is true, say the ledger may miss recent updates and check status.search.google.com before drawing conclusions. A date overlap is a hypothesis, never proof of cause.

Error Handling

ScenarioAction
URL unreachable (DNS failure, connection refused)Report the error clearly. Do not guess site content. Suggest the user verify the URL and try again.
robots.txt blocks crawlingReport which paths are blocked. Analyze only accessible pages and note the limitation in the report.
Rate limiting (429 responses)Back off and reduce concurrent requests. Report partial results with a note on which sections could not be completed.
Timeout on large sites (500+ pages)Cap the crawl at the timeout limit. Report findings for pages crawled and estimate total site scope.
Subagent hits its maxTurns budget on a large siteFindings are not lost: every audit subagent writes a partial output_dir/findings/*.md after its first analysis pass and overwrites it with the complete findings before finishing. Read whatever findings file exists and merge it into the report, noting it may be partial.

來源與署名

來源:agricidaniel/claude-seo位於skills/seo-audit提交4b99de2

授權條款: MIT

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架