← ClaudeAtlas

seo-auditlisted

Run a complete SEO audit for any domain and any size of site using the Ahrefs connector plus a live on-page crawl, then automatically build the client-ready branded report (PDF + editable docx + implementation sheet) without being asked. Use whenever someone asks for an SEO audit, asks "how is [domain] doing in search", wants a site's rankings, keywords, backlinks, domain rating or traffic checked, wants keyword opportunities, asks why a site isn't ranking, or wants competitive SEO analysis. Also trigger for AI visibility questions — whether a brand shows up in ChatGPT, Perplexity, Gemini or AI Overviews — when someone names a client site and asks to "pull the SEO numbers" or "find quick wins", and when someone asks how to connect Ahrefs to Claude (setup included). Always use this skill for SEO diagnostic work: it encodes the Ahrefs call sequence, schema gotchas, claim-verification discipline and analysis framework.
chadjardine/seo-audit-skill · ★ 0 · AI & Automation · score 70
Install: claude install-skill chadjardine/seo-audit-skill
# SEO Audit Runs a structured SEO audit combining Ahrefs data with a direct on-page crawl, synthesizes a diagnosis and prioritized recommendations, then **always builds the client-ready report and implementation sheet** as the final step. The audit answers one core question: **what is the binding constraint on this site's organic growth — authority, on-page, content, technical, or greenfield — and what's the highest-leverage fix?** **This file is self-contained.** Ahrefs schemas, AI-visibility rulings, connector setup, the report design spec, the full report-builder source, and the brand logomarks are all in the appendices. There are no sibling `assets/` or `references/` files, and **no dependency on any other skill**. The only external requirement is the Ahrefs connector, which Phase 0 checks. **It is also client-agnostic.** Site size, market, business model, property boundaries and delivering agency are all variables — Phase 0b sets them, and getting them wrong is the most common way this skill produces a confident but useless deliverable. --- ## Claim discipline — read before writing a single finding This becomes a client-facing document that a developer or in-house SEO will read adversarially. Every rule below exists because it was violated on a real engagement and produced a wrong deliverable. **1. Empty is not absent.** A failed, timed-out, blocked or empty tool response is never evidence that something does not exist. Every negative finding — "there is no robot