
A product comparison should help the reader choose for a particular use. Explain the criteria, the evidence, and the tradeoffs behind the recommendation. Repeating a supplier’s description under several headings adds little information for someone trying to make a decision.
Reconstructed archive: April 2021. Written in November 2026 using contemporary historical sources. The archive date organizes this series; this text is not a recovered original.
The April 2021 update
Google’s April 8, 2021 product reviews announcement emphasized in-depth research and original analysis for English-language reviews. Its guidance discussed expertise, practical differences, and benefits and drawbacks. The historical update provides a useful context for distinguishing substantive comparison from thin summaries.
December 2021: evidence behind firsthand claims
Google’s December 1, 2021 guidance built on the April update with advice about evidence of actual experience and, where sensible, purchase options from multiple sellers. That is dated historical guidance, not a universal requirement or guaranteed ranking formula. Both archive narratives were reconstructed in November 2026; they do not claim that Guardian conducted the product tests described as examples.
State how the comparison was made
Be clear whether the writer used the product, reviewed documentation, or relied on other sources. Do not imply firsthand testing that did not happen. The reader needs to know the basis of the observations before assessing the recommendation.
Keep the product and version, tested workflow, conditions, date and original notes or approved photographs with the conclusion. Distinguish direct observations from inferences based on documentation: seeing one workflow succeed does not establish that a product suits every business. Supplier images, staged scenes and generated illustrations are not evidence of firsthand use.
Choose criteria that matter
Start with the intended user and one task the product must support. For a small business selecting software, that might be handing an accepted inquiry to its existing office system. Maintenance responsibilities, compatibility and the actual workflow matter more than an undifferentiated feature list.
For each product and decision criterion, complete this compact comparison record using the evidence and version details described above:
- Required task: what the user needs to complete and any essential constraint.
- Evidence reference: the test note or dated documentation supporting the claim, with the method made clear.
- Finding and limit: what was established, what is inferred and what remains unknown.
- Tradeoff and fit: the practical benefit or drawback for this user, and who would need a different option.
- Next check: any unanswered question that prevents a supported recommendation.
Hypothetical desk-research example: a company needs to export inquiries into its office system. In this fictional comparison, one product’s documentation describes a CSV export; the other product’s documentation does not explain its export options. Record the first capability as documented but untested, and the second as unknown. Missing documentation does not prove that a feature is unavailable. Ask for the relevant format and a suitable sample before claiming either product fits the workflow. These are imaginary products, not a Guardian test or recommendation.
Google’s current review guidance emphasizes useful decision factors, evidence, comparable alternatives and benefits or drawbacks. Let those findings determine the recommendation rather than filling a fixed article length.
Discuss limitations honestly
A product can suit one user and be unsuitable for another. Describe relevant constraints and alternatives without inventing weaknesses. Keep commercial relationships understandable when they affect the publication or purchase links.
Keep practical alternatives and any relevant seller choices understandable so the review remains useful even if the reader chooses another option. Disclose applicable commercial relationships rather than allowing purchase links to obscure the basis of a recommendation.
Maintain the comparison
Name a reviewer and record when the comparison was last checked. Revisit the affected claims when a product version, plan restriction, integration, price used in the comparison or the reader’s requirements change. A changed product needs a review of the evidence, not merely a new date on the article.
Keep earlier observations tied to the version and conditions tested. Recheck an important recommendation before presenting it as current, and label unresolved facts. Preserve the existing source trail, original evidence and commercial disclosures so readers can assess the conclusion.
Explore website design, digital marketing strategy, or contact Guardian Solutions to discuss your next step.
Historical source: Google announcement dated 2021-04-08.
