How contractors get more Google reviews
A contractor with 40 reviews and four new ones this month will usually outrank one with 300 reviews and nothing since last year. Here’s the system that produces the steady flow — and the shortcuts that get profiles suspended.
Updated July 2026 · Engineered Reach
Reviews are not a trophy shelf, they are a live signal. Google’s local ranking weighs prominence, and a steady, recent flow of reviews is one of the clearest ways to feed it. The contractors who win aren’t asking more persuasively — they’ve made asking automatic, built into job closeout the same way invoicing is. Ask at the moment the work is finished and the customer is standing in front of it, send one link, follow up once, respond to every review, and never gate, buy, or incentivize them.
Why velocity beats count
Most contractors treat reviews as a scoreboard. You hit 100, you feel good, you stop thinking about it. Then a year later the phone is quieter and nobody can explain why.
Here is what changed. Total review count still functions as a credential — a homeowner comparing three companies notices the difference between 12 reviews and 120. But the ranking behavior most local SEO practitioners observe is that recency and consistency carry disproportionate weight. A profile receiving new reviews every week reads as an active business currently serving customers. A profile that collected 300 reviews between 2021 and 2023 and nothing since reads as a business that may have slowed down, retired, or closed.
Google does not publish a review velocity metric, and anyone who tells you they know the exact formula is guessing. But the pattern shows up consistently enough in local search that it’s worth treating as real: the newer company with fewer but fresher reviews frequently outranks the older company sitting on a stale pile.
The practical translation for your business: two to four new Google reviews a month, indefinitely, beats forty reviews in one push and then silence. A burst looks unnatural and does nothing for you six months later. A steady drip compounds.
What Google actually does with your reviews
Reviews aren’t doing one job. They’re doing at least four, and each one has a different mechanism.
| Where it acts | What’s being read | Why it matters to you |
|---|---|---|
| Map pack ranking | Volume, recency, rating, and the words inside the reviews | Feeds the prominence side of local ranking — see our Google Business Profile guide |
| Click-through | Star rating and count shown in the listing | Two companies rank next to each other; the one with 4.9 and 87 reviews gets the tap |
| Local Services Ads | Rating, review count, and your responsiveness | Google’s own documentation lists rating and number of reviews among the profile quality factors in LSA ad ranking |
| AI answers | Review text as evidence about who you are and what you do | Assistants summarizing “best plumber in…” pull heavily from review language — see AI search visibility |
That fourth row is the newest and the least understood. When a homeowner asks an AI assistant for a recommendation, the assistant is not reading your homepage copy about being family owned since 1998. It is reading what other people wrote about you. Your reviews are increasingly the primary source material for how machines describe your business.
The one moment that reliably works
There is a single highest-converting moment to ask, and almost every contractor misses it.
It is at the end of the job, in person, while the homeowner is looking at the finished work. The furnace is running. The leak stopped. The panel is clean and labeled. Satisfaction is at its absolute peak and it will never be higher than it is right then.
What most contractors do instead: pack up, drive off, and send a review request email three days later when the homeowner has moved on and the warm feeling has faded into “that thing I paid for on Tuesday.”
The in-person ask works because it is specific, human, and unavoidable in a way an email is not. It also takes about eleven seconds:
- “Before I head out — if you were happy with how this went, would you leave us a quick Google review? It genuinely makes a difference for a company our size.”
- Then hand them something. A card with a QR code, or send the link to their phone while you’re standing there.
- If they say yes, that’s the moment. Don’t leave it to memory.
The reason this matters more than any wording trick: the ask has to happen when the person is already feeling it. Everything else is recovery work.
Building the ask into the job, not the good intentions
“Ask for reviews” is not a system. It’s a wish. The tech who remembers is the tech who wasn’t running forty minutes behind.
A system is something that happens whether or not anyone remembers. In practice that means four pieces:
- It’s a step in closeout. Not a suggestion — a line item on the same checklist as collecting payment and cleaning the work area. If your field software has a job completion flow, the review request lives inside it.
- One link, no friction. Grab your Google review link from your Business Profile and shorten it. Not your homepage. Not “search us on Google.” A homeowner who has to hunt will not hunt.
- Automated text within the hour. Text open rates crush email for this, and an hour later the job is still fresh. One message, plain language, no marketing voice.
- Exactly one follow-up, three days later. Then stop. One reminder is a courtesy; three is harassment and it damages a relationship worth more than the review.
The failure mode to watch for is the one nobody catches: the automation gets set up in March, a phone number changes in July, and it silently stops sending. Someone should be looking at the monthly review count and noticing when it drops. If nobody owns that number, it will drift.
Count your completed jobs last month, then count the reviews you received. If you did 60 jobs and got 2 reviews, your problem is not that customers dislike you — it’s that you asked 4 of them. A functioning process asks close to everyone and converts a meaningful fraction of them.
The four things that will get you in trouble
This is the part where good intentions become an actual liability, so it is worth being blunt.
Do not gate reviews. Review gating means surveying customers first and only sending the happy ones to Google. It is a direct violation of Google’s policies, and the platforms that sold it to contractors as a feature have quietly removed it. Suppressing negative feedback while soliciting positive feedback is also the sort of thing the FTC has taken an active interest in.
Do not incentivize. No gift cards, no discounts, no drawing for a free tune-up. Offering anything of value in exchange for a review violates Google’s policy and, if not disclosed, creates exposure under the FTC’s rules on endorsements. The review is worth less than the risk.
Do not buy reviews. They are detectable, they get removed in sweeps, and a profile that has been through a review purge can lose its ranking foothold in a way that takes a long time to rebuild. There is no version of this that ends well.
Do not have your team write them. Reviews from employees, family, or the same handful of IP addresses are the easiest pattern to spot. It also means your review text describes a business nobody actually experienced, which shows.
The honest framing: every one of these shortcuts exists because the legitimate path takes months. It does. The legitimate path also cannot be taken away from you in a single algorithm update, which is the entire point.
Getting reviews that are actually useful
A five-star review that says “Great service!” does very little. It counts toward volume and it does nothing else.
A review that says “Our AC died during that heat wave in July and they had a tech out to our place in Tollgate the same afternoon — replaced the capacitor and walked me through what failed” is doing real work. It contains the service, the urgency, the neighborhood, and a description of the process. That is the text that gets read by ranking systems, by AI assistants, and by the next homeowner deciding whether to call.
You cannot script what customers write, and you absolutely should not try. What you can do is prompt memory:
- “If you mention what we fixed and roughly how fast we got out there, that helps other folks in the neighborhood know what to expect.”
- Ask by name where it’s natural — reviews that name the technician tend to be more specific, and they’re good for your team to read.
- Never provide sample text. Beyond the policy problem, it produces a wall of reviews that read identically, which is obvious to everyone including the homeowner.
One more thing worth saying plainly: a perfect 5.0 is not the goal. A handful of 4-star reviews and one thoughtfully-handled 3-star makes a profile read as real. Flawless is the thing people have learned to be suspicious of.
Responding is not optional
Response rate is a signal, and it is one of the few that costs nothing but time.
Respond to every review. All of them. Positive ones get two sentences that reference the actual job — not a copy-pasted “Thank you for your business!” repeated ninety times, which reads exactly as automated as it is. Reference the service, thank them by name, and stop.
The reason this matters beyond politeness: your responses are indexed text on your profile, and a reply that mentions the service and the area adds relevant language you didn’t have to ask a customer to write. It also demonstrates, to anyone reading, that a human is paying attention.
Set a rule — within 48 hours, no exceptions — and make one person responsible. Not “whoever gets to it.”
The negative one
You will get a bad review. Some will be fair. Some will be from someone you never worked for, or someone furious about a price you quoted accurately before starting.
The instinct is to defend yourself in detail. Resist it. Your response is not written for the reviewer — that argument is already lost. It is written for the next fifty people who read it while deciding whether to call you.
What works:
- Respond within a day, calmly. A long gap looks like you didn’t notice or didn’t care.
- Acknowledge the experience without litigating the facts. “I’m sorry the install ran long — that’s not the experience we want anyone to have.”
- Move it offline. Give a name and a direct number. Publicly showing that you want to fix it is most of the value.
- Never mention private details. Not what they paid, not what happened in their home, not their behavior. It is a privacy problem and it reads badly regardless of who was right.
If a review genuinely violates Google’s policies — it’s from a competitor, it contains no actual customer experience, it’s abusive — you can report it. Expect that process to be slow and inconsistent. Plan on the response mattering more than the removal.
And the thing worth remembering: a well-handled negative review sitting under a wall of specific positive ones can help you. It proves the rest are real.
Where else this shows up
Two places contractors underestimate.
Local Services Ads. If you run LSAs, reviews are not just decoration. Google’s ad ranking documentation names your rating and number of reviews as part of profile quality, alongside your responsiveness to inquiries. So the review system and the phone-answering system feed the same ranking machinery. We cover the second half of that in why response time decides who books the job, and the LSA-versus-search-ads decision in this comparison.
Other platforms, in order of usefulness. Google is the one that moves rankings. Facebook recommendations and BBB are mild trust signals. Yelp matters in some metros and for some trades, and effectively not at all in others — and it has no documented influence on Google’s local ranking. Industry-specific directories are worth a profile mostly for the citation and link, which we cover in how contractors earn backlinks.
The practical allocation: put roughly all of your review-generation energy into Google. Claim the others, keep them accurate, and don’t split the ask.
What to do in the next 30 days
Nothing here requires a platform purchase or a consultant. It requires deciding that this is a process and not a hope.
| Week | What to actually do |
|---|---|
| Week 1 | Pull your Google review link and shorten it. Count last month’s jobs against last month’s reviews so you know your real conversion rate. |
| Week 1 | Reply to every unanswered review on the profile, oldest to newest. This alone is often a visible change. |
| Week 2 | Add the ask to the closeout checklist and tell the crew why, with the actual script. Print the QR cards. |
| Week 2 | Set up the automated text at job completion plus one follow-up at day three. Test it on your own phone. |
| Week 3 | Assign one person the 48-hour response rule. Put the monthly review count somewhere it gets looked at. |
| Week 4 | Check the number. If jobs went up and reviews didn’t, the ask isn’t happening in the field — that’s a crew conversation, not a software problem. |
Give it ninety days before you judge it. Review velocity is a slow-moving signal and the compounding is the point — a business adding three reviews a month is unrecognizable two years later, and there is no shortcut that gets you there faster without risking the profile entirely.
Want a look at where your profile actually stands against the other companies in your market? Book a free 30-minute Revenue Plan with Engineered Reach and we’ll go through it with you.