Review velocity
Two profiles with 100 reviews are not equal. One earned five a month for two years; the other got 100 in a fortnight three years ago and nothing since. Google can tell, and so can customers reading the dates.
This is why review campaigns to past customers should be paced rather than blasted. Importing 600 old customers and messaging them all on Tuesday produces a spike that looks purchased. The same 600 dripped over eight weeks produces reviews that stick.
Safe pace is relative to your job volume. A shop doing six jobs a week that gains thirty reviews in that week has a plausibility problem regardless of how genuine each review is.
Velocity is the fastest-moving prominence signal you control, and mishandling it is the most common way businesses lose reviews they legitimately earned.
Common questions
How many reviews should I get per week?
As many as your actual job volume supports. Asking every completed customer, every time, produces a natural rate that never looks manufactured.
Do old reviews stop counting?
They still count toward your total and your rating, but recency matters to both Google and the customer reading them. A profile whose newest review is 14 months old reads as stale.
Related terms
Having this problem right now?
Want this handled for you?
RapidLocal runs your Google Business Profile end to end — categories, services, posts, review capture, and map pack tracking on a geo-grid so you can see it move.