Skip to content
XpandShow Me What To Fix First
The five engines we track
  • Google AI OverviewsGoogle search surface
  • ChatGPTAnswers and search
  • PerplexityVisible source links
  • GeminiGoogle product surfaces
  • ClaudeAnswers and web tools
Where Outrigger is included, the written scope defines the supported systems, buyer questions, comparison set, and observation cadence.
AI Search Optimization

Search just turned into a synthesis problem.
Optimize for the new mechanics.

Five major AI engines retrieve, synthesize, and cite sources differently. Their shared foundation is structural: schema graphs, citation-ready content, and entity clarity, paired with engine-specific measurement and tuning.

What changed in search since 2024
5
AI engines now intercept buyer-research queries before Google ever loads
32%
of B2B buyer journeys now begin in an AI engine, not a search box
1.4×
more likely a buyer is to mention a vendor by name when AI surfaced it first
0
of those interactions appear in your traditional analytics stack
Definition

What is AI search optimization?

AI search optimization is the practice of structuring your website, content, and external citations so that AI-powered search engines retrieve, synthesize, and cite your business when users ask category-relevant questions.

Where traditional search returns ten ranked links and lets the user choose, AI search returns one synthesized answer with a citation footnote. The optimization implications cascade from there. Schema becomes more important than meta descriptions. Citation density beats keyword density. Entity disambiguation beats page-level relevance. The buyer experience compresses from "research and click" to "ask and decide."

The discipline overlaps heavily with traditional SEO, strong content and clean technical foundations underpin both, but adds an additional structural layer specifically engineered for AI extraction and citation. We treat them as one integrated workstream because the same operator who ranks your blue links is the operator who engineers your AI citations. For the underlying playbook, read our guide on how to get found in AI search.

The five-engine matrix

Each engine retrieves and cites differently.
Optimize accordingly.

Engine 01

Google AI Overviews

Above the organic results
Search
availability varies by query and date
Retrieval

Answers can draw on Google's search systems and eligible web sources. The exact selection process is not disclosed.

Citation behavior

Interfaces can show linked sources, but presentation and referral behavior vary by query and date.

Tactical lever

Question-formatted H2s, definition-style answer paragraphs, and matching FAQ schema can make an eligible page easier to extract. Citation movement depends on the starting ranking, entity signals, authority, and query competition.

Engine 02

ChatGPT

Generated answers and search
Varies
by mode, prompt, and date
Retrieval

Answers may use live retrieval and existing model knowledge. Xpand cannot inspect or alter undisclosed training data or weights.

Citation behavior

Some experiences show linked sources while others may not. The output must be checked for the specific prompt and date.

Tactical lever

Search visibility, entity clarity, attributable content, and credible third-party corroboration are controllable inputs. None guarantees inclusion.

Engine 03

Perplexity

Answer engine with visible sources
Live
source behavior changes over time
Retrieval

The product commonly retrieves current web sources, but source selection varies by prompt and date.

Citation behavior

Linked sources are observable in many answers. Referral behavior still depends on the query and interface.

Tactical lever

Keep material facts current, crawlable, attributable, and aligned with visible structured data, then measure the resulting answers.

Engine 04

Gemini

Google's native AI assistant
Google
behavior varies by product surface
Retrieval

Answers may use Google systems and public web sources. The exact selection process is not disclosed.

Citation behavior

Some response modes show source links. The specific interface and prompt must be checked.

Tactical lever

Search visibility, entity clarity, current attributable content, and consistent public facts are controllable inputs. None guarantees citation.

Engine 05

Claude

Technical / B2B audience
Anthropic
web behavior changes over time
Retrieval

Answers may use web retrieval and existing model knowledge. Source selection varies by product mode and date.

Citation behavior

Web-enabled answers may show linked sources. Xpand records the observed output rather than assuming a fixed behavior.

Tactical lever

Clear authorship, attributable expertise, crawlable pages, and consistent public profiles can reduce ambiguity. They do not control model weights.

The workstreams

Six workstreams across five engines.
Engine-specific tuning layers on top.

Step 01

Baseline measurement

An agreed set of buyer questions is observed across the supported systems in scope. The date, prompt context, visible sources, and comparison set create the starting record.

Step 02

Schema graph upgrade

Site-wide @graph JSON-LD chaining Organization → Person → Service/Article. This can reduce entity ambiguity, with the effect assessed against the measured baseline.

Step 03

FAQ + AEO content layer

FAQ schema with 4-8 Q&A pairs per page. Direct-answer paragraphs under every H1. Question-formatted H2s. These patterns can make important passages easier for engines to retrieve and assess.

Step 04

Content and source clarity

Direct answers, attributable claims, clear authorship, and useful internal relationships can make important passages easier to retrieve and evaluate. The visible page remains the source of truth.

Step 05

Authority-citation campaigns

Outreach built around original research, expert commentary, and relevant podcast opportunities. Xpand may use PressForge to organize research, pitching, and follow-up. Every placement remains subject to editorial judgment.

Step 06

System-specific observation

The team checks which sources and page patterns appear for the agreed prompts, then prioritises controllable search, content, entity, and corroboration gaps. Hidden weights are not treated as an agency lever.

What doesn't work

The four patterns we see most agencies get wrong.

Four recurring failure patterns worth checking before more content or authority work is added.

Treating all engines as one

ChatGPT browsing leans on Bing. Gemini leans on Google. Perplexity leans on recency. Generic 'GEO content' that ignores those differences captures none of the engine-specific upside.

Skipping baseline measurement

If you don't know your starting citation share, you can't know if any tactic is working. Establish the baseline first so later reporting can show what changed and what did not.

On-site only, no authority work

Schema and FAQs cannot establish independent corroboration. Credible third-party sources may appear in retrieval and citation sets, so on-site clarity and off-site evidence should be assessed together. Xpand cannot alter model weights or guarantee inclusion.

Producing AI-generated content to optimize for AI search

Google's helpful-content systems catch unedited LLM output and penalise the entire site. Our editorial pass strips every AI tell. AI as leverage; humans as final voice.

Common questions

What teams ask before scoping an AI search engagement.

AI search optimization is the practice of structuring your website, content, and external evidence so AI-powered search engines can identify and assess it when users ask category-relevant questions. It is the operational discipline beneath the marketing term 'GEO'. Where traditional search returns ranked links, AI search may return one synthesized answer with cited sources. The work improves source eligibility, while each engine independently decides what to retrieve and cite.

Three architectural differences. First, retrieval: traditional search retrieves a ranked list of documents; AI search retrieves a smaller set of documents and synthesizes them into a single response. Second, presentation: traditional search shows you the documents and lets you choose; AI search shows you an answer and a citation footer. Third, intent: traditional search assumes the user will click through and read; AI search assumes the user has already gotten what they need by the time they finish reading. The optimization implications cascade from there: schema becomes more important than meta descriptions, citation density beats keyword density, and entity disambiguation beats page-level relevance.

All five major engines, with priority based on your audience. Google AI Overviews appears above the organic results on roughly 13% of queries (and growing): biggest near-term opportunity. ChatGPT has 300M+ weekly active users and is now the dominant top-of-funnel research engine for B2B buyers. Perplexity sends meaningful click-throughs because every answer cites sources by default. Gemini integrates across Google Workspace and is the default for many enterprise users. Claude (which we use ourselves) drives a smaller but extremely high-intent technical audience. Optimize for all five: the underlying patterns largely overlap, but tune emphasis to where your buyers actually live.

Yes, with significant overlap. ChatGPT browses Bing's index plus a curated source list. Perplexity browses an internal index that draws from the broader web with a strong recency bias. Gemini draws from Google's index, so traditional Google SEO directly influences Gemini visibility. Claude's web tool uses Brave and similar privacy-respecting search infrastructure. Google AI Overviews pulls from Google's indexed pages, weighted toward sites with strong E-E-A-T signals. Strong baseline SEO (Google + Bing) underpins all five. The differences are most pronounced in citation behavior, not retrieval source.

Schema graph and FAQ markup are useful starting points. A site-wide @graph JSON-LD that chains Organization to Person to Article or Service helps AI engines identify the entity and who is responsible for the content. FAQ markup should match the visible answer exactly. Direct-answer paragraphs, citation-friendly evidence blocks, and question-formatted H2s can then make important passages easier to retrieve. The right sequence depends on the baseline, and no individual change guarantees citation movement.

We use Outrigger, the separate AI-visibility joint venture Joel co-founded with Andrew, to monitor 30-50 priority keywords across all five engines weekly. For each keyword, the dashboard tracks: was your brand mentioned, was it cited with a link, what was the citation context, what was the sentiment, which page was the source, and how does your citation share compare to the top three competitors. The composite output is a citation share percentage: your share of voice across AI answers in your category, tracked over time. We report this monthly alongside traditional GSC and GA4 metrics.

You can do the on-site portion yourself if you have a senior in-house operator: schema graph, FAQ markup, llms.txt, direct-answer paragraphs, question-formatted H2s. The harder workstream is external: earning third-party citations from tier-1 publications, expert-comment placements, original-data research that journalists quote. That's the work that compounds long-term, and it's the work most in-house teams don't have the relationships or production cadence to run consistently. Most agencies (us included) earn fees on that workstream, not the on-site retrofit.

There is no fixed result window. Each engine refreshes sources differently, while your starting rankings, entity clarity, authority profile, and query competition all affect timing. We baseline the priority queries, fix the clearest technical and content gaps first, and monitor each engine separately so the reporting shows what changes and what does not.

Measure the gap across five engines

Five engines. One framework.
Audit the gap. Close it.

A scoped baseline can cover ChatGPT, Perplexity, Gemini, Claude, and Google AI Overview, benchmark selected competitors, and prioritise the citation gaps found in the data.