Why Review Count and Velocity Move Your Map Pack Ranking
Google's local ranking algorithm weighs three factors: relevance, distance, and prominence. Review count and review score sit inside prominence, and prominence is the factor a contractor can actually influence week to week. A roofer with 6 reviews and a 4.9 average is not competing with a roofer three towns over who has 140 reviews at 4.7. Google reads the second profile as more established, more trusted by searchers, more likely to satisfy the query, even though the star average is lower.
Review velocity, meaning how recently and how consistently new reviews land, matters as much as total count. A profile that got 40 reviews in 2019 and nothing since reads as dormant. A profile adding 3 to 5 reviews a month reads as an active, operating business. Google's systems can see the date stamp on every review. A stale review history is a signal, same as a stale post history or an unanswered Q&A section.
This is why review flow belongs inside profile management, not as a side project run once a quarter. The review count on your Business Profile is one of the few ranking inputs that updates in near real time and is entirely within a contractor's control, unlike citations, backlinks, or the searcher's physical location.
Trade also matters here. A locksmith or emergency plumber competing on "near me" searches lives or dies by how fresh the reviews look, since those searches skew toward a decision made in minutes. A remodeler or a roofer selling a project worth five figures gets read more slowly, with searchers scrolling further into the review text itself, looking for detail about crew conduct, cleanup, and whether the final price matched the quote. Both trades need volume and velocity. The remodeler additionally needs review text with substance, not just a star rating.
What review signals do NOT do
- They do not override a category mismatch. If you're listed as "Contractor" instead of "Roofing Contractor," reviews will not fix that gap.
- They do not substitute for service-area setup. A profile with no service areas defined will not show for searches outside its pin, no matter how many reviews it carries.
- They do not fix a suspended or unverified profile. Reviews accrue on a live profile only.
Review flow is one lever on a profile that also needs correct categories, complete services, and service-area coverage. Treat it as part of the whole, not a fix on its own. A contractor who fixes review flow on a profile that's still miscategorized or missing service areas is polishing a truck that won't start.
Find and Share Your Google Review Link
Every Business Profile has a direct review link, sometimes called a short link or review URL, that drops a customer straight onto the star-rating screen. This is the single biggest lever most contractors are missing. Without it, a customer has to search your business name, find the right listing among duplicates, click through to Maps, and then find the review tab. Each of those steps loses people.
To get your link: open your Business Profile (either through Google Search by searching your business name, or through the Google Business Profile Manager), find the "Ask for reviews" or "Get more reviews" button, and copy the short link it generates. It typically looks like g.page/r/[code]/review. That link is what goes in every request from this point forward.
Where the link should live
- Text message sent after job completion (highest response rate for home-service work, since most customers read a text within minutes)
- Invoice or final paperwork, printed or emailed, as a QR code and a typed link
- Email receipt if you send one, as a plain clickable link, not buried in a signature block
- A physical card or magnet left with the customer, useful for trades that do return visits like HVAC or pest control
A QR code is worth generating once and reusing everywhere. Point it at the same short link. For truck decals, invoice footers, or a laminated card in the service van, a QR code removes the typing step entirely, which matters more than it sounds like it should. Customers who have to type a link on a phone abandon the request more often than customers who scan and tap.
One caution: don't route the link through a review-gating tool that filters unhappy customers to a private form and only sends happy customers to Google. Google's guidelines prohibit this, and it puts the whole profile at risk if flagged. Send every customer to the same public link.
If your profile is a duplicate, unclaimed, or shows up twice in Maps under slightly different names, the review link problem gets worse before it gets better: reviews can end up split across two listings, both under-counted. That's a profile-cleanup issue, not a request-flow issue, and it should get fixed before a review push, otherwise the effort is split between two profiles instead of building one strong one.
When to Ask: Timing That Actually Gets a Response
Timing decides whether a request gets answered or ignored. For most home-service trades, the request should go out within 24 hours of job completion, while the work is still visible and the relief of a finished project is still fresh. Wait a week and the moment passes; the customer has moved on and the request reads as an afterthought.
The exact window shifts by trade. A locksmith finishing an emergency lockout job should send the request that same evening, while gratitude is at its highest. A roofer wrapping a multi-day reroof should send it the day after final cleanup and walkthrough, once the customer has seen the finished job in daylight, not mid-project. A pest control company on a recurring service plan should ask after the second or third visit, once the customer has evidence the treatment is working, rather than after the first visit when results aren't yet visible.
A simple timing framework by job type
| Job type | Best time to ask |
|---|---|
| Same-day service call (locksmith, emergency plumbing) | Same day, within a few hours of completion |
| Multi-day project (roofing, remodel, install) | Day after final walkthrough |
| Recurring service (pest control, lawn, HVAC maintenance) | After 2nd or 3rd visit, once results are visible |
| Warranty or follow-up call | Skip the ask; focus on the fix, request later |
One request is rarely enough. A single follow-up reminder 3 to 5 days later, sent only to customers who haven't clicked the link, lifts response rate without becoming a nuisance. Beyond one reminder, stop. Repeated requests read as pressure and can prompt a customer to leave a review out of irritation rather than satisfaction.
What to Say: Request Scripts That Don't Sound Like a Form Letter
The request itself should be short, specific to the job, and free of guilt-tripping language. A generic "please review us" text gets ignored because it could have come from any business. A request that names the job, the crew, or the specific fix gets read because it feels personal.
Text message script (send within 24 hours)
Hey [Name], it's [Company], thanks for having us out for the [job type, e.g. "gutter install"] yesterday. If you've got 60 seconds, a Google review helps other homeowners in [town] find us. Here's the link: [link]. Thanks again.
Email script (for jobs where email is the primary contact method)
Subject: Quick favor, [Name]?
Hi [Name], glad we could get the [job type] handled. If the crew did right by you, a short Google review would mean a lot, and it helps neighbors in [town] find a contractor who shows up and does the job correctly. Link's below. No pressure either way, and call us anytime if anything needs a second look.
What makes a request script work
- Name the job type, not just "our service"
- Name the town or neighborhood, which subtly signals to Google (and future readers) the service area
- Keep it under 40 words for text, under 80 for email
- Offer an out ("call us anytime if anything needs a second look") rather than only chasing a star rating
- Never offer a discount, gift card, or incentive tied to leaving a review. Google's guidelines prohibit incentivized reviews, and a flagged pattern can trigger a content policy suspension on the whole profile
Field crews are often the best people to make the ask verbally at the end of a job, with the follow-up text as the actual delivery mechanism for the link. "I'll send you a text with a link if you don't mind leaving us a quick review" spoken on the doorstep, followed by the text ten minutes later, converts better than a cold text with no verbal heads-up.
Responding to Reviews: What Google (and Searchers) Expect to See
Every review, positive or negative, should get a response. This is a profile-side signal Google's systems can read, and it's one of the first things a searcher checks before calling. An unanswered negative review sitting at the top of a profile for months tells a searcher the business doesn't engage; a thoughtful response to that same review tells a searcher the business handles problems like an adult.
Responding to positive reviews
Keep it short and specific. Thank the customer by name, reference the job if the review mentions it, and avoid a copy-pasted "Thank you for your feedback!" on every single review, which reads as automated even when a human wrote it. A response that names the crew member or the specific fix reinforces the review's credibility for future readers.
Responding to negative reviews
Acknowledge the specific complaint, state what was done or will be done to address it, and move the detailed back-and-forth off the public review (a phone number or direct contact, not a generic "please reach out"). Never argue with a reviewer in the response, never accuse them of lying, and never disclose private customer details in a public reply, which can violate Google's policies and the customer's privacy. A calm, factual response to a bad review often does more for conversion than the review itself does damage, because searchers read the response as a preview of how the business handles them if something goes wrong.
Flagging reviews that violate policy
Reviews from someone who was never a customer, reviews left by a competitor, or reviews containing off-topic content (politics, unrelated complaints) can be flagged for removal through the profile dashboard. Google removes a portion of flagged reviews after manual assessment, not all, and there's no guaranteed timeline. Flagging is worth doing for clearly fake or malicious reviews; it's not a tool for removing an accurate but unflattering review of real work.
Fixing a Stalled Review Flow
Some profiles get stuck: a burst of reviews when the business first opened, then years of near-silence. A few common causes, and the profile-side fix for each.
No one is asking
The most common cause by a wide margin. If the request depends on an owner remembering to send a text at the end of a busy week, it happens inconsistently or not at all. The fix is building the ask into the job-completion routine itself: the same step every time, done by whoever closes out the job (dispatcher, crew lead, or an automated text triggered off job-completion status in whatever scheduling software the business already runs).
The link is missing or wrong
A surprising number of contractor profiles send customers to a generic "leave a review" search result instead of the direct short link, or worse, to a duplicate or unclaimed listing. Test your own link from a phone that's logged into a personal Google account (not the business account) to confirm it lands exactly where it should: the star-rating screen for the correct, live profile.
The profile itself is suppressed or under-optimized
A profile with an incomplete category, missing services, or an unverified status can suppress how prominently reviews display, or can suppress the profile from search results entirely, meaning new reviews are landing on a page almost no one sees. Review flow fixes are wasted effort on a profile that isn't otherwise set up correctly.
Review volume dropped suddenly
A sudden drop, especially paired with reviews disappearing rather than just slowing, can indicate a content policy issue or a suspension in progress. That's a different problem than a weak request flow and needs to be diagnosed on its own before spending more effort on outreach.
One person owns the routine, or no one does
On multi-truck operations, review flow tends to work only when one person is accountable for it: usually whoever handles dispatch or invoicing, since they already touch every completed job. Splitting the responsibility across the whole crew, with no single owner checking that the text actually went out, is how a business ends up with three reviews from six months of steady work despite dozens of satisfied customers.
A profile-side review system is maintenance, not a one-time project. The trades that keep a steady 3 to 5 reviews a month build the ask into the job-close routine, assign it to one person, and never treat it as optional.