| Dimension | Review velocity | Total count |
|---|---|---|
| Google ranking weight | High – recency-weighted | Moderate – diminishing returns past 100 |
| Consumer trust signal | "Active and current" | "Established but possibly outdated" |
| Decay over time | Resets monthly – must be maintained | Permanent but loses ranking power |
| Competitive advantage | Hard to fake at scale | Easy to accumulate with one-time campaigns |
| AI platform visibility | Critical – stale listings get dropped | Not a factor in AI answer selection |
A 4.8-star restaurant with 2,000 reviews lost its Local 3-Pack position after three months without a single new review. A 4.3-star competitor with 140 reviews took its spot – because that competitor was collecting 15 new reviews per month. Total count did not save the higher-rated restaurant. Review velocity did.
What is review velocity?
Review velocity is the rate at which new reviews arrive over a given period. It is measured as reviews per week or reviews per month – not as a lifetime total. The formula is simple: take the number of reviews received in the last 30 days and divide by 4. That gives you a weekly velocity. A restaurant that received 24 reviews last month has a velocity of 6 per week. One that received 4 has a velocity of 1. Both might have 500 total reviews. But Google treats them very differently. Velocity is a flow rate, not a stockpile. A restaurant that stopped receiving reviews six months ago is treated like a restaurant that stopped operating – regardless of how many reviews it accumulated before going quiet. Google's local ranking algorithm rewards active businesses, and review activity is one of the clearest signals of an active business.
Why velocity outranks total count
Google weights recent reviews more heavily
Google's local ranking algorithm applies a recency multiplier to reviews from the last 30 days. Research from Whitespark and Moz local ranking factor studies consistently shows that recent review activity carries approximately 20% more weight than older reviews in determining local pack placement. A business with 10 reviews this month ranks better than one with 100 reviews from last year, all else equal.
The 90-day decay curve
Reviews older than 90 days begin losing ranking weight. This is not a cliff – it is a gradual decay. A review from 60 days ago carries less weight than one from last week, and a review from 6 months ago carries significantly less. This decay exists because Google optimizes for consumer relevance: a review describing a restaurant's service 8 months ago is less useful than one from last Tuesday.
Response rate amplifies velocity
Businesses that respond to every review receive 12% more new reviews than those that respond sporadically. When potential reviewers see that the owner replies to feedback, they are more likely to leave their own review. This creates a compounding effect: higher response rate leads to higher velocity, which leads to better ranking, which leads to more visibility and more reviews.
Monthly review benchmarks by tier
Google sees your listing as inactive. You are losing ranking weight every week. Competitors with steady velocity will push you out of the Local 3-Pack within 60 days. Common in restaurants that collected reviews once (grand opening push) and then stopped asking.
Enough to avoid the decay penalty but not enough to climb rankings. This is the floor for restaurants in low-competition suburbs. In competitive urban markets, 5 – 10 per month means you are treading water while competitors pull ahead.
The target for most independent restaurants. At this velocity, you maintain Local 3-Pack eligibility in mid-competition markets. Fine-dining restaurants with lower foot traffic can aim for the lower end. Quick-service restaurants with high volume should aim for 20+.
You are outpacing 90% of restaurants in most local markets. At this velocity, Google's recency weighting works heavily in your favor. Achievable for high-traffic restaurants that systematically ask every guest. Multi-location groups should target this per location.
The velocity decay timeline
When review flow stops, ranking damage follows a predictable pattern:
Existing velocity carries you. Google still sees recent activity. No visible ranking change yet.
Your most recent reviews are now aging out of the high-weight window. Competitors with active velocity begin overtaking you in local results. Profile views start dropping.
AI-powered search tools (Google AI Overviews, ChatGPT, Perplexity) rely on review freshness to determine which businesses to recommend. A listing with no reviews in 60+ days stops appearing in AI-generated answers.
Google treats your listing as potentially inactive. You lose Local 3-Pack eligibility in competitive markets. Consumers see your last review was months ago and question whether you are still open. Recovery from this state takes 4 – 8 weeks of consistent new reviews.
How to measure your review velocity
Open your Google Business Profile dashboard and go to the Reviews section. Count the reviews received in the last 30 days. Divide by 4 to get your weekly velocity. Compare against the benchmarks above. If you manage multiple locations, measure each one separately – a strong flagship velocity does not compensate for a stagnant second location. Track velocity monthly in a spreadsheet. The trend matters more than any single month: a business going from 8 to 12 to 15 reviews per month is in a stronger position than one fluctuating between 5 and 20.
velocity = reviews_last_30_days / 4
When total count still matters
Velocity is not everything. Below 50 total reviews, volume is the priority. Consumers use total review count as a credibility threshold: a 4.8-star restaurant with 9 reviews triggers skepticism ("Is this real?"), while the same rating with 80 reviews feels trustworthy. The Spiegel Research Center found that purchase likelihood plateaus around 50 – 100 reviews for local businesses. Below that threshold, every new review adds both velocity and volume – a double benefit. Once you cross 100 total reviews, velocity becomes the dominant factor. At 200+, total count is essentially irrelevant to ranking – what matters is how many arrived in the last 30 days. The practical takeaway: new restaurants should focus on accumulating volume first. Established restaurants with 100+ reviews should focus exclusively on maintaining velocity.
How to maintain review velocity
100% response rate with AI
Responding to every review signals active management to Google and encourages future reviewers. Businesses that reply to all reviews receive 12% more new reviews. ReviewTactic generates personalized replies within minutes of each review arriving, keeping your response rate at 100% without daily manual effort.
Sub-24-hour response time
Speed matters for both ranking and perception. A reply posted within hours tells Google your listing is actively managed. It tells the reviewer their feedback was heard. And it tells future guests that this business pays attention. ReviewTactic's AI drafts go live in minutes, keeping your average response time under an hour.
Ask every guest, not just happy ones
Most restaurants only ask guests who seem satisfied. This creates a sporadic review flow and introduces review gating risk (which violates Google policy). Ask every guest the same way, at the same point in the experience. The satisfied ones will leave positive reviews. The unsatisfied ones give you a chance to recover the relationship before they post publicly.
Key takeaways
Review velocity – reviews per week – outweighs total review count in Google's local ranking algorithm once you pass 50 – 100 total reviews.
Google applies a recency multiplier: reviews from the last 30 days carry approximately 20% more ranking weight than older reviews.
After 90 days without new reviews, your listing begins losing Local 3-Pack eligibility and AI platform visibility.
Target 10 – 20 reviews per month for independent restaurants. Under 5 per month puts you in the decay zone.
Responding to 100% of reviews creates a compounding effect: higher response rate drives 12% more new reviews, which increases velocity.