GoodMarksWhy total count is the wrong metric to optimize
When a service business asks "how do we get more reviews?", the implicit goal is usually the total number displayed on their Google Business Profile. Get to 50, then 100, then 200. The number gives the appearance of accumulated trust.
The problem is that Google's local algorithm does not treat a 200-review profile from 2020 the same as a 200-review profile updated through this month. Recency is a distinct signal — one that tracks whether a business is actively serving customers right now, not whether it was popular several years ago.
This is the velocity signal. Not how many reviews you have, but how quickly new ones are arriving.
How Google uses freshness in local rankings
Google's ranking documentation for local results describes "prominence" as a factor — the general measure of how well-known and active a business is. Within prominence, review activity is one of the strongest signals Google has that a local business is operational, regularly serving customers, and generating enough transactions to produce authentic feedback.
A steady stream of reviews tells Google: this business is open, active, and customers are leaving it regularly. A profile that last received a review eight months ago signals ambiguity. The business might still be operating normally, but from Google's perspective, absence of activity looks like reduced relevance.
This creates a dynamic that counter-intuitively hurts established businesses more than new ones. A business with 300 reviews but no new activity in four months may lose local pack positions to a competitor with 60 reviews but consistent weekly inflow, because the velocity signal favors the active business.
The compounding effect of velocity maintenance
The businesses that hold strong local pack positions over multi-year periods tend to share one operational pattern: they never stop asking. Review collection is not a campaign they run when rankings drop — it is a system embedded in their service delivery workflow.
The compounding effect is significant. A business receiving two to four Google reviews per week accumulates 100 to 200 reviews annually. At that pace, the profile looks perpetually fresh to Google's recency systems. The review dates visible to consumers show recent activity. Both the algorithmic signal and the consumer trust signal are maintained simultaneously.
Contrast this with a business that ran a review collection push once, reached 150 reviews, then stopped asking. Two years later, the profile shows a last review from 18 months ago. The total count looks credible, but to an informed consumer — and to Google — the absence of recent activity is itself a data point.
Velocity benchmarks by trade category
Velocity requirements are not uniform across service trades. They track two variables: market competition density and service transaction frequency.
High-frequency, competitive trades (HVAC, plumbing, electrical in suburban and urban markets): Local pack leaders typically sustain two to five new reviews per week. These trades have high transaction volume and tight local competition, which means velocity requirements are correspondingly high.
Lower-frequency, higher-ticket trades (roofing, remodeling, custom work): Transaction frequency is lower, which means velocity expectations are scaled down. Local pack leaders in these categories often sustain one to three reviews per month. The consumer also expects fewer reviews because they understand that full roofing jobs are not daily occurrences.
Professional services adjacent to trade work (landscape design, pool installation, home automation): These fall between the categories above. The key variable is how many jobs the business completes in a month, not an industry average.
The practical benchmark question for any service business is: among the businesses currently occupying the local pack for my primary keyword, how many reviews did they receive in the last 90 days? That number — not their total count — is the velocity baseline you are competing against.
What kills review velocity
The most common cause of velocity decline is not customer dissatisfaction. It is operational friction in the request process.
When review collection depends on individual staff remembering to ask at the end of a job, velocity becomes inconsistent. Some technicians ask every time. Others never do. The result is a business that gets a review burst when morale is high and collects almost nothing when the team is busy or tired.
A second common cause is channel mismatch. Businesses that request reviews through methods customers rarely check — a link buried in an email footer, a note on a paper invoice — see low conversion rates not because customers are unwilling but because the request never reached the moment of willingness.
The moments of willingness are brief. Research on customer satisfaction consistently shows that positive emotional response to a service experience peaks shortly after completion and decays over time. A request delivered within minutes of job completion captures that peak. A request delivered three days later, through an email that arrives on a busy Tuesday, competes with the full noise floor of daily life.
Building sustainable velocity
Sustainable velocity requires that review requests happen automatically, immediately after service completion, through the channel most likely to reach the customer at their peak satisfaction moment.
For most service trades, that channel is SMS. Open rates for text messages are dramatically higher than email, and the review completion path — tap the link, tap the stars, submit — takes under 90 seconds on mobile. The friction reduction is not incremental; it is structural.
The businesses that maintain the strongest velocity over time are not the ones with the best review scripts. They are the ones with systems that make asking so automatic that it happens whether or not any individual employee remembers.
The velocity floor: what signals decline
If velocity drops below roughly one new review per 30 days for a business in a competitive market, the freshness signal starts to work against it. The longer the gap extends, the larger the deficit becomes relative to competitors who continued collecting.
Recovery is possible, but it requires accepting that the first several weeks of renewed collection are largely catching up to where the profile should have been, not yet gaining ground on competitors. This is why the operational calculus strongly favors consistency over campaigns: the cost of maintenance is far lower than the cost of recovery.
The most important strategic implication of the velocity signal is this: a business's review strategy is never finished. It is, instead, a process permanently embedded in how jobs close.