# Improve Aeo Geo > 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. - **Type:** Skill - **Install:** `agentstack add skill-onvoyage-ai-gtm-engineer-skills-improve-aeo-geo` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [onvoyage-ai](https://agentstack.voostack.com/s/onvoyage-ai) - **Installs:** 0 - **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [onvoyage-ai](https://github.com/onvoyage-ai) - **Source:** https://github.com/onvoyage-ai/gtm-engineer-skills/tree/main/improve-aeo-geo ## Install ```sh agentstack add skill-onvoyage-ai-gtm-engineer-skills-improve-aeo-geo ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # 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 `` 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. ### Step 5: Verify - 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 - Target: 80+ overall score (B+ grade or higher) --- ## Scoring Model The AEO audit score combines two halves: - **Foundational Score (50%)** — 16 deterministic checks, pass/fail per page, aggregated site-wide (80%+ pages must pass) - **Intelligence Score (50%)** — 6 LLM-evaluated content quality dimensions (0-5 scale) **Final Score** = 50% Foundational + 50% Intelligence → letter grade (A+ = 95-100, A = 90-94, B+ = 80-84, ..., F = below 40). --- ## Priority 1: Blockers (fix these first) ### AI Bot Access (12 pts) robots.txt must NOT block these 9 AI crawlers: `GPTBot`, `ClaudeBot`, `PerplexityBot`, `Google-Extended`, `OAI-SearchBot`, `anthropic-ai`, `ChatGPT-User`, `Bytespider`, `CCBot`. **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: ```txt User-agent: * Allow: / User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: OAI-SearchBot Allow: / User-agent: anthropic-ai Allow: / User-agent: ChatGPT-User Allow: / User-agent: Bytespider Allow: / User-agent: CCBot Allow: / Sitemap: https://YOURDOMAIN.com/sitemap.xml ``` If AI bots are blocked, nothing else matters. This is the #1 prerequisite. ### AI-Accessible Meta Tags (6 pts) Pages 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. ### Indexability (10 pts) Pages must NOT have `` on public-facing pages. Search codebase for `noindex` and remove where inappropriate. --- ## Priority 2: High-Impact Structure ### Structured Data / JSON-LD (8 pts) Every page needs at least 1 `` block. Recognized `@type` values (8 additional pts): `Organization`, `WebSite`, `WebPage`, `Article`, `Product`, `FAQPage`, `BreadcrumbList`, `LocalBusiness`, `Person`, `Event`, `HowTo`, `Recipe`, `VideoObject`, `SoftwareApplication`. Minimum setup: - **Site-wide**: Organization schema in the root layout - **Homepage**: WebSite schema with SearchAction - **Blog posts**: Article schema with author, datePublished, dateModified - **Product pages**: Product schema - **FAQ sections**: FAQPage schema ### Page Titles (10 pts) Every `` must be 10+ characters. Each page needs a unique, descriptive title. Format: `[Page Topic] | [Brand]`. Aim for 50-60 characters. ### Meta Descriptions (10 pts) Every page needs `` with 50+ characters. Write unique descriptions (120-160 chars ideal). Lead with the answer/value, not filler. ### Text Depth (12 pts) Each page needs 250+ words of readable body text (excluding nav, footer, boilerplate). Aim for 500-2000 words on key pages. Articles over 2,900 words average 5.1 AI citations vs. 3.2 for under 800 words (SE Ranking, 2025 — 2.3M pages analyzed). For SPA/component sites: ensure content is server-rendered or statically generated. ### llms.txt (10 pts) Create `/.well-known/llms.txt` with a heading, links, and 100+ characters: ```markdown # [Your Site Name] > Brief description of what your site/product does. ## Documentation - [Getting Started](https://yourdomain.com/docs/getting-started) - [API Reference](https://yourdomain.com/docs/api) ## Key Pages - [About](https://yourdomain.com/about) - [Pricing](https://yourdomain.com/pricing) - [Blog](https://yourdomain.com/blog) ## Policies - [Terms of Service](https://yourdomain.com/terms) - [Privacy Policy](https://yourdomain.com/privacy) ``` Also consider creating `llms-full.txt` with the complete content of key pages inlined for direct LLM consumption. --- ## Priority 3: Content Quality ### Heading Hierarchy (6 pts) Proper H1 → H2 → H3 nesting. Exactly 1 `` per page (8 pts). 2+ heading levels. No skips (H1 → H3 without H2 is wrong). Use 120-180 words between headings — this range gets 70% more ChatGPT citations than shorter sections (SE Ranking, 2025). ### Internal Linking (10 pts) 5+ internal links per page. Use descriptive anchor text. Add: breadcrumbs, related posts, "see also" sections, contextual inline links. ### Canonical URL (8 pts) Every page needs `` with an absolute URL. Handle trailing slashes consistently. ### Open Graph (8 pts) Every page needs `og:title` and `og:description`. Also add `og:image`, `og:url`, `og:type`. ### Image Alt Coverage (8 pts) 80%+ of `` tags must have `alt` attributes. Decorative images: `alt=""`. Alt text should describe the **conclusion**, not the visual form. AI engines and screen readers both need the takeaway: - BAD: `alt="bar chart"` or `alt="graph showing results"` - GOOD: `alt="GEO-optimized pages earn 41% more AI citations (KDD 2024, N=10K queries)"` For charts and data visuals: the image alone is invisible to LLMs. Every chart needs a text summary and HTML data table alongside it — that's what AI actually cites. Use the **create-geo-charts** skill for data visualizations that need the full GEO text layer. ### RSS/Atom Feed (8 pts) Publish a feed and add the discovery link: ```html ``` ### Sitemap with lastmod Not scored directly but critical for freshness signals. Generate `sitemap.xml` with `` dates. Reference it from robots.txt. --- ## Priority 4: GEO Content Optimization These strategies are backed by peer-reviewed research from the GEO paper (Aggarwal et al., KDD 2024 — Princeton, Georgia Tech, IIT Delhi, Allen AI) and large-scale industry studies. ### Add Quotations from Authoritative Sources (+41% visibility) The single most effective GEO strategy. Include direct quotes from experts, studies, or official sources. This is the #1 optimization per the GEO paper. ``` WEAK: "Experts say this approach works well." STRONG: "As Dr. Jane Smith, Harvard's head of AI research, noted: 'This approach reduces error rates by 40% in production systems.'" ``` ### Add Statistics and Data Points (+33% visibility) The #2 GEO strategy. Include specific numbers, percentages, dates, and measurements. Every 150-200 words should contain at least one data point. ``` WEAK: "Our platform is significantly faster." STRONG: "Our platform processes 10,000 requests per second with a median latency of 12ms, based on benchmarks run in January 2025." ``` ### Cite Sources with In-Text References (+28% visibility) The #3 GEO strategy. Name sources inline. Link to studies, reports, and official documentation. ``` WEAK: "Studies show this is effective." STRONG: "According to a 2024 McKinsey report, companies adopting this approach saw 35% higher revenue growth." ``` **Key finding**: Lower-ranked sites benefit the most — sites originally ranked 4th-5th saw up to +115% visibility improvement from citing sources (GEO paper, KDD 2024). ### Answer-First Content Structure 44.2% of ChatGPT citations come from the first 30% of page content (Kevin Indig, Growth Memo, 2026 — 1.2M AI answers analyzed). Lead every section with the direct answer: ``` [H2: Question-format heading] [1-2 sentence direct answer] [Supporting detail with evidence] [Statistic or source citation] [Internal link to related content] ``` **Before**: "Our company was founded in 2015 with a vision to transform..." **After**: "[Product] is a [category] tool that [primary function]. It helps [audience] achieve [specific outcome], reducing [metric] by [X]%." ### FAQ Sections Pages with FAQ sections average 4.9 AI citations vs. 4.4 without (SE Ranking, 2025 — 2.3M pages). The FAQ *content* matters more than FAQ schema markup. Add both: ```html Frequently Asked Questions What is [topic]? [Direct answer]. [Supporting detail with evidence]. How does [topic] work? [Step-by-step explanation]. ``` Plus FAQPage JSON-LD schema for the section. ### Quotable Blocks Write self-contained paragraphs that make sense when extracted in isolation: - 40-60 words per block - No pronouns referring to prior context ("it", "this") - Name the subject explicitly - End with a concrete fact or number - Use comparison tables, numbered lists, and definition blocks ### Freshness Signals AI agents cite fresher content. Content updated within 3 months averages 6 citations vs. 3.9 for 2+ year old content (SE Ranking, 2025). AI assistants cite content 25.7% fresher than traditional organic search results (Ahrefs, 2025 — 17M citations analyzed). Add to every content page: ```html ``` Show "Last updated: [date]" visibly on the page. Maintain a blog or changelog with regular updates. ### Structural Clarity Use semantic HTML: ``, ``, ``, ``, ``. Content with clear H2/H3 hierarchy is 2.8x more likely to earn citations (AirOps, 2025). Ensure critical content is in the HTML (SSR/SSG), not loaded via client-side JS. --- ## Framework-Specific Patterns ### Next.js (App Router) **Metadata** (`app/page.tsx` or `app/layout.tsx`): ```typescript import type { Metadata } from 'next' export const metadata: Metadata = { title: 'Page Title | Brand', description: 'Descriptive meta description of 120-160 characters.', alternates: { canonical: 'https://yourdomain.com/page' }, openGraph: { title: 'Page Title', description: 'Social sharing description.', url: 'https://yourdomain.com/page', images: [{ url: 'https://yourdomain.com/og-image.jpg' }], }, robots: { index: true, follow: true }, } ``` **JSON-LD**: ```tsx export default function Page() { const jsonLd = { '@context': 'https://schema.org', '@type': 'Article', headline: 'Article Title', datePublished: '2025-01-15', dateModified: '2025-06-01', author: { '@type': 'Person', name: 'Author Name' }, } return ( <> Article Title{/* Content */} ) } ``` **robots.txt** (`app/robots.ts`): ```typescript import type { MetadataRoute } from 'next' export default function robots(): MetadataRoute.Robots { return { rules: [ { userAgent: '*', allow: '/' }, { userAgent: 'GPTBot', allow: '/' }, { userAgent: 'ClaudeBot', allow: '/' }, { userAgent: 'PerplexityBot', allow: '/' }, { userAgent: 'Google-Extended', allow: '/' }, { userAgent: 'OAI-SearchBot', allow: '/' }, { userAgent: 'anthropic-ai', allow: '/' }, { userAgent: 'ChatGPT-User', allow: '/' }, { userAgent: 'Bytespider', allow: '/' }, { userAgent: 'CCBot', allow: '/' }, ], sitemap: 'https://yourdomain.com/sitemap.xml', } } ``` **Sitemap** (`app/sitemap.ts`): ```typescript import type { MetadataRoute } from 'next' export default function sitemap(): MetadataRoute.Sitemap { return [ { url: 'https://yourdomain.com', lastModified: new Date(), changeFrequency: 'weekly', priority: 1 }, { url: 'https://yourdomain.com/about', lastModified: new Date(), changeFrequency: 'monthly', priority: 0.8 }, ] } ``` ### Nuxt 3 **Metadata** (in `app.vue` or page components): ```vue useSeoMeta({ title: 'Page Title | Brand', description: 'Descriptive meta description.', ogTitle: 'Page Title', ogDescription: 'Social sharing description.', ogImage: 'https://yourdomain.com/og-image.jpg', }) useHead({ link: [{ rel: 'canonical', href: 'https://yourdomain.com/page' }], }) ``` **JSON-LD** (using `useSchemaOrg` from `nuxt-schema-org`): ```vue useSchemaOrg([ defineArticle({ headline: 'Article Title', datePublished: '2025-01-15', dateModified: '2025-06-01', author: { name: 'Author Name' }, }), ]) ``` ### SvelteKit **Metadata** (in `+page.svelte` or `+layout.svelte`): ```svelte Page Title | Brand ``` **JSON-LD**: ```svelte {@html `${JSON.stringify({ "@context": "https://schema.org", "@type": "Article", "headline": "Article Title", "datePublished": "2025-01-15" })}`} ``` ### Astro **Layout** (`src/layouts/Base.astro`): ```astro --- const { title, description, canonical, publishedDate } = Astro.props --- {title} {publishedDate && } ``` Use `@astrojs/sitemap` for automatic sitemap generation with lastmod. ### WordPress **functions.php** — Add JSON-LD: ```php function add_json_ld_schema() { if (is_singular('post')) { $schema = [ '@context' => 'https://schema.org', '@type' => 'Article', 'headline' => get_the_title(), 'datePublished' => get_the_date('c'), 'dateModified' => get_the_modified_date('c'), 'author' => ['@type' => 'Person', 'name' => get_the_author()], ]; echo '' . json_encode($schema) . ''; } } add_action('wp_head', 'add_json_ld_schema'); ``` **robots.txt** — WordPress manages via Settings > Reading. Add AI bot rules via a plugin (Yoast, Rank Math) or a custom `robots.txt` in the web root. **llms.txt** — Create `.well-known/llms.txt` in the WordPress root directory, or use a plugin/rewrite rule. ### Hugo **Metadata** (in `layouts/partials/head.html`): ```html {{ .Title }} | {{ .Site.Title }} {{ if .Date }}{{ end }} {{ if .Lastmod }}{{ end }} ``` **JSON-LD** (in `layouts/partials/schema.html`): ```html {{ if .IsPage }} { "@context": "https://schema.org", "@type": "Article", "headline": "{{ .Title }}", "datePublished": "{{ .Date.Format "2006-01-02" }}", "dateModified": "{{ .Lastmod.Format "2006-01-02" }}", "author": { "@type": "Person", "name": "{{ .Params.author | default .Site.Params.author }}" } } {{ end }} ``` Hugo generates RSS at `/index.xml` by default. Use `hugo --minify` for clean HTML output. ### Jekyll / 11ty **Jekyll** — Use `jekyll-seo-tag` and `jekyll-sitemap` gems. Add JSON-LD in `_includes/head.html`. RSS via `jekyll-feed` gem. **11ty** — Use `@11ty/eleventy-plugin-rss` for feeds. Add metadata via Nunjucks/Liquid templates in `_includes/base.njk`. Generate sitemap with a custom template or `eleventy-plugin-sitemap`. ### Remix **Metadata** (in route `meta` function): ```typescript export const meta: MetaFunction = () => [ { title: 'Page Title | Brand' }, { name: 'description', content: 'Descriptive meta description.' }, { property: 'og:title', content: 'Page Title' }, { property: … ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [onvoyage-ai](https://github.com/onvoyage-ai) - **Source:** [onvoyage-ai/gtm-engineer-skills](https://github.com/onvoyage-ai/gtm-engineer-skills) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-onvoyage-ai-gtm-engineer-skills-improve-aeo-geo - Seller: https://agentstack.voostack.com/s/onvoyage-ai - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.