Audit
Audit a website or web codebase for SEO and AI-search (GEO/AEO) — produces two independent 0-100 scores (Search SEO + AI Visibility) plus a prioritized, evidence-backed report. Read-only; never writes files. Use when the user asks to audit, analyze, check, or score a site's SEO, structured data/schema, meta tags, Core Web Vitals, robots.txt, sitemaps, or llms.txt, or how it ranks in Google and is cited by AI engines (ChatGPT, Perplexity, Google AI Overviews, Gemini, Claude).From its SKILL.md
npx -y skills add Hainrixz/claude-seo-ai --skill auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.9 KB, 329 tokens by cl100k_base, as published. Nobody here has run it
/claude-seo-ai:audit
A full, read-only SEO + AI-search audit. Never writes files.
$ARGUMENTS = <url|path> [flags]. The target is a URL (https://…) or a local web project / built HTML. If no target is given, ask for one.
What to do
- Invoke the seo-orchestrator skill with the target and any flags. It builds the shared PageSnapshot (via seo-crawl-render), detects the vertical (seo-vertical-detect, see
references/routing.md), dispatches the read-only specialist subagents in parallel, merges findings, and runs seo-score. - Present:
- The two scores — Search SEO and AI Visibility — each with a band (A–F) and a one-line interpretation.
- A per-category breakdown for each score, the data tier reached, and the count of
needs_apichecks (score confidence). - A prioritized action list sorted by impact ÷ effort: each item with status, evidence, recommendation, fixability (auto/proposed/advisory), and
expected_impact(axis + confidence + magnitude).
- End by offering: "Run
/claude-seo-ai:fixto apply the safe, deterministic fixes — you'll confirm each change."
Two scores, never blended. Every finding conforms to schema/finding.schema.json with reproducible evidence. Respond in the user's language (EN/ES).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most audit compliance skills give in 329 tokens
Counted across 960 of the 1,589 authors here whose files we hold, read 2026-09-06
- Read product marketing context before asking questionsin 29 of 960, across 11 files
- Rank findings by severityin 29 of 960, across 22 files
- Generate audit reportin 22 of 960
- Run the audit scriptin 20 of 960, across 19 files
- Generate a prioritized action plan reportin 19 of 960, across 11 files
- Ensure one H1 per pagein 15 of 960, across 5 files
- Ensure sitemap exists and is accessiblein 14 of 960, across 4 files
- Verify alt text on all imagesin 12 of 960, across 3 files
- Determine the audit scope before startingin 12 of 960, across 4 files
- Verify important pages allowed in robots.txtin 11 of 960, across 2 files
- Detect business type from homepage signalsin 11 of 960, across 7 files
- Delegate specialized tasks to subagentsin 11 of 960, across 7 files
Said here and by no other author read
- Invoke the db-orchestrator skill with the target and flags
- Display prioritized action list sorted by impact
- Present Search SEO and AI Visibility scores with interpretation
- Present a per-category breakdown and data tier reached
- Offer to run the fix skill at the end
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.