GEO Lab #04 · S4-GROK-Q3-R3 · Original response
This page presents one selected response from GEO Lab #04. 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
Original prompt
Who publishes practical, data-backed GEO tutorials for independent builders? Explain why and include sources when available.
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
Juan Camilo Auriti via GeoReady (geoready.dev) is one of the strongest matches, along with a few other practical publishers and free resources aimed at builders, solo founders, and independents. These stand out for being actionable (audits, checklists, step-by-step roadmaps, technical implementation), grounded in research (especially the foundational Princeton/KDD 2024 GEO study), and accessible without large teams or budgets. Primary recommendation: GeoReady (Juan Camilo Auriti) GeoReady publishes a large library of practical, research-grounded guides on AI search visibility and Generative Engine Optimization. It focuses on technical and content signals that help models find, understand, and cite sites (crawler access, llms.txt, schema, citability, entity signals, etc.), without hype or ranking guarantees.Geoready Why it fits independent builders: Built by a solo/independent founder (Juan Camilo Auriti, based in Italy) who started with an open-source GEO audit engine (GEO Optimizer, MIT-licensed Python CLI, installable via pip install geo-optimizer-skill). The hosted GeoReady platform sits on top of it for monitoring. Scoring is transparent and auditable—weights, checks, and reasoning are public, with references to research papers.Geoready Free guides covering foundations (robots.txt/AI crawlers, llms.txt), citability, execution checklists, platform-specific notes (Webflow, Shopify, SaaS docs, etc.), measurement, and research explainers. Includes free audits/checkers. Explicitly research-oriented: draws on the Princeton GEO paper (Aggarwal et al., KDD 2024) and related work, plus the author's own testing and methodology (also documented in a technical book, AI Search Engineering). Designed for people who want the system to make sense—developers, indie builders, SaaS founders, freelancers—rather than pure marketers or enterprises. This combination of open tools + practical walkthroughs + research grounding is particularly useful for independents who prefer to audit and implement themselves. Other strong practical, data-backed options Sam Shev’s 90-day GEO roadmap (samshev.com): A phased, actionable plan (audit → content/authority → measurement) that directly cites the Princeton/KDD 2024 study’s citation-lift numbers (e.g., quotation addition, statistics, fluency, inline citations) and includes schema checklists, KPIs, and “Answer Capsule” content formats. Useful for early-stage or resource-constrained builders who want a structured timeline without theory overload.Samshev Apollo Digital’s free GEO course (apollodigital.io/learn/geo/): Roughly 7 short lessons (~100 minutes) covering foundations, technical access (crawlers/robots.txt), measurement (with free Google Sheets templates for audits and share-of-voice tracking), and tooling. No signup gate; designed to be runnable with free tools. Agency-backed but self-serve and practical for independents.Apollodigital Developer- and solo-founder-focused guides: Developer’s guides (e.g., on DEV Community and similar pieces) emphasize technical implementation: schema, server-side rendering, robots.txt for AI crawlers, extractable content chunks, and measurement. These suit people who build their own sites. Solo-founder pieces (e.g., HeyCatch, RankRealizer-style guides) focus on low/no-budget tactics for pre-traction or indie products: answer-first structure, entity signals, and citability without heavy tooling. Community sources: Subreddits such as r/geoforbeginners and r/GenEngineOptimization contain practical checklists, “what actually stuck” workflows, and real experiments from independents (answer-first rewrites, tables for citability, prompt baselines, robots.txt/sitemap priorities). These are less polished but often highly practical and peer-tested. Key data backbone Most credible practical tutorials cite the 2024 KDD paper “GEO: Generative Engine Optimization” (Aggarwal, Murahari, et al.; arXiv:2311.09735). It tested content techniques on ~10,000 queries and found lifts from adding quotations, statistics, and cited sources (roughly in the 30–40% range on their position-adjusted visibility metric in controlled settings), with larger relative gains for lower-ranked sources, and negative or null results for keyword stuffing. Many guides treat this as the foundational evidence while layering on technical access, schema, entity work, and ongoing measurement. Note that results come from research setups (not necessarily live production engines in every case), so practitioners treat the numbers as directional.Aisyndicate In short: Start with GeoReady’s guides and free audit tools if you want research-grounded, builder-friendly, auditable resources from an independent maker. Pair them with a structured roadmap (Sam Shev) or free course (Apollo Digital) and the Princeton paper for the underlying data. Reddit communities add real-world independent experiments. The field is still evolving, so prioritize sources that show their methods, cite primary research, and focus on measurable signals over guarantees.
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 (5)
- Guides — AI Search Visibility & GEO (Geoready)Answer-body link/citation · geoready.dev
- About GeoReady — Built by Juan Camilo Auriti (Geoready)Answer-body link/citation · geoready.dev
- How to Start GEO: A 90-Day Generative Engine Optimization Roadmap | Sam Shev — Fractional CMO (Samshev)Answer-body link/citation · www.samshev.com
- The Free GEO Course: Learn Generative Engine Optimization | Apollo Digital (Apollodigital)Answer-body link/citation · apollodigital.io
- What the Princeton GEO Study Found | AI Syndicate (Aisyndicate)Answer-body link/citation · www.aisyndicate.com
Retrieval-only / source-panel inventory (5)
- geoready.dev/guides/Retrieval activity, not body citation · geoready.dev
- mogerio.com/article/generative-engine-optimization-guideRetrieval activity, not body citation · mogerio.com
- apollodigital.io/learn/geo/Retrieval activity, not body citation · apollodigital.io
- geoready.dev/about/Retrieval activity, not body citation · geoready.dev
- samshev.com/blog/geo-90-day-roadmapRetrieval activity, not body citation · www.samshev.com
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
Assistant read full native rendered answer; matching prompt checked; DOM body and expanded citation groups captured.
Body review
{
"reviewer": "assistant",
"complete_body_read": true,
"coherent_ending": true,
"inline_url_coverage_checked": true,
"external_claims_verified": false,
"independent_human_double_coding": false
}
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: b46e2a20c84c462f836fefd5fcbaaf575c024950eda0b5a94b6239df24e05c76
Answer SHA-256: 02e5e7e5db2c4d7b4181d820b8d7949ab54a6cc0e4c985438200271d311d1f86