Review Velocity Rules Every Trades Business Needs to Know

Review velocity is the rate at which your Google Business Profile collects new reviews, measured week by week or month by month. Not your total star count. Not your average rating. The rate.

Google's local algorithm treats recent reviews as a real-time signal that your business is active and serving customers right now. Google's own guidance on reviews makes clear that reviews help customers evaluate businesses, and recency is a core part of that evaluation. A profile with 280 reviews, the last one eight months ago, does not look as alive as one with 55 reviews that picked up four more last week.

This is why understanding how review velocity feeds your map pack ranking is the right starting point. Reviews don't live in isolation. They feed a larger set of signals that decides whether you show up in the top three results or get buried on page two.

For trades businesses, velocity beats volume every time. The plumber down the road with 60 reviews and a steady four a month will outrank the firm with 200 reviews that stopped asking two years ago. Total review count is a lagging indicator of past effort. Velocity is a live signal of how the business is doing now.

You are not running a review-count competition. You are trying to look like the busiest, most trusted trades business in your area, this month and every month.

Plenty of tradespeople work out that reviews matter, then do the worst possible thing: batch-text 40 past customers over a weekend and watch 20 new reviews land on their profile in 48 hours.

Google flags that pattern.

Google's review policies explicitly prohibit review manipulation and call out unnatural patterns: sudden spikes in volume, reviews from accounts with no prior review history, reviewer accounts clustered in one location. The algorithm looks for genuine customer behaviour building over real time. Twenty reviews in a weekend from accounts that have never reviewed any other business do not look genuine.

What happens: those reviews get filtered, removed from your visible count, sometimes permanently, with no notification and no appeals process. In repeated cases, Google can take wider action against the profile itself. There is no number to ring and no support ticket that brings those reviews back.

The damage goes beyond the lost count. A profile that trips the spam filter takes months to rebuild trust signals, even if you do everything right afterwards. You cannot undo the pattern once it registers.

What actually works: a steady trickle of two to five genuine reviews a week, from real customers you have just served. That pattern looks exactly like what it is, a busy trades business with a proper process for asking, and it builds over time.

The right number depends on your local market, but finding it takes five minutes.

Open Google now and search '[your trade] near me' from your business address. Look at the top three map pack results. Count how many reviews each profile picked up in the last 60 days by checking the review dates. That rate is your baseline. You need to match or beat the number-three business to compete for that spot.

The figure varies a lot by area. In big, busy cities such as London, Manchester or Birmingham, the top plumbing, heating and electrical profiles tend to move faster. In smaller towns, a couple of new reviews a month may be enough to hold a top-three spot. Your own search tells you which situation you are in.

BrightLocal's consumer research shows that most consumers consider reviews older than three months less relevant to their buying decision, which is exactly the behaviour the local algorithm is modelling.

For a business completing 15 to 25 jobs a week, turning 20 per cent of happy customers into reviews gives you 3 to 5 a week. That is ahead of most local competitors. The businesses hitting that rate have a system. The ones falling behind do not.

The right time to ask for a Google review is the moment the customer shows they are happy, while your engineer is still on the doorstep.

Job done. Customer says 'that looks great, thanks.' That is your 30-second window. Satisfaction is at its peak, the experience is fresh, and you have a natural moment to ask. Do it in the next sentence: 'Glad you're happy with it. It would mean a lot if you left us a quick Google review. I can text you the link now, it takes about a minute.'

That on-site ask, followed straight away by a text, beats any delayed follow-up. Wait three days to send an email and you are competing with everything else going on in that customer's life: the invoice, problems at work, the kid who got ill. Your boiler repair is now just a transaction they want to move on from.

Ask on the day and text on the day. That is the combination to aim for.

The wrong times to ask: after a complaint, after a dispute over the price, before the job is confirmed finished, or after you have already chased two unpaid invoices. Those situations produce reviews you do not want. Read the room.

The simple rule: if you would confidently say 'that customer is happy right now', ask. If there is any doubt, sort out the problem first, then ask.

Scripts matter. Most tradespeople ask in a way that gives the customer an easy way out or makes the moment awkward. Here are word-for-word versions that work.

On-site ask, from the engineer at the end of the job: 'Thanks for having us. We're a small local business and Google reviews make a real difference to us. I'll send you a text with a direct link now, it takes about a minute on your phone. Is that OK?'

Send the text before you walk back to the van. Do not rely on them looking you up from memory later.

Text, sent within 15 minutes of leaving the job: 'Hi [First Name], it's [Engineer Name] from [Business Name]. Thanks for having us round today. If you have a minute, a Google review really helps us. Here's the direct link: [link]. No pressure, and thanks again.'

Keep it short. The link does the work. A paragraph-long request reads like a form letter and gets deleted.

What you cannot do: Google's review policies prohibit offering anything in exchange for a review: no discounts, no vouchers, no 'leave a review and get 10 per cent off your next call-out.' Beyond the policy risk, it trains customers to expect something in return before they engage, which causes a different problem down the line.

Ask with confidence. You did good work, the customer is happy, and a review is a completely reasonable request.

Responding to reviews is not just good manners. It is a GBP engagement signal. Google tracks whether the owner responds, how quickly and how consistently. A profile with 80 reviews and no responses looks abandoned. Respond to every review within 24 hours.

5-star response, short and specific: 'Thanks, [Name], really appreciate you taking the time. Glad we could get the [job type] sorted quickly. Give us a ring any time.'

One or two sentences. Mention the specific job if they did. Do not write three paragraphs thanking them for their custom.

4-star response, acknowledge without overdoing it: 'Thanks [Name], your feedback means a lot. If there's anything we could have done better, get in touch directly. We want to earn that fifth star next time.'

1-star response, where tradespeople lose their cool and cost themselves more work: Stay factual. Do not argue. Everyone who reads your reply to a 1-star review is judging how you handle conflict, and that audience is far bigger than one unhappy customer.

Framework: 'Hi [Name], I'm sorry the experience didn't meet the standard we aim for. Please call us on [number] and I'll personally make sure we deal with it. We stand behind our work.'

Take the conversation offline. Stay professional. That is it.

Combine a consistent habit of responding with weekly GBP posts that reinforce your review signals and you are running a full GBP engagement routine: reviews and posts together, every week.

The businesses that consistently outrank everyone on reviews are not spending hours on it. They have a three-step process that runs after every completed job, about 30 seconds per job.

Once you are doing more than 15 jobs a week, the manual process starts to break. The engineer forgets. The text does not go out. Responses pile up for a fortnight and get a batch reply that reads like it was typed at midnight. That is when automation takes the load: a system that sends the review request automatically when the job is marked complete, drafts responses for one-tap approval, and tracks which customers left a review and which did not.

If the manual process is slipping, that is your signal to automate it. How to ask is already solved. What remains is doing it consistently at scale, and that needs a system, not willpower.

Start the three steps this week. Run them for 30 days. If it holds, you have your routine. If it slips, you know exactly where it is breaking.