~900M weekly users

ChatGPT playbook

Bing indexation first, OAI-SearchBot access, sources-panel monitoring, memory-layer consistency.

Open →
App + AI Overviews

Gemini playbook

Knowledge Graph hygiene, answer blocks, and testing on the conversational surface, not just Search.

Open →
Fastest entry

Perplexity playbook

Fetchability, passage shape, freshness cadence — and why Perplexity is where POC results show first.

Open →
Enterprise surface

Copilot playbook

Bing Webmaster + IndexNow discipline for the B2B desktop where procurement research happens.

Open →
Analyst influence

Claude playbook

Primary documents, clear authorship, precision — winning the engine that writes tomorrow's sources.

Open →

How to sequence playbooks

Don't run five playbooks at once. The free audit shows which engines your buyers use; run those two first, in parallel — foundations (crawler access, indexation, entity consistency) are shared across all engines anyway. Add engines as the first two stabilize. Grok is covered in the Engines section; it follows a conversation-first rather than page-first logic.

Frequently asked questions

Which playbook should I start with?
The audit decides: run the GEO Checker, see which engines your buyers' prompts resolve on, and start there. Defaults if you can't measure yet: B2B → ChatGPT + Perplexity; consumer → Gemini/AI Overviews; enterprise software → add Copilot.
How much do the playbooks overlap?
Foundations are ~60% shared (crawler access, answer blocks, entity consistency, corroboration). The divergent 40% — index dependencies, citation surfaces, freshness weighting — is where engine-specific wins live.