The Ultimate AEO, SEO & GEO Optimization Checklist

SEO (Search Engine Optimization) is the foundation: technical health, content quality, and links that help search engines rank you. AEO (Answer Engine Optimization) formats that same content so featured snippets, voice assistants, and Google's People Also Ask can extract a direct answer from it. GEO (Generative Engine Optimization) goes a layer further, focusing on whether AI systems like ChatGPT, Perplexity, and Google's AI Overviews actually cite your content in a generated answer. The three build on each other rather than replacing one another — a technically broken, poorly-written site won't succeed at any of them.

It depends which AI surface you mean. Google has been explicit that for its own AI Overviews and AI Mode, there's no separate playbook — its Search Central guidance states this is still SEO, built on the same ranking and quality systems as regular Search. But that framing doesn't fully extend to ChatGPT, Perplexity, or Claude, which crawl, retrieve, and cite sources through entirely different systems than Google's index. In practice, most of the work overlaps (E-E-A-T, structured data, clear direct answers), which is exactly why this checklist treats SEO as the shared foundation underneath both AEO and GEO rather than three unrelated workstreams.

AI Overviews are the AI-generated summaries that can appear above traditional results for a single search query. AI Mode is a more conversational, multi-turn search experience launched in March 2025 for complex questions that benefit from follow-up queries and deeper reasoning. By Google I/O in May 2026, AI Mode had surpassed 1 billion monthly users with Gemini 3.5 Flash as its default model, and Google added the ability to ask a follow-up question from an AI Overview and continue directly into AI Mode, carrying the search context forward.

The evidence through 2026 says not much, at least not yet. Crawl-log studies, including an analysis of 300,000 domains, have found that major AI search crawlers largely don't fetch llms.txt when indexing content for citation purposes, and sites with one show no measurable traffic difference from sites without. Where llms.txt has found real traction is with IDE coding agents (Cursor, Claude Code, GitHub Copilot) reading software documentation — a different use case entirely. It's a reasonable low-cost hedge to publish one, but treat your actual citation rate as driven by schema, E-E-A-T, and content structure, not by this file.

Start by separating AI-search crawlers, which retrieve content to answer live queries (GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot), from AI-training crawlers, which collect content for model training datasets (CCBot, Bytespider, and similar). Blocking a search/citation crawler removes you from that platform's AI answers entirely, which is usually a real cost for most businesses. Blocking a training-only crawler doesn't affect whether you're cited today, only whether your content trains a future model — a decision with different tradeoffs that's worth making deliberately rather than via a blanket disallow rule copied from somewhere else.

Interaction to Next Paint (INP) officially replaced First Input Delay (FID) as the third Core Web Vital in March 2024, alongside LCP and CLS. Page speed isn't a direct AI-citation factor the way content quality and structure are, but it remains a baseline signal for ranking and crawl efficiency — and a page that's too slow to render reliably can fail to get indexed or crawled by AI bots in the first place, which makes Core Web Vitals a prerequisite rather than a citation booster.

For a new site, expect 6–12 months before meaningful organic traffic, regardless of how well AEO and GEO items are executed — search and AI systems both need time to crawl, index, and build trust in a domain. For an established site with existing authority, AI citation can move faster on narrow or branded queries (sometimes weeks), while competitive, high-volume topics still take months. The fastest visible wins usually come from the Quick-Win Checklist in Part 6, since those target pages and signals that already have some existing authority to build on.

Preferred Sources is a 2026 Google Search feature that lets individual users select specific publishers they want to see more often, including inside AI Overviews and AI Mode. It doesn't change anyone's rankings, but it does mean an engaged audience can directly increase how often you surface in their personal AI search results. The practical implication for this checklist's Brand Signals and E-E-A-T items: prompting your existing newsletter subscribers, social followers, and returning visitors to add you as a Preferred Source is now a legitimate, if modest, AI-visibility tactic in its own right.

Start with Part 1's Technical SEO and On-Page SEO subsections, then move to the Quick-Win Checklist at the end of Part 6. Every layer of AEO and GEO assumes a technically sound, well-structured, indexable site underneath it — fixing a crawl error or adding FAQ schema to your highest-traffic pages will move the needle faster than any AI-platform-specific tactic if those fundamentals aren't already in place.