Practitioner's Guide

    SEO. GEO. AEO. Three disciplines. One strategy.

    A practitioner's guide to how each discipline works, what technical signals each requires, and the specific configurations that determine whether AI engines cite your brand — or someone else's.

    14 min read·MeetGEO Team·Updated May 14, 2026
    Section 01

    The search landscape has changed

    For two decades, Search Engine Optimization was the entire game. That has changed — not because SEO stopped working, but because a second and third discovery channel now run alongside it, operating on entirely different logic.

    In the first five months of 2025, AI-referred sessions to websites grew 527% year-over-year. ChatGPT now processes over 2 billion queries daily. Perplexity, Gemini, and Claude route millions of additional searches every day. And most of those users do not click through to a website. They get an answer synthesized from sources the AI selected — sources the user never sees by name unless the AI chooses to cite them.

    That selection process is not random. It is governed by specific, measurable signals — and the companies that understand those signals are earning disproportionate visibility in AI answers right now, regardless of their traditional search rankings.

    527%

    year-over-year growth in AI-referred sessions in early 2025

    Previsible / Search Engine Land, Aug 2025

    4.4×

    higher conversion rate from AI-referred visitors vs. traditional organic

    Semrush, 2025

    12%

    overlap of cited sources across ChatGPT, Perplexity, and Google AI Overviews

    Profound, 2025

    The problem with a single-channel strategy

    Ranking first on Google does not guarantee inclusion in AI answers. Nearly 90% of ChatGPT citations come from URLs that rank outside the top 20 in Google. Conversely, 76.1% of URLs cited in Google AI Overviews do rank in the top 10 — so strong SEO still matters for Google's own AI surfaces. But ChatGPT, Perplexity, and Claude operate on different selection logic, prioritizing entity clarity, structured data, content architecture, and topical authority signals over raw link equity.

    Section 02

    How they relate to each other

    • SEO builds the foundation: crawlability, speed, content authority, and link equity. Without it, the other two disciplines have nothing to build on.
    • GEO builds the machine-readability layer: structured data, entity disambiguation, content architecture, and the signals that tell AI crawlers exactly who you are.
    • AEO builds the answer layer: content formatted so AI systems extract it as a direct answer, attribute it cleanly, and use it in response to the specific questions your audience is asking.
    The relationship in one sentence: SEO earns you eligibility. GEO earns you comprehension. AEO earns you the citation. All three are required. None of them compete.
    Section 03

    SEO: the foundation that enables everything else

    Search Engine Optimization is the practice of configuring your website so that search engines can crawl, understand, index, and rank your pages. It has been the primary driver of non-paid discovery for over twenty years — and it remains the prerequisite for both GEO and AEO.

    Google still processes an estimated 16.4 billion searches per day and holds over 89% of the global search engine market. But approximately 69% of all Google searches in 2025 end without a click to any external website. When Google's AI Mode is active, that figure reaches 93%.

    Core technical signals SEO requires

    • Crawlability: a clean robots.txt, no unintended noindex directives, a current XML sitemap.
    • Core Web Vitals: LCP under 2.5 seconds is the primary page experience benchmark.
    • Mobile-first indexing: Google indexes your mobile version first.
    • Structured data: JSON-LD schema that accurately describes your content and entities.
    • Topical authority: depth-first coverage of your category.
    • Internal link architecture: a logical site structure that distributes authority.
    • External authority: backlinks from relevant, trusted domains.
    SEO is not the focus of this guide. The disciplines that are new, less understood, and currently representing the largest first-mover opportunity are GEO and AEO. The remainder of this guide focuses on those.
    Section 04

    GEO: Generative Engine Optimization

    GEO is the practice of making your content and brand entity machine-readable enough that AI systems can extract, attribute, and cite you with confidence. It is a configuration discipline, not a content volume discipline.

    When an AI engine receives a query, it processes it semantically, retrieves candidate content, ranks sources by relevance, authority, and structural clarity, and synthesizes a response — attributing specific claims to source URLs. Your content may contain exactly the right information. If the AI cannot parse it cleanly, identify who produced it, and confirm the entity behind it, you do not get cited.

    1. Build your entity graph

    Before an AI system will confidently cite your brand, it needs to resolve who you are. Entity resolution determines whether "Acme Corp," "Acme Corporation," and "Acme" all refer to the same organization. If that resolution fails, the AI avoids attributing content to you rather than risk citing the wrong source.

    Google's Knowledge Graph

    A product

    • ○Proprietary database Google maintains
    • ○Powers Knowledge Panels in search
    • ○Requires Wikidata Q-ID, Wikipedia, or Google's entity recognition
    Your entity graph

    A representation

    • ●Internal model the AI builds of your brand
    • ●Strengthened by Organization schema + sameAs
    • ●Clearer entity = higher citation confidence

    How to build your entity graph

    • Organization schema with sameAs: link to LinkedIn, Wikidata, Crunchbase, Google Business Profile, industry associations.
    • Consistent entity naming: one canonical brand name, everywhere.
    • Person schema for authors: connects content to a verifiable human expert.
    • Third-party corroboration: mentions across multiple independent sources.
    • Wikidata Q-ID: the canonical ID path to Google's Knowledge Graph.

    2. Schema markup — the right way and the wrong way

    A Semrush test of how GPT-4 processed content found that proper schema implementation improved AI accuracy of information extraction from 16% to 54% — a 3× improvement with no content changes. That result requires the schema to be readable by the AI crawler in the first place.

    The JavaScript schema rule: If your schema is not present in the raw HTML response from your server — visible when you View Source on the page, before any JavaScript executes — AI crawlers are not reading it. GPTBot, ClaudeBot, and PerplexityBot do not execute JavaScript.

    Priority schema types for GEO

    SchemaWhat it communicates
    OrganizationWho you are, with sameAs — the anchor of your entity graph.
    WebSiteConfirms canonical site identity for AI systems.
    FAQPageBridges GEO and AEO — labels Q&A content for extraction.
    Article / BlogPostingAuthor, dates, publisher — recency and attribution.
    PersonConnects content to a verifiable human expert entity.
    Product / ServiceCritical for commercial AI recommendation queries.
    BreadcrumbListSite hierarchy and category relationships.
    LocalBusinessAddress, hours, service area for local queries.

    3. Content architecture for machine extraction

    AI retrieval operates at the chunk level, not the page level. It looks for the most precise, self-contained answer to the query — not the most comprehensive page.

    • Every H2 section should stand alone. No pronoun references without an explicit noun anchor.
    • Short paragraphs, one idea each. Frequently-cited pages average ~3 sentences per paragraph.
    • Definition patterns: "X is Y" is heavily extracted by LLMs.
    • Statistical anchors with full attribution. Cited statistics achieve 30–40% higher AI visibility.
    • Freshness signals: publication and dateModified on every piece.

    4. llms.txt — an honest assessment

    llms.txt is a proposed convention modeled on robots.txt — a plain-text Markdown file at your domain root listing important pages. It is worth adding. It is low-effort. But it is a lightweight clarity signal, not a citation driver. Deploy it alongside your schema and content architecture work — not in place of them.

    Section 05

    AEO: Answer Engine Optimization

    AEO is the discipline of writing and structuring content so that AI systems select it as the direct answer to a user's question. GEO makes your content machine-readable. AEO makes it the answer.

    Over 60% of search queries now generate AI-powered answers that reduce direct website clicks. Position one in traditional search no longer guarantees inclusion in those AI answers.

    1. BLUF: Bottom Line Up Front

    BLUF is the single most impactful and most underused AEO tactic. State the conclusion first, then provide supporting detail. Content using a BLUF structure saw a 40% increase in AI citation rates compared to traditionally written articles.

    • Heading states the question in the exact language a user would type.
    • First sentence answers it in 40 to 60 words.
    • Next two or three sentences provide supporting detail.
    • Total answer block under 80 words.
    Before

    Written for narrative

    • ○"When it comes to structured data, there are a number of different formats available. Understanding which format to choose can be confusing…"
    After

    Written for extraction

    • ●"JSON-LD is the preferred format for structured data because it is entirely separate from your HTML, can be rendered server-side, and is the format Google recommends and AI crawlers parse first."

    2. FAQPage schema

    FAQPage schema is the highest-leverage AEO investment for most sites. Practitioner testing reported by Frase.io put FAQPage citation rates near 67% on queries where structured Q&A content existed.

    • Schema must match on-page content.
    • Phrase questions as users would type them.
    • Answers follow BLUF. 40–60 words, direct answer first.
    • Schema must be server-rendered.

    3. E-E-A-T — the trust signals AI systems use

    • Named authors with Person schema.
    • Visible publication and update dates in Article schema.
    • First-person experience signals: "In our testing…"
    • External citations within content — primary sources.
    • Third-party validation: Wikipedia, G2, Capterra, industry coverage.

    4. Brand entity consistency

    Brand search volume — not backlink count — is the single strongest predictor of AI citations, with a 0.334 correlation coefficient across 1.96 million LLM sessions analyzed by Previsible in 2025. Brand building is AEO work.

    Section 06

    Technical signals at a glance

    Overlap is intentional — these signals reinforce each other.

    SEO foundationGEO configurationAEO content layer
    XML sitemap + robots.txtOrganization schema with sameAsBLUF-structured H2 sections
    Core Web Vitals (LCP < 2.5s)Server-rendered JSON-LD in <head>FAQPage schema (server-rendered)
    Mobile-first renderingFAQPage + Article schemaNamed authors + Person schema
    Internal link architecturePerson schema for content authorsFirst-person experience signals
    Topical authorityConsistent entity naming site-wideExplicit definitions ("X is Y")
    Backlinks from trusted domainsSelf-contained, chunk-level contentSelf-contained stat + source + date
    Helpful, original contentdateModified in Article schemaNo pronoun dependencies in copy
    E-E-A-T content qualityThird-party corroborationAnswer block under 80 words
    Section 07

    Where to start, based on your site type

    Priority order is the same regardless of platform: entity graph first, then server-rendered schema, then BLUF content restructuring. What varies is how you implement each.

    WordPress sites

    wordpress.org

    WordPress is the most implementation-flexible platform and the most inconsistent schema deployer. Most SEO plugins miss Organization, FAQPage, and Person types — or inject them via JavaScript.

    • Schema: add Organization JSON-LD manually in your theme's <head>. FAQPage via a server-rendering plugin.
    • BLUF restructuring: rewrite the opening sentence of each H2 on your top 10 pages.
    • llms.txt: a 30-minute task, not a strategy.

    Shopify sites

    shopify.com

    Shopify's default schema covers Product and breadcrumb. Organization, FAQPage, and Person are absent by default. JS-injected schema via third-party apps is the most common error.

    • Schema: add Organization via a custom Liquid snippet that renders server-side.
    • BLUF restructuring: product descriptions are the highest-impact target.
    • Brand entity: identical brand name across schema, social, Faire, press.

    Custom, headless & SaaS sites

    next.js · vercel · cloudflare

    Next.js with React Streaming/Suspense can hide JSON-LD from AI crawlers even when schema appears in browser DevTools — the crawler receives the server HTML before the stream completes.

    • Schema: JSON-LD must be injected before the stream payload completes — not inside a Suspense boundary.
    • Entity graph: maintain Organization schema as a single JSON file in your codebase.
    • FAQPage: generate from structured CMS data at build or request time.
    Section 08

    Frequently asked questions

    Each is written BLUF-first so an AI engine can extract it as a self-contained citation.

    What is the difference between SEO, GEO, and AEO?+
    SEO, GEO, and AEO are three complementary disciplines. SEO configures your site so search engines can crawl, index, and rank pages. GEO (Generative Engine Optimization) makes your content and brand entity machine-readable so AI systems can cite you confidently. AEO (Answer Engine Optimization) structures content so AI selects it as the direct answer. SEO earns eligibility. GEO earns comprehension. AEO earns the citation.
    What is GEO (Generative Engine Optimization)?+
    GEO is the practice of making your content and brand entity machine-readable enough that AI systems can extract, attribute, and cite you with confidence. It is a configuration discipline — not a content volume discipline — built on server-rendered JSON-LD schema, a clear entity graph, and chunk-level content architecture.
    Why does JavaScript-injected schema fail for AI crawlers?+
    AI crawlers like GPTBot, ClaudeBot, and PerplexityBot do not execute JavaScript. They fetch the raw HTML response from your server and read it as delivered. Schema markup injected via Google Tag Manager or rendered by a client-side React component is invisible to them. Validate by viewing your page source directly — not through a rendering-dependent testing tool.
    What is BLUF and how does it improve AI citation rates?+
    BLUF (Bottom Line Up Front) is a content structure that states the conclusion first, then provides supporting detail. Research from Semrush found content using BLUF structure saw a 40% increase in AI citation rates versus traditionally written articles. Each H2 section should phrase the heading as a question and answer it directly in the first 40–60 words, total answer block under 80 words.
    Do I need to publish an llms.txt file?+
    llms.txt is worth adding but should not be your priority. It is a plain-text Markdown file at your domain root that lists important pages — a lightweight clarity signal, not a citation driver. There is no confirmed evidence it materially improves AI citation rates on its own. Deploy it alongside server-rendered schema and BLUF content, not in place of them.
    How do I build an entity graph for AI citation?+
    Start with Organization schema that includes sameAs links to your LinkedIn, Wikidata, Crunchbase, and Google Business Profile — these connect every external reference to one canonical entity. Add Person schema for authors, use one consistent brand name everywhere, earn third-party mentions in trusted publications, and pursue a Wikidata Q-ID if you qualify. Consistency across sources is what reduces the ambiguity that prevents citation.
    Which schema types matter most for GEO?+
    Five schema types are essential: Organization (with sameAs links — your entity anchor), WebSite, FAQPage (the bridge to AEO), Article or BlogPosting (with author, datePublished, dateModified), and Person (for content authors). Product or Service is essential for commercial sites; LocalBusiness for local. All must be server-rendered JSON-LD in the raw HTML response.
    Does SEO still matter in the age of AI search?+
    Yes. SEO is the prerequisite for both GEO and AEO. Google AI Overviews draw 76.1% of citations from URLs ranking in the top 10 organic results. Core Web Vitals, crawlability, mobile-first rendering, and topical authority are the foundation every AI crawler also benefits from. A weak SEO foundation caps your AI visibility regardless of how much structured data you add.
    Section 09

    Bottom line

    The three disciplines are not competing strategies. SEO earns you eligibility for AI citation on Google surfaces. GEO earns you entity comprehension and citation readiness across all AI platforms. AEO earns you the direct answer citation — the placement where AI platforms actively name your brand as the source.

    The GEO and AEO work is almost entirely configuration: server-rendered schema, entity disambiguation, and BLUF-structured content. It does not require a content production campaign. It requires understanding the specific signals AI systems use to make citation decisions — and systematically closing the gaps.

    AI-referred visitors currently convert at 4.4× to 15.9× the rate of organic search visitors, depending on the platform. The channel is small but growing at 165× the velocity of organic search. The brands building citation authority now will own the answer layer in their categories when the channel scales.

    See where your site stands.

    MeetGEO audits your GEO and AEO technical gaps — entity graph, schema rendering, content architecture, and citation readiness — in one report, and shows you exactly what to fix first.

    Audit My Site Free →