Writing · Series: How AI Search Works · Follow-on 2
The GEO Documentation Gap: Why Three Platforms Haven't Told You How to Rank in Their Systems.
Google published a guide. Microsoft published measurement tooling. Anthropic, OpenAI, and Perplexity have published nothing equivalent. Understanding why is more useful than waiting.
Published1 June 2026
ByThomas Cox
Read time8 minutes
Filed underSeries · Platform Strategy · Follow-on 2
Google published its first explicit AI search optimisation guide in May 2026. Microsoft launched citation measurement tooling in February 2026. Both documents are notable not just for what they say, but for the fact that they exist at all.
Anthropic has published nothing equivalent. OpenAI has published nothing equivalent. Perplexity has published nothing equivalent. This is not an accident, and it is not a temporary gap that will be filled soon. Understanding why these platforms haven't published publisher-facing optimisation guidance — and what that absence implies for how to approach them — is more useful than waiting for guidance that may never arrive.
Why Google published a guide.
Google published an AI search optimisation guide because it had to.
Google's relationship with publishers is structurally adversarial in a way that OpenAI's, Anthropic's, and Perplexity's are not — yet. Google's core business is built on indexing and surfacing publisher content. Publishers have always had the ability to de-index their content from Google if they chose. The rise of AI Overviews intensified this tension: if Google's AI generates a synthesised answer that satisfies the user's query without a click to the publisher, the publisher's traffic decreases even as their content contributes to the AI's response.
Publishers need a reason to remain indexed and crawlable by Google. A guide that explains how to be cited in AI responses — turning AI Overviews from a traffic threat into a visibility opportunity — is a strategic response to that tension. The guide also serves Google's legal and regulatory interests: publishing explicit guidance creates a record of transparency about how AI features use web content.
Microsoft published the Bing AI Performance report for analogous reasons. Bing has always had a smaller publisher relationship to manage than Google, but the Copilot integration into Microsoft 365 — used by hundreds of millions of enterprise users — creates a new scale of publisher dependency. The measurement tool is a gesture of transparency that supports the publisher relationship.
Why OpenAI has not published a guide.
OpenAI's relationship with publishers is different. ChatGPT's training data — the source of its parametric knowledge — has been the subject of copyright litigation from publishers including The New York Times. OpenAI is in active legal and commercial negotiation with publishers over training data licensing, not optimisation guidance.
Publishing an explicit guide to getting content cited in ChatGPT Search would implicitly acknowledge the degree to which ChatGPT depends on publisher content and could be used in ongoing legal proceedings. It would also invite regulatory scrutiny of the boundary between licensed and unlicensed use of publisher content in AI training and retrieval.
The documentation OpenAI has published is developer-focused: API documentation explaining how the web search tool works technically. This is useful for building on top of ChatGPT, not for publishers trying to improve citation frequency. The asymmetry is intentional.
Why Anthropic has not published a guide.
Anthropic's situation is different again. Anthropic is primarily a research and API company — its customer base is developers and enterprises building on Claude, not publishers optimising for consumer AI search citation. The product surface where citation visibility matters (claude.ai with web search enabled) is newer and smaller than Google's AI Overviews or ChatGPT.
More importantly: Anthropic's Constitutional AI framework positions Claude's outputs as a function of explicit values rather than publisher optimisation incentives. Publishing guidance on how to get content cited by Claude would be in mild tension with the Constitutional AI premise — that Claude cites content because it is the best answer to the user's query, not because the publisher has optimised for citation.
Anthropic has published its retrieval architecture (web search documentation, Citations API documentation) and its alignment principles (Claude's Constitution). These are the available signals. Publisher-facing optimisation guidance is not currently part of Anthropic's product philosophy.
Why Perplexity has not published a guide.
Perplexity sits in an interesting position. It has no legacy search index to protect, no established publisher relationship to manage, and no enterprise software business creating complex data governance obligations. Its relationship with publishers is the most openly acknowledged of the three: the publisher revenue-sharing programme is a direct attempt to create economic alignment between citation and compensation.
The absence of explicit optimisation guidance from Perplexity likely reflects the company's size and prioritisation rather than a strategic decision to withhold it. Perplexity is a small company relative to Google, Microsoft, and OpenAI — building a revenue-sharing programme and growing to 1 billion monthly queries in under three years has consumed resources that might otherwise go toward publisher-facing documentation.
The Sonar documentation's explicit framing around factuality and readability as optimisation targets is the closest thing Perplexity has published to content guidance. It is directionally useful even without being a dedicated optimisation guide.
What the documentation gap means in practice.
The absence of explicit guidance from three of the five major AI search platforms has a practical consequence: practitioners who understand the underlying architecture — the RAG pipeline, the passage-level retrieval mechanism, the semantic similarity basis for retrieval — are not disadvantaged by the absence of platform guidance. They have derived the requirements from first principles.
The requirements that emerge from the architecture are consistent across all five platforms: content must be crawlable and indexable; content must be factually precise and clearly attributed; content must be structured for passage-level extraction; content must provide non-commodity value that the model cannot generate without consulting the source.
These requirements do not change because a platform has or has not published a guide confirming them. They are properties of the retrieval mechanism. The practitioner who understands the mechanism does not need the guide.
The documentation gap also creates a measurement gap. Without platform-provided citation data, the available proxies — traffic from AI-referring domains, brand mention tracking, manual query-by-query checking — are indirect and labour-intensive. The Bing AI Performance report is the only exception. Until Google, OpenAI, Anthropic, and Perplexity provide equivalent tooling, measurement will remain harder than optimisation.
The GEO documentation gap will narrow. Google has shown what explicit guidance looks like. Microsoft has shown what citation measurement looks like. The competitive pressure between platforms will push the others toward greater transparency. The practitioners who have invested in understanding the architecture rather than waiting for platform guides will not be caught flat-footed when the guides arrive. They will already know what the guides say.
/ Next in the series
Article 9 is the most technically ambitious piece in this series: why ChatGPT's RLHF alignment and Claude's Constitutional AI produce different citation preferences — and what that means at the margin. Read Article 9 →