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.
Why this can grow a startup
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.
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.
Source-reported evidence
Source: PostHog: LLMs are picking winners. Here's how to become one. · Browse PostHog: LLMs are picking winners. Here's how to become one. tactics
PostHog explicitly works from at least four AEO data layers: referrer traffic, self-reported attribution, bot analytics, and prompt visibility tracking.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Analytics, AI visibility, SEO is relevant to reporting, multi-source analysis, measurement honesty and you can run a bounded test with a medium budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Analytics and AI visibility, using evidence from PostHog: LLMs are picking winners. Here's how to become one. as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.