How roofing companies get more Google reviews
The tear-off day ask, the final walkthrough script, the exact text to send, and what a healthy review pace looks like when you only do 120 jobs a year.
A plumbing shop can afford to be sloppy about reviews. It runs 2,000 service calls a year, so even a lazy process produces a trickle. A roofing company completes somewhere between 60 and 200 jobs in a year. Every single one of them has to produce a review or the count never moves.
That is why the numbers look the way they do. Across 102,385 roofing companies on Google, the median has 13 reviews and 44.2% have fewer than ten. Only 14.1% have passed 100. In a competitive metro, the three companies in the map pack are usually past that. The gap is not luck and it is not tenure. It is whether the ask is built into the job or left to memory.
The two moments that actually work
There are two windows where a roofing customer will leave a review, and both of them close fast.
The first is the end of tear-off day. The old roof is in the dumpster, the new decking or underlayment is down, the yard is clean, and the homeowner is standing in the driveway genuinely relieved that the biggest, loudest, most stressful part is over. That relief is the emotion that writes five-star reviews.
The second is the final walkthrough, when you hand over the warranty packet and the magnet sweep is done. Relief is lower by then but trust is at its peak.
Use both. The tear-off day ask gets the review written; the walkthrough ask catches everyone who forgot.
The script
The crew lead or the production manager says this while the homeowner is looking at the clean yard:
"Mrs. Alvarez, that is the hard part done. If you are happy with how today went, the single most useful thing you could do for us is a Google review. I am going to text you the direct link right now so you do not have to hunt for it. If anything about the job is not right, tell me first and I will fix it before you write anything."
That last sentence matters. It is not review gating, because you are texting the link to everyone regardless of the answer. It just gives an unhappy customer a place to say so that is not the internet.
The link and the text
Get the short review link from your Google Business Profile under "Ask for reviews". Save it as a text template on every crew lead's and every sales rep's phone:
"Hi [name], this is [name] with [company]. Thanks for having us out on [street]. Here is the direct link to leave us a Google review: [link]. It takes about a minute and it makes a real difference for a local company. If you can, mention it was a [shingle/metal/flat] roof in [city]."
Under 320 characters. No emoji, no "we would love your feedback". The customer already decided in the driveway.
Ask for the job and the town by name
That last line is worth more than it looks. Reviews that name the work and the location feed both Google's local ranking and the AI answer engines that now summarize businesses for people who ask ChatGPT or Google for a roofer in their city.
Fifty reviews that say "replaced our hail-damaged architectural shingle roof in Broken Arrow in two days, handled the insurance paperwork" outperform two hundred that say "great job, highly recommend". Ask for the specific and you get the specific about a third of the time, which is plenty. The same plain, specific language is what gets you named in AI answers, which is covered in the AI search guide.
What healthy pace looks like
Set the target as a percentage of completed jobs, not a monthly number, because your volume swings with the weather.
A well-run process converts 40% to 60% of completed roofs into a Google review. A company doing 120 roofs a year at 50% adds about 60 reviews annually. Start at 15 reviews and you clear the 75th percentile for the trade, which sits at 50, inside twelve months, and you are on your way to the 141 at the 90th percentile in year two.
Track it on the production board next to the job: asked, texted, reviewed. If a crew lead runs eight roofs and produces zero reviews, he is not asking. If he produces six, have him show the others how he opens the conversation. Pay a spiff on the documented ask if you like, never on the review itself, which keeps you inside Google's rules.
What Google actually prohibits
Google's review policies ban offering customers anything of value in exchange for a review, ban review gating (surveying first and only sending the link to the happy ones), and ban reviews from employees, family or subcontractors. Any of those can get reviews stripped or the profile suspended, and a suspension in the middle of storm season is a serious problem.
Asking everyone, every time, is entirely allowed. So is texting the link, and so is one reminder.
Storm work needs a different rhythm
After a hail event you may sign 40 roofs in three weeks and complete them over the following two months, often with the insurance payment still in play. Homeowners are less inclined to review while a supplement is outstanding.
The fix is to ask at tear-off anyway and then run a second ask 14 days after final payment clears, when the file is closed and the feeling about your company is settled. That second ask recovers a meaningful share of storm customers who were distracted the first time.
Handling the bad one
Every company doing volume gets a one-star review. Reply inside 24 hours, three sentences, calm and specific: "We installed this roof in April and I am sorry the ridge vent leaked in the June storm. Our production manager has been out twice and we are replacing the section at no charge this week." Homeowners read the reply more carefully than the complaint. Across the dataset 80.4% of roofing companies are at 4.5 stars or better, so your rating alone is not a differentiator. How you answer trouble is.
A 90-day rollout
- Week 1: pull the review link, write the saved text, brief every crew lead and rep, add three columns to the production board.
- Weeks 2 to 6: ask at tear-off on every job. Expect about one review per three asks at first.
- Week 7: add the 48-hour reminder text for anyone who has not reviewed. One reminder only.
- Week 10: add the second ask for storm files after final payment, and start asking for the job type and city by name.
- Week 12: review the per-rep tally, fix the outliers, and set the annual target as a percentage of completed roofs.
Frequently asked
Should I buy review software? Only after the manual ask works. Software automates the text; it cannot make a crew lead stand in the driveway and ask, and the driveway is where the review comes from.
Can I put the link on the invoice or the warranty packet? Yes, with a QR code. It converts far worse than the spoken ask, but it costs nothing and catches a few.
What about the sales rep asking instead of the crew? The rep should ask too, at contract signing, for a review of the sales experience. Two asks from two people on two days beats one.
Where should reviews show up besides Google? On your own service and city pages, three per page, which is covered in the website guide. Google is where they earn rankings; your site is where they close.
Set up correctly, this is a system you run once and then just measure. If you would rather have it built for you, review generation is one of the services in the free 14-day trial, and the benchmark report shows where your count sits today. Text or call (385) 832-6175.