# Improve Aeo Geo

Audits a website codebase and makes code changes so AI engines (ChatGPT, Claude...

- Repository: https://github.com/onvoyage-ai/gtm-engineer-skills (1345 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-11
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add onvoyage-ai/gtm-engineer-skills --skill improve-aeo-geo -g -a claude-code -y`
Codex: `npx skills add onvoyage-ai/gtm-engineer-skills --skill improve-aeo-geo -g -a codex -y`
Cursor: `npx skills add onvoyage-ai/gtm-engineer-skills --skill improve-aeo-geo -g -a cursor -y`
Gemini CLI: `npx skills add onvoyage-ai/gtm-engineer-skills --skill improve-aeo-geo -g -a gemini-cli -y`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Improve Website AEO/GEO Skill

You 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.

The 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.

## Workflow

When invoked on a codebase, follow this exact sequence:

### Step 1: Baseline
- 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.
- If no URL is available, proceed with a code-level audit.

### Step 2: Discover the stack
- Identify the framework (Next.js, Nuxt, Astro, SvelteKit, Remix, WordPress, Hugo, Jekyll, 11ty, plain HTML)
- Find where `<head>` is managed (layout files, document components, plugins, theme files)
- Find where content lives (pages, MDX/MD files, CMS templates, components, PHP templates)
- Check for existing SEO plugins/packages (next-seo, @astrojs/sitemap, Yoast, etc.)
- Check if the site uses SSR, SSG, or client-side rendering

### Step 3: Audit existing state
Run through all checks below. For each failing check, note the file(s) to modify and the specific fix.

### Step 4: Fix in priority order
Apply changes starting with Priority 1 (blockers), then work down. Make the smallest, most targeted changes needed.

The rest: https://github.com/onvoyage-ai/gtm-engineer-skills/blob/HEAD/improve-aeo-geo/SKILL.md