Build a product review website readers can trust
A review site earns its readers by showing it actually used the thing. Each review needs who tested it, for how long, what went wrong, a verdict with its trade-offs and, if you earn from links, a disclosure next to them. Keep reviews as structured entries so every page answers the same questions in the same place.
What separates a review from a product listing
Search results are full of pages that rephrase a manufacturer's spec sheet and add a buy button. Readers and search engines have learned to skip them. A review that holds up has first-hand evidence: photos you took, measurements you made, the conditions you tested in, and the faults you found. If you've only read about a product, say so, and call the page a roundup rather than a review.
- Testing context. How long you used it, where, and against what. "Three months of daily commuting in rain" tells a reader more than "extensively tested".
- The awkward bits. Every product has some. A review with no downsides reads as an advert.
- Who it's for and who it isn't. A tent that's excellent for car camping may be the wrong choice for a long walk; say which reader should buy something else.
- A verdict in one or two sentences. Near the top, because many readers won't scroll.
Give every review the same fields
Consistency is what makes a gear review website easy to use. If every review has a verdict, a price band, a testing period and a list of pros and cons in the same order, readers learn where to look and you can build comparison pages from the same data. In Anticode this is what a CMS collection is for: a collection with typed fields, edited in the dashboard, where each entry is served at its own address such as /reviews/trail-shoe-x.
| Field | What goes in it |
|---|---|
| Product and maker | The exact model name and version you tested |
| Verdict | One or two sentences, written last |
| Tested for | Duration and conditions, in plain words |
| Good | Three to five specific strengths |
| Not so good | Real faults, including small irritations |
| Who should skip it | The reader for whom something else is better |
| Price band | Written as a range in words, checked on the date shown |
| Disclosure | Whether you bought it, were lent it or were given it, and whether links earn you money |
| Last checked | The date you last confirmed price and availability |
A review site lives or dies on updates. When a product gets a new version, add a note to the old entry rather than quietly rewriting it, and change the last-checked date so readers know the advice is current.
Affiliate links and disclosures
If an affiliate review website earns a commission when readers buy, most advertising regulators expect that to be clear before the reader clicks, not hidden in a footer. The US Federal Trade Commission's Endorsement Guides and the UK's advertising rules both work on this principle. A short line above the first link, such as "We earn a commission if you buy through these links; it doesn't change what we recommend", does the job. Say the same about free samples and loans.
Link out to each retailer or maker with a normal link. Anticode's pages can't embed shopping widgets or price feeds, because published pages allow no frames and no scripts, so prices on the page are ones you typed and should carry a date. Search engines also ask for affiliate links to be marked as sponsored; check the published HTML for the link attributes you need, since you can't hand-edit links in the code editor; if they're missing, ask for them in a change request and test again.
Building the site in Anticode
Describe it in a sentence, for example "a review site for budget trail-running gear with a reviews collection, a roundups page, a how-we-test page and an about page". The Architect plans the pages and asks what changes the build. Editorial (Geist) and Technical (IBM Plex Sans) suit review writing because they read well at length. Upload your own product photos to the build; they're more convincing than any stock image.
The Critic's checks help with the tone problem review sites often have. It flags stock AI phrases, and the design gate blocks placeholder text and empty links before publishing, which catches the generic praise that makes a review site read as filler. Neither checks that retailer links still work, so click through your outbound links whenever you update a review. A how-we-test page is worth its own entry in the navigation, next to an about page that says who you are (writing an about page covers that); they're the pages sceptical readers look for first.
What a review site built here won't have
- No reader ratings, reviews or comments. Visitors can't post star ratings or replies. If you want reader opinions, collect them with the contact form and quote them with permission.
- No live prices or stock levels. Prices are what you enter; date them.
- No shop. Readers buy from the retailer you link to. If you sell your own product alongside, point a button at a payment link.
- No RSS or scheduled posts. The CMS collections hold entries, but there's no feed, comments or publish scheduling.
Questions people ask
Do I need to have bought every product I review?
No, but say how you got it. A loaned or free product is fine if the review states it and the verdict isn't softened because of it.
Can I show a comparison table across several reviews?
Yes. Build a roundup page with a table, and keep the numbers in it consistent with each review entry. Update both when something changes.
Can readers vote on products or rate them?
Not on a published Anticode page. Pages run no scripts and there are no visitor accounts, so ratings would need a separate tool you link to.
How often should I update reviews?
Whenever the price, model or your opinion changes, and at least check your top pages a few times a year. Show the last-checked date on each one.