1. Define the experience
Name the answer experience, query, audience, locale, language, and date. Do not merge unlike surfaces.
GEO checklist · reference
Use this checklist to make generative-search research explicit: define the experience, capture the evidence, and write down what the observation cannot prove.
Direct answer
A good GEO checklist is a documentation habit: define the question, provider, target, operation, returned fields, date, and limitations before drawing a conclusion.
Reference guide
Name the answer experience, query, audience, locale, language, and date. Do not merge unlike surfaces.
Capture the operation, provider or model, sources, search results, brands, and other fields only when they are actually returned.
Write what the observation does not establish: no guarantee, exhaustive coverage, automatic optimization, or future outcome.
Check crawler access, ordinary indexing eligibility, important textual content, internal links, and whether structured data matches visible content. Record the result without turning it into a score.
Primary sources
Google Search Central. Platform guidance can change; recheck the source before acting.
OpenAI. Platform guidance can change; recheck the source before acting.
Perplexity. Platform guidance can change; recheck the source before acting.
Related guides
Return to the educational GEO reference hub.
Use precise documented directives for the intended crawler.
Keep people-first content and ordinary Search eligibility central.
Validate relevant markup without claiming special AI schema.
Questions
No. It improves research clarity; it does not create a ranking or outcome guarantee.
Have a real research question?
Use supported workflows and keep their boundaries visible.
Start free trial