Quality and evidence · Branch Q.C, Originality and defensible value
Q-09 Publish first-party data and explain where it comes from
Anonymised operations, sales, service, usage, survey or test data must be presented with sample, period and scope information.
- Scope
- All public content
- Priority
- High priority.
- Quality bucket
- Original, non-commodity value
- Legacy coverage
- GEO-21
Why it matters
Data shown without its sample, period or scope cannot be judged, so readers have no way to tell whether it applies to them. Search engines and AI answer engines also have little reason to trust or cite figures that arrive without context. Publishing raw data before data protection duties are settled creates a separate risk.
How to implement
- List the anonymous operational, sales, service, usage, survey or test data you could use.
- Resolve personal data and data protection obligations before publishing anything raw.
- State the sample size, period and inclusion and exclusion criteria next to each dataset.
- Present aggregate results separately from individual cases.
- Add a version and date system for any data that is updated.
Checklist
- Inventory the anonymous operational data that can be used.
- Do not publish raw data until personal data and data protection obligations are resolved.
- Write down the sample size, period and inclusion and exclusion criteria.
- Distinguish aggregate results from individual cases.
- If the data is updated, set up a version and date system.
How to audit
- Check that a data provenance record exists.
- Check the sample size and methodology.
- Review the data for sensitive information.
How UltimateSEO checks this automatically
This control needs human evidence: the first-party dataset, how it was collected and the provenance statement published with it.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
Part of The UltimateSEO Framework v4.1, revised 2026-10-07. Evidence states, control states and the publish gate are explained on the hub.