# PostHog AEO reporting quilt before single-source certainty > Report AEO from a stitched set of sources such as referrer traffic, self-report, bot analytics, and prompt visibility instead of pretending one clean dashboard can settle it. - Canonical HTML: https://growth.iangoh.com/growth-ideas/posthog-aeo-reporting-quilt-before-single-source-certainty/ - Source: [newsletter.posthog.com](https://newsletter.posthog.com/p/llms-are-picking-winners-heres-how) - GrowthDex source hub: [PostHog: LLMs are picking winners. Here's how to become one.](/sources/posthog-llms-are-picking-winners-here-s-how-to-become-one-newsletter-pos/) - Last checked: 2026-06-09T14:12:06.000Z - Rarity: rare - Budget: medium - Channels: Analytics, AI visibility, SEO - Stages: reporting, multi-source analysis, measurement honesty, mcp workflows ## Why this can grow AEO reporting breaks teams that expect one source of truth too early. PostHog's description is unusually honest: each source answers a different question, and each source is incomplete. Referrer data only catches some visits. Self-report gets closer to user intent but not everybody answers. Bot analytics show what crawlers see, not what models say. Prompt visibility tools only cover prompts the team decided to track. Treating the report as a quilt keeps the team from overclaiming and makes it easier to explain uncertainty upstream. That honesty matters because bad certainty creates worse strategy than partial truth. ## Ian's take From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it. ## Action plan 1. Define one narrow startup segment where posthog aeo reporting quilt before single-source certainty can create a measurable lift. 2. Turn the tactic into one offer, page, campaign, or workflow for the Analytics and AI visibility channel. 3. Use the evidence from newsletter.posthog.com to set the first version of the message, format, and audience. 4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal. 5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook. ## Source-backed example PostHog combines prompt-visibility data, Google Search Console data, product traffic and conversion data, bot-crawl patterns, self-attribution answers, and MCP-powered analysis instead of trusting a single dashboard. ## Adjacent tactics in the same lane - [PostHog private-mode three-prompt benchmark before AEO tool sprawl](/growth-ideas/posthog-private-mode-three-prompt-benchmark-before-aeo-tool-sprawl/) - same source, 2 shared channels - [PostHog citable content chunks before monolithic SEO pages](/growth-ideas/posthog-citable-content-chunks-before-monolithic-seo-pages/) - same source, 2 shared channels - [PostHog owned-surface cleanup before off-domain AEO sidequests](/growth-ideas/posthog-owned-surface-cleanup-before-off-domain-aeo-sidequests/) - same source, 2 shared channels - [PostHog synthetic prompt reset when real user language disagrees](/growth-ideas/posthog-synthetic-prompt-reset-when-real-user-language-disagrees/) - same source, 2 shared channels ## Read GrowthDex essays Browse the plain-English essay index at [GrowthDex Blog](/blog/). ## Related GrowthDex essays - [The answer should be easy to quote before you chase the mention](/blog/the-answer-should-be-easy-to-quote-before-you-chase-the-mention/) - AI visibility, SEO, content strategy ## Advisory If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.