geo
Skill9 starsChanged 7 months agoMITView on GitHub
GEO Audit Toolkit — evidence-based Generative Engine Optimization audit for websites. Diagnostic-only (no commercial framing): produces a multi-page audit with per-LLM presence assessment (ChatGPT/Google, Gemini/Google, Perplexity/multi, Claude/Brave, Le Chat/Brave), a unified action plan with per-LLM impact tags, and technical appendices. Use when the user says "geo", "audit", "AI search", "AI visibility", "schema", "BLUF", or provides a URL for analysis.
22 other projects use a version of this.
Adopted by
Most recently taken up by
- alpit-patel/seo-aeo-geo-kittheir own version, first seen Nov 8, 2026
- cihantopac/searvextheir own version, first seen Nov 8, 2026
- sneakers-the-rat/muse-skillstheir own version, first seen Nov 1, 2026
- Hainrixz/claude-seo-aitheir own version, first seen Nov 1, 2026
- flavien-ia/hypervibe-crafttheir own version, first seen Oct 25, 2026
- flavien-ia/hypervibe-harnesstheir own version, first seen Oct 23, 2026
Used with
Projects with it also use geo-report-pdf, geo-technical and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
kennyolofsson23-netizenSkillgeo-report-pdf
Generate a professional PDF report from GEO audit data using ReportLab. Creates a polished, client-ready PDF with score gauges, bar charts, platform readiness visualizations, color-coded tables, and prioritized action plans.
Also in 5 projects that use this
kennyolofsson23-netizenSkillgeo-technical
Technical SEO audit with GEO-specific checks — crawlability, indexability, security, performance, SSR, and AI crawler access
Also in 5 projects that use this
- +8 more from kennyolofsson23-netizen
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- zubair-trabzada/geo-seo-claude★ 11ksame name
- liangdabiao/GEO-Content-Optimizer-Skill★ 183same name
- Hainrixz/claude-seo-ai★ 81same name
- flavien-ia/hypervibe-craft★ 50same name
- flavien-ia/hypervibe-harness★ 50same name
- rainday/smart-blog-skills★ 35same name
- sneakers-the-rat/muse-skills★ 24same name
- techhorizonlabs/thl-open★ 16same name
- yuanhao667/Skills★ 10same name
- melgarafael/youtube-growth★ 8same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- geo-auditSkill
- geo-clientSkill
- geo-content-healthSkill
- geo-crawlersSkill
- geo-rrfSkill
- geo-schemaSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 90
Every audit lands in site-client/<slug>/audits/<YYYY-MM-DD>-audit.md.
- Very specific: line 128
Audit-only: no pricing tiers, no MRR projections, no "client-ready" framing.
- Very specific: line 130
Evidence triage: every finding tagged with confidence (high → experimental).
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GEO Audit Toolkit — Claude Code skill
Philosophy: audit-only, evidence-based, no sales framing. Findings are reported in
severity × confidence × per-LLM impact, never in pricing tiers or revenue projections.
Single command
/geo audit <url> [--positioning "<query>"] [--vs comp1.com,comp2.com] [--output-lang fr|en]Examples:
# Audit with positioning + 2 competitors, output in French
/geo audit https://example.com --positioning "agence powerpoint" --vs mprez.fr,laboiteaslides.fr --output-lang fr
# Audit without RRF measurement (on-page only)
/geo audit https://example.comInternally calls python3 -m scripts.run_audit <url> .... The orchestrator is
sequential (not parallel-subagent) and produces a single Markdown audit at
site-client/<slug>/audits/<date>-audit.md.
Per-LLM retrieval map (rev. 2026-04-26)
| LLM (in scope) | Backend | Engine in audit |
| ChatGPT / SearchGPT | Google (OpenAI–Google deal 2025) | google (Startpage proxy) |
| Gemini / Google AI Overviews | google | |
| Perplexity | Multi (Google + Brave) | google + brave |
| Claude | Brave (Anthropic–Brave 2025) | brave |
| Le Chat (Mistral) | Brave (Brave–Mistral 2025) | brave |
Bing Copilot, Meta AI, Grok are out of scope (user decision, 2026-04-26).
Mapping validated empirically: 80–90% Google SERP similarity vs ~30% Bing
when comparing ChatGPT citations to scraper-baseline. See
docs/LLM_RETRIEVAL_ARCHITECTURE.md.
Audit pipeline (5 phases, sequential)
| Phase | What runs | Output |
| 1. Locale detection | scripts/site_locale.py (HTML lang → Content-Language → TLD → fallback) | fr-FR, en-US, etc. |
| 2. Multi-page sampling | scripts/site_crawler.py (sitemap + strategic diversity: home + service + article + about + case-study) | up to 8 pages |
| 3. Crawler audit (site-level) | scripts/checks/crawlers.py (robots.txt parse + 3-category bot taxonomy) | findings |
| 4. Per-page schema + content health | scripts/checks/schema.py + scripts/checks/content_health.py | findings per page |
5. RRF measurement (when --positioning) | scripts/rrf.py + scripts/serp/{google,brave}.py (10 fan-out queries × 2 engines) | per-LLM presence stats |
Audit output structure
1. État des lieux par LLM ← verdict table + 5 detail blocks
2. Plan d'action ← unified, per-LLM impact tags + experimental sub-bucket
3. Ce que l'audit ne mesure pas
Annexes techniques:
A. RRF mesuré (détail)
B. Politique des crawlers IA
C. Données structurées (schema)
D. Content health (BLUF, etc.)
E. Findings — vue agrégée
Glossaire techniqueEvery audit lands in site-client/<slug>/audits/<YYYY-MM-DD>-audit.md. Path
resolved via scripts/client_paths.py.
Active sub-skills (6)
| # | Skill | Wraps | Purpose |
| 1 | geo-audit | scripts/run_audit.py | Main orchestrator |
| 2 | geo-schema | scripts/checks/schema.py | Schema.org + Enhanced Entity Pages audit |
| 3 | geo-content-health | scripts/checks/content_health.py | BLUF + Mount AI anti-patterns |
| 4 | geo-crawlers | scripts/checks/crawlers.py | robots.txt + 3-category bot taxonomy |
| 5 | geo-rrf | scripts/rrf.py | Reciprocal Rank Fusion measurement |
| 6 | geo-client | scripts/client_paths.py | Per-site folder manager (site-client/<slug>/) |
The fork dropped 9 upstream skills that did not fit the audit-only pivot
(geo-prospect, geo-proposal, geo-brand-mentions, geo-citability,
geo-llmstxt, geo-platform-optimizer, geo-technical, geo-content,
geo-report, geo-report-pdf, geo-compare). See tasks/lessons.md.
Local-only tooling
local/ is gitignored. Contains personal scripts that don't ship in the
public toolkit:
local/docx_export.py— convert audit Markdown to a styled.docx(Google Docs ready). Usage:python3 local/docx_export.py site-client/<slug>/audits/<date>-audit.md
Quality gates
- Audit-only: no pricing tiers, no MRR projections, no "client-ready"
framing. Findings carry
effort × score-gain × confidence. - Evidence triage: every finding tagged with confidence (
high→experimental). Single-study correlations and emerging patterns are flagged, not promoted to critical. - Free, no-setup: pipeline runs without paid APIs or signup. SERP scraping uses public interfaces (Google via Startpage proxy, Brave HTML).
- Output language follows audited site's locale (override with
--output-lang fr|en). - Per-LLM retrieval map re-verified every 6 months — partnership deals
change quickly. See
tasks/lessons.md(2026-04-26 entry).
Reference docs
docs/LLM_RETRIEVAL_ARCHITECTURE.md— per-LLM backend mappingdocs/CRAWLERS_TAXONOMY.md— 29 AI bots catalogueddocs/STRUCTURED_DATA_BEST_PRACTICES.md— Schema.org / EEP methodologydocs/CONTENT_HEALTH_PATTERNS.md— Mount AI anti-patterns + BLUFdocs/BRAVE_GRAIL_SIGNALS.md— Brave-rooted LLM evidence (Test #1 result)docs/sources/— 8 archived methodology articles with critical-thinking triage
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

