Does an answer-first opening change how often we're cited?

Status: closed as inconclusive on 21 October 2026. The original review date remains 8 July 2026. The design below records what was intended in that window; it is not a promise that the current article versions remain unchanged.

Closure review — 21 October 2026

The production readout inspected on 21 October 2026 was inconclusive: treatment 8 before / 5 after (13 total), control 14 before / 4 after. The treatment total was below the existing minimum of 20 claimed requests. These are historical User-Agent counts, not verified identities. The analyser uses 14 calendar days before and 14 after 8 June (25 May–7 June and 8–21 June); this is narrower than the protocol's 8 July review date. We disclose that mismatch rather than retrospectively change the analysis window to seek a result. The observation does not establish that the intervention caused more citations. Crawler requests are a proxy, not human exposure or citation. Historical requests cannot be retrospectively verified without appropriate IP evidence. A small pair and short baseline cannot settle a weak effect; a null or unavailable observation is not evidence that the method never works.

We preserved the article and protocol snapshots with SHA-256 checksums before the October editorial updates. That preservation establishes the pre-update state, not byte identity across the original window. The scheduled July review was overdue; this closure must not be backdated to July.

The monthly site-wide citation history is available in the Lab, including a September citation. It is not page-level attribution and is outside the original review window. No new paid panel run was made for closure. A restart requires a new versioned protocol, dates, page snapshots, equal measurement of both arms, minimum analysable sample, missing-data rules and an approved provider budget. This protocol has not restarted.

Historical protocol

The question

If we open an article with the answer instead of a wind-up, do LLMs cite it more? Answer-first structure is the most repeated piece of GEO advice — including in our own playbook. Before we keep repeating it, we test it on a page we control.

The design

• Treatment: the opening of JSON-LD recipes for GEO was rewritten to state the core answer first, in clean standalone sentences — replacing a soft "you don't need to remember the whole spec" lead-in. The body below the fold is untouched.
• Control: the llms.txt spec article opening was designated to remain unchanged during the original window.
• Primary metric: AI-crawler re-fetch frequency per page (free, page-level), treatment vs control.
• Window: the before window is whatever per-page crawl history exists (short — tracking began ~2026-05-31); the review is 2026-07-08.

Why these two pages

Both are technical articles, so page type is held roughly constant. They differ in kind — the treatment is a spoke recipe page, the control a cornerstone audit — which is disclosed as a residual confounder, as is a minor co-intervention: the treatment gained a new inbound link from the just-published geo-methods-taxonomy on the same day. Both are disclosed above; on this short, near-zero before-window the honest expectation is an early inconclusive.

The honest catch (and the parked half)

This experiment targets citation, and our citation harness measures the whole domain, not a single page. So we cannot cleanly answer "did this rewrite get this page cited more." The analyzer says so: for a page-level citation question on site-wide data, it returns inconclusive and attaches only the site-wide trend as context. That citation half is also parked — it needs LLM-API spend, which is off; no harness was run for this launch, and the site-wide context will only be attached at review if/when API spend is re-enabled.

What we can measure per page, for free, is crawler re-fetch frequency — a proxy for "the bots noticed a change worth re-reading." We treat that as the readable signal and are explicit that it is a proxy.

What would count as a result

A sustained rise in crawler re-fetches of the treatment page that the control does not share, ideally alongside (not proven by) a site-wide citation uptick. We will not claim the rewrite "raised citations" on site-wide data alone.