Audit Websites for AI Search Visibility with GEO SEO Claude
Use GEO SEO Claude when Claude Code should run repeatable AI-search and SEO audits with citability, crawler, schema, platform, and report workflows.
npx skills add agentskillexchange/skills --skill audit-websites-for-ai-search-visibility-with-geo-seo-claude
Use GEO SEO Claude when an operator wants Claude Code to audit a website for AI-search visibility and SEO foundations. The workflow exposes /geo commands for full audits, quick snapshots, citability scoring, AI crawler access checks, llms.txt analysis, brand mentions, platform readiness, schema analysis, technical SEO, content quality, reports, PDF reports, prospect tracking, proposals, and monthly comparison reports.
What this skill actually does
Invoke this instead of using a normal SEO product or a one-off prompt when the user wants Claude Code to inspect a specific site and produce repeatable, evidence-backed GEO/SEO findings or client-ready deliverables from the same command surface.
The scope boundary is website-focused AI-search audit and reporting inside Claude Code. It is not a generic crawler, broad SEO platform, marketing community listing, SDK, or product card. Its value is the repeatable Claude Code skill/subskill workflow around AI citation readiness, crawler access, structured data, and report generation.
Inputs and prerequisites: Claude Code CLI, Python 3.8+, Git, optional uv, optional Playwright for screenshots..
Setup notes: Use the upstream manual install path: clone https://github.com/zubair-trabzada/geo-seo-claude, change into the checkout, inspect the installer for your environment, then run ./install.sh on macOS/Linux or ./install-win.sh from Git Bash on Windows.
Source and verification boundary: use https://github.com/zubair-trabzada/geo-seo-claude#readme as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Claude Code workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.