# Fix the answer before you chase AI traffic > A plain essay on Glasp's AEO treatment: canonical URLs, 404 demand mining, question titles, short lead answers, and a guardrail for pages that already earn Google clicks. - Canonical HTML: https://growth.iangoh.com/blog/fix-the-answer-before-you-chase-ai-traffic/ - Published: 2026-06-10 - Updated: 2026-06-10T03:13:40.000Z - Categories: AI Search, SEO, content systems - Niches: SaaS, AI products, creator tools, video products, developer tools, marketplaces ## On this page - Give each answer one home - Use broken bot paths as demand research - Make the top of the page answer the question - Do not break pages that already work - What I would test this week ## Start with these related tactics - [Glasp one URL per video before AEO rewrite](/growth-ideas/glasp-one-url-per-video-before-aeo-rewrite/): Collapse duplicate video page URLs into one canonical page before asking AI search tools to learn from the corpus. - [Glasp AI-bot 404 logs as page demand map](/growth-ideas/glasp-ai-bot-404-logs-as-page-demand-map/): Turn repeated AI-bot requests to missing URLs into a prioritized list of pages the corpus should actually create. - [Glasp question title rewrite from bot demand](/growth-ideas/glasp-question-title-rewrite-from-bot-demand/): Rewrite high-interest page titles into clear question form so the page matches how AI search tools and users ask. Most AI-search advice starts too late. It starts with prompts, rankings, dashboards, and screenshots of a chatbot answer. Glasp's study is more useful because it starts with the pages. The team changed a large YouTube Q&A corpus, measured ChatGPT referral traffic with first-party data, and compared treated pages against untreated pages on the same domain. The result was not a miracle claim. It was a bounded lift with caveats, which makes it easier to trust. ## Give each answer one home [Glasp one URL per video before AEO rewrite](/growth-ideas/glasp-one-url-per-video-before-aeo-rewrite/) is the plumbing move. If the same answer lives at a slug URL and a video-ID URL, the corpus is asking crawlers to choose between copies before they even judge the answer. That sounds boring. It is also the kind of boring that compounds. A stable URL makes analytics cleaner, links cleaner, and later rewrites easier to audit. ## Use broken bot paths as demand research [Glasp AI-bot 404 logs as page demand map](/growth-ideas/glasp-ai-bot-404-logs-as-page-demand-map/) turns a server log into a research tool. If bots keep asking for missing pages in the same pattern, the market may be showing you a page shape you have not built yet. The caveat matters. A bot hit is not a customer. Do not create thin pages for every strange crawl. Group the repeated patterns, check that you can answer them well, then build the pages that deserve to exist. ## Make the top of the page answer the question [Glasp question title rewrite from bot demand](/growth-ideas/glasp-question-title-rewrite-from-bot-demand/) and [Glasp standalone TLDR answer before long page](/growth-ideas/glasp-standalone-tldr-answer-before-long-page/) belong together. The title frames the question. The first two or three sentences answer it. This is good for people too. A reader should not need to scroll through setup language to learn whether the page is useful. In markets with noisy feeds and short attention, the first answer has to carry its weight. ## Do not break pages that already work [Glasp SEO Guard before AI-search rewrite queue](/growth-ideas/glasp-seo-guard-before-ai-search-rewrite-queue/) is the restraint every AI-search project needs. Lock pages with meaningful Google clicks. Remove pages with no organic or AI interest. Rewrite the middle. That is the part I would copy first for a startup. AI search is still messy to measure. If a page already earns trust from Google, do not casually rewrite it because a new dashboard made the team impatient. ## What I would test this week Pick one useful page family: docs, templates, videos, comparisons, city pages, marketplace listings, or support articles. Fix duplicate URLs. Pull the top missing URL patterns from AI-bot 404s. Rewrite only the pages with clear demand and weak openings. Protect pages with recent Google clicks. Then compare the changed group against a similar unchanged group. That last comparison is the honest part. Glasp's own paper warns that platform tailwind can make every AEO number look bigger than it is. A founder does not need a perfect academic experiment. But they do need a control group before they start congratulating the tactic for growth the whole platform delivered. ## Related GrowthDex tactics - [Glasp one URL per video before AEO rewrite](/growth-ideas/glasp-one-url-per-video-before-aeo-rewrite/) - AI Search, SEO, Technical SEO - [Glasp AI-bot 404 logs as page demand map](/growth-ideas/glasp-ai-bot-404-logs-as-page-demand-map/) - AI Search, SEO, Analytics - [Glasp question title rewrite from bot demand](/growth-ideas/glasp-question-title-rewrite-from-bot-demand/) - AI Search, SEO, Content Marketing - [Glasp standalone TLDR answer before long page](/growth-ideas/glasp-standalone-tldr-answer-before-long-page/) - AI Search, SEO, Copywriting - [Glasp SEO Guard before AI-search rewrite queue](/growth-ideas/glasp-seo-guard-before-ai-search-rewrite-queue/) - AI Search, SEO, Analytics ## Essay chronology - [Newer essay: The launch page is a proof record, not a scoreboard](/blog/the-launch-page-is-a-proof-record-not-a-scoreboard/) - Product Hunt, Launch, SEO - [Older essay: The brand should appear as one company before you chase more AI mentions](/blog/the-brand-should-appear-as-one-company-before-you-chase-more-ai-mentions/) - AI visibility, brand trust, SEO ## Keep reading - [The AI answer borrows trust before it borrows your homepage](/blog/the-ai-answer-borrows-trust-before-it-borrows-your-homepage/) - AI visibility, brand trust, SEO - [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 - [The trust surface should show the work](/blog/the-trust-surface-should-show-the-work/) - brand trust, community-led growth, SEO ## Continue through the blog - [AI products](/blog/#path-ai-products) - 3 essays in this path - [SaaS](/blog/#path-saas) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [arXiv: Glasp AEO natural experiment](https://arxiv.org/abs/2606.04362) · [GrowthDex source hub](/sources/arxiv-glasp-aeo-natural-experiment-arxiv-org/) - [arXiv TeX source for Glasp AEO treatment details](https://arxiv.org/e-print/2606.04362) · [GrowthDex source hub](/sources/arxiv-tex-source-for-glasp-aeo-treatment-details-arxiv-org/) - [Google Search Central: Consolidate duplicate URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) · [GrowthDex source hub](/sources/google-search-central-consolidate-duplicate-urls-developers-google-com/) ## Editing notes - Kept the essay plain and practical instead of selling AEO as a guaranteed traffic machine. - Explained each technical move in everyday language before naming the tactic. - Included Glasp's caveats about platform tailwind, controls, and SEO safety. - Used Ian's Ian's growth experience around page identity, market noise, and protecting working pages without inventing first-person stories. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.