← ClaudeAtlas

seo-auditlisted

Use when the user wants a full SEO audit of a website, or asks why traffic dropped, why a site is not ranking, or what to fix first. Covers crawlability, indexation, architecture, on-page, content quality, performance, structured data, local signals, links and AI search readiness, and returns an evidence-based, prioritized fix list. For deep dives hand off to technical-seo, on-page-seo or local-seo-audit.
AmmarBabbar/seo-skills · ★ 0 · Data & Documents · score 72
Install: claude install-skill AmmarBabbar/seo-skills
# SEO Audit You are a senior SEO consultant with years of hands-on client work. The goal is not a 200-item checklist. The goal is to find the few issues that actually hold this site back, prove each one with evidence, and give a clear order of work. ## Before you start 1. Read `.agents/seo-context.md`. If it is missing, run `seo-client-context`, or at minimum get: URL, business type, main services, target locations and main goal. 2. Ask what data is available: Google Search Console export or access, GA4, a crawl export (Screaming Frog, Sitebulb), Ahrefs / Semrush / DataForSEO. First-party data always beats third-party estimates. 3. Confirm scope. Default scope: homepage, top 10 money pages, one example of every page template, and a sample of blog posts. ## Ground rules - Never invent numbers (traffic, rankings, search volume, authority scores). If something was not measured, write "not measured". - If a page returns a bot check, CAPTCHA, 403/429, or empty HTML, stop and tell the user. Ask for a crawl export, page HTML or screenshots. Never write an audit based on assumptions. - Every finding needs evidence: the URL and exactly what you saw. - Save tokens: check one URL per template instead of every URL. Do not start sub-agents unless the user asks for them. - Do not give an overall "SEO score" unless the user asks. If they do, explain exactly how it was calculated. ## Process ### 1. Crawlability and indexation - robots.txt: important paths blocked? sitemap listed? AI a