How to Get 50 Google Reviews in Six Months (The Exact System)

Two plumbers in the same town. One has 9 reviews, the other has 61. Same price, same truck, same work. The one with 61 reviews gets the call.

That’s the whole game. Google’s local pack shows three businesses. Review count and rating are a big part of how you rank and almost all of how a stranger picks between the three. A contractor sitting at 9 reviews is invisible to anyone who doesn’t already know his name.

Fifty reviews in six months is not hard. It’s roughly two a week. If you run 4–8 jobs a week, you need maybe a 30% conversion on asks. The reason most contractors don’t get there isn’t effort — it’s that they ask at the wrong moment, in the wrong words, with no follow-up.

What 50 reviews is actually worth

Put a dollar figure on it so you take it seriously.

Say your average job is $1,800 and you close half the estimates you write. If better review standing moves you from the fourth result to the local pack and adds just two extra calls a month, that’s one extra job a month:

Item	Amount
Extra jobs per month	1
Average job	$1,800
Annual added revenue	$21,600
At 15% net margin	$3,240/yr profit
Cost of the review system	~$0–30/month

And that’s a conservative version. For a lot of trades the jump from “under 10 reviews” to “over 40” changes who even considers you. Nobody hires a roofer with 6 reviews for a $14,000 job.

If your Google Business Profile isn’t fully set up yet, fix that first — reviews land on a profile, and an empty profile wastes them. Google Business Profile for Contractors walks through the setup.

The math: how many asks you need

Work backward.

Goal: 50 reviews in 26 weeks
Realistic conversion on a good ask with one follow-up: 30–40%
Asks needed: 50 ÷ 0.35 ≈ 143 asks
Per week: about 5–6 asks

If you run fewer than five jobs a week, you have two options: ask everyone including small service calls, or go back through your last 18 months of customers and ask them too. Both work. More on the backlog in a minute.

The number to track is asks, not reviews. Reviews are the output. Asks are the input you control.

The timing: there is one right moment

Ask when the customer is happiest. That is almost never the next day, and it is definitely not two weeks later when the invoice is still unpaid.

The right moment is when the customer says something nice to your face.

They walk into the bathroom, look at the tile, and say “oh wow, that looks great.” That sentence is your cue. Not tomorrow. Right then.

Second-best moment: within two hours of finishing the job, by text, while the new work is still the most interesting thing in their house.

Worst moments:

Before final payment clears. You’re mixing two asks, and one of them is money.
A week later. The emotional peak is gone.
After any problem, even a solved one. Give it a full week and let the fix settle.

Timing by job type

Job type	Ask when
Service call (2–4 hrs)	Standing there, before you load the truck
One-day install	Walkthrough, right after they inspect it
Multi-day remodel	Final walkthrough, after the punch list is cleared
Emergency / after-hours	Next morning by text — they were stressed at 11pm
Warranty or callback fix	One week later, by text

The ask: exact words

Vague asks get vague results. “Leave us a review if you get a chance” converts at maybe 10%. Here’s what to say instead.

In person:

“Glad you’re happy with it. Can I ask a favor? Most of my work comes from Google, and reviews are basically how people find me. I’m going to text you a link right now — if you’ve got two minutes tonight, it would really help.”

Then actually send the text while you’re standing there. Say “sending it now” and send it. The customer watches their phone buzz. That one move probably doubles your conversion versus “I’ll send it later.”

The text itself:

Hi Dana — Mike from Harbor Electric. Thanks again for having me out today. If you have 2 minutes, a quick Google review would mean a lot — it’s how most of my customers find me. [link]

Three rules on the text:

Use your name and the customer’s name. Templates that read like a system get ignored.
One link, direct to the review form. Not to your profile, not to your website. Grab the “Ask for reviews” short link from your Google Business Profile dashboard.
Say how long it takes. “Two minutes” removes the main objection.

What never to do

Do not offer anything in exchange. No discount, no gift card, no entry into a drawing. Google’s policy prohibits incentivized reviews, and the risk isn’t just removal of that review — it’s your whole profile getting flagged. Reviews are the one asset in your marketing you can’t buy back.

Do not filter. Some tools ask “were you happy?” first and only send the Google link to the people who say yes. That’s review gating, it violates Google’s terms, and it’s exactly the kind of thing that gets a profile penalized. Ask everyone the same way.

The follow-up that doubles your results

Most reviews you earn come from the second message, not the first. People mean to do it. They’re making dinner. They forget.

Send one follow-up, three days later, and then stop:

Hi Dana — following up once in case this got buried. No worries if you’d rather not, but if you have a minute the review link is here: [link]

One follow-up. Not three. The “no worries if you’d rather not” is doing real work — it keeps you from feeling like a telemarketer and gives the customer an easy out, which paradoxically makes more of them do it.

Automating it so it actually happens

You will not do this manually for six months. Nobody does. Build it into the thing you already touch at the end of every job.

Three options by budget:

Approach	Cost	How it works
Phone shortcut	$0	Save the ask + review link as a text replacement. Type “rev” and the whole message appears. Set a recurring Friday reminder to send any you missed.
Spreadsheet column	$0	Add “Review asked” and “Follow-up sent” columns to your job tracker. Review it weekly.
Field service software	$30–150/mo	Jobber, Housecall Pro and similar fire a review request automatically when you mark a job complete, with built-in follow-up.

If you’re already paying for software, turn this feature on today — most contractors have it and never enabled it. Jobber and Housecall Pro both include automated review requests in their standard plans.

If you’re on the free stack, the phone shortcut plus a weekly 10-minute block is genuinely enough. Set a calendar block Friday at 4pm: open your job list, send every ask you owe, send every follow-up you owe. Fifteen minutes, 5–6 asks, done.

The system beats the intention. Put the ask inside a process you already run.

Mining your backlog

If you’re starting from 9 reviews, don’t wait for new jobs. Go back through 12–18 months of invoices and pull every customer who was happy and whose job went clean. Skip anyone with a dispute, a late payment fight, or a callback you argued about.

Text them in batches of 10, one batch a week:

Hi Tom — Mike from Harbor Electric, did your panel upgrade back in March. Hope it’s still running well. I’m trying to build up my Google reviews this year — if you’d be up for leaving a quick one, the link is here: [link] Thanks either way.

Expect lower conversion than fresh jobs — maybe 15–20%. From 60 old customers, that’s 9–12 reviews in your first month. That’s a real head start.

Handling the bad one

You will get a bad review. At 50 reviews you’ll probably have one or two under three stars. That’s normal and, honestly, useful — a profile with 50 reviews and a perfect 5.0 looks fake to a lot of people. A 4.7 with a well-handled complaint reads as real.

What matters is the response, because the response is written for the next customer reading it, not for the angry one.

The response formula

Thank them by name.
State one specific verifiable fact, neutrally.
Say what you did or offered to do.
Give a direct contact.
Stop. Under 100 words.

Bad response:

This customer is lying. We were there on time every day and they refused to pay the final invoice. Some people just can’t be pleased.

Good response:

Tom — thanks for the feedback, and I’m sorry the finish date slipped. We hit a water line behind the old vanity on day two, which added the plumbing work we discussed on the 14th. I offered to credit the two extra days of labor, and that offer still stands. Call me directly at 555-0148. — Mike

Nobody reading that thinks less of Mike. Several readers think more of him.

Other rules:

Never respond the same day. Draft it, sleep on it, send it tomorrow.
Never reveal private details — no payment amounts, no medical info, no “she was drunk when we arrived.” You will lose that exchange even if you’re right.
Move it off the platform fast. “Call me directly” is the point of the whole reply.
Don’t beg for removal. Google only removes reviews that violate policy — fake, off-topic, harassing. If it’s genuinely one of those, flag it, then move on. Most flags fail.

The best defense against a bad review is documentation and a clear scope. If you’re getting complaints about surprise costs or timelines, the fix lives upstream in change orders and jobsite photos, not in your review replies.

Respond to the good ones too

Thirty seconds each. Mention the job type — it’s a signal to Google and it tells the next reader what you actually do:

Thanks Dana — glad the new panel and the kitchen circuits are working out. Call anytime.

Don’t copy-paste the same four words 50 times. It’s visible and it looks lazy.

The six-month schedule

Weeks	Focus	Target
1	Profile complete, review link saved, phone shortcut built	0 new
2–5	Backlog campaign, 10 texts/week	8–12
2–26	Every job gets an ask + one follow-up	35–45
Ongoing	Respond to every review within 48 hours	—

That lands you between 43 and 57. If you’re short at month five, run a second backlog pass on anyone who never replied the first time.

Your next step

Open your Google Business Profile right now, find “Ask for reviews,” and copy the short link. Save it in your phone as a text replacement — type “rev” and the full ask appears.

Then send it to the last three customers you finished for. Today. Those three take four minutes total, and they’re the proof you need that the system works before you build the rest of it.