Your Reviews Never Mention the Services You Sell

A roofing company with 212 Google reviews and a 4.8 average could not get found for flat roof repair. The reviews were real, recent, and glowing. Not one of them contained the word "flat." The company sold five services and its review corpus only described one of them, in vague terms, over and over.

That is a coverage problem, not a reputation problem. And it is invisible if you only look at star ratings and review counts, which is what most owners and most reporting dashboards look at.

Export sixty reviews and build the coverage matrix

The audit takes about ninety minutes and requires no tools beyond a spreadsheet.

Pull your last 60 Google reviews into a document. Sixty is enough to be representative and small enough that you will actually read all of them. Then, in a separate column, list two things:

• Every service you sell, written the way a customer would say it, not the way your invoice says it. "Water heater replacement," not "hydronic systems."
• Every objection you handle on the phone. Price uncertainty, weekend availability, whether you work in a specific neighborhood, whether you handle insurance, whether you touch older properties, how long the job takes.

Now mark each row with a simple count: how many of those 60 reviews contain language that names that service or resolves that objection. Not implies it. Names it.

Most businesses end this exercise with a column of zeros. A six-service company will typically find that three services have zero mentions, one has heavy mentions, and the remaining two appear once or twice in passing. Neighborhood names appear in under 10 percent of reviews. Price range almost never appears. The specific problem that brought the customer in appears far less often than owners expect, because customers write about how they felt, not about what was wrong.

Treat that column of zeros exactly like a keyword gap report. Those are the jobs your own customers have never publicly said you do well.

The friendly, fast, professional trap

Roughly 80 percent of unprompted reviews land in the same narrow band: some combination of friendly, fast, professional, fair price, would recommend. These reviews are genuinely positive and almost completely non-differentiating. Every competitor in your map pack has the same sentences.

This matters more now than it did three years ago because of what is reading the reviews. Jessica Bowman, speaking to Search Engine Land in September 2026, made the point directly: AI systems weigh reviews, operations, and reputation rather than content alone. Search Engine Journal published a 90-day local AI visibility plan the same week built primarily around review and reputation signals rather than page optimization.

The practical consequence is that when someone asks an assistant for "a plumber near me who can handle a slab leak in an older house," the system is looking for corroboration that you have done that specific thing. Your service page claiming it is a first-party assertion. A customer saying "found and fixed a slab leak under our 1962 ranch in two visits" is third-party evidence. SEOGOD horizon signals show local discovery moving steadily from keyword matching toward proof, with third-party corroboration acting as a primary selection input rather than a tiebreaker.

Generic praise cannot corroborate anything. It confirms you are pleasant to deal with, which the ten businesses beside you have also established.

Time the ask to the moment of proven value

Specific reviews come from specific moments, not from better templates.

Most review requests go out on a schedule: two days after invoice, three days after delivery, whenever the CRM fires. By then the customer has moved on and writes from memory, which produces exactly the generic summary you already have too many of.

Ask instead at the moment the value becomes visible. The leak stops. The unit turns on. The customer says "oh wow" out loud. That is the window, and it is usually the same day, often the same hour. A field tech asking in person at that moment gets both higher response rates and dramatically more detail than any automated sequence.

Then replace your script with a single open question. Not "please leave us a five star review." Something closer to:

• "If you have a minute for a Google review, what would help most is what the actual problem was and how it got sorted."
• "Would you mind mentioning what we came out for? It helps other people in the neighborhood find the right service."

You are not telling anyone what to write or how many stars to leave. You are asking a question that naturally produces a narrative instead of an adjective. The difference in output is stark. Adjective prompts return "great service, highly recommend." Narrative prompts return "our AC died the week of the heat wave and they had a new compressor in by Thursday."

For multi-location operators, this is a field training problem, not a marketing problem. The ask has to be built into the job close-out procedure and coached the same way safety steps are, or it decays to nothing within two months.

Use owner replies to add context, and stay on the right side of the line

Your replies are the one part of the review corpus you control completely, and most businesses waste them on "Thanks Karen!"

A reply is a legitimate place to restate what the job actually was and where it happened, in plain language, without asking the customer to change anything:

"Thanks Karen. Glad the sump pump replacement in Elmwood held up through last week's rain. Call us anytime."

That reply adds a service name and a neighborhood to a review that contained neither. Do this consistently across 60 reviews and you have materially changed what your profile says about your service range, using accurate statements about work you performed.

The compliance line is firm and worth stating plainly:

• No gating. You cannot screen customers for satisfaction and route only the happy ones to Google.
• No incentives. No discounts, gift cards, entries, or credits in exchange for reviews.
• No writing reviews for customers. Not drafts, not suggested wording, not "just copy this."
• No bulk requests to people who did not buy anything.

Specificity protects you here as well. Review batches that get filtered or flagged tend to share a profile: many reviews arriving in a short window, similar length, similar generic phrasing, no unique detail. A corpus where each review names a different job, a different street, a different complication looks like what it is, which is a set of real customers describing real work. Detail is both a ranking asset and a defense.

The review coverage checklist

1. Export the last 60 reviews to a spreadsheet with date, rating, and full text.
2. List every service you sell in customer language, one per row.
3. List every objection you answer on the phone, one per row.
4. Count mentions per row. Zero is the number you are hunting for.
5. Count how many reviews name a neighborhood, suburb, or landmark.
6. Count how many reference a price range, quote accuracy, or cost outcome.
7. Count how many describe the problem, not just the outcome.
8. Flag your three highest-margin services with the lowest mention counts.
9. Check that owner replies exist on at least the last 30 reviews.
10. Check that replies name the service performed where you can do so accurately.
11. Confirm no request in your current process gates, incentivizes, or drafts.
12. Record today's counts as a baseline with the date attached.

What to fix first

Work in this order. The sequence matters more than the speed.

First, pick one service with zero mentions and high margin. Not all of them. One. For the next 30 days, every customer who buys that service gets an in-person ask at the moment of proven value, using the open question. Nothing else in your process changes.

Second, reply to your last 30 reviews. Add service and location context where it is factually true. This is a single afternoon of work and it changes the profile immediately.

Third, fix the timing of your existing automated request. Move it from a fixed delay to a trigger tied to job completion, and cut the template down to one open question.

Fourth, audit your ask for compliance. If any part of your process filters unhappy customers or offers anything of value, remove it before you scale volume. A high-risk process running at higher volume is a bigger problem, not a smaller one.

Leave the remaining zero-mention services alone until the first one moves. Sequential focus produces measurable change; simultaneous focus produces a slightly busier team and identical review text.

Measure it like inventory, not like sentiment

Rerun the coverage matrix every quarter using the same 60-review window. You are watching one number per row: mentions moving off zero.

Alongside that, run the same buyer prompts your customers actually use through Google Maps and through an AI assistant, quarterly, and record which businesses get named. Ask for the specific job in the specific area. When your newly covered service starts appearing, the review language is doing its work. When a service is still invisible after two quarters of asking, the ask is not reaching those customers, and that is an operations fix rather than a marketing one. Review coverage sits at the decision stage, where a buyer is choosing between two acceptable options and looking for evidence that you have handled their exact situation. That is the gap SEOGOD is built to find and close across a site and its off-site proof signals, treating discovery as one connected system rather than a set of disconnected channels. You can see where your own conversion-stage proof is thin with a free audit.