New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Improve Aeo Geo

by onvoyage-ai in onvoyage-ai/gtm-engineer-skills

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.

MITAuto-check passedMarketing & SEO

Install Improve Aeo Geo

skills CLI
$ npx skills add onvoyage-ai/gtm-engineer-skills --skill improve-aeo-geo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install onvoyage-ai/gtm-engineer-skills improve-aeo-geo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/onvoyage-ai/gtm-engineer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/improve-aeo-geo .claude/skills/improve-aeo-geo && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
improve-aeo-geo
GitHub stars
1.3k
Token cost
~5.2k tokens
SKILL.md length
1,742 words
Files
4
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 5 steps: Baseline → Discover the stack → Audit existing state → …
  • Tasks that involve AI search optimization
  • SKILL.md covers Workflow, Scoring Model, Priority 1: Blockers (fix… and Priority 2: High-Impact…, plus 2 more sections
  • Reaches schema.org

What it does

Improve Aeo Geo is an agent skill from onvoyage-ai/gtm-engineer-skills. 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.

Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `README.md`, `examples/nextjs-blog-before-after.md` and `examples/wordpress-business-before-after.md`).

It sits in Marketing & SEO, covering AI search optimization and Schema markup. It works with OpenAI and Perplexity. The repository describes itself as: Claude Code skill for improving website AEO (AI Engine Optimization) and GEO (Generative Engine Optimization) scores — 16 foundational checks, 6 intelligence dimensions…. The licence is MIT.

When your agent uses it

  • Tasks that involve AI search optimization
  • Tasks that involve Schema markup

Example prompts

  • “Use the improve-aeo-geo skill to audit a website codebase and makes code changes so AI engines (ChatGPT, Claude, Perplexity, Google AI Overviews)…”
  • “/improve-aeo-geo”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Baseline
  2. Discover the stack
  3. Audit existing state
  4. Fix in priority order
  5. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 3777930. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are html, typescript, vue, svelte, markdown, astro and php).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • schema.org

    Also links to:

    • aeo-audit.sh
    • arxiv.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Improve Aeo Geo loads about 5.2k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 1,742 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~5.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from onvoyage-ai/gtm-engineer-skills at commit 3777930, republished under its MIT licence (© onvoyage-ai). 1,742 words, ~5,186 tokens.

Download SKILL.mdSave it as .claude/skills/improve-aeo-geo/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
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.

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

Step 5: Verify
  • Re-run the audit (audit-website-aeo skill, or 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 <meta name="robots" content="noindex"> 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 <script type="application/ld+json"> 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 <title> 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 <meta name="description"> 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 <h1> 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 <link rel="canonical" href="..."> 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 <img> 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
<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml" />
Sitemap with lastmod

Not scored directly but critical for freshness signals. Generate sitemap.xml with <lastmod> 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).

Show full SKILL.md (709 more words)Show less
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
<section>
  <h2>Frequently Asked Questions</h2>
  <h3>What is [topic]?</h3>
  <p>[Direct answer]. [Supporting detail with evidence].</p>
  <h3>How does [topic] work?</h3>
  <p>[Step-by-step explanation].</p>
</section>

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
<meta property="article:published_time" content="2025-01-15T00:00:00Z" />
<meta property="article:modified_time" content="2025-06-01T00:00:00Z" />

Show "Last updated: [date]" visibly on the page. Maintain a blog or changelog with regular updates.

Structural Clarity

Use semantic HTML: <main>, <article>, <section>, <nav>, <aside>. 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 (
    <>
      <script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }} />
      <article><h1>Article Title</h1>{/* Content */}</article>
    </>
  )
}

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
<script setup>
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' }],
})
</script>

JSON-LD (using useSchemaOrg from nuxt-schema-org):

vue
<script setup>
useSchemaOrg([
  defineArticle({
    headline: 'Article Title',
    datePublished: '2025-01-15',
    dateModified: '2025-06-01',
    author: { name: 'Author Name' },
  }),
])
</script>
SvelteKit

Metadata (in +page.svelte or +layout.svelte):

svelte
<svelte:head>
  <title>Page Title | Brand</title>
  <meta name="description" content="Descriptive meta description." />
  <link rel="canonical" href="https://yourdomain.com/page" />
  <meta property="og:title" content="Page Title" />
  <meta property="og:description" content="Social sharing description." />
</svelte:head>

JSON-LD:

svelte
<svelte:head>
  {@html `<script type="application/ld+json">${JSON.stringify({
    "@context": "https://schema.org",
    "@type": "Article",
    "headline": "Article Title",
    "datePublished": "2025-01-15"
  })}</script>`}
</svelte:head>
Astro

Layout (src/layouts/Base.astro):

astro
---
const { title, description, canonical, publishedDate } = Astro.props
---
<head>
  <title>{title}</title>
  <meta name="description" content={description} />
  <link rel="canonical" href={canonical} />
  <meta property="og:title" content={title} />
  <meta property="og:description" content={description} />
  {publishedDate && <meta property="article:published_time" content={publishedDate} />}
  <link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml" />
</head>

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 '<script type="application/ld+json">' . json_encode($schema) . '</script>';
  }
}
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>{{ .Title }} | {{ .Site.Title }}</title>
<meta name="description" content="{{ .Description }}" />
<link rel="canonical" href="{{ .Permalink }}" />
<meta property="og:title" content="{{ .Title }}" />
<meta property="og:description" content="{{ .Description }}" />
{{ if .Date }}<meta property="article:published_time" content="{{ .Date.Format "2006-01-02T15:04:05Z07:00" }}" />{{ end }}
{{ if .Lastmod }}<meta property="article:modified_time" content="{{ .Lastmod.Format "2006-01-02T15:04:05Z07:00" }}" />{{ end }}

JSON-LD (in layouts/partials/schema.html):

html
{{ if .IsPage }}
<script type="application/ld+json">
{
  "@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 }}" }
}
</script>
{{ 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: 'og:description', content: 'Social sharing description.' },
  { tagName: 'link', rel: 'canonical', href: 'https://yourdomain.com/page' },
]

Verification Checklist

After making changes, confirm:

  • robots.txt allows all 9 AI bots
  • No noindex, nosnippet, noai on public pages
  • Every page has: title (10+ chars), meta description (50+ chars), canonical URL
  • Every page has: exactly 1 H1, proper heading hierarchy (H1 → H2 → H3)
  • Every page has: JSON-LD with recognized @type
  • Every page has: og:title + og:description
  • Every page has: 250+ words of body content
  • Every page has: 5+ internal links
  • 80%+ images have alt text
  • /.well-known/llms.txt exists and is valid
  • RSS/Atom feed exists and is discoverable via <link> tag
  • Sitemap.xml exists with <lastmod> dates
  • Publication/modification dates on content pages (meta + visible)
  • Content leads with direct answers, not preamble
  • FAQ sections on key pages with FAQPage schema
  • Statistics and named sources cited inline
  • Authoritative quotations included where relevant

Target: 80+ AEO score (B+ grade or higher). Validate at aeo-audit.sh.

Research References

All statistics in this skill are from verifiable, peer-reviewed or large-scale primary research:

ClaimSource
Quotations = +41% visibility; Statistics = +33%; Cite Sources = +28%Aggarwal et al., "GEO: Generative Engine Optimization," KDD 2024 (arXiv)
Lower-ranked sites gain up to +115% from GEO optimizationSame GEO paper — sites ranked 4th-5th saw largest gains
44.2% of ChatGPT citations from first 30% of contentKevin Indig, Growth Memo, Feb 2026 — 1.2M AI answers, 18K citations
Articles 2,900+ words = 5.1 citations vs. 3.2 for <800 wordsSE Ranking, Nov 2025 — 2.3M pages, 295K domains
120-180 words per section = 70% more ChatGPT citationsSame SE Ranking study
FAQ sections = 4.9 citations vs. 4.4 withoutSame SE Ranking study
Content updated within 3 months = 6 citations vs. 3.9 for 2+ year oldSame SE Ranking study
AI cites content 25.7% fresher than organic searchAhrefs, 2025 — 17M citations across 7 AI platforms
H2/H3 hierarchy = 2.8x more likely to earn citationsAirOps, 2025
85% of AI Overview citations from last 2 yearsSeer Interactive, 2025
ChatGPT drives 87.4% of AI referral trafficConductor, Nov 2025 — 13.7K domains, 3.3B sessions

© onvoyage-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in improve-aeo-geo of onvoyage-ai/gtm-engineer-skills.

  • SKILL.md
  • README.md
  • examples/nextjs-blog-before-after.md
  • examples/wordpress-business-before-after.md

Open the folder on GitHubat commit 3777930

Compare with similar skills

Improve Aeo Geo next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Improve Aeo Geo compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Improve Aeo Geo this skillonvoyage-ai/gtm-engineer-skills1.3k—~5.2kAutomated safety check: PassMIT
SEO GeoReScienceLab/opc-skills1.8k4 repos~2.1kAutomated safety check: PassApache-2.0
GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude11k—~2.8kAutomated safety check: NotesMIT
Geoliangdabiao/GEO-Content-Optimizer-Skill2051 repos~2.3kAutomated safety check: NotesMIT
Geo Optimizerliangdabiao/GEO-Content-Optimizer-Skill205—~1.1kAutomated safety check: PassNone
Global SEO Growthminhnv0807/ai-business-skills609—~5kAutomated safety check: PassMIT

Similar skills

  • SEO Geo

    ReScienceLab/opc-skills

    SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.

    1.8k GitHub starsUsed in 4 repos~2.1k tokens
    Marketing & SEOAuto-check passed

  • GEO-First SEO Audit Tool

    zubair-trabzada/geo-seo-claude

    Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.

    11k GitHub stars~2.8k tokensUpdated yesterday
    Marketing & SEOAuto-check: notes

  • Geo

    liangdabiao/GEO-Content-Optimizer-Skill

    完整的 GEO（生成式引擎优化）服务流水线：给一个产品官网 URL 和介绍材料， 做站点诊断与 AI 答案采样、生成带验收标准的执行工单、产出可直接部署的资产 （llms.txt / JSON-LD / 定义块 / FAQ / 内容大纲与初稿）、自动验收工单是否闭环、 并打包成可直接发给客户的交付物。可按周期复跑，做长期 GEO 运营与月报。

    205 GitHub starsUsed in 1 repo~2.3k tokens
    Marketing & SEOAuto-check: notes

  • Geo Optimizer

    liangdabiao/GEO-Content-Optimizer-Skill

    GEO (Generative Engine Optimization) 全流程优化工具。帮助品牌内容被 ChatGPT、Perplexity、Gemini 等 AI 搜索引擎引用。

    205 GitHub stars~1.1k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed

  • Global SEO Growth

    minhnv0807/ai-business-skills

    Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.

    609 GitHub stars~5k tokensUpdated 29 days ago
    Marketing & SEOAuto-check passed

  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed

More from onvoyage-ai/gtm-engineer-skills

All 12 skills in this repo

  • Audit Website Aeo

    onvoyage-ai/gtm-engineer-skills

    Audits a live website for AI-engine discoverability (AEO/GEO).

    1.3k GitHub stars~2.9k tokensUpdated 4 mo ago
    Auto-check passed

  • Research Brand

    onvoyage-ai/gtm-engineer-skills

    Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging.

    1.3k GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed

  • Research Keywords

    onvoyage-ai/gtm-engineer-skills

    Finds high-value SEO and GEO keywords using web search, AI analysis, and optionally paid tools like Ahrefs or Semrush.

    1.3k GitHub stars~4k tokensUpdated 4 mo ago
    Auto-check passed

  • Audit Content

    onvoyage-ai/gtm-engineer-skills

    Verifies truthfulness, accuracy, and link integrity of content before publishing.

    1.3k GitHub stars~1.9k tokensUpdated 4 mo ago
    Auto-check passed

  • Build Backlinks

    onvoyage-ai/gtm-engineer-skills

    Finds free backlink and brand mention opportunities across Hacker News, Quora, GitHub, directories, and niche communities.

    1.3k GitHub stars~2.3k tokensUpdated 4 mo ago
    Auto-check passed

  • Build Resource Pages

    onvoyage-ai/gtm-engineer-skills

    Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system.

    1.3k GitHub stars~3.6k tokensUpdated 4 mo ago
    Auto-check passed

Works with

Categories

Questions about Improve Aeo Geo

What does Improve Aeo Geo do?

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. Improve Aeo Geo is an agent skill from onvoyage-ai/gtm-engineer-skills. 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.

When should I use Improve Aeo Geo?

Improve Aeo Geo fits situations like: tasks that involve AI search optimization; tasks that involve Schema markup.

How do I install Improve Aeo Geo in Claude Code?

Run `npx skills add onvoyage-ai/gtm-engineer-skills --skill improve-aeo-geo -a claude-code`. Or copy the skill folder (improve-aeo-geo in onvoyage-ai/gtm-engineer-skills) into .claude/skills/improve-aeo-geo in your project. Claude Code loads it when a task matches its description.

How do I install Improve Aeo Geo in Codex?

Run `npx skills add onvoyage-ai/gtm-engineer-skills --skill improve-aeo-geo -a codex`. Or copy the skill folder (improve-aeo-geo in onvoyage-ai/gtm-engineer-skills) into .agents/skills/improve-aeo-geo in your project. Codex loads it when a task matches its description.

Can I use Improve Aeo Geo in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add onvoyage-ai/gtm-engineer-skills --skill improve-aeo-geo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/improve-aeo-geo, .gemini/skills/improve-aeo-geo, .github/skills/improve-aeo-geo and .opencode/skills/improve-aeo-geo in your project.

What does Improve Aeo Geo need to run?

SKILL.md names no scripts, command-line tools or credentials: Improve Aeo Geo is instructions for the agent only.

Does Improve Aeo Geo access the network?

SKILL.md names 3 domains. In commands or code: schema.org; the agent is likely to contact it when it follows the instructions. As links in the text: aeo-audit.sh and arxiv.org. This is read from the text; nothing was executed.

Is Improve Aeo Geo safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Improve Aeo Geo use?

Improve Aeo Geo is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Improve Aeo Geo use?

About 5.2k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Improve Aeo Geo?

Skills that share tags, products or a category with Improve Aeo Geo: SEO Geo (ReScienceLab/opc-skills, 1.8k stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars), Geo (liangdabiao/GEO-Content-Optimizer-Skill, 205 stars) and Geo Optimizer (liangdabiao/GEO-Content-Optimizer-Skill, 205 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Improve Aeo Geo?

onvoyage-ai (a GitHub organization) maintains it in onvoyage-ai/gtm-engineer-skills, which has 1,320 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on June 7, 2026.

Source: onvoyage-ai/gtm-engineer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.