# Glasp on-domain control before AEO multiple claim

> Measure answer-engine work against an untreated on-domain control group before claiming an AEO lift from the platform tailwind.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/glasp-on-domain-control-before-aeo-multiple-claim/
- Source: [arxiv.org](https://arxiv.org/abs/2606.04362)
- GrowthDex source hub: [arXiv: Glasp AEO natural experiment](/sources/arxiv-glasp-aeo-natural-experiment-arxiv-org/)
- Last checked: 2026-06-09T05:05:50.000Z
- Rarity: rare
- Budget: medium
- Channels: AI Search, SEO, Analytics
- Stages: AEO measurement, control group, ChatGPT referrals, treated pages, platform tailwind


## Why this can grow

AEO numbers are getting noisy. If the whole platform is receiving more ChatGPT referrals, a treated page cluster can look brilliant even when the intervention only explains part of the lift. The Glasp arXiv study is useful because it separates treated YouTube Q&A pages from untreated pages on the same high-traffic domain. That is a more honest way to read the work. For founders, the tactic is to pick a page subset, make the answer-engine changes there, leave a comparable subset alone, and compare the treated/control ratio. Ian's operator lens: in fast consumer growth, platform tailwinds are real, but confusing tailwind for tactic makes the next budget decision worse.

## 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 glasp on-domain control before aeo multiple claim can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the AI Search and SEO channel.
3. Use the evidence from arxiv.org 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

A 2026 arXiv field study on Glasp analyzed hundreds of thousands of YouTube Q&A pages, comparing treated AEO pages with untreated pages on the same domain to separate intervention lift from ChatGPT referral tailwind.

## Adjacent tactics in the same lane

- [Onboarding discovery bundle for AI-native sites](/growth-ideas/onboarding-discovery-bundle-for-ai-native-sites/) - 2 shared channels
- [Recurring docs audit for broken links and style drift](/growth-ideas/recurring-docs-audit-for-broken-links-and-style-drift/) - 2 shared channels
- [AI SaaS persona-use-case pages before template multiplication](/growth-ideas/ai-saas-persona-use-case-pages-before-template-multiplication/) - 2 shared channels
- [Ahrefs real-search prompt set before synthetic LLM scorecard](/growth-ideas/ahrefs-real-search-prompt-set-before-synthetic-llm-scorecard/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The answer should travel before the page ranks](/blog/the-answer-should-travel-before-the-page-ranks/) - Community SEO, answer ops, AI visibility

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.