A buyer's guide has one job: help someone who has already decided to buy pick the right option for their situation. The guides that do this well have the same shape. They cover a short list of products, each one matched to a type of reader, with the drawbacks stated and the recommendation at the top.
Most of the work is judgment you exercise before writing: which products make the cut, what you can honestly say about the ones you haven't used, and how to handle details that will be wrong in three months. Below is how I'd handle each, plus an outline you can copy.
Start with the buyers, then pick the products
Before you look at a single product, write down the three to five situations your readers are in. For a guide to email tools for bloggers, that might be someone starting a first list with no budget, someone selling digital products, and someone leaving a tool that got expensive as their list grew.
Then find the best fit for each situation. This gives every product a reason to be in the guide, and it hands you the "best for" labels without any forcing.
It also sets the length. You need about as many products as you have situations, which usually means four to six. A guide with fifteen products is a catalog, and the reader still has to do the deciding.
Two more calls I'd make at this stage:
- Choose first, check commissions second. If the best fit for a situation has no affiliate program, include it anyway with a plain link. A guide where every pick happens to pay you is easy to spot.
- Cover the popular option you wouldn't pick. Readers are already considering it. Saying who it suits and why you'd pass does more for your credibility than leaving it out.
Your situation list doubles as keyword research, because "best X for Y" searches are those same situations typed into a search box. If you need help judging which ones a small site can rank for, see how to size up a keyword's real opportunity.
An outline that works for most buyer's guides
- Disclosure. One plain sentence before the first link.
- The short answer. A small table: situation, pick, one-line reason.
- How you chose. What you used yourself, what you only researched, and the two to four criteria that matter in this category.
- One section per pick, in the same order every time. Who it's for, what it does well, where it falls short, who should skip it, then the link.
- What you left out. The well-known options that didn't make it and why, in a sentence or two each.
- Still unsure? A few "if this, then that" lines for readers stuck between two picks.
- Last updated. The date you last rechecked the guide and what changed.
The table in step 2 can be this simple:
| If you are… | Pick | Why |
|---|
| Starting with no budget | Product A | Free plan covers the basics |
| Selling your own products | Product B | Checkout is built in |
| Outgrowing your current tool | Product C | Pricing stays flat as you grow |
Three columns fit on a phone. Anything a reader needs beyond that belongs in the product's own section. The same thinking applies to the rest of the page, and the layout choices that affect readability are worth getting right on a format people skim.
Organize by situation, not by ranking
A numbered ranking tells the reader that number one is best for everybody, which is rarely true, and leaves them to work out whether number four is the one that fits them. Headings like "Best if you're starting with no budget" do that work for them.
You can still name an overall pick when one option suits most readers. Say who it doesn't suit in the same breath.
The same rule applies to specs. Include a spec only when it changes the decision, and translate it into a consequence. "Sends up to 1,000 emails a month on the free plan" matters to a new blogger; a full feature grid copied from the pricing page doesn't help anyone choose.
What to say when you haven't tested a product
Say so. Hardly anyone can buy and use every product in a category, and readers don't expect it. What they can't forgive is finding out that a "hands-on" verdict was assembled from the manufacturer's sales page.
Google's guidance on writing high-quality reviews asks for evidence of your own experience, such as visuals, audio or links, and says that when you call something the best overall or best for a purpose, you should explain why with first-hand supporting evidence. The FTC is blunter in its endorsement FAQ: you can't talk about your experience with a product you haven't tried.
In practice:
- Label each pick as used or researched, in the "how you chose" section and again in the product's own section.
- For products you used, show it. Your own photos, screenshots and measurements are details nobody can copy from a spec sheet.
- For products you researched, name the sources: the documentation, the pricing page, patterns in owner reviews. Say what you couldn't check.
- Keep experience language out of researched picks. "Feels sturdy" and "setup took ten minutes" are claims about something that happened.
A guide where you used two of five products and said so is more useful than one that fakes all five. It's also harder to copy, which matters more now that anyone can generate a passable roundup in a minute. I'd treat that first-hand material as the part of your site that cheap AI content can't replicate.
Handling prices and availability that go stale
Exact prices are the first thing to go wrong, so keep them out of your sentences. Relative statements last longer: "the cheapest of the five", "roughly double the price of Product A". Then send the reader to the seller for the current number.
Some programs don't leave this up to you. Amazon's Associates Program Policies only allow you to show prices and availability when Amazon serves the link that displays them or when you pull the data through its API, so a hand-typed Amazon price is a compliance problem as well as a stale one. The other Amazon Associates terms that affect how you write are covered separately.
For everything else that changes, keep the volatile facts in one place, ideally the summary table, so an update is a single pass. On each pass, check four things:
- Is every product still sold in the form you describe?
- Have plans, tiers or features changed?
- Has a new option appeared that deserves a slot?
- Do all the links still work?
I'd recheck software and electronics guides every quarter and slower categories twice a year. Put a "last updated" date near the top, and only change it when you've actually rechecked.
Where the recommendation, links and disclosure go
The recommendation goes at the top. Readers who only wanted the answer get it, and those who want the reasoning keep reading.
Put a link in the summary table and one at the end of each product's section, after the reasoning. Linking every mention of a product name makes the page read like an ad. Google's review guidance also suggests linking to more than one seller where you can, so the reader has options.
The disclosure goes before the first affiliate link, in plain words. The FTC's FAQ says the closer it sits to the recommendation the better, gives "I get commissions for purchases made through links in this post" as an example, and says the words "affiliate link" alone aren't enough. The wording and placement details are in this guide to FTC-compliant affiliate disclosures.
Earning more from one pick than another is fine. Letting the commission choose the pick isn't. The test I'd use: if every product paid the same, would the guide recommend the same things?
Before you publish
Read only the summary table and the first two paragraphs. If a reader could make a reasonable choice from those alone, and the sections below back up each pick with something you checked yourself, the guide is ready. For the drafting itself, this framework for writing articles faster and more clearly picks up where the outline leaves off.