Review velocity

Review velocity tracks how many reviews a business collects over a specific time window, usually a rolling 30-day period. Instead of looking at cumulative count — 842 reviews total — velocity asks: how many reviews did this business receive last month, and how does that compare to the month before?

The typical metric is reviews/month, often expressed with a comparison to a historical baseline (usually rolling 12-month average or prior-year same period). A business accumulating 8 reviews/month against a 6 reviews/month baseline is trending up; one dropping from 12/month to 3/month is in trouble.

Total review count is a lagging indicator — it captures what already happened. Velocity is leading — it shows what's happening now and signals where a business is headed.

A business with 800 reviews accumulated over three years, now receiving only 2 reviews/month (down from 10/month two years ago), is in worse shape than a startup with 50 reviews collected in the last six months at 10/month and accelerating. Velocity shows decline long before count becomes obviously problematic. Owners typically notice and react 3 months after velocity starts dropping. Agents running automated velocity checks catch the decline that same week.

Velocity calculation is straightforward: count reviews in a window (typically 30 days) and divide by the number of months in that window. For a rolling 12-month baseline, compute the average monthly count over the past 12 months.

Key methodology notes: Use platform-specific review counts (Google reviews separate from Trustpilot, for example) or aggregate if comparing cross-platform velocity. Month-over-month (MoM) delta shows immediate change; year-over-year (YoY) delta removes seasonal noise. A business with high seasonal variation (e.g., tour operators, ice cream shops) benefits from YoY comparison over MoM.

Declining velocity signals a root cause. Common patterns:

• Owner apathy — new management stopped asking for reviews, or review request emails got paused
• Service quality decline — the business changed, staff turned over, or quality slipped
• Seasonal patterns — expected dips during off-season; use YoY comparison to distinguish from structural decline
• Competitor poaching — nearby competitor opened and is winning new customers
• Review platform changes — Google made changes to how/when reviews surface, affecting the ask rate
• Bad reputation cascade — one viral negative review caused customers to look elsewhere

Diagnosis requires cross-referencing velocity with sentiment trends, reply rate, and competitor velocity. A drop in velocity paired with stable or improving sentiment usually points to fewer interactions, not quality decline.

Reversing a declining velocity trend requires systematic execution across four areas. First, rebuild request cadence — every transaction (appointment, purchase, service completion) gets a follow-up text within 24 hours requesting a review. Second, concentrate effort on one platform first, typically Google, rather than spreading requests across five surfaces. Third, assign owner or staff member to commit to replying to reviews within 24 hours — velocity compounds with owner reply rate. Fourth, batch backlog correction — don't try to fix six months of silence overnight. Organic recovery looks like 2-3 new reviews per week; 20 reviews in a single week signals artificial inflation to consumers and platforms.

Review request tools (Birdeye, Podium, Yelp Pulse, GatherUp) automate the request workflow but don't fix the underlying operational issue. Tools send reminders; staff and process rebuild velocity. The most successful recoveries combine automated requests with human ownership — a staff member checking reply rate daily and adjusting the request send time if needed.

Velocity is a secondary ranking signal compared to rating, review count, and proximity. But within similar businesses — same rating tier, similar review count — the one with growing velocity outranks the one with flat or declining velocity. Industry studies consistently rank "recent reviews" among the top 15 local ranking factors.

A tracked drop in velocity from 8/month to 2/month over 90 days typically correlates with a 1-3 position drop in Local Pack rankings for the affected business. The operational workflow is straightforward: run velocity checks weekly via the Review Velocity API, establish alert thresholds (e.g., MoM decline > 40%), and escalate material drops to the client with diagnosis and recovery plan. Because velocity trends 3-4 weeks ahead of ranking impact, weekly monitoring catches declines before they manifest in pack visibility. This lead time advantage is why velocity monitoring is most valuable during the early stages of decline.

Monitoring velocity at scale used to mean quarterly manual audits. Now, agents run cron-scheduled velocity checks across all client locations. The Review Velocity API returns trend data, delta vs. baseline, and monthly breakdown — structured for agents to reason over.

A typical agent workflow: run velocity for all locations, flag any with MoM deltas below -20%, chain into sentiment analysis to diagnose cause (quality issue vs. volume issue), and surface a prioritized list to the human. Velocity becomes a weekly metric, not a quarterly surprise.