Reviews and reputation watch
Collects new reviews for you and named rivals on each run, de-duplicated and themed, and shows which themes moved.
Solutions · by problem
We have good reviews. Why aren't they turning into enquiries?
Your Google rating beats theirs. Their homepage shows their reviews and yours shows none. A buyer comparing three sites may never open Google Maps, so proof missing from the pages they read does no work. The free report shows where your proof is missing, page by page, beside your named rivals.
Answered today
The problem
What owners say.
- Our reviews are better than theirs. Why do they get the calls?
- We've got loads of five-star reviews and nobody mentions them on the phone.
- I don't know what people actually say about us, beyond the stars.
- Should we be on Trustpilot as well as Google?
Composite phrasings of a common problem, not quotes from named customers.
Why it is hard
Why checking by hand fails.
The star rating says the least. What persuades a new buyer is the detail: the job, the problem, the person they dealt with. Sorting your reviews and your rivals' into themes by hand is slow, and you read your own with a bias.
Placement decides whether a review works. In the sample report, run on a constructed test firm, the on-site testimonials carry first names only. The top-scoring rival embeds its Google reviews with full names. First-name-only attribution reads as low trust to a first-time buyer.
Review sources differ. Some read reliably. Some change their pages often enough to break a reading. Each source carries a health flag, and the reading lists the sources it could not read.
The limits. We read reviews that already exist. We never write, buy or post them. Tracking which themes grow or shrink needs the reviews watch, which is in build and not on sale.
What we read
Each source, and the code that reads it.
Every source names the module in our code that reads it. A source marked in build does not run for customers yet.
- Google reviewsRating and review count for you and each rival, as published.
src/lib/connectors/places.ts - Review sites and forumsReview text from the sources that can be read, grouped into themes in the words buyers use.
src/lib/reviews/sources.ts - Theme analysisRecurring praise and complaints, each theme backed by verbatim quotes instead of a score.
src/lib/reviews/analyze.ts - Your pages, read by buyer typeWhether proof shows on the pages a buyer reads before deciding, and how each buyer type weighs it.
src/lib/prompt/evaluate.ts
What you get
What you get back.
- Your rating and review count beside each rival's
- The themes buyers repeat about you and about them, quoted
- The pages where proof is missing before a buyer decides
- Once the reviews watch ships: which themes grew or shrank since the last run
Today and in build
What runs today, and what is in build.
Live tools run now. Loops in build will answer it again on a cadence you choose. They are not on sale.
Where it comes up
Industries that ask this.
Each industry page puts the problem in that trade's terms.
FAQ
Questions about “Why aren't my reviews converting”
Will you write or post reviews for us?
No. We read reviews that exist. We never write, buy or post them.
Which review sources do you read?
Google reviews through the Places data, plus review sites and forums whose pages read reliably. Each source carries a health flag. A reading lists every source it could not read.
Do I need more reviews?
Sometimes. More often the gap is placement and detail: proof missing from the pages buyers read, or reviews that say less than your rivals' reviews do. The reading shows which.
Can I see what my rivals' customers complain about?
Yes, where their reviews are public. A rival's complaint themes are a list of what buyers in your market want and are not getting.
Is the reviews watch available?
Not yet. It is in build and not on sale. The one-off readings above are live today.
Name the rivals you lose to.
The free report reads your site beside theirs, five buyer types on one rubric. No account and no card to start.