Review Methodology

This page explains how a review gets published on this site, and what has to be true before it does. It exists so you don't have to take "we tested it" on faith.

The rule a review can't skip

A review only goes live if the tool was actually signed up for and used against a real task on this site — not read about, not summarized from a pricing page. This is enforced in the site's own code, not just a style guideline: a review page simply cannot publish without a hasFirsthandTestingflag set to true. If a tool hasn't been tested yet, it doesn't get a review page, no matter how interesting it looks.

What we actually check

• Price and trial terms — verified against the tool's own official pricing page directly, not against third-party blogs repeating each other's claims. This started after a Surfer SEO signup based on a "7-day money-back guarantee" that turned out to not be stated anywhere on Surfer's own official page.
• What actually breaks — bugs, confusing UX, and silent failures are treated as the most valuable part of a review, not something to smooth over. Examples already published: a Make.com scenario that logged "success" while an email silently never sent, an n8n default trigger interval that burns a free-tier quota in under 17 hours, and a missing og:image tag our own notes had marked "done" that a third-party audit caught.
• What a solo builder specifically needs — not "is this tool good in general," but whether it's usable on a real, small, low-traffic site without a team or a big budget.

Evidence, not just claims

Reviews include real screenshots from the actual testing session, exact error text where something failed, and specific numbers (not "fast" or "affordable," but the actual trial length, the actual price, the actual score a tool produced). When a tool's own output includes a statistic or a recommendation, it gets checked against an independent source before it's repeated as fact — this is the same standard applied to every vendor's marketing claims, applied to what the tools themselves generate too.

Affiliate relationships don't change the verdict

Some reviewed tools have an affiliate program and some don't. Three published reviews on this site (Screaming Frog, CoSchedule Headline Studio, Google PageSpeed Insights) have no affiliate program at all — they're published anyway, because the standard for publishing is "did we actually test it and find something worth telling a solo builder," not "does this pay a commission." See thedisclosure page for the affiliate policy itself.

Keeping reviews current

A tool's pricing and trial terms are confirmed at the time a review is tested and published, and that date is tracked internally against every reviewed tool. Reviews older than 90 days without a fresh check are flagged for a spot-check against the tool's current official pricing page before that information gets relied on. This site is new enough that nothing has hit that threshold yet, but the check exists now rather than waiting for a review to go stale first.