Skip to main content

REVIEWS & REPUTATION · September 2026 · ~9 min read

Two reviews a month is the real constraint in an auto repair shop

A shop can fix its profile in an afternoon and its website in a week. What it cannot fix quickly is a review profile that grows slowly and gets no replies, and that is the thing deciding which three shops appear when somebody searches with a warning light on the dash.

01

Why is this the constraint rather than the website?

Because it is the only input that takes time and cannot be bought.

Categories, hours, services and photographs are all one-afternoon jobs. A symptom page is an hour of writing. Every one of those can be fixed this week by anyone who decides to.

Reviews cannot. They arrive at the rate customers leave them, they cannot be accelerated with money without breaking the rules, and a shop starting from eleven of them is starting from behind against a competitor with two hundred, no matter how good the rest of the work is.

That makes the review process the only part of local marketing where starting today genuinely matters more than doing it well. A mediocre process running for a year beats a perfect one starting next quarter, and the gap between them compounds rather than closing. Shops routinely spend the first three months choosing a tool and the next three deciding on wording, and arrive in month seven with the same eleven reviews they started with.

02

What does the policy actually allow?

Asking, including asking everybody. Three things are out.

Google's policy expressly permits merchants to "Solicit or encourage the posting of content that does represent a genuine experience, without offering incentives to do so or attempting to influence the rating or the contents of the review."

Incentives are out, named directly: "Offer incentives - such as payment, discounts, free goods and/or services - in exchange for posting any review or revision or removal of a negative review." A free oil change for a review is the textbook case and it is common in this trade.

Selection is out. "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers." That catches the survey that routes happy customers to Google and unhappy ones to a private form, which is sold to shops as reputation management and is prohibited conduct described exactly.

Pressure and content direction are out. "When soliciting reviews, merchants should not require or pressure users to leave ratings or write reviews while on the premises, nor should they request that specific content be included."

That last clause has a specific consequence here. Asking a customer to mention the technician by name is a common practice in shops, done kindly, and Google names it as an example: "Merchants requesting that staff solicit reviews that include specific content, including content that identifies a staff member." Review targets for the front counter are named too.

03

Where does federal law sit on top of that?

Alongside it, and the useful clause is the one that protects you.

The FTC's rule on consumer reviews and testimonials, 16 CFR Part 465, has been in force since October 2024. Section 465.4 prohibits incentives "in exchange for, or conditioned expressly or by implication on, the writing or creation of consumer reviews expressing a particular sentiment." The phrase or by implication is doing the work, because nobody says it out loud.

Section 465.2(d) is the safe harbor: the prohibitions do not apply to reviews that "resulted from a business making generalized solicitations to purchasers to post reviews or testimonials about their experiences." Ask every completed job, do not condition on sentiment, do not script the content, and you are inside it by construction.

Two more. Section 465.5 makes an owner liable where an insider review carries no disclosure and the owner "did not instruct that prospective reviewers disclose clearly and conspicuously their relationship to the business," so technicians should not be reviewing the shop. And section 465.7(a) prohibits using "an unfounded or groundless legal threat, a physical threat, intimidation, or a public false accusation" to prevent or remove a review, which retires the lawyer's letter to a one-star customer.

This is information, not legal advice.

04

When should the request go out?

The same day, a few hours after collection, and the reason is specific to this trade.

The car is running better right now. By next week it is just a car again and the improvement has become the baseline. That window is narrower in auto repair than in almost any other trade, which is why the cadence differs from the general recommendation.

This is our operating judgment rather than a finding from a study, and we have not read a source that establishes an optimal send time. Anyone quoting one to a decimal place is selling something. The reasoning by trade, including the vet and CPA cases where the timing runs the other way, is in the review request after the ticket closes.

Send once, then once more three or four days later if there is no review, then stop.

05

What should the message say?

The car, the link, and nothing else.

"Thanks for bringing the Civic in on Tuesday. If you have a minute, a Google review helps other drivers find us: [link]" is the whole message. Naming the vehicle helps the customer remember what they are writing about.

Do not ask for five stars, do not suggest what to mention, and do not name the technician. Send it the way the customer already talks to you, which in this trade is almost always a text.

One practical note: the customer has to be signed into a Google account to leave a review at all, which quietly explains a share of the non-responses that shops usually attribute to indifference. It is not a reason to skip anyone, and it is a reason the link matters more than the wording does.

06

Why do the replies matter more than people think?

Because the prospective customer is reading them for evidence about how you behave when something goes wrong.

Nobody believes a shop never has a bad job. What they want to know is what happened next, and the reply is the only place they can see it. A profile with three bad reviews and three calm, specific, non-defensive replies reads better than a profile with none of either.

Two rules. Do not argue the facts in public, because you lose in front of an audience even when you are right. And do not offer money in the reply, because it reads as buying the review down and sits too close to the incentive rules. What to write instead, and the template that makes it worse, is in responding to a bad review.

Reply to the good ones too, briefly and without a template. Four different reviews answered with the same sentence reads worse than no reply at all, because it is visibly automatic. It is the cheapest signal available that somebody is paying attention, and the cheapest way to prove nobody is.

07

What about the customers who will never leave one?

Most of them, and the arithmetic is worth doing honestly.

A shop that closes forty jobs a month and asks every one of them does not get forty reviews. It gets a handful, because most people who intend to write one never do. That is not a failure of the process, it is the ordinary response rate, and shops that expect otherwise abandon a working system after six weeks.

Two things follow. Ask on every job, because the only lever you control is the size of the top of the funnel, and asking selectively is both prohibited and self-defeating. And judge the process on a quarter, not a fortnight, because at these volumes a month of data is mostly noise.

There is one exception worth making. A customer who has just had a large or difficult job go well, who said something appreciative at the counter, is a person who will actually write something. That is not selective solicitation as long as everybody else is asked too. The rule is against asking only the happy ones, not against noticing.

And do not chase the ones who do not respond. A third message converts almost nothing and turns a neutral non-response into an irritation, which is a bad trade in a business built on repeat visits.

08

Who owns the sending?

One named person, with a named backup, attached to an event that already happens.

The most common failure is not policy and not wording. It is that the service advisor who used to send them left in April and nobody noticed until August, because nothing breaks visibly when reviews stop arriving.

Attach the send to the invoice being closed, so it happens as part of work that already has to happen and does not depend on anybody remembering, and give it to somebody by name with the backup written down. That systems argument, and why it survives a departure, is in building a review system that survives a staff change.

09

What does this do for rankings?

Steadiness does more than count, and none of it replaces the profile itself.

A profile collecting reviews steadily reads differently, to a customer and to a ranking system, than one that collected forty in a burst two years ago. What the evidence supports and what it does not is in review velocity as a local ranking factor.

What reviews cannot do is fix a wrong primary category, hours that are false, or a missing symptom page. That side is in the check engine light search.

Be honest with yourself

When you do not need this

If you have fewer than ten reviews, do not design a system yet. Ask everybody from the last six months, once, and see where you land first.

If reviews already arrive steadily with no process, do not add one. A working habit beats a formal system nobody follows, and formalizing it is how a shop accidentally introduces the staff target the policy names as prohibited.

And if the recent ones are poor, a faster cadence makes the problem arrive faster. Fix the thing being reviewed. More requests against an unresolved service problem is a louder version of the same signal.

11

Where these numbers come from

There are no statistics in this article, deliberately. We could not read a primary source for how many reviews a shop collects, what share of customers respond to a request, or what a review is worth in car count, and this topic is full of numbers that trace back to vendor marketing rather than to data. Where this article gives timing, it is our recommendation from operating these systems and it is labeled as that.

Google's prohibited and restricted content policy for Maps contributions supplies the solicitation rules, the on-premises sentence and the staff-direction examples. Google's tips to get more reviews supplies the incentive label, the review link mechanism and the signed-in requirement. Both read 2026-09-07.

The federal material is from the text of 16 CFR Part 465 rather than a summary: sections 465.2(d), 465.4, 465.5 and 465.7. Read 2026-09-07.

Related reading

For the cadence in other trades and why it differs, the review request after the ticket closes. For the reply, responding to a bad review. For the process surviving a departure, building a review system that survives a staff change.

For what steadiness does, review velocity as a local ranking factor. For the profile and page work underneath it, the check engine light search. The rest of our writing on this sits in Reviews and Reputation.

If you want a look at your request process before you change it, email eric@seod.com and describe how it works today. We will tell you whether it has a gating problem, which is the one that matters, and what the cheapest fix is.

If you would rather we built and ran it alongside the profile work, that is part of Search visibility.

Written by

Eric Lee, founder of SEOD

Sixteen years running restaurant, retail and nonprofit operations before starting SEOD in 2016, with more than $54 million in annual P&L managed. He writes these because the same questions come up on the same calls.

More about Eric · How these are sourced

Call Eric Email Eric