Quality and evidence · Branch Q.C, Originality and defensible value
Q-11 First-hand experience claims must be backed by evidence
A claim such as 'we tested', 'we used' or 'we implemented' must be supported by real screenshots, photos, logs, measurements or case evidence.
- Scope
- All public content
- Priority
- High priority.
- Quality bucket
- Original, non-commodity value
- Legacy coverage
- GEO-23
Why it matters
Readers lose trust quickly when a claim of hands-on testing turns out to rest on stock images or nothing at all. Search engines and AI answer engines look for real experience, and unsupported claims of it undermine the page. Evidence is what separates genuine first-hand work from a claim of it.
How to implement
- Capture original screenshots or photos while you run the test.
- Redact sensitive customer data before publishing.
- Add the date, model and version to each piece of evidence.
- Replace any stock media that implies you tested something with real evidence, or remove the claim.
- Keep project records so each claim can be traced to its evidence.
Checklist
- Save original screenshots or photos during testing.
- Redact sensitive customer data.
- Add the date, model and version to the evidence.
- Do not use stock media to create the impression that 'we tested this'.
How to audit
- Run a reverse image check.
- Check the evidence metadata and project records.
- Check that each claim matches its evidence.
How UltimateSEO checks this automatically
This control needs human evidence: proof (photos, logs, samples, records) behind any first-hand experience claim.
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.