{"slug":"onvoyage-ai-improve-aeo-geo","name":"improve-aeo-geo","description":"Audits a website codebase and makes code changes so AI engines (ChatGPT, Claude, Perplexity, Google AI Overviews) can better discover, parse, quote, and cite the site. Covers structured data, content structure, technical signals, and freshness.","long_description":"---\nname: improve-aeo-geo\ndescription: Audits a website codebase and makes code changes so AI engines (ChatGPT, Claude, Perplexity, Google AI Overviews) can better discover, parse, quote, and cite the site. Covers structured data, content structure, technical signals, and freshness.\n---\n\n# Improve Website AEO/GEO Skill\n\nYou are an expert at AI Engine Optimization (AEO) and Generative Engine Optimization (GEO). When invoked, you analyze the user's website codebase and make concrete, actionable code changes so AI agents — ChatGPT, Claude, Perplexity, Google AI Overviews, and others — can better discover, parse, quote, and cite the site.\n\nThe web is shifting from human-first to AI-first discovery. AI agents don't browse like humans. They extract structured data, scan for direct answers, and decide in milliseconds whether content is worth citing. This skill makes websites visible to that new audience.\n\n## Workflow\n\nWhen invoked on a codebase, follow this exact sequence:\n\n### Step 1: Baseline\n- If the user has a live URL, get a baseline score first. Run the **`audit-website-aeo`** skill for a local crawl + scored report, or use the hosted [aeo-audit.sh](https://aeo-audit.sh). If an `aeo_audit_report.md` already exists, read it — its prioritized fixes and weakest pages tell you exactly what to fix.\n- If no URL is available, proceed with a code-level audit.\n\n### Step 2: Discover the stack\n- Identify the framework (Next.js, Nuxt, Astro, SvelteKit, Remix, WordPress, Hugo, Jekyll, 11ty, plain HTML)\n- Find where `` is managed (layout files, document components, plugins, theme files)\n- Find where content lives (pages, MDX/MD files, CMS templates, components, PHP templates)\n- Check for existing SEO plugins/packages (next-seo, @astrojs/sitemap, Yoast, etc.)\n- Check if the site uses SSR, SSG, or client-side rendering\n\n### Step 3: Audit existing state\nRun through all checks below. For each failing check, note the file(s) to modify and the specific fix.\n\n### Step 4: Fix in priority order\nApply changes starting with Priority 1 (blockers), then work down. Make the smallest, most targeted changes needed.\n\n### Step 5: Verify\n- Re-run the audit (`audit-website-aeo` skill, or [aeo-audit.sh](https://aeo-audit.sh)) and compare against the Step 1 baseline to confirm the score improved\n- Target: 80+ overall score (B+ grade or higher)\n\n---\n\n## Scoring Model\n\nThe AEO audit score combines two halves:\n\n- **Foundational Score (50%)** — 16 deterministic checks, pass/fail per page, aggregated site-wide (80%+ pages must pass)\n- **Intelligence Score (50%)** — 6 LLM-evaluated content quality dimensions (0-5 scale)\n\n**Final Score** = 50% Foundational + 50% Intelligence → letter grade (A+ = 95-100, A = 90-94, B+ = 80-84, ..., F = below 40).\n\n---\n\n## Priority 1: Blockers (fix these first)\n\n### AI Bot Access (12 pts)\n\nrobots.txt must NOT block these 9 AI crawlers: `GPTBot`, `ClaudeBot`, `PerplexityBot`, `Google-Extended`, `OAI-SearchBot`, `anthropic-ai`, `ChatGPT-User`, `Bytespider`, `CCBot`.\n\n**Fix**: Open `robots.txt` (project root, `public/robots.txt`, or framework equivalent). Remove any `Disallow` rules for these bots. If no robots.txt exists, create one:\n\n```txt\nUser-agent: *\nAllow: /\n\nUser-agent: GPTBot\nAllow: /\n\nUser-agent: ClaudeBot\nAllow: /\n\nUser-agent: PerplexityBot\nAllow: /\n\nUser-agent: Google-Extended\nAllow: /\n\nUser-agent: OAI-SearchBot\nAllow: /\n\nUser-agent: anthropic-ai\nAllow: /\n\nUser-agent: ChatGPT-User\nAllow: /\n\nUser-agent: Bytespider\nAllow: /\n\nUser-agent: CCBot\nAllow: /\n\nSitemap: https://YOURDOMAIN.com/sitemap.xml\n```\n\nIf AI bots are blocked, nothing else matters. This is the #1 prerequisite.\n\n### AI-Accessible Meta Tags (6 pts)\n\nPages must NOT have `nosnippet`, `noai`, or `noimageai` in robots meta tags or `X-Robots-Tag` headers. Search for these and remove from public content pages.\n\n### Indexability (10 pts)\n\nPages must NOT have `` on public-facing pages. Search codebase for `noindex` and remove where inappropriate.\n\n---\n\n## Priority 2: High-Impact Structure\n\n### Structured Data / JSON-LD (8 pts)\n\nEvery page needs at least 1 `