PostHog wins the AI answer. Its own site doesn’t get the credit.
We ran three real buyer prompts through ChatGPT, Perplexity and Google AI Overview, live, on the same day. PostHog got named in all three — it’s already winning the AI answer. But when we checked who actually earned the citation, posthog.com was missing from 9 of the 10 sources on the broadest query, and the site itself carries zero structured data to claim a win it’s already earning by reputation alone.
By Nikesh Sundar · 14 August 2026
answer engines named PostHog live, unprompted — ChatGPT, Perplexity, Google AI Overview
Perplexity sources on the broad discovery query that were actually posthog.com
JSON-LD structured-data blocks found on the homepage, product page, or comparison pages
lines in PostHog’s llms.txt — written entirely for coding agents, none for buyers
What we did
PostHog isn’t a Nivonto client — we picked it because it’s a well-known, well-documented product with genuinely strong content, which makes it a fair test case. On 14 August 2026 we asked ChatGPT, Perplexity and Google three versions of a real buyer question — “best product analytics tools for startups 2026” and “PostHog vs Mixpanel” — from guest or default sessions, with no prompt engineering. Then we checked posthog.com directly: its robots.txt, its llms.txt, and whether its pages carry any structured data at all.
What each engine actually said
“What are the best product analytics tools for startups in 2026?”
“best product analytics tools for startups 2026”
“best product analytics tools for startups 2026”
“PostHog vs Mixpanel, which should I choose for my startup?”
Live-queried 14 August 2026, guest/default sessions, no prompt engineering. AI answers change over time — re-running these prompts today may surface different results.
Finding 1: PostHog is already recommended — that part isn’t the problem
All three engines named PostHog, unprompted, as a top pick for startups. That’s the outcome most companies are chasing when they ask for an AEO audit, and PostHog already has it. Strong comparison pages, an honest pricing story, and a well-known open-source brand are doing real work here. The problem isn’t visibility. It’s who gets credit for it.
Finding 2: the citation is going to strangers, not posthog.com
For the broad discovery query — the one a buyer types before they’ve heard of any specific tool — Perplexity cited 10 sources. Every single one was a third-party listicle. Not one was posthog.com.
Who actually got the citation
Perplexity’s 10 sources for “best product analytics tools for startups 2026”
Google AI Overview did the same thing: it named PostHog, then linked the claim to trackraptor.com — a site PostHog has no control over, no relationship with, and no way to correct if it gets a detail wrong. This is the exact dynamic behind Nivonto’s own research into the “AEO for AEO” pattern: a small set of listicle domains sit between well-known products and the AI engines that cite them, quietly capturing the authority those products already earned.
Finding 3: head-to-head queries are the exception — and the proof
It isn’t hopeless. When we asked the direct comparison question — “PostHog vs Mixpanel” — Perplexity’s answer cited posthog.com itself among its sources. PostHog’s own comparison pages are good enough to win the citation when the query is specific enough to surface them. The gap is entirely in the broader, earlier-stage discovery queries, where third-party content still beats PostHog’s own site to the punch.
Finding 4: the technical foundation isn’t helping
We checked posthog.com directly rather than taking anyone’s word for it.
Crawler access
robots.txt places no disallow rules on GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, or PerplexityBot. Only Googlebot, Bingbot, DuckDuckBot and Yeti are blocked — and only from .md files.
Structured data
Zero JSON-LD blocks on the homepage, the Product Analytics page, or the PostHog vs Mixpanel comparison page. No Organization, SoftwareApplication, or FAQPage schema anywhere we checked.
llms.txt
3,609 lines — entirely SDK install commands, API base URLs, and MCP setup for coding agents. Nothing written to help an answer engine describe PostHog to a buyer.
What this means
PostHog’s AEO problem isn’t “get mentioned by AI” — it already is. It’s “make sure the citation lands on a page you control.” That’s a narrower, cheaper fix than most companies need: structured data (Organization + SoftwareApplication + FAQPage) so engines can lift facts directly from posthog.com instead of a summary of a summary; more of the direct comparison-style content that already wins citations, aimed at the broader discovery queries it currently loses; and treating llms.txt as what it is — a developer-integration doc, not an AEO deliverable, so buyer-facing content has to live somewhere engines actually cite from.
Methodology & honesty note
This is an independent audit, not a case study — PostHog has never engaged Nivonto, and nothing here implies otherwise. All quoted answers are verbatim from live sessions on 14 August 2026; nothing was cherry-picked or re-rolled for a better result. AI answers are not static — the same prompts run today may return different names, different sources, or a different ranking entirely. The value here is the pattern (strong brand, weak citation ownership, no structured data) more than any single number, and it’s the same methodology we run for every Audit Sprint client.