CASE.05 · Case study
An AI-readable mirror of my site that widened citation coverage, lifted positions and grew user visits referred by AI by 60% in five weeks.
AI search engines read the web differently from humans, and most sites aren’t built for them. I ran a five-week experiment on StillMind: a parallel /ai/ layer of the same content, restructured for retrieval and canonicalised back to the human pages so it couldn’t hurt SEO. Three things moved at once. Coverage widened by 12%, positions improved across three engines, and user visits referred by AI settled at +60% above their pre-launch baseline and have held at that level since. For a small brand with little authority, the coverage shift is the result that matters most.
- citation coverage
- +12%
- user visits referred by AI
- +60%
- across three engines
- #1
- not inferred
- Retrieved
AI engines retrieve from a different web than humans read, and a small brand with no authority can’t afford to be misread.
Human-facing sites carry navigation, hero sections, animations, sticky CTAs, cookie banners and recently-published carousels. Useful for a person scanning for trust signals; mostly noise for an engine trying to extract the answer to a question. The content shape problem is sharper still. Humans like narrative; AI engines reward short, self-contained question-and-answer blocks with the answer in the first 75 to 120 words.
Before I shipped anything, StillMind’s AI citations were usually directionally accurate and quietly wrong on the specifics. Pricing framings didn’t match my pricing. Features were attributed that weren’t mine. Generic descriptors got stitched together from competitor copy. The product was being described by inference, not retrieval. On a small brand, inaccurate citations are worse than no citations, because they set an expectation the install experience then has to undo.
Ship a parallel /ai/ layer of the same content, canonicalised back to the human pages, and measure everything that matters.
The bet was specific: if I gave the engines a structurally clean version of the same content, stripped of decoration, ordered as direct question-and-answer, schema-tagged, sourced verbatim from copy I already had, they’d retrieve from it instead of inferring. The risk was duplicate-content damage to organic SEO, which was already growing roughly 40% month on month and was the part I most wanted to protect. So every page on the /ai/ layer is canonicalised to its human equivalent, lives in a separate sitemap, and sits behind a feature flag I can flip off in one deploy.
The harder, more original work was the measurement harness around it. AI citations without measurement are noise. To call this a result, I needed five closed-loop signals running together: Search Console snapshots for the SEO safety net, GA4 referrer tracking for traffic attribution, a custom bot logger for crawl behaviour, cross-engine citation tracking across Claude, ChatGPT and Perplexity, and a written rollback rule keyed to two consecutive weeks of decline. The combination is what turned “we shipped some AI pages” into a defensible read on what changed.
- STEP.01 Build the mirror, not new content Every Q&A on /ai/ traces verbatim back to FAQPage schema or editorial entries on the human page. Plausible-sounding new content is hallucination, and I refused to ship that. /ai/topics/ and /ai/q/ pages, plus a flat index for crawl entry.
- STEP.02 Protect SEO by construction Every /ai/ page is canonicalised to its human equivalent. The /ai/ layer lives in a separate sitemap-ai.xml, kept out of the primary indexation signal. A feature flag flips the whole layer off in one deploy if anything goes wrong.
- STEP.03 Three discovery channels for AI bots A public llms.txt listing every topic hub, a <link rel="alternate"> on every human page pointing to the mirror, and direct fetch on citation resolution. None of them conflict with the human SEO setup.
- STEP.04 Wire the measurement harness Weekly Search Console snapshots; GA4 referrer attribution with a maintained AI-host list; a 1×1 bot-logger pixel on /ai/ pages capturing vendor and discovery method; cross-engine citation tracking across Claude (47 prompts), ChatGPT (25, Responses API), and Perplexity (16, Playwright, no public API).
- STEP.05 Write the rollback rule first Two consecutive weeks of declining trend on position, impressions or Lighthouse triggers a hard rollback. Clicks are confirming-signal only. Knowing the rule before launch is what let me ignore the dashboard dip a few days in.
Three results moved at once, and on a low-authority brand the coverage shift is the one that matters.
- citation coverage
- +12%
- user visits referred by AI
- +60%
- across three engines
- #1
- rollback triggers
- Zero
Coverage widened by roughly 12%: StillMind is now cited for more terms across more engines than before the layer existed. That’s the number to weigh most carefully, because for a small brand at our authority level, a 12-point coverage jump from a single piece of infrastructure is the disproportionate result, not the headline percentage. Positions inside that wider corpus also lifted. Claude holds StillMind at #1 on the journaling cluster across three consecutive weekly snapshots, ChatGPT at #1 on the journaling and ADHD prompts, Perplexity at #2 on the journaling query. User visits referred by AI settled at +60% above their pre-launch baseline after an initial +300% launch wave and have held at that level since (this is the slice of human visitors who clicked through from an AI engine, not the site’s overall traffic), with Gemini referrals appearing for the first time in week five.
The combination is what makes the read defensible. A spike in AI-referred visits on its own reads as luck. A coverage gain plus position lifts plus growing AI-referred visits reads as a system working. Nothing about my domain authority, backlinks or PR coverage changed across the window. The AI-readable layer was the only variable that moved, which is what lets me attribute the lift to it rather than to a coincidental authority boost in the background.
The mirror brought the lift; the harness gave me the confidence to ship it.
A few days after launch the Search Console dashboard looked bad: average position dipped, impressions softened on key terms, clicks went flat. Every founder instinct said the AI layer had broken something, and the rollback was one decision away. The pre-written rule held (single-day declines at this traffic volume are noise), but knowing the rule and watching the dashboard dip in real time are different things. What let me hold the line was the snapshot baseline: impressions were up 75% versus pre-launch, average position had improved 25% over the prior month, and the consecutive-declines counter sat firmly at zero. The real story turned out to be a recent stats post normalising back to its new (still elevated) floor, pulling the site-wide average down as it did.
The citation-accuracy shift was the part I underestimated most. Today’s engines retrieve real product copy: Perplexity now describes StillMind as “meditation plus journaling, core features free, optional Plus features unlock more insights … a freer starting point.” That tracks the product. The pricing framing is right, the journaling-plus-meditation framing is right, the freemium framing is right. Inaccurate citations cost more than no citations because they misalign expectations all the way through to install. Fixing that is worth more than the +60% on its own suggests.
Coverage and position are a roadmap. Authority is the ceiling.
The cross-engine tracking turned out to be the most durable output of the experiment. I now have three structured surfaces I didn’t have before: the queries I’m consistently #1 on (the journaling cluster, durably, across all three engines); the queries I’m inconsistently cited for (a clear list of pages to strengthen); and the queries I’m completely missing on (most condition-specific themes like anxiety and sleep, most demographic themes like parents and nurses). That turns “AI SEO” from a vibe into a workable next-twelve-weeks plan.
The honest ceiling is authority. AI search engines reward it the same way Google does, and a content layer alone can only take a small brand so far without reputation, backlinks and editorial mentions behind it. That isn’t a problem with the strategy. It’s the same dynamic that has always governed search. The next move is fuel: backlinks from publications in the journaling, ADHD and mindfulness adjacencies. The AI layer makes me retrievable. Authority makes me preferred.