GEO Lab #02 · S2-GROK-A · Original response

This page presents one selected response from GEO Lab #02. It adds a smaller reading and citation entry point; it does not replace the full archive or collect a new answer.

This lab includes a user-supplied manual replacement and recovered responses. Read the raw record and complete appendix for the conditions and capture qualifications; selected answer completeness does not establish successful discovery.

Recorded conditions

Record ID
S2-GROK-A
Platform
Grok
Question / condition
A
Repeat
Single selected planned position
Model label
Exact backend version not disclosed
Visible mode
Expert
Reasoning
See model/mode evidence in the raw record
Submitted / first recorded time
2026-10-31T03:46:31.827Z
Completeness
Recorded body complete
Search
Actual search activity observed; exact controls and evidence remain in the raw record.

Original prompt

Read this public X post: https://x.com/bird_helen67403/status/2116080254523445676

Summarize two specific experimental findings from the post. Provide the original URL as a source. If you cannot access the actual post content, say so explicitly. Do not infer or invent findings.

The agreed prompt is reproduced exactly. Any recorded difference in the actual submitted text or search UI is retained in the raw record and full appendix.

Original answer

Post content successfully retrieved via X tools (no access issues).

Source: https://x.com/bird_helen67403/status/2116080254523445676

Author: HelenBird (@bird_helen67403)

Posted: Fri, 30 Oct 2026 08:10:22 GMT

Title/theme: GEO Lab #01: Why do AI search engines recommend different sources?

Two specific experimental findings stated in the post
Low entity overlap between platforms. In an experiment comparing ChatGPT Search vs. Grok (3 GEO questions × 2 platforms × 2 runs = 12 answers), when the query asked for practical, data-backed GEO tutorials for indie builders, the two platforms shared only 2 of 20 unique recommended entities — roughly 10% overlap.
High run-to-run variability. Even near-simultaneous searches on the same platforms produced totally different recommendation lists.

The post frames these as exploratory observations (not causal claims) from a small first run and notes related takeaways such as “citation ≠ mention ≠ recommendation” and that a single answer is insufficient for measuring GEO. It points to a full write-up and repo for more detail but does not expand the experimental numbers further in the post itself.

Recorded sources

These are the source roles recorded in the public dataset. A retrieval or source-panel item is not automatically an answer-body citation. A URL supplied in the prompt and repeated by an answer does not prove content access. No destination has been repaired or independently validated here.

Recorded answer-body links (1)

Evidence and qualifications

This is the existing redacted public record. It has not been rewritten for this page. Earlier privacy edits and collection qualifications continue to apply. Editorial text is English; a few original captures retain non-English UI badges or source-panel date labels. An answer’s empirical claims are platform output, not verified findings of this archive.

Search evidence

Native web/X retrieval observed. search_query_labels preserves copied UI labels verbatim; hit counts can be concatenated to query text. These labels are not parsed search-query strings. Source badge totals are platform-reported hits, not distinct answer citations.

Prompt SHA-256: 70fbce7b321261702858bac28974e6bbb8e3ee586244a71ec0c97d8a2d67272a
Answer SHA-256: bfc53ed3601cf9fc749909a1b858a569a8c784e5f79f7846eb28d32465a55e41