Can you write a credible product review without hands-on testing?

Yes, and disclosing how is what makes it credible. The honest alternative to fabricated testing is synthesis of owner experience at scale, verified manufacturer specs, and triangulated expert sources. Done at scale and disclosed, that is demonstrable original analysis, and Google's reviews system explicitly recognizes demonstrable original research and analysis as an alternative to first-hand experience. The one rule is that the piece never claims hands-on time that did not happen.

What are the four evidence tiers?

Tier 1 is verified manufacturer specs, cited to the maker's own current page and dated, supporting factual comparisons but never a quality verdict on its own. Tier 2 is owner-experience synthesis at scale, read across retailer corpora and forums with the sample size stated and splits surfaced as findings. Tier 3 is expert-source triangulation, named sources compared against each other with disagreements surfaced rather than averaged. Tier 4 is hands-on, stated only when true, flagged, and quantified. A strong piece usually combines two or three and says which.

What goes in the methodology block?

Four things: the criteria in the order they were weighted, stated before the picks; the tiers actually used, specifically, with sources; what was done hands-on or the words "none claimed for this piece"; and a dated update line saying what changed. It sits with the criteria, in body-size text, never in a footer. The hands-on line is mandatory even when the answer is none, because the absence stated plainly is the trust mechanism and the absence omitted is the lie of implication.

When is Review schema honest to use?

Markup is a claim, held to the same honesty as prose. Review and Product markup assert an evaluative review of an item the reviewer assessed, so use them only when the piece's claims support that, which in practice means tier 4 is real and stated. A buying guide built on tiers 1 to 3 uses guide-shaped markup instead: ItemList for the picks and Article for the piece. When genuine hands-on arrives later, add Review markup then, per piece, not as a template default.

Where should the affiliate disclosure go?

In plain language, placed where the recommendation is, not in a footer. The disclosure travels with the monetized content: near the picks, in body-size text, before or beside the first affiliate link a reader can act on. Plain language means a reader who has never heard the word affiliate understands that the site earns a commission and that the price they pay does not change. Euphemisms like "partner links" or "support the site" fail the plain-language test. The affiliate block is a sibling to the methodology block, not a substitute: one discloses the money, the other the evidence.

What if genuine hands-on testing exists?

The skill still applies. The tiers do not change; the methodology block simply states tier 4, and the testing protocol becomes the disclosed basis, with the extent quantified: what was done, how much, under what conditions. When hands-on experience arrives for a piece originally published on tiers 1 to 3, the piece is upgraded and the update is marked with what changed. It is never backfilled to look like it was always hands-on, because the upgrade trail is itself a trust signal.

Skill · Evidence-based reviews

Evidence-based reviews.

Produce reviews whose claims match their evidence. Never claim hands-on time that did not happen.

Most review sites fail one rule quietly: "We tested" appears above content assembled from spec sheets, and readers have learned to smell it. The honest alternative is stronger, not weaker. Synthesis of owner experience at scale, verified specifications, and triangulated expert sources is demonstrable original analysis, and disclosing it builds the trust that fabricated testing destroys.

The method is evidence synthesis with a disclosed basis: four tiers, a methodology block that names what each piece's verdicts rest on, and structured data that asserts only what the prose can support.

Audience: review and affiliate sites, editorial teams producing buying guides, and anyone writing product recommendations where hands-on access is partial or absent.

View the skill on GitHub Browse the full catalog

The framework

One rule, four evidence tiers.

The anchor rule: never claim hands-on time that did not happen. Every other part of the method exists to make honest content strong enough that the lie is unnecessary. A strong piece usually combines two or three tiers and says which.

Tier 1

Verified manufacturer specs

Specs cited to the maker's own current page, not aggregator copies that drift. Cross-check, date the pull, and flag discrepancies between sources instead of picking one silently. A fact layer, never a quality verdict on its own.

Tier 2

Owner-experience synthesis at scale

Retailer corpora, forums, warranty and return patterns read across sources. Recurrence over volume, sample-size candor, splits surfaced as findings, corpora named. The workhorse tier, and genuine original analysis when done at scale.

Tier 3

Expert-source triangulation

Named experts compared against each other. Surface agreement and disagreement rather than averaging verdicts into mush. When credible testers reach opposite conclusions, say so and explain the conditions. Anonymous "experts agree" is decoration, not a tier.

Tier 4

Hands-on, only when true

Stated only when it happened, flagged as such, with the extent quantified: what was done, how much, under what conditions. When hands-on arrives later, the piece is upgraded and the change is marked. Never backfilled to look like it was always hands-on.

The tiers are not a ladder of prestige; they are different kinds of knowledge with different verification work and different claims they can support.

The disclosure

Every piece names its evidence basis.

Every review and buying guide carries a short disclosure block naming its evidence basis, placed with the criteria, written for readers rather than lawyers. The block names the criteria in the order they were weighted, the tiers actually used (specifically, with sources), what was done hands-on or the words "none claimed," and the update line. A block that claims a tier the piece did not use is the same lie the anchor rule bans, in smaller type.

Placement is part of the honesty. The block sits with the criteria, before or immediately after the picks summary, never below the fold and never in a footer, in body-size text. The hands-on line is mandatory even when the answer is "none claimed": the absence stated plainly is the trust mechanism; the absence omitted is the lie of implication.

The affiliate disclosure is a sibling, not a substitute. The methodology block discloses the evidence; the affiliate block discloses the money. A piece with affiliate links carries both.

Structure the method implies

What the method requires of the page.

Honest evidence is only half the work. The structure has to make the honesty visible and traceable.

01Criteria stated and ordered before picks. A verdict the reader cannot trace to a stated criterion is an opinion wearing a methodology costume.
02A named drawback per recommended pick. Every product has one; a review that finds none has not looked. Consistent placement makes the honesty visible.
03Update transparency. Dated updates with what changed. Stale best-of content silently rotting is one of the most common failures in the category.
04Google reviews-system alignment via the original-analysis branch: synthesis, comparative tables from verified data, and decision frameworks, not rearranged spec bullets.
05FTC alignment: affiliate relationships disclosed in plain language, placed where the recommendation is, before or beside the first affiliate link a reader can act on.
06Schema judgment: markup is a claim. ItemList and Article by default; Review and Product markup only where tier 4 is true and stated.

The workflow

Seven steps from inventory to maintenance.

The method runs the same way whether the engagement is a site-wide methodology standard or a single piece.

01
Inventory the evidence honestly
What tiers are actually available for this category? What hands-on exists, if any? The inventory decides what the piece can claim.
02
Set the criteria first
Ordered, before any product is examined, so the criteria cannot quietly bend toward a favored pick.
03
Gather per tier
Verify specs at the source. Pull owner corpora at scale and note sample sizes. Collect named expert sources, including the disagreements.
04
Synthesize
Findings per criterion, drawbacks per pick, splits surfaced rather than averaged away.
05
Write the methodology block
From what was actually done, not from what sounds good. Every line true per piece.
06
Match the markup to the claims
ItemList and Article by default; Review only where tier 4 is true. Markup is a claim held to the same honesty as prose.
07
Maintain
Date updates, state what changed, upgrade pieces when hands-on arrives, and mark the upgrade.

Failure patterns

How review content lies, usually quietly.

Each pattern is a way the prose or the markup claims more than the evidence supports.

Anchor violation

"We tested" inflation

Hands-on language above spec-sheet content. It is also unnecessary: honest synthesis outperforms fake testing once readers compare the work.

Tier 1

Aggregator specs

Spec tables copied from other reviews, drift included. Verify at the maker's page or do not publish the number.

Tier 2

Anecdote dressed as synthesis

Three forum posts is not owner experience at scale. State the sample or downgrade the claim.

Tier 3

Averaged experts

Splitting the difference between conflicting verdicts erases the most useful information: that credible testers disagree, and why.

Structure

The drawback-free pick

A recommendation with no named drawback reads as advertising because it is structured like advertising.

Schema

Schema overreach

Review markup on synthesis content. The piece's prose is honest and its markup lies. Backfilled hands-on and footer disclosures fail the same way.

Reference files

Two references that go alongside the SKILL.md.

references/evidence-tiers.md
The four tiers in depth: the verification step for specs, synthesis honesty (scale, recurrence over volume, splits as findings, no cherry-picking, naming the corpora), triangulation practice with an independence check, and the upgrade-and-mark pattern for tier 4.
references/methodology-block-template.md
The fillable per-piece disclosure block, a worked example for a generic category, placement rules, and the anti-patterns that turn a block back into a claim generator.

Browse all reference files on GitHub

Bridges to other skills

Where the evidence layer hands off.

This skill governs the evidence and claims layer of review content specifically. These cover the writing, the voice, the page optimization, and the per-piece brief around it.

The writing layer
content-and-copy
Writes and edits the content itself. This skill governs what the review may claim and how the basis is disclosed; content-and-copy handles the prose that carries it.
The claims audit
editorial-qa
Audits drafts before publish, including claims content's evidence cannot support. The methodology block gives editorial-qa a concrete thing to check the prose against.
The per-piece brief
content-brief-authoring
Briefs each piece. The brief names the criteria and the evidence tiers planned; this skill is the discipline that keeps the published piece honest to them.
How the brand sounds
brand-voice
Defines the voice the review is written in. This skill stays in the evidence and claims lane; brand-voice owns tone and register.
Optimizing the page
seo-onpage
Optimizes the review page for search. Schema judgment here decides which markup is honest; seo-onpage handles the rest of the on-page optimization.

Open source under MIT

Read the SKILL.md on GitHub.

The skill source lives in the rampstackco/claude-skills repository alongside dozens of other skills covering the full lifecycle of brand and product work. This page is a structured overview; the SKILL.md is the source. MIT licensed.

View SKILL.md Browse the full catalog

Frequently asked questions.

Can you write a credible product review without hands-on testing?: Yes, and disclosing how is what makes it credible. The honest alternative to fabricated testing is synthesis of owner experience at scale, verified manufacturer specs, and triangulated expert sources. Done at scale and disclosed, that is demonstrable original analysis, and Google's reviews system explicitly recognizes demonstrable original research and analysis as an alternative to first-hand experience. The one rule is that the piece never claims hands-on time that did not happen.
What are the four evidence tiers?: Tier 1 is verified manufacturer specs, cited to the maker's own current page and dated, supporting factual comparisons but never a quality verdict on its own. Tier 2 is owner-experience synthesis at scale, read across retailer corpora and forums with the sample size stated and splits surfaced as findings. Tier 3 is expert-source triangulation, named sources compared against each other with disagreements surfaced rather than averaged. Tier 4 is hands-on, stated only when true, flagged, and quantified. A strong piece usually combines two or three and says which.
What goes in the methodology block?: Four things: the criteria in the order they were weighted, stated before the picks; the tiers actually used, specifically, with sources; what was done hands-on or the words "none claimed for this piece"; and a dated update line saying what changed. It sits with the criteria, in body-size text, never in a footer. The hands-on line is mandatory even when the answer is none, because the absence stated plainly is the trust mechanism and the absence omitted is the lie of implication.
When is Review schema honest to use?: Markup is a claim, held to the same honesty as prose. Review and Product markup assert an evaluative review of an item the reviewer assessed, so use them only when the piece's claims support that, which in practice means tier 4 is real and stated. A buying guide built on tiers 1 to 3 uses guide-shaped markup instead: ItemList for the picks and Article for the piece. When genuine hands-on arrives later, add Review markup then, per piece, not as a template default.
Where should the affiliate disclosure go?: In plain language, placed where the recommendation is, not in a footer. The disclosure travels with the monetized content: near the picks, in body-size text, before or beside the first affiliate link a reader can act on. Plain language means a reader who has never heard the word affiliate understands that the site earns a commission and that the price they pay does not change. Euphemisms like "partner links" or "support the site" fail the plain-language test. The affiliate block is a sibling to the methodology block, not a substitute: one discloses the money, the other the evidence.
What if genuine hands-on testing exists?: The skill still applies. The tiers do not change; the methodology block simply states tier 4, and the testing protocol becomes the disclosed basis, with the extent quantified: what was done, how much, under what conditions. When hands-on experience arrives for a piece originally published on tiers 1 to 3, the piece is upgraded and the update is marked with what changed. It is never backfilled to look like it was always hands-on, because the upgrade trail is itself a trust signal.