跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

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.

onvoyage-ai · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add onvoyage-ai/gtm-engineer-skills --skill 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.

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:

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:

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

阅读完整来源 ↗