GEO Lab #03 · S3-GROK-M1-R3 · Original response

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

The OpenAI arm uses the Responses API with web search and does not represent consumer ChatGPT Search. Grok records identify their actual consumer-interface mode and available model label.

Recorded conditions

Record ID
S3-GROK-M1-R3
Platform
Grok
Question / condition
M1
Repeat
3
Model label
Exact backend version undisclosed
Visible mode
Expert
Reasoning
Not independently selectable
Submitted / first recorded time
2026-11-02T06:49:23.031Z
Completeness
Recorded body complete
Search
Actual search activity observed; exact controls and evidence remain in the raw record.

Original prompt

I'm a solo SaaS founder with no GEO budget. How can I reliably measure whether ChatGPT and Grok recommend my product to potential buyers?

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

You can measure this reliably for free with a fixed set of buyer-intent prompts, repeated manual tests on ChatGPT and Grok, and a simple spreadsheet. This is the standard low-cost approach used by solo founders and small teams for GEO (Generative Engine Optimization).⁠Shmeer

Paid AI visibility tools exist, but you do not need them for a usable signal.

1. Build a fixed prompt set (15–30 prompts)

Create questions a real potential buyer would ask without naming your product. Keep the wording identical every time so you can compare results over weeks.

Include a mix of:

Category / “best of” queries (“best [category] for [specific use case]”, “top tools for [problem]”)
Problem-solving queries (“how do I [problem your product solves]”)
Comparison / alternative queries (“[competitor] alternatives”, “cheapest [category] that does X”)
Evaluation queries (“what to look for in a [category] tool”)

Start with 15–20 high-intent ones. Add more later if needed. These become your permanent test panel.⁠Gomega

2. Run them manually and log everything

For each prompt:

Run it 3–5 times on ChatGPT and on Grok (answers vary a lot; single runs are noisy).⁠Geoaura
Prefer modes that can search the web when available, since product recommendations often rely on current information rather than pure training data.
Record in a Google Sheet (or any free spreadsheet):
Date	Engine	Prompt	Mentioned? (Y/N)	Position in list	Cited your site?	Competitors mentioned	Sentiment / accuracy notes	Sources cited

Key metrics to calculate from the log:

Mention rate — % of runs where your product appears at all
Share of voice — your mentions vs. competitors
Average position — where you appear when mentioned
Citation rate — how often your domain is linked or referenced as a source
Accuracy / sentiment — whether the description is correct and positive

Do this weekly or every two weeks. Look at trends, not any single answer. One-off results fluctuate heavily.⁠Snezzi

3. Use free one-time or limited tools for a baseline
HubSpot AEO / AI Search Grader — free, no account required for the basic check. Enter your brand + category and it scores how ChatGPT, Perplexity, and Gemini characterize you (sentiment, presence, share of voice, etc.). Good for a quick snapshot.⁠Hubspot
Mangools AI Search Watcher — free plan includes 5 prompts monitored weekly across multiple engines, including ChatGPT and Grok. Useful for a small recurring automated check while you do the rest manually.
Free page-level GEO checkers (various sites) — these score how “citable” a page is (structure, schema, crawler access, etc.). They do not replace prompt testing but help explain why you might or might not appear.
4. Check actual traffic impact (lagging indicator)

In Google Analytics 4:

Go to Reports → Acquisition → Traffic acquisition.
Look for the AI Assistant channel (added in 2026) or filter by session source for chatgpt.com (and similar for other tools).
Note: many AI visits arrive without a clear referrer and show as Direct. OpenAI has documented that ChatGPT can add utm_source=chatgpt.com to links.⁠Goodatmarketing

Also check:

Google Search Console for AI Overviews / AI Mode impressions (when relevant).
Bing Webmaster Tools AI Performance report for citations in Copilot/Bing AI.

This shows whether mentions are turning into visits, not just whether the models know you exist.

Practical tips for a solo founder
Keep the prompt list short enough that a full cycle takes 1–2 hours. Consistency beats volume.
Test both ChatGPT and Grok the same way so you can compare engines.
When you get mentioned, note how (brief list item, detailed recommendation, with link or without). That tells you what to improve.
Technical readiness still matters: make sure AI crawlers can reach your site, important content is in the HTML (not only behind JS), and key pages have clear structure + schema. Free GEO checkers flag the biggest blockers.
Expect noise. The reliable signal is directional change over 4–8 weeks of consistent testing, not day-to-day jumps.

This method is what most practical GEO guides recommend when you have zero budget: fixed buyer prompts + repeated manual logging + free graders + GA4/Search Console for confirmation.⁠Explaingeo

Start with your 15–20 prompts this week, establish a baseline, then re-run on a schedule. You’ll quickly see whether ChatGPT and Grok surface your product for real buyer questions and whether that improves as you update content or get more mentions elsewhere.

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 (7)

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.

Capture method

Complete rendered Grok article innerText; UI heading/duration and source badge removed. Exact inline hrefs extracted from scoped rendered article.

Existing public-text privacy policy

{
"body_changed": false,
"policy": "Only actual URL tracking, signed/session URL parameters and necessary identifying information are removed; original wording, including analytics parameter examples outside URLs, remains.",
"annotation_positions": "Original position indexes omitted because URL/privacy edits can change character locations."
}

Prompt SHA-256: 709fd6fc82fe3f87b623fb3dd8b2adecdd6655c3508115f8b40c573d2397776d
Answer SHA-256: 627052d5c8f83a146fb045bcc8ecce38f2814d2cdd38f7848b8a67cd8548e8c9