On-Site Local SEO: LocalBusiness Schema and City Pages
The website side of local SEO: NAP consistency, the contact page, LocalBusiness structured data, the review ma...
Read
One element in local SEO does two different jobs at once: it moves rankings and it closes sales. That element is reviews.
Google confirms the ranking side itself: "More reviews and positive ratings can help your business's local ranking." The sales side is visible to the naked eye — three businesses sit side by side in the local pack, all three have a name, an address and opening hours; what separates them is the stars and the number in brackets.
So review work is not something to do "when there's time". And yet this is where the guidelines are broken most often, because the most tempting shortcuts also live here. This article covers both: how to build the system, and which shortcut quietly damages your profile.
Job one — ranking. Google counts reviews as part of the prominence factor and says so directly: "More reviews and positive ratings can help your business's local ranking." Two words in that sentence matter: more (count) and positive (rating). A high score alone is not enough, and volume alone is not enough either.
Job two — conversion. This one often weighs more. Users decide within seconds in the local pack, and the main input is stars plus review count. The pattern you meet constantly:
| Business | Rating | Reviews | What the user reads |
|---|---|---|---|
| A | 5.0 ★ | 7 | "New, untested" |
| B | 4.7 ★ | 284 | "Lots of people went, generally happy" |
| C | 4.9 ★ | 41 | "Good, but less proven than B" |
Statistically B wins. Review count is the quantitative measure of trust — a 5.0 built on a handful of reviews is both a weak signal and a source of suspicion.
There is a third, less-discussed effect: review text feeds relevance. Whichever service customers mention becomes part of the profile's topical picture. This cannot be manufactured, but adding "which service did you use?" to your request helps naturally.
Google Maps' content policy starts from one principle: "Contributions to Google Maps should reflect a genuine experience at a place or business. Fake engagement is not allowed and will be removed."
Concrete prohibitions follow from it.
| Action | Status | Official basis |
|---|---|---|
| Saying "please leave us a review" | ✅ Allowed | Encouraging genuine reviews without incentives is permitted |
| Sharing a review link or QR code | ✅ Allowed | "To encourage customers to leave reviews, you can share a review request link or QR code." |
| Replying to every review | ✅ Allowed | "Helpful and positive replies to reviews can show that you're responsive to your customers." |
| Offering a discount for a review | ❌ Prohibited | "Offer incentives – such as payment, discounts, free goods and/or services - in exchange for posting any review" |
| Buying reviews | ❌ Prohibited | "Reviews or ratings that have been paid for, directly or in kind." |
| Having employees write reviews | ❌ Prohibited | Conflict of interest — "current or former employment, a contractual or consultory relationship..." |
| Asking only satisfied customers | ❌ Prohibited | "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers." |
| Suppressing or deterring negative reviews | ❌ Prohibited | Same clause |
| Dictating the text of a review | ❌ Prohibited | An attempt to influence rating and content |
The permitted approach is stated officially too: you may encourage reviews that reflect a genuine experience without offering incentives and without attempting to influence the rating or the contents of the review.
The line fits in one sentence: "Please leave a review" — fine; "Leave a review, coffee's on us" — not fine.
This deserves its own section, because among prohibited practices it is the one most often presented as a clever idea.
The scheme runs like this: the customer first gets an internal survey — "rate us from 1 to 5". Those who answer 4 or 5 receive the Google review link; those who answer 1 to 3 are routed to a "complaint form" and never reach Google.
The result looks perfect: only high ratings on the profile. It is also a direct policy violation, stated plainly: "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers."
Beyond the risk, it does practical damage too:
The correct approach is the opposite: ask every customer, and manage negative reviews with replies. One negative review answered well is more persuasive than a profile with no negatives at all.
The secret to growing review count is not a campaign but a repeatable process. A business receiving four to six reviews a month, steadily, looks more natural and outperforms one that collected sixty once and went quiet.
Who do you ask? Everyone, without exception. Filtering is prohibited and harmful anyway.
When? As the service ends — when treatment finishes, when the bill arrives, when the job is handed over. A request sent a week later has a sharply lower response rate.
How? The sequence that works best:
Preparing the team is the most-forgotten part. The system only runs if the person in direct contact with the customer executes it — the receptionist, the technician, the salesperson. Giving them the wording in writing is enough. One red line: never reward staff by review count — that creates an indirect incentive mechanism and pushes people towards gating.
Google provides an official mechanism: "To encourage customers to leave reviews, you can share a review request link or QR code."
The link comes from your profile's management panel and opens the review window directly — the customer does not search for you, does not have to find the profile, just picks stars and writes. Removing each of those steps lifts the response rate substantially.
Practical notes:
Replying is both officially recommended — "Helpful and positive replies to reviews can show that you're responsive to your customers." — and, in practice, the highest-impact action available at the lowest cost.
The reason is simple: the reply is not read only by its author. A reply is written for future customers.
Replying to a positive review — short, personal, never templated:
Replying to a negative review takes a separate skill; that is the next section.
A negative review is not a disaster. The disaster is a negative review left unanswered.
1. Wait 24 hours, then write. An emotional reply always makes things worse. But a week's delay reads as indifference.
2. Accept the account; do not argue. "That never happened" pushes the reader onto the reviewer's side. Even when there was no fault, "We're sorry about the experience you had" holds a position without starting a fight.
3. Be specific. A generic reply ("We'll take your feedback on board") says nothing. "We discussed the morning-shift waiting times and changed the queue system" tells the reader something real.
4. Move the conversation off the channel. Offer a phone number or email. A long public argument benefits nobody.
5. Come back if it was resolved. Once the issue is fixed you can write again. Do not ask them to change the review — just say the matter was resolved. Some customers update it themselves.
The structure of a good reply: thanks → acknowledgement → concrete step → an offer to talk. Four sentences is enough.
Some reviews are not merely negative — they are policy violations. Telling the two apart matters, because only the second kind can be removed.
Cases with a chance of removal:
Cases with no chance: a negative review you dislike but which reflects a genuine experience. Slow service, prices felt to be high, an interaction that went badly — all legitimate reviews.
The reporting process: report the review from the menu beside it, choose the reason, and Google assesses it. Keep in mind:
If you face a coordinated fake-review attack (many similar negatives in a single day), document it differently from a routine report: dates, screenshots, reviewer profiles. That documentation matters in any follow-up.
Watching only the average rating is misleading. The metrics worth tracking:
| Metric | Why it matters |
|---|---|
| New reviews per month | The number that shows whether the system runs at all |
| Average rating | Useful as a trend, thin as a single figure |
| Competitors' review counts | Comparison is essential; an isolated number means nothing |
| Percentage of reviews replied to | Target: 100%. Entirely within your control |
| Response time | 24–48 hours is a healthy figure |
| Service names appearing in reviews | Feeds relevance and reveals weak areas |
| Themes across negative reviews | A repeated complaint signals an operational problem |
That last row is often the most valuable: reviews are free customer research. If five people complained about the same thing in three months, the problem is not the reviews — it is the service.
No, asking is allowed. What is prohibited is asking in exchange for an incentive, approaching only satisfied customers, and dictating the content of the review. Encouraging reviews that reflect a genuine experience causes no problem at all.
No. The policy lists payment, discounts, free goods and services explicitly: none of them may be offered in exchange for a review. "Small" makes no difference.
No. That counts as a conflict of interest — the policy names current and former employment and contractual or consultancy relationships directly.
Report it from the menu beside the review and select the type of violation. The outcome is not guaranteed and can take time. Most importantly: reply as well as reporting, because it may not be removed.
A single negative review has no serious effect. Google weighs review count and rating together — three negatives among two hundred reviews is normal and even makes the profile look more credible. The danger is not the negative itself but leaving it unanswered, and repeated complaints about the same thing.
There is no absolute number — the comparison is with competitors. A practical goal is to approach the review count of the top three in your field and maintain a steady monthly flow. Consistency is a stronger signal than the total.
Freshness matters to users: a most-recent review from two years ago raises the question "is this business still operating?" Which is why a continuous flow matters for both ranking and trust.
Yes, and it helps. But note that adding Review structured data to reviews shown on your own site has to follow Google's rules — there are restrictions around marking up reviews you collected about your own business on your own site. That topic is covered in on-site local SEO.
Check what you just read on your own site — free, no sign-up.
Shows a URL's status code and the full redirect chain step by step — 301s, 302s, loops and long chains become visible instantly.
Open toolTitle, meta description, canonical, robots directives, schema and heading structure — the whole on-page picture in one check.
Open toolSee live how your title and meta description will look in Google — desktop and mobile, with a length meter.
Open tool
The website side of local SEO: NAP consistency, the contact page, LocalBusiness structured data, the review ma...
Read
How Google ranks local results: the official definitions of the three factors, which of them you control, how...
Read
Setting up a Google Business Profile properly from scratch: eligibility, reclaiming ownership, verification me...
Read