← ClaudeAtlas

seo-geo-auditlisted

Runs a complete SEO + GEO audit of any website, covering technical health, tags, images, site architecture, content, keywords, e-commerce, local, backlinks, and AI visibility (ChatGPT, Perplexity, Google AI Overviews), then delivers a prioritized action plan or a plain-language summary. Use this skill whenever the user gives a URL and wants to know what to improve, asks to audit or review a site, asks why a site does not rank or never gets mentioned by AI assistants, wants to compare a site against competitors, or asks "what is wrong with my site" or "is my site ready for SEO". Also use it to establish a baseline before any larger SEO project. After the audit, hand off deep work to the specialized skills (seo-technical, seo-content-blog, seo-backlinks, geo-visibility, geo-tracking).
Thibaultbm/claude-seo-geo · ★ 2 · AI & Automation · score 78
Install: claude install-skill Thibaultbm/claude-seo-geo
# Full SEO + GEO site audit Audit a website the way a senior practitioner does: collect verifiable facts first, judge them against a field-tested checklist, benchmark against the competitors that actually rank, and deliver a short list of fixes ordered by impact. The methodology was distilled from 115+ real agency audit calls and updated with sourced 2025-2026 evidence on AI search. ## Company knowledge first (Obsidian) If the working environment contains an Obsidian vault or any local knowledge base (a folder of .md notes, often with a .obsidian directory), read the relevant notes before acting: brand and product facts, target keywords, competitors, and the SEO action log of what was already tried. Ground every recommendation in that context instead of asking the user for facts the vault already holds. At the end of the session, append the actions taken to the vault's SEO action log so the next session starts informed. Vault structure, read-first and write-back protocols: the obsidian-brain skill. ## Why this audit is different 1. Facts before judgment. Every claim in the final report must trace back to something measured (by the bundled script, a browser check, or data the owner provided). Never guess a title length or assume a sitemap exists. 2. Competitors over abstract thresholds. "Your page has 400 words" means nothing alone. "The three sites outranking you average 1200 words on this query" is a finding. When competitors are known, benchmark page versus page. 3. Tw