Choose a crawl question and an observation window
Start with a question that request records can answer.
Use this for: Any SEO log analysis, including a targeted investigation on a small site.
Choose an issue such as repeated failures on category pages, unexpected parameter crawling or whether new articles were requested after publication. Name the hostname, affected URL group, bot and dates before asking the administrator for an existing access-log export.
Use a window that covers the relevant publishing or incident cycle and check its retention, missing intervals and sampling. A week that includes an outage may answer an incident question but not describe normal behavior. Request logs can show a fetch; they do not by themselves establish indexing or rendered content.
Hypothetical example: A catalog team wants to know whether product pages received requests after Friday’s release. It chooses that cohort and the available following period, rather than analyzing every request ever retained.
- Name the question, host, URL group and bot.
- Choose dates that cover the relevant event or publishing cycle.
- Confirm retention and sampling before treating the result as complete.
More help and optional notes
If it fails: Narrow the question or obtain an approved existing view with the missing coverage.
Retest: Recheck coverage whenever the export source, dates or filters change.
Not applicable: No request-level investigation is needed.
Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.
Changing this result updates your checkmark and progress immediately. Notes are optional.

