Start with authoritative documentation
Product descriptions should be checked against provider documentation, published plan specifications, terms, status records, and other sources appropriate to the claim. Provider materials describe an offer; they do not independently prove service quality.
AI citations are research evidence, not automatic verification. A cited page must support the specific statement attributed to it.
Qualify performance and security claims
A published uptime promise is different from observed availability. Benchmark results depend on workload, location, configuration, and date. Security claims should identify the protection, certification, scope, and source rather than imply universal protection.
- Distinguish introductory pricing from renewal pricing.
- Identify resource caps, acceptable-use policies, and plan-dependent features.
- Keep service guarantees separate from independent measured results.
- Do not imply that a compliance claim makes every hosted application compliant.
Describe the checks that actually happened
Our consensus research measures recorded AI recommendations. It does not imply that we purchased, deployed, or stress-tested every plan mentioned. Independent testing belongs in an article only when the testing and conditions are documented.