A WordPress Agency’s Guide to Managing Client Reviews

Review collection is one of the easiest services a WordPress agency can productise: the client already has a site you maintain, the work is set-up-once, and the results are visible on a Google Business Profile the client checks anyway. The delivery choice that decides your margin is whether you resell a per-client monthly platform or deploy a flat-fee plugin inside the site you already run.

The part nobody writes about is the risk. Standardise one review process across thirty clients and you have also standardised whatever is wrong with it — including, in more agencies than you would think, review gating that the client asked for and nobody checked.

The economics of the two delivery models

Agency retainers in this space are tight and the labour maths is unforgiving. An agency owner running a productised model described it plainly: a $500 monthly management fee against an internal rate of $125 an hour means “we should only be spending a maximum of 4 hours per month on a client. If we spend more time than that, we’re wasting labor inventory.”

Two ways to deliver reviews inside that constraint:

• Resell a reputation platform. White-label dashboards exist and the pricing guides promise enormous margins. What they cost you is a per-client monthly fee that scales with your client list, a platform to administer, and a dependency you have to migrate if you ever change vendor.
• Deploy a self-hosted plugin per site. A flat annual licence on the client’s own WordPress install. No per-seat charge, nothing to administer centrally, and the data lives in the client’s database.

The second model wins for a WordPress agency for a reason beyond price: you are already in that site every month. Installing and configuring a plugin is work you are set up to do; running a separate SaaS account per client is a new operational surface. The full cost comparison is in Self-Hosted vs SaaS Review Tools.

One underrated advantage: a licence the client owns is easy to hand over when the relationship ends. A seat on your platform account is not, and a messy exit costs you referrals.

The compliance problem is yours too

This deserves the top of the page rather than a footnote, because it is the risk that scales with your client count.

Clients ask for gating by name, without knowing what it is. An SEO described the request in a forum: a local client “asked about software that intercepts bad reviews… collecting the review within the software itself and then only posting it if it’s five stars.” The replies were unanimous — that is review gating, it breaks Google’s policy against selectively soliciting positive reviews, and it is not a grey area.

Three things follow for an agency specifically:

1. Check the default settings of whatever you standardise on. Several WordPress review plugins ship a rating threshold, some with it enabled out of the box. Install it on thirty client sites and you have built thirty gated funnels without deciding to.
2. Have the conversation early. When a client asks for the “only send happy ones” flow, explain what it costs them — businesses caught gating have lost the overwhelming majority of their reviews. Saying no is easier before you have taken the money.
3. Never touch review removal as a service. An ORM-agency employee described their firm’s “biggest moneymaker by far” as a Google review removal service, white-labelled to other agencies, adding that the field is “definitely not the most ethical.” Only the platform hosting a review can remove one, and only when it breaks policy. Everything else on that market is either a flagging workflow the client could run themselves or something worse.

Review Gating: Why It Breaks Google and FTC Rules is the piece to send a client who wants to argue about it — it separates Google’s policy from the FTC’s 2024 rule and reconciles the penalty figures.

The operational questions you will actually hit

Who does the review request come from?

Not you, and not an address the customer will not recognise. An agency owner put the problem well: “the client probably isn’t going to want me to have access to their email. And then if not… do I send the message pretending to be the owner?” The clean answer from the same thread is to ask the client for an address on their own domain — reviews@ or hello@ — that you can configure. The email comes from the business, deliverability holds up, and you never impersonate anyone.

This is also an argument for a plugin that sends from the client’s own site rather than a third-party service sending on their behalf, which is a recurring complaint about hosted review tools.

How do you get access to the Business Profile?

Ask to be added as a manager on the client’s profile. Never share a login — it breaks your audit trail and it will eventually lock somebody out. The client stays the owner, you get the access you need, and removing you at the end is a single click, which clients find reassuring.

Who replies to the reviews?

Decide it in writing at onboarding. Agencies can draft replies for approval, or the client replies and you monitor for anything unanswered after 48 hours. What fails is the assumption that the other party is handling it — reviews sit unanswered for weeks and both sides blame each other at the quarterly review.

What do you report?

Per client, monthly, four numbers: new reviews this month, average rating over the last 90 days, response rate, and the top two recurring complaint themes. The last one is the only line that changes the client’s business, and it is the reason they renew.

Packaging it as a service

The setup is a fixed-scope job and the ongoing work is genuinely light, which suits either a small standalone package or an addition to an existing care plan.

A defensible scope looks like this:

• Setup: plugin installed and configured, branded review page, direct review link generated and tested on a phone, request timing set, private feedback route wired to a real inbox.
• Placement: the link added to the client’s email signature, receipts, thank-you page, and a printed card or QR if they have a counter.
• Monthly: the four-number report, a check that requests are still sending, and a nudge on anything unanswered.
• Explicitly out of scope: writing reviews, removing reviews, and any guarantee of a rating or a ranking.

Put that last line in the proposal. It sets the expectation before it becomes an argument, and it distinguishes you from the firms selling removal.

Standardise one stack, document it once

The margin in agency work comes from not re-deciding things. Pick one review plugin and use it everywhere, with a written default configuration: which trigger fires the request, the delay, follow-up cap, the private feedback destination, and the confirmed setting that no rating threshold is in play.

Two practical cautions from the WordPress side. Avoid stacking another heavy plugin onto sites you are already trying to keep fast — the plugin-bloat complaint is the most common criticism of agency-built WordPress sites. And check the review plugin’s support forum for recent fatal-error reports before you roll it out to thirty sites; an update that breaks the front end is a very expensive afternoon.

FAQ

Should I white-label a reputation platform or use a plugin per client?

If your clients are WordPress sites you already maintain and the requirement is review collection, a per-site plugin is cheaper, simpler to hand over, and keeps the data with the client. Platforms earn their price when clients need multi-channel inboxes, listings management and many locations.

Can I send review requests from my agency’s email?

Send from an address on the client’s domain that they provide. Customers should recognise the sender, and you should never write as the owner from an address that hides who is sending it.

A client wants only happy customers asked. What do I say?

That it is review gating, that Google prohibits it, and that enforcement has removed the majority of collected reviews from businesses caught doing it. Then offer the compliant version — everyone invited, private feedback available alongside — which produces more reviews anyway.

What should I charge?

Price the setup as a fixed job and the ongoing part against the hours it genuinely takes — for most agencies that is under an hour a month once it is running. The tool cost should be a rounding error rather than the thing eating your margin.

Can I promise a rating improvement?

No. You control the asking, not what customers write. Promise the process and report the numbers — and if the rating is not moving, the answer is usually operational rather than a review problem.

A service worth standing behind

The version of this service that survives is the boring one: one plugin, one documented configuration, requests from the client’s own domain, every customer invited, a private route for problems, four numbers reported monthly, and no promises about removal or rankings.

Reviews Wall is built to be that plugin — a self-hosted WordPress install at a flat annual licence per site the client owns, with no per-client platform fee and no rating threshold anywhere in the flow.

Sources

• Google Maps User-Generated-Content Policy — Prohibited & restricted content
• Federal Trade Commission — 16 CFR Part 465, Rule on the Use of Consumer Reviews and Testimonials
• Google Business Profile Help — Add and remove profile managers
• Sterling Sky — Review gating is against the Google Business Profile guidelines