skills/geo-audit/SKILL.md
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.
npx skillsauth add kennyolofsson23-netizen/claude-code-config geo-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill performs a comprehensive Generative Engine Optimization (GEO) audit of any website. GEO is the practice of optimizing web content so that AI systems (ChatGPT, Claude, Perplexity, Gemini, etc.) can discover, understand, cite, and recommend it. This audit measures how well a site performs across all GEO dimensions and produces an actionable improvement plan.
Traditional SEO optimizes for search engine rankings. GEO optimizes for AI citation and recommendation. Sites that score high on GEO metrics see 30-115% more visibility in AI-generated responses (Georgia Tech / Princeton / IIT Delhi 2024 study). The two disciplines overlap but have distinct requirements.
Step 1: Fetch Homepage and Detect Business Type
Use WebFetch to retrieve the homepage at the provided URL.
Extract the following signals:
Classify the business type using these patterns:
| Business Type | Detection Signals | |---|---| | SaaS | Pricing page, "Sign up" / "Free trial" CTAs, app.domain.com subdomain, feature comparison tables, integration pages | | Local Business | Physical address on homepage, Google Maps embed, "Near me" content, LocalBusiness schema, service area pages | | E-commerce | Product listings, shopping cart, product schema, category pages, price displays, "Add to cart" buttons | | Publisher | Blog-heavy navigation, article schema, author pages, date-based archives, RSS feeds, high content volume | | Agency/Services | Case studies, portfolio, "Our Work" section, team page, client logos, service descriptions | | Hybrid | Combination of above signals -- classify by dominant pattern |
Step 2: Crawl Sitemap and Internal Links
/sitemap.xml and /sitemap_index.xml.<a href> links pointing to the same domainrobots.txt directives -- do not fetch disallowed paths.Step 3: Collect Page-Level Data
For each page in the crawl set, record:
Delegate analysis to 5 specialized subagents. Each subagent operates on the collected page data and produces a category score (0-100) plus findings.
Subagent 1: AI Citability Analysis (geo-citability)
Subagent 2: Platform & Brand Analysis (geo-brand-mentions)
Subagent 3: Technical GEO Infrastructure (geo-crawlers + geo-llmstxt)
Subagent 4: Content E-E-A-T Quality (geo-content)
Subagent 5: Schema & Structured Data (geo-schema)
The overall GEO Score (0-100) is a weighted average of six category scores:
| Category | Weight | What It Measures | |---|---|---| | AI Citability | 25% | How quotable/extractable content is for AI systems | | Brand Authority | 20% | Third-party mentions, entity recognition signals | | Content E-E-A-T | 20% | Experience, Expertise, Authoritativeness, Trustworthiness | | Technical GEO | 15% | AI crawler access, llms.txt, rendering, speed | | Schema & Structured Data | 10% | Schema.org markup quality and completeness | | Platform Optimization | 10% | Presence on platforms AI models train on and cite |
Formula:
GEO_Score = (Citability * 0.25) + (Brand * 0.20) + (EEAT * 0.20) + (Technical * 0.15) + (Schema * 0.10) + (Platform * 0.10)
| Score Range | Rating | Interpretation | |---|---|---| | 90-100 | Excellent | Top-tier GEO optimization; site is highly likely to be cited by AI | | 75-89 | Good | Strong GEO foundation with room for improvement | | 60-74 | Fair | Moderate GEO presence; significant optimization opportunities exist | | 40-59 | Poor | Weak GEO signals; AI systems may struggle to cite or recommend | | 0-39 | Critical | Minimal GEO optimization; site is largely invisible to AI systems |
Every issue found during the audit is classified by severity:
Generate a file called GEO-AUDIT-REPORT.md with the following structure:
# GEO Audit Report: [Site Name]
**Audit Date:** [Date]
**URL:** [URL]
**Business Type:** [Detected Type]
**Pages Analyzed:** [Count]
---
## Executive Summary
**Overall GEO Score: [X]/100 ([Rating])**
[2-3 sentence summary of the site's GEO health, biggest strengths, and most critical gaps.]
### Score Breakdown
| Category | Score | Weight | Weighted Score |
|---|---|---|---|
| AI Citability | [X]/100 | 25% | [X] |
| Brand Authority | [X]/100 | 20% | [X] |
| Content E-E-A-T | [X]/100 | 20% | [X] |
| Technical GEO | [X]/100 | 15% | [X] |
| Schema & Structured Data | [X]/100 | 10% | [X] |
| Platform Optimization | [X]/100 | 10% | [X] |
| **Overall GEO Score** | | | **[X]/100** |
---
## Critical Issues (Fix Immediately)
[List each critical issue with specific page URLs and recommended fix]
## High Priority Issues
[List each high-priority issue with details]
## Medium Priority Issues
[List each medium-priority issue]
## Low Priority Issues
[List each low-priority issue]
---
## Category Deep Dives
### AI Citability ([X]/100)
[Detailed findings, examples of good/bad passages, rewrite suggestions]
### Brand Authority ([X]/100)
[Platform presence map, mention volume, sentiment]
### Content E-E-A-T ([X]/100)
[Author quality, source citations, freshness, depth]
### Technical GEO ([X]/100)
[Crawler access, llms.txt, rendering, headers]
### Schema & Structured Data ([X]/100)
[Schema types found, validation results, missing opportunities]
### Platform Optimization ([X]/100)
[Presence on YouTube, Reddit, Wikipedia, etc.]
---
## Quick Wins (Implement This Week)
1. [Specific, actionable quick win with expected impact]
2. [Another quick win]
3. [Another quick win]
4. [Another quick win]
5. [Another quick win]
## 30-Day Action Plan
### Week 1: [Theme]
- [ ] Action item 1
- [ ] Action item 2
### Week 2: [Theme]
- [ ] Action item 1
- [ ] Action item 2
### Week 3: [Theme]
- [ ] Action item 1
- [ ] Action item 2
### Week 4: [Theme]
- [ ] Action item 1
- [ ] Action item 2
---
## Appendix: Pages Analyzed
| URL | Title | GEO Issues |
|---|---|---|
| [url] | [title] | [issue count] |
development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
testing
Full QA pass: run all tests, check types, catch regressions, write missing tests. Use when the user says "run tests", "QA", "verify changes", "check for regressions", "test everything", or "make sure it works".
development
Provides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.
development
Initialize a new project with Kenny's universal conventions and stack-appropriate infrastructure. Use this skill whenever: setting up a new project, creating a new repo, scaffolding a new app, starting fresh on a new idea, 'init project', 'new project', 'set up a new app', 'create a project for X', or any variant of starting a new codebase from scratch. Also trigger when the user says 'bootstrap', 'scaffold', or 'kickstart'. This skill ensures every project gets the same quality gates and conventions while adapting infrastructure to the chosen stack.