Can You Pay for Google Reviews? The Actual Rules in 2026 (Google + FTC)

A tech finishes a condenser swap on an HVAC service call in a Houston subdivision, the customer is delighted, and he hands over a card the office printed: $25 off your next service call when you leave us a 5-star review. Or a vendor emails your shop offering “50 verified Google reviews, $399, drip-fed over 60 days.” Or your service manager puts a number on the whiteboard — four reviews per tech per week — and ties it to the bonus.

Every one of those is a policy violation. Two of them are potentially a federal one. And the answer you’ll get if you ask around is some version of “everybody does it, Google doesn’t care.” That’s not a rule, that’s a guess about enforcement, and it’s the same guess the contractors who lost their profiles were making. Enforcement is quiet and it is not reliable, but when it lands it can take the whole profile with it — which is a slower, more expensive problem than it sounds, as anyone who has been through a Google Business Profile suspension and reinstatement will tell you.

The real structure is this: Google’s review policy and the FTC’s review rule are two different documents with two different tests. Google bans incentives outright. The FTC bans incentives that are conditioned on sentiment. Google bans review gating in plain language. The FTC’s rule contains no express gating prohibition at all. Conflate the two and you’ll either take a risk you didn’t know you were taking, or refuse to do something that’s perfectly permitted.

This piece quotes both rulebooks verbatim, tells you which practices fall on which side of each line, flags the two genuine grey areas honestly instead of pretending they’re settled, and ends with the review-generation system that’s fully compliant with both — because that system still works, and it’s what we build for clients in our reviews and reputation work.

What’s in this guide

1. The short answer, in one paragraph
2. What Google’s policy actually says, word for word
3. What the FTC rule actually says, section by section
4. Review gating: the distinction most articles get wrong
5. Employees, family, and friends of the shop
6. Asking on the driveway, and review quotas for your crew
7. Allowed, not allowed, and genuinely grey
8. The compliant system that still works
9. Questions contractors actually ask

The short answer, in one paragraph

You cannot pay for Google reviews. You cannot offer a discount, a gift card, a free filter change, a raffle entry, or anything else of value in exchange for a review — not for a positive one, not for any one.

Google’s Maps user-generated content policy prohibits “reviews or ratings that have been paid for, directly or in kind,” and separately prohibits merchants from offering incentives “in exchange for posting any review.” On top of that, since October 21, 2024, the FTC’s Rule on the Use of Consumer Reviews and Testimonials (16 CFR Part 465) has made it a federal violation to provide compensation conditioned on a review expressing a particular sentiment, with civil penalties running to $53,088 per violation (subject to annual inflation adjustment).

What you can do is ask. Google says so explicitly, in a line most contractors have never read. We’ll get to it.

What Google’s policy actually says, word for word

Most contractors have never opened the source document, which is why so much of the advice floating around is somebody’s memory of somebody’s blog post. Google’s Prohibited and Restricted Content policy for Maps is short, public, and written in plain English. Here are the clauses that govern reviews, quoted exactly.

Under fake engagement, not allowed:

Reviews or ratings that have been paid for, directly or in kind.
Google — Prohibited & Restricted Content, Maps user-generated content policy

“In kind” is the part people miss. A gift card is in kind. A free service call is in kind. A $20 bill folded into the invoice is not more of a violation than a free air filter — they are the same violation.

Also under fake engagement:

Content that has been posted from multiple accounts by or at the request of one person.
Google — Prohibited & Restricted Content

That’s the clause that catches the owner who posts from his own account, his wife’s account, and the shop’s tablet.

Then there’s a separate section aimed directly at business owners, headed rating manipulation. Merchants must not:

Offer incentives – such as payment, discounts, free goods and/or services – in exchange for posting any review or revision or removal of a negative review.
Google — Prohibited & Restricted Content, rating manipulation

Read the tail of that sentence again: or revision or removal of a negative review. Offering a customer a refund to take down a one-star review is the same prohibited act as paying for a five-star one. That comes up constantly, and it’s the subject of its own guide — what to do when someone threatens a bad review unless you refund them.

And the line that settles the gating argument, which we’ll come back to in a moment:

Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers.
Google — Prohibited & Restricted Content, rating manipulation

What the FTC rule actually says, section by section

The Federal Trade Commission announced its final rule banning fake reviews and testimonials in August 2024. It took effect October 21, 2024. It is a rule, not a guideline, which matters: violating a rule exposes you to civil penalties, where the older Endorsement Guides mostly exposed you to an enforcement action.

Most contractors assume this is a problem for Amazon sellers. It isn’t. The rule applies to any business that solicits or uses consumer reviews, and several of its sections describe things happening in trade shops right now.

16 CFR Part 465 — the sections that reach a trades business

Section	What it prohibits	How it shows up in a trade shop
§465.2	Creating, selling, buying or disseminating fake or false reviews — from people who don’t exist or never used the service. The FTC explicitly names AI-generated fake reviews.	Buying a review package from a vendor. Writing reviews for jobs that never happened. Generating review text with an AI tool and posting it under a customer’s name.
§465.4	“Providing compensation or other incentives conditioned on the writing of consumer reviews expressing a particular sentiment.” Applies to third-party platforms and your own website.	The $25-off-for-a-5-star card. A raffle entry for “positive feedback.” A bonus to a tech for reviews that mention his name favourably.
§465.5	Undisclosed insider reviews. Reviews by officers, managers, employees or their immediate relatives must “clearly and conspicuously disclose the giver’s material connection to the business.”	Your install crew reviewing the company. Your brother-in-law reviewing the company. Both without saying so.
§465.6	Company-controlled review websites misrepresented as providing “independent reviews or opinions.”	A “best plumbers in Austin” site your marketing company quietly owns, where you happen to be number one.
§465.7	Review suppression using “unfounded or groundless legal threats, physical threats, intimidation” or false accusations.	The reflexive “get my lawyer to send them a scary letter” move, when there’s no real claim behind it.
§465.8	Fake social media indicators — bought followers, purchased views.	Buying followers for the company page to look established.

Note what §465.4 turns on: the conditioning on sentiment. The violation isn’t giving someone something. It’s giving them something because the review says what you wanted it to say. That single word — “conditioned” — is the difference between the two rulebooks, and it’s the thing nearly every competing article gets wrong.

Review gating: the distinction most articles get wrong

Review gating is the practice of asking customers how satisfied they are first, then routing the happy ones to your Google profile and the unhappy ones to a private feedback form. Dozens of software products sold to contractors do exactly this, some of them very expensive, some of them still marketing it as a feature.

Here’s the honest verdict, and it has two halves.

Under Google’s policy, gating is a clear violation. Not arguable, not a grey area. The rating manipulation section prohibits merchants from acting to “discourage or prohibit negative reviews, or selectively solicit positive reviews from customers.” Filtering by satisfaction before you send the Google link is, by definition, selectively soliciting positive reviews. That’s the whole design of the feature.

Under the FTC Rule, the picture is different. The Rule as finalised contains no express prohibition on gating. Legal analysis of the final rule — including the National Law Review’s fifteen-point breakdown for advertisers — notes there is “no specific prohibition” on the practice in the Rule itself, though it “could violate the FTC Act” under the Endorsement Guides, because a curated review set can misrepresent what customers actually experienced.

So the accurate statement is: gating is a Google policy violation, and an FTC Act risk, but not a per-se violation of the Rule. Most contractor-marketing content flattens that into “gating is illegal,” which is overstated, or into “the FTC didn’t ban gating so you’re fine,” which is worse. Neither of those helps you make a decision.

The practical answer doesn’t change much, because Google’s policy alone is enough reason to stop. But knowing which rulebook you’re violating tells you what the consequence looks like: a Google violation costs you reviews and potentially your profile; an FTC Act problem costs you a lot more and involves lawyers.

Two rulebooks, two different lines

Six review practices, ordered by how much they interfere with what the customer writes — and where each rulebook’s prohibition actually starts.

Employees, family, and friends of the shop

This is the most common violation in the trades, and almost nobody who does it thinks of it as cheating. A new shop opens in Lubbock with zero reviews, the owner asks the five guys on payroll to leave one, and the profile has a foundation by Friday.

Google’s conflict-of-interest clause covers it directly. Not allowed:

Content that is based on a conflict of interest. A conflict of interest may include current or former employment, a contractual or consultory relationship.
Google — Prohibited & Restricted Content, conflict of interest

Note “former employment” and “contractual relationship.” Your subcontractors are covered. So is the tech who quit in March. So is your web developer.

The FTC reaches the same conduct from a different angle. §465.5 doesn’t ban insider reviews outright — it bans undisclosed ones. An employee review that “clearly and conspicuously” discloses the material connection isn’t a Rule violation. It is still a Google violation, and it’s also worthless to you, because a review that opens “I work here and…” persuades nobody.

Family is the part people argue about. The FTC’s language covers officers, managers, employees and their immediate relatives. Your spouse leaving a glowing review without disclosure is squarely within that. A cousin who genuinely hired you and paid an invoice is a different case — but if you’re relying on the distance of the relationship to make it fine, you already know the answer.

Asking on the driveway, and review quotas for your crew

Two lines in Google’s policy get almost no coverage anywhere, and both describe standard practice in the trades.

Asking while you’re still on the job

Google’s guidance for merchants states that they:

should not require or pressure users to leave ratings or write reviews while on the premises.
Google — Prohibited & Restricted Content, rating manipulation

Read it precisely, because the operative words are require or pressure. A tech handing over a card with a QR code and saying “if we did right by you today, a review helps us a lot” is not requiring or pressuring anybody. A tech standing in the kitchen with his phone out, watching the customer type, waiting for the stars to land — that’s pressure, and it’s exactly the scenario the clause was written for.

The practical version we give clients: ask on site, collect the review off site. Hand over the card, send the follow-up text a few hours later, and leave.

Review quotas on the whiteboard

Google’s policy also prohibits “merchants requesting that staff solicit a certain number of reviews” and “merchants requesting that staff solicit reviews that include specific content.”

That’s the four-per-tech-per-week board. That’s also the script that tells techs to ask customers to mention the city, or the brand, or the tech’s name. A lot of the review-generation advice sold to contractors is precisely this, and it’s precisely what the clause names.

Most contractors stop at “don’t buy reviews” and assume they’re compliant. That is not analysis. The quota on the whiteboard and the script in the tech’s pocket are separate prohibitions from the one about money, and they’re the ones a well-run shop is most likely to be breaking without knowing it.

Allowed, not allowed, and genuinely grey

Here is every practice we get asked about, sorted, with the governing rule named for each so you can check it yourself rather than taking our word for it.

Review practices in the trades — verdict and governing rule

Practice	Verdict	Governing rule
Asking every customer for a review, no incentive, no filtering	Allowed	Google expressly permits soliciting content that “does represent a genuine experience, without offering incentives.”
Sending a follow-up text with a direct review link a day after the job	Allowed	Same clause. Convenience isn’t an incentive. Nothing in Part 465 touches it.
Handing over a card with a QR code on the driveway	Allowed	Permitted as long as you don’t “require or pressure users to leave ratings or write reviews while on the premises.”
Responding to every review, good and bad	Allowed	Encouraged. No rule against it, and 89% of consumers expect it (BrightLocal 2026).
$25 off, a gift card, or a raffle entry for a 5-star review	Not allowed	Google: incentives “in exchange for posting any review.” FTC §465.4: compensation “conditioned on … expressing a particular sentiment.”
A small gift to everyone who reviews, whatever they write	Not allowed	Google: “paid for, directly or in kind.” Clear of FTC §465.4 — no sentiment condition — but the Google violation stands on its own.
Buying a review package from a vendor	Not allowed	Google fake engagement. FTC §465.2 — buying reviews from people who never used the service. Penalties apply.
Employees or their immediate family reviewing the company	Not allowed	Google conflict of interest: “current or former employment, a contractual or consultory relationship.” FTC §465.5 if the connection isn’t disclosed.
Review quotas for techs, or scripts specifying what the review should say	Not allowed	Google names both: “staff solicit a certain number of reviews” and “reviews that include specific content.”
Offering a refund in exchange for taking down a one-star review	Not allowed	Google: incentives for “revision or removal of a negative review.” Also brushes FTC §465.7 territory depending on how it’s put.
Gating — survey first, route the happy ones to Google	Google violation	Google: “selectively solicit positive reviews from customers.” No express prohibition in the FTC Rule; may still violate the FTC Act under the Endorsement Guides.
Asking only the customers who seemed pleased, informally	Grey	The same “selectively solicit” clause reaches it in principle; enforcement against informal judgement calls is not something Google has documented. Softer facts, same rule.
Paying a marketing agency a bonus tied to review count	Grey	Not a direct violation as written — but it creates the incentive for the agency to violate on your behalf, and the profile that gets penalised is yours.
Running a monthly prize draw for all customers, reviewers or not	Grey	If entry genuinely has nothing to do with reviewing, no incentive is being offered for a review. If the review link and the draw share a landing page, a regulator may read it differently.

The compliant system that still works

Everything above is prohibition. Here’s the permission, quoted, because it’s the clause that tells you what to build. Google says merchants may:

Solicit or encourage the posting of content that does represent a genuine experience, without offering incentives to do so or attempting to influence the rating or the contents of the review.
Google — Prohibited & Restricted Content

Three conditions, and they’re the whole design brief: genuine experience, no incentive, no influence on rating or content. Inside those three lines you can be as systematic and as relentless as you like. Nothing says you can only ask once. Nothing says you can’t make it easy.

Ask everyone, every time, with no filter

The compliant system is also the one that performs best under Google’s ranking signals, which is a happy accident rather than a coincidence. Whitespark’s 2026 Local Search Ranking Factors survey of 47 practitioners puts review signals at roughly 17% of local pack weight — a meaningful slice of what any local SEO program is working on, and the report notes that “for 2026, the biggest changes we’re seeing are an increased importance of review signals and behavioural signals.”

More usefully, it breaks out which review signals: high numerical rating ranks 6th overall, quantity of native Google reviews with text 9th, recency 11th, and — the one that argues directly against any burst tactic — “sustained influx of reviews over time (rather than bursts)” at 14th. A filtered system produces bursts. An unfiltered one produces a steady line.

Make the ask land at the right moment

The moment is when the customer is most satisfied, which for most trades is the hour the work finishes, not three weeks later when the invoice arrives. Asking at the right moment is not gating — you’re asking everyone, you’re just asking well.

BrightLocal’s 2026 Local Consumer Review Survey of 1,002 US adults found 74% of consumers want reviews from the last three months, 32% want the past two weeks, and 18% only trust reviews under a week old. Recency isn’t only a ranking factor; it’s what the customer reading your profile is checking.

Respond to all of them, including the bad ones

The same survey found 89% of consumers expect owners to respond to reviews, 80% are more likely to use a business that responds to all of them, and — the part that should change how your responses get written — 50% are put off by templated or generic responses. Nineteen percent expect a response the same day, and 81% within a week.

Responding to a negative review is fully permitted, costs nothing, and does more for the reader’s impression than the review itself does damage. What you can’t do is offer them something to take it down. If a review is genuinely fake or violates policy, there’s a proper route — we walk through it in how to remove a fake Google review, and what to do when Google says no.

Questions contractors actually ask

What to do with this on Monday

Open your review software and look for a satisfaction question that sits between the customer and the Google link. If it’s there, switch it off. That’s the change with the biggest gap between how easy it is and how much risk it removes.

Then look at whatever you’re currently offering. Cards, discounts, raffle entries, the tech bonus tied to review count — all of it goes. Not because enforcement is certain, but because the entire asset you’re building is a public record of what your customers think, and its value comes from being true. A profile built on incentives is a liability that looks like an asset until the day it doesn’t.

Then build the boring version: ask everyone, ask at completion, follow up once, respond to all of them in your own words. It converts worse per ask than the $25 card. It also produces the sustained, unfiltered, recent flow that both Google’s ranking signals and your next customer are actually looking for — whether you’re working Houston, Austin, or a Hill Country territory where twelve reviews is a market-leading position.

And if a vendor is still selling you gating in 2026, ask them to show you the clause in Google’s policy that permits it. There isn’t one.