Your Restaurant Rating Dropped, But Revenue Went Up — Is Your Score Lying to You?

Your rating dropped from 4.5 to 4.2 and you panicked. But what you didn't see: the neighborhood average is 3.9. Your score is falling, but your relative position is rising. An absolute score without a benchmark is as dangerous as having no number at all.

Your Restaurant Rating Dropped, But Revenue Went Up — Is Your Score Lying to You?

From 4.5 to 4.2

A restaurant owner looks at his dashboard. Google rating dropped from 4.5 to 4.2.

He immediately calls a meeting. The servers get chewed out. The kitchen is told to speed up. Marketing is asked to push a “review campaign.”

Three months later, the rating crawls back to 4.3. He breathes a sigh of relief.

But the financials show: during those three months when the rating was “declining,” monthly revenue actually grew by 22%.

He’s confused. Rating goes down, business gets better — how is that possible?

What Are You Comparing Your Score Against?

The problem isn’t the score. The problem is what you’re comparing it to.

If the neighborhood average rating is 3.9, your 4.2 isn’t a decline — you’re number one in the area. The reason your score dropped could be that two new competitors opened and pulled down the overall neighborhood average, or that increased foot traffic brought a larger sample size (more guests = more extreme ratings = average gets pulled down).

But if you only look at your own absolute score, you’ll make completely wrong decisions: pressuring staff, pushing review campaigns, cutting prices to compensate — all attacking a problem that doesn’t exist.

What’s Hidden in the 22% Revenue Growth

Let’s go back to that 22% revenue growth. It didn’t appear out of thin air.

What happened at this restaurant during those three months? The lunch service started handling a surge of takeout orders from a nearby tech park. These new customers were first-timers with low expectations (it’s takeout, after all), and what they got was consistent quality and fast service. Their satisfaction was actually decent — but “decent” maps to three or four stars, not five. And this group’s review volume surged, diluting the high-score base that had been built primarily from dinner guests.

So hidden in your 4.5 → 4.2 are a piece of good news and a piece of bad news. Good news: your customer base is expanding, revenue is growing, and a new revenue stream is being established. Bad news: your overall rating has been pulled down, and you looked at that number and made decisions that pressured your staff.

What’s more ironic is that the “review campaign” you pushed — requiring servers to remind guests to leave five stars at checkout — only accelerates the dilution. Because new guests naturally leave three or four stars. When you push them to leave five stars, what they leave are reluctant positive reviews bearing the traces of being “asked to.” Once potential customers read these, the effect backfires.

Review Velocity: A Signal That Turns Before the Score Does

Beyond the score itself, there’s another metric fewer people pay attention to: review accumulation velocity.

Say your restaurant gets 15 new reviews per month over six months. Suddenly, last month brought 45 new reviews. The rating barely changed — but review volume tripled.

Most operators don’t even look, because “the score didn’t change.” But a surge in review volume is a signal in itself. It could mean a significant increase in foot traffic (a good thing, but it brings a dilution effect). It could also mean a specific event triggered a large-scale emotional response — possibly positive (a dish went viral) or possibly negative (a service failure generated widespread complaints, but most guests chose to leave three stars instead of one — the score didn’t collapse, but you’re already walking a tightrope).

Review velocity is a “leading indicator” of the score. When you see velocity change but the score hasn’t moved yet — that’s your intervention window. Once the score moves, the trend has already formed.

One-Minute Lesson

Simpson’s Paradox

In 1973, UC Berkeley was accused of gender discrimination. The data looked like an ironclad case: overall admission rate — men 44%, women 35%.

But when statistician Peter Bickel broke it down by department, he found that in 85 departments, most departments actually favored admitting women. Where did the gap come from? Women tended to apply to departments with lower admission rates (humanities, social sciences), while men tended to apply to departments with higher admission rates (engineering, physics).

The aggregate numbers showed men had an advantage. The grouped numbers showed no discrimination. The two conclusions were completely opposite.

This is Simpson’s Paradox: aggregate data shows one trend, but when broken into groups, each group shows the opposite trend.

This paradox isn’t an academic curiosity. It happens every day in the real data of the restaurant and hospitality industries. And every time you make decisions based on the “overall rating,” you might be falling into the same trap.

Your 4.5 → 4.2 is the same. The overall score is declining. But if you separate lunch and dinner service, dinner ratings are actually rising — climbing from 4.5 to 4.7, because you brought in a new head chef last month and dinner quality noticeably improved. It’s the influx of new lunch customers dragging down the overall average — and the increase in lunch traffic is exactly why your revenue grew 22%.

The aggregate numbers tell you “decline.” The grouped numbers tell you “growth.” You’ve been looking at the wrong one.

This isn’t your fault. The human brain naturally gravitates toward looking at aggregate numbers — it’s more efficient from an evolutionary standpoint. But the value of data analysis lies precisely in overcoming intuition and asking a counterintuitive question: “If I break this apart, is the story still the same?”

Why You Don’t Have a Benchmark

Most operators looking at their own score are like a person looking at their hand in a dark room — you know where your hand is, but you don’t know how big the room is or where others are standing.

The reason you don’t have a benchmark is simple: the cost of obtaining one is too high.

To know your neighborhood average, you’d have to manually open Google Maps, check each competitor’s rating, review count, and response rate one by one, then calculate the weighted average yourself. A restaurant might have 30 competitors nearby. Three minutes per check. An hour and a half later, you get a number — but it’s outdated next month.

So you don’t do it. So you don’t have a benchmark. So you make wrong decisions based on absolute scores.

It’s not that you’re lazy. It’s that the tools are wrong.

Three Traps of Absolute Scores

First, sample size changes. A 4.5 with 100 reviews isn’t the same thing as a 4.2 with 1,000 reviews. As review count increases, the influence of extreme values increases, and the average naturally gets pulled down. This doesn’t mean quality is declining — it just means more people came.

Second, temporal structure. Weekend guests are pickier than weekday guests (more crowds, longer waits, higher expectations). If your weekend traffic proportion increases, the overall rating naturally drops. This isn’t decline — it’s a peak-season effect.

Third, competitor dynamics. A beautifully renovated restaurant opens next door and temporarily pulls away some of your high-satisfaction guests (they went to try something new). Those who remain are mostly regulars — and regulars hold higher standards. Your score drops, but your customer mix is shifting.

The common thread across all three traps: without industry benchmarks and segmented data, absolute scores will lead you to completely wrong conclusions.

What You Need Is a Map

You need to know where you stand.

Not “my score is 4.2” — but “my score is 4.2, the neighborhood average is 3.9, and I’m in the top 15%.”

Not “my rating is dropping” — but “my rating is dropping, but the neighborhood overall is dropping even more, so my relative position is rising.”

This is the value of industry benchmarks. It transforms your absolute score into a relative position. Relative position is what should drive decisions.

And relative position delivers more than just “where I rank” — it tells you “where I should go.” If you’re in the top 15% of your neighborhood, your focus shouldn’t be “improving the score” but “maintaining quality while expanding the customer base.” If you’re in the middle, your focus is “finding out what the restaurants ranked above you are doing that you aren’t.” If you’re at the bottom, that’s when you should seriously ask “what’s wrong with the quality?”

The same 4.2 score, three relative positions, three completely different action plans. Without a benchmark, you don’t even know what battle you’re fighting.


Download the Industry Rating Benchmark Report

Where does your score rank in the market? Leave your email to get our industry rating benchmark — including industry-wide averages across five dimensions, your relative position reference, and response rate benchmarks.

When you receive it, you might think: “If I have to manually update these numbers every month, who has the time?”

That thought is the starting point of the problem.


Further Reading

← Your reports are beautifully formatted and logically coherent, but they don’t tell you why guests stopped coming

Three revenue analysis methods (financial statements, order data, market research) — why can’t any of them see the real reason customers are leaving?

Read

Was this article helpful?

Discussion

Loading…

Related Articles