# The answer should be easy to quote before you chase the mention > Why PostHog's AEO playbook starts with plain prompts, quoteable chunks, owned-surface cleanup, prompt capture, stitched reporting, and the willingness to throw away a bad prompt set. - Canonical HTML: https://growth.iangoh.com/blog/the-answer-should-be-easy-to-quote-before-you-chase-the-mention/ - Published: 2026-06-09 - Updated: 2026-06-09T14:12:06.000Z - Categories: AI visibility, SEO, content strategy - Niches: SaaS, AI products, developer tools, creator tools, B2B software, marketplaces ## On this page - Start with a reality check, not a vendor deck - Pages need to survive extraction - Clean your own house before chasing every side street - Ask the buyer what they actually typed - Reporting is stitched, not discovered whole - Be willing to throw away a flattering prompt set ## Start with these related tactics - [PostHog private-mode three-prompt benchmark before AEO tool sprawl](/growth-ideas/posthog-private-mode-three-prompt-benchmark-before-aeo-tool-sprawl/): Check ChatGPT, Claude, and Gemini in private mode with 3-5 plain buyer prompts before you disappear into dashboards, exports, and vendor demos. - [PostHog citable content chunks before monolithic SEO pages](/growth-ideas/posthog-citable-content-chunks-before-monolithic-seo-pages/): Write pages in quotable chunks with direct answers, question-led headings, short paragraphs, and specific numbers before you chase giant SEO essays. - [PostHog owned-surface cleanup before off-domain AEO sidequests](/growth-ideas/posthog-owned-surface-cleanup-before-off-domain-aeo-sidequests/): Fix the pages you own before chasing Reddit threads, Wikipedia dreams, Medium cleanup, and every other AEO side quest. A lot of teams talk about AI visibility like it starts on somebody else's website. More Reddit. More press. More mentions. More everything. That is usually backwards. The answer should be easy to quote before you chase the mention. PostHog's new AEO write-up is useful because it treats the problem less like a magic trick and more like content, attribution, and judgment work. ## Start with a reality check, not a vendor deck [PostHog private-mode three-prompt benchmark before AEO tool sprawl](/growth-ideas/posthog-private-mode-three-prompt-benchmark-before-aeo-tool-sprawl/) is the clean opening move. Ask the models the boring buyer questions first. See whether the product shows up, disappears, or gets described badly. That sits well beside [Fern API catalog before agent scrape guesswork](/growth-ideas/fern-api-catalog-before-agent-scrape-guesswork/). Before the team buys more reporting, it should make the product legible enough to be found at all. ## Pages need to survive extraction [PostHog citable content chunks before monolithic SEO pages](/growth-ideas/posthog-citable-content-chunks-before-monolithic-seo-pages/) is the core lesson. The page still matters, but the quoteable unit is smaller now. A heading, a definition, a table row, a specific number. I would read that with [llms-full single-file context export](/growth-ideas/llms-full-single-file-context-export/) and [well-known llms aliases for agent compatibility](/growth-ideas/well-known-llms-aliases-for-agent-compatibility/). The easier it is to retrieve the right chunk, the less guesswork the model has to do. ## Clean your own house before chasing every side street [PostHog owned-surface cleanup before off-domain AEO sidequests](/growth-ideas/posthog-owned-surface-cleanup-before-off-domain-aeo-sidequests/) is the part most teams want to skip because it sounds ordinary. Ordinary is the point. Fast pages, direct language, healthy internal links, and obvious routes still do most of the work. This belongs next to [custom docs 404 page with task-led redirects](/growth-ideas/custom-docs-404-page-with-task-led-redirects/) and [recurring docs audit for broken links and style drift](/growth-ideas/recurring-docs-audit-for-broken-links-and-style-drift/). A citation is wasted if the next click lands on fog or friction. ## Ask the buyer what they actually typed [PostHog onboarding prompt capture for AI attribution](/growth-ideas/posthog-onboarding-prompt-capture-for-ai-attribution/) is my favorite move in the batch. The growth team does not need another synthetic prompt brainstorm if real converting users are willing to hand over the sentence that brought them in. That is high-signal language. It is better than a Slack debate. Better than a vendor screenshot. Better than a brainstorm where everybody pretends to be the customer for twenty minutes. ## Reporting is stitched, not discovered whole [PostHog AEO reporting quilt before single-source certainty](/growth-ideas/posthog-aeo-reporting-quilt-before-single-source-certainty/) matters because AEO is still messy. One source tells you what was crawled. Another tells you what got said. Another tells you what converted. None is enough alone. That fits with [Fern search scope by product before cross-doc noise](/growth-ideas/fern-search-scope-by-product-before-cross-doc-noise/). Retrieval systems get worse when the team mistakes one partial view for the whole map. ## Be willing to throw away a flattering prompt set [PostHog synthetic prompt reset when real user language disagrees](/growth-ideas/posthog-synthetic-prompt-reset-when-real-user-language-disagrees/) is the discipline most teams avoid. If the tracked prompts do not resemble what real users say, the history is comforting but useless. This is strongest for SaaS, AI products, developer tools, marketplaces, and creator software where the buyer often arrives with a question before they arrive with brand loyalty. If I were tightening one AEO program this week, I would benchmark a few plain prompts, rewrite the owned pages into quoteable chunks, ask AI-sourced signups what they actually typed, stitch together a report from multiple imperfect sources, and scrap any prompt set that no longer sounds like a real buyer. That is slower than hype and much more useful. If you want help turning docs, answer surfaces, and AI discovery into a cleaner acquisition path, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [PostHog private-mode three-prompt benchmark before AEO tool sprawl](/growth-ideas/posthog-private-mode-three-prompt-benchmark-before-aeo-tool-sprawl/) - AI visibility, SEO, Research - [PostHog citable content chunks before monolithic SEO pages](/growth-ideas/posthog-citable-content-chunks-before-monolithic-seo-pages/) - AI visibility, SEO, Content Marketing - [PostHog owned-surface cleanup before off-domain AEO sidequests](/growth-ideas/posthog-owned-surface-cleanup-before-off-domain-aeo-sidequests/) - SEO, Brand Trust, AI visibility - [PostHog onboarding prompt capture for AI attribution](/growth-ideas/posthog-onboarding-prompt-capture-for-ai-attribution/) - AI visibility, Onboarding, Attribution - [PostHog AEO reporting quilt before single-source certainty](/growth-ideas/posthog-aeo-reporting-quilt-before-single-source-certainty/) - Analytics, AI visibility, SEO - [PostHog synthetic prompt reset when real user language disagrees](/growth-ideas/posthog-synthetic-prompt-reset-when-real-user-language-disagrees/) - AI visibility, Analytics, Positioning ## Essay chronology - [Newer essay: Zero ad spend is still a marketing budget](/blog/zero-ad-spend-is-still-a-marketing-budget/) - organic marketing, product-led growth, SEO - [Older essay: The link should sell the infrastructure quietly](/blog/the-link-should-sell-the-infrastructure-quietly/) - open source, product-led growth, developer platform ## Keep reading - [The AI visibility report should point to a page that can win](/blog/the-ai-visibility-report-should-point-to-a-page-that-can-win/) - AI visibility, SEO, brand trust - [The proof surface should answer before the call](/blog/the-proof-surface-should-answer-before-the-call/) - proof surfaces, brand trust, SEO - [The answer should travel before the queue grows](/blog/the-answer-should-travel-before-the-queue-grows/) - support-led growth, brand trust, SEO ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [PostHog: LLMs are picking winners. Here's how to become one.](https://newsletter.posthog.com/p/llms-are-picking-winners-heres-how) · [GrowthDex source hub](/sources/posthog-llms-are-picking-winners-here-s-how-to-become-one-newsletter-pos/) - [PostHog: Non-obvious SEO advice for startups](https://newsletter.posthog.com/p/non-obvious-seo-advice-for-startups/) · [GrowthDex source hub](/sources/posthog-non-obvious-seo-advice-for-startups-newsletter-posthog-com/) - [PostHog: What nobody tells developers about documentation](https://newsletter.posthog.com/p/what-nobody-tells-developers-about/) · [GrowthDex source hub](/sources/posthog-what-nobody-tells-developers-about-documentation-newsletter-post/) ## Editing notes - Kept the essay on one blunt claim: make the answer quoteable before chasing more mentions. - Used concrete objects like prompts, headings, tables, audits, Slack reports, and onboarding questions instead of vague talk about the future of AI search. - Cut hype around AEO and left in the uncertainty about stitched reporting and resetting bad prompt history. - Ended with a weekly operating sequence and one advisory CTA instead of a padded conclusion about changing landscapes. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.