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.
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
"${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.shopify-env ("${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run shopify_env.py precheck <url> reports "mode": "signed"), crawl with the seo-shopify extension (extensions/shopify) instead: uncapped, sitemap-complete, and its summary.json and sample.json replace the link crawl as subagent inputseo-technical -- robots.txt, sitemaps, canonicals, Core Web Vitals, security headersseo-content -- E-E-A-T, readability, thin content, AI citation readinessseo-schema -- detection, validation, generation recommendationsseo-sitemap -- structure analysis, quality gates, missing pagesseo-performance -- LCP, INP, CLS measurementsseo-visual -- screenshots, mobile testing, above-fold analysisseo-geo -- AI crawler access, llms.txt, citability, brand mention signalsseo-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-maps has no MCP tools: first get the DataForSEO maps data (business listings, Maps SERP geo-grid, GBP profile, reviews) through the seo-dataforseo agent or your own DataForSEO MCP tools, then pass it in the seo-maps prompt; without it seo-maps runs the free tier. The report must say which tier was used)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){domain}-audit/Max pages: 500
Respect robots.txt: Yes
Follow redirects: Yes (max 3 hops)
Timeout per page: 30 seconds
Concurrent requests: 5
Delay between requests: 1 second{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)"${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.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:
{
"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/"
}
}| Category | Weight |
|---|---|
| Technical SEO | 22% |
| Content Quality | 23% |
| On-Page SEO | 20% |
| Schema / Structured Data | 10% |
| Performance (CWV) | 10% |
| AI Search Readiness | 10% |
| Images | 5% |
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).
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.
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.
Before attributing a traffic or ranking change to anything, list the confirmed Google updates in that window from the primary-source ledger:
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run seo_updates.py --since <yyyy-mm> --limit 0 --json--limit 0 lists every match; without it only the 10 newest are returned and
truncated is true, so an older core update in the window can go unseen.
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.
| Scenario | Action |
|---|---|
| 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 crawling | Report 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 site | Findings 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. |
sandbox: false (or stderr shows a claude-seo warning that the page is rendered without Chromium's sandbox), tell the user once in the report that the page was rendered without the browser sandbox on this system and why. Never set CLAUDE_SEO_CHROMIUM_NO_SANDBOX or CLAUDE_SEO_CHROMIUM_REQUIRE_SANDBOX yourself. If a launch fails with the strict-mode error (it names both variables), report it and ask the user. In a full audit say it once, not once per subagent.AgriciDaniel/claude-seo
468ed5b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.