Write the research question narrowly
An original study needs a question that the collected data can actually answer. Which domains appeared in a defined set of answers is a narrower question than which brands dominate all AI search. Specify the population, observation unit, and time window before collecting data. Decide whether the study is exploratory or intended to test a particular hypothesis. Keep the scope small enough that another person can understand what was observed. A strong methodology begins by limiting the claim, not by collecting a large spreadsheet and searching for a dramatic headline afterward.
Record the collection conditions
Save prompts or queries, dates, locations where relevant, account state, model or service labels, and any filters applied. Record failures and exclusions instead of silently dropping them. Keep raw observations separate from cleaned tables so a reviewer can inspect transformations. If the data includes customer information, publish only material you have permission to share and protect private records. Your public methodology does not need to expose secrets, but it should explain enough about the process for readers to assess whether the findings apply to their own situation.
Distinguish counting from interpretation
Define what counts as a mention, a citation, a recommendation, or a successful result before scoring. These are different observations. Explain how ambiguous cases were handled and whether a second reviewer checked a sample. Google's helpful-content guidance and AI-content documentation are useful editorial references, but they do not validate your dataset. The strength of the study comes from the documented method and evidence. Keep statements about observed frequency separate from explanations about why that frequency occurred, especially when you cannot isolate the causes.
Hypothetical example: a small citation study
Imagine researchers collect answers to twelve fictional buyer questions from two services on one day. They record cited domains and discover that one domain appears in several answers. They can report that frequency within this sample. They cannot conclude that the domain is preferred by all users or that a specific optimization caused its presence. The article includes the question list, collection date, scoring rules, and a sample answer with sensitive information removed. A follow-up collection can test whether the pattern persists rather than treating the first snapshot as permanent.
Publish limitations beside the findings
Place important limitations where readers encounter the result, not only in a distant appendix. Explain what is missing: repeated runs, broader markets, personalized sessions, or a representative sampling frame. Provide a downloadable table when you can do so responsibly, with column definitions and a version identifier. Keep a correction log for data or analysis errors. If the method changes in a later edition, explain the break before comparing totals. A transparent study can be useful without claiming to measure an entire market or predict future results.
- Publish definitions for every counted category and explain ambiguous cases.
- Keep failed observations and exclusions visible in the internal research record.
- Describe method changes before comparing a new edition with previous findings.
Make the claim no broader than the observed sample and publish the rules used to interpret it.
Sources & further reading
Official documentation informs this guide. Examples are illustrative, and product interfaces or limits can change.
From search signals to a useful first draft.
SERP.so is in development. Join the waitlist for a workspace that connects research, content review, and publishing.
Join early access ↗