Review Velocity

What is Review Velocity?

Review velocity is the pace at which new reviews arrive for your business. It is usually expressed as reviews per week or per month, for each location and each platform, such as "10 new Google reviews per location per month."

Where your total review count shows what you have built up over the years, review velocity shows what is happening now. It tells you whether guests are still writing about you, whether your review requests are reaching them, and whether one location has quietly stopped collecting feedback.

For a multi-location restaurant brand, review velocity is one of the most practical online reputation management metrics. It moves quickly when you change how you ask for reviews, it keeps your star rating current, and it feeds directly into how fresh your reviews look to the next guest.

Review velocity is closely related to review recency, which measures how old your newest reviews are. The two are explained side by side later on this page.

How to calculate review velocity

Review velocity is a simple rate. To compare periods and locations fairly, it helps to convert every figure to the same length of time and to one location:

Review velocity per location per month = new reviews ÷ number of locations ÷ days in the period × 30

Using 30 days as a standard month keeps the arithmetic easy to check. For a weekly figure, you multiply by 7 instead of 30.

Worked review velocity example

Suppose your fast casual brand has 12 locations and gained 360 new Google reviews in the last 90 days.

• Brand-wide velocity: 360 ÷ 90 × 30 = 120 reviews per month.
• Per location: 360 ÷ 12 ÷ 90 × 30 = 10 reviews per location per month, or about 2.3 per week.

The average hides a lot. Splitting the same 90 days by location usually shows a much wider spread:

A location gaining three reviews a month will see its rating and its newest reviews change very slowly, so it usually deserves attention first.

Review velocity per 1,000 orders

Busy locations naturally gain more reviews, so a second view divides reviews by guest traffic. If a location gains 10 reviews in a month in which it served 5,000 orders, its velocity is 2 reviews per 1,000 orders.

This normalized figure shows how well each location turns visits into reviews, which makes a small store comparable with your flagship.

What review velocity implies for review requests

If you know your review rate, the share of invited guests who go on to leave a review, you can work backwards from a target. Your own rate depends on the channel, timing and platform, so the 2% used here is only an example.

At a 2% review rate, 10 reviews a month means about 500 invitations (10 ÷ 0.02). Reaching 15 reviews a month means about 750 invitations, which for a location serving 5,000 orders a month means inviting 15% of its guests.

Review velocity calculator

Enter your own numbers. The review rate is an example input, and dividing reviews by the requests you sent in the same period gives you your real rate.

Types of review velocity

Review velocity by platform

Google, delivery apps, booking platforms and review sites each gather reviews at their own pace. Tracking them separately shows where guests talk about you, and a fall on one platform while the others hold steady usually points to something specific, such as a broken review link.

Review velocity by location

Location-level velocity is the most actionable view for a multi-location brand. Ranking every location by reviews per month, ideally in a weekly operator report, shows which managers need help with review requests.

Review velocity by rating

Splitting new reviews by star rating shows whether growth is coming from happy or unhappy guests. Rising velocity driven by one- and two-star reviews is an early warning, and sentiment analysis can show which topics those reviews share.

Rolling and period review velocity

A period figure counts reviews in a fixed window, such as last month. A rolling figure counts the last 30 or 90 days on any given date, which smooths out noise and suits small locations, where three or four reviews a month can swing widely by chance.

Review velocity vs. review recency vs. volume

These metrics are often mentioned together, and each answers a different question about your reviews.

Review velocity measures a rate over a period, while review recency measures the age of your newest reviews on a given day. They usually move together, and they can still diverge.

A location that gained 30 reviews in one week of a campaign three months ago and none since can show a respectable 90-day velocity, while its latest review is almost three months old. Recency reveals that gap immediately.

The reverse also happens: one review yesterday gives you excellent recency for a day, even if it is the only review in two months. Tracking both gives you the full picture.

Why review velocity matters for restaurants

Review velocity and guest decisions

Guests look at how many reviews you have and how recent they are. In BrightLocal's Local Consumer Review Survey 2026, 47% of US consumers said they wouldn't use a business with fewer than 20 reviews, and 74% looked for reviews written in the last three months.

A steady review velocity keeps both numbers in your favor at every location, including new openings that start with no reviews.

Review velocity and local search

Google says local results are based mainly on relevance, distance and prominence, and that review count and review score factor into local search ranking. Healthy velocity grows your count, and fresh reviews give your rating the chance to rise.

Many local search practitioners believe the pace and freshness of reviews matter in their own right. Google hasn't confirmed this, so it is best treated as industry belief.

Review velocity and your star rating

An established average moves slowly, and only new reviews can move it. With low velocity, improvements in food or service take months to show in your rating, while a steady flow lets it catch up with the experience you deliver today. The online reputation management calculator shows how many reviews a rating change takes.

Review velocity as an operational signal

Because reviews follow visits, a sudden drop in velocity at one location can reflect lower traffic, a broken review link or a receipt template that lost its QR code. Watching it weekly turns velocity into an early warning, and operational insights help you trace the cause.

What is a good review velocity?

No independent study publishes a review velocity benchmark for restaurants, and any single number would ignore large differences in traffic, format and market. A drive-thru serving thousands of orders a week and a fine dining room with a few hundred covers should expect very different counts.

Three comparisons give you a useful target instead:

1. Your own locations. Comparing reviews per 1,000 orders across locations shows what your best teams achieve with the same guests and brand.
2. Your recent trend. Velocity that holds steady or rises over several months shows that your review requests are working.
3. Nearby competitors. Sorting nearby restaurants' Google reviews by newest and counting last month's shows the pace guests in that market see.

A practical floor is enough reviews to keep your newest reviews from going stale. If you want guests to see a review from the past week at every location, each location needs at least one new review every week, which is about four or five a month.

How to measure review velocity

1. Choosing the platforms. Most brands start with Google and add the delivery and booking platforms that carry a meaningful share of their reviews.
2. Fixing the window. A rolling 30-day or 90-day count, recalculated each week, balances responsiveness with stability.
3. Normalizing. Dividing by locations, days and, where you have the data, orders makes every figure comparable.
4. Splitting by rating. Recording how many new reviews have one to five stars shows the mix behind the pace.
5. Recording review requests. Logging how many invitations each location sends lets you calculate your review rate and separate a request problem from an experience problem.
6. Counting new reviews directly. Platforms remove reviews that break their policies, so the difference between two totals can understate the reviews you actually gained.

Bringing every platform into a unified inbox, a step known as review aggregation, makes these counts automatic. A weekly operator report for each location then puts the figure in front of the managers who can change it.

How to improve review velocity

Raising velocity comes down to asking more guests, at a better moment, with less effort on their part, while delivering an experience they want to write about. The practice of asking is covered in more depth under review solicitation.

• Inviting every guest in the same way. A consistent invitation through receipts, post-order messages and table QR codes reaches far more guests than occasional verbal requests, and it keeps you within platform rules on review gating.
• Asking soon after the visit. Messages sent within hours of a meal or delivery, as in a post-order survey workflow, reach guests while the details are still fresh.
• Removing friction. Google lets you create a review link or QR code that opens the review form directly, which saves guests from searching for your profile.
• Making it part of each shift. Mentioning reviews in pre-shift briefings and sharing each location's weekly count helps teams keep the habit going.
• Replying to the reviews you receive. A visible owner reply shows guests that reviews are read, and keeping your review response rate high is good practice in its own right.
• Fixing the reasons guests stay silent or complain. Velocity built on a good experience brings a better rating along with it, while recurring problems attract more negative reviews.

For an example at scale, Caribou Coffee achieved 61% more reviews across 57 locations in the GCC.

Review velocity rules and limits

Some ways of raising review velocity break platform policies and consumer protection law. Google's prohibited and restricted content policy bars paid reviews, incentives such as discounts or free items in exchange for reviews, and content that doesn't reflect a genuine experience.

When Google finds fake engagement on a profile, its help page on Business Profile restrictions says it may block new reviews for a period, unpublish existing ones or show guests a warning. Any of these would stop your velocity entirely.

In the US, the FTC's rule on consumer reviews and testimonials, announced in August 2024, bans fake reviews, buying reviews, and incentives conditioned on a particular sentiment. Yelp goes further and asks businesses to refrain from requesting reviews at all.

Policies change, so checking the current version for each platform and market is a sensible habit.

Limitations of review velocity

• Pace says nothing about quality. A high velocity of negative reviews is a problem, so velocity belongs next to your rating and the review text.
• Traffic drives the count. Busy locations gain more reviews without doing anything differently, which is why reviews per 1,000 orders is a fairer comparison.
• Seasonality. Holidays, tourist seasons and local events change traffic, so year-on-year comparisons are often more meaningful than month-on-month ones.

Best review velocity tools for restaurants

A tool for review velocity needs to do two jobs: invite guests to review across your channels, and report new reviews by location, platform and rating so you can see the pace. For a restaurant brand, coverage of Google and delivery platforms and a clear location-level view matter most.

Each of these tools approaches review requests and reporting differently, so comparing them against your own platforms, ordering channels and number of locations is the most reliable way to choose.

Common review velocity mistakes

• Running review drives in bursts. A one-off push produces a spike and then silence, which leaves your newest reviews aging again within weeks. A steady, always-on invitation keeps both velocity and review recency healthy.
• Looking only at the brand total. A strong brand-wide figure can hide locations that gain almost no reviews, a common gap in franchise reputation management.
• Inviting only happy guests. Selective requests break Google's policies and inflate your rating in a way guests eventually notice.
• Offering rewards for reviews. Discounts or free items in exchange for reviews break Google's rules and can bring profile restrictions.
• Chasing the number alone. Velocity built on a poor experience brings more negative reviews, and recovering unhappy guests before they post is part of a healthy review program.

History of review velocity

Once guests began choosing restaurants on review sites such as TripAdvisor (founded 2000) and Yelp (founded 2004), and later on Google's local listings, the number of reviews became a visible signal of popularity.

The total alone could mislead, though. A restaurant with hundreds of reviews collected years ago looked established even if hardly anyone had written about it recently, so practitioners began measuring the rate of new reviews to see current momentum.

The phrase "review velocity" spread through local search practice and review management software, where it describes the pace of new reviews alongside count and rating. Google's own ranking guidance talks about review count and review score and doesn't use the term.