Elevator Talk: Should You Optimize Content Differently for ChatGPT, Gemini, and Claude?
It started when JennyB asked the team a question in Slack: has anyone actually tested how ChatGPT, Gemini, and Claude cite content, and noticed where they differ? She'd been treating “optimize for AI” as a single bucket, but with client data showing some audiences skew heavily toward one assistant over another, she wondered whether that approach needed to change. What followed was a thread about shared fundamentals, assistant-specific quirks, and how to actually go test the difference instead of guessing at it. Here's how the conversation went.
One Bucket, Even When the Skew Is Obvious
Test the Experiment Before You Trust the Hunch
Same Fundamentals, Different Logic
Same Fundamentals, Real Differences — The Data Says Both
The Search Engine Behind Claude's Citations
Rachel Builds the Thing
The Takeaway
Nobody on the thread had run the test, but outside data backs up the split verdict. Across 17.2 million citations, Yext found that verified, structured content is still the biggest driver for every assistant — but each one clearly weights different signals within that field. Gemini leans on Google's index, Perplexity stays stable across industries, ChatGPT shifts by industry, and Claude cites reviews and user-generated content at 2–4x the rate of the others. The fundamentals aren't a myth. Neither is assistant-specific logic.
So the plan is to test it: pick a topic for an audience that already skews toward one assistant — Claude, given how differently it weighs UGC, is the most interesting case — optimize deliberately for that assistant, then track citations across all three to see whether the lift stays isolated or spills over. Until that data exists, “optimize for one optimizes for all” stays a working hypothesis, not a rule to build strategy on.
There's already one concrete lever on the table, too: Blake's point that an estimated 80% of Claude's citations trace back to Brave's top 10 results (per a Profound study) means SERP analysis on Brave, not just Google, could be its own pillar for Claude-specific optimization — and it's worth folding into whatever test gets built.
And the infrastructure the thread was asking for on day one already exists: Rachel's comparison tool runs a prompt across every assistant and shows, side by side, what they agree on, where they diverge, and what all of them are missing. The hunch and the tooling are both in place now. What's left is pointing it at a real, platform-skewed audience and watching what happens.
You might also like
Elevator Talk: Does Domain Authority Even Matter for AI Visibility?
Elevator Talk: What Markup, Markdown, and Schema Are Really Doing for AI Search


