What we call researched
A researched page uses public product information, provider surfaces, structured comparison logic, and explicit citations. It does not claim hands-on testing unless real test evidence exists.
- Source product/vendor materials
- Cross-check third-party references when available
- Use citations for factual, non-first-party claims
What we do not fake
We do not write as if a product was tested if it was only researched or verified against docs. We do not invent reviewer identities or imply lab-grade validation that did not happen.
- No fake testing badges
- No fake reviewer bios
- No artificial confidence inflation on thin pages
How researched pages differ from verified docs and field notes
Researched pages synthesize credible sources and explicit trade-offs. Verified docs pages check official docs, pricing, integration, or support materials directly. Field notes pages add documented operator observations from a real browser or runtime workflow, but they are still not presented as lab testing.
- Researched = desk research with citations and synthesis
- Verified docs = official source materials verified directly
- Field notes = operator observations captured with an evidence packet
- Tested and Expert reviewed are reserved internal states
How pages get updated
Pages are refreshed when programme availability, content quality signals, or affiliate/commercial fit changes. Significant refreshes should keep update language honest.
- Corrections take priority over routine updates
- Material changes should keep a visible updated date
- If a page becomes too weak, it should be rewritten or removed from publication