Google Reviews WordPress Plugin Alternative: Add a Google Reviews Widget or Slider to WordPress

This is the question behind most of the frustration in this category, and the answer is not in any plugin feature list. It is in Google documentation.

There are two different Google APIs that can hand over reviews, and they behave nothing alike.

The Places API is the one most plugins start with, because it works against any place on Google Maps and needs nothing from you except a billing-enabled API key. Its reference documentation describes the reviews field in one sentence: a list of reviews about this place, sorted by relevance, and a maximum of 5 reviews can be returned. There is no page token, no count parameter, and no sort option. Developers have been asking for pagination on this since 2015 and it has not arrived.

The Google Business Profile API is a different animal. Its reviews list endpoint documents that "the maximum pageSize is 50" and pages through the rest, so it can genuinely return everything you have. The catch is in the same document: "This operation is only valid if the specified location is verified", and it requires an OAuth scope of business.manage. In plain terms, it only works on a profile you own and have verified, and you have to log in and grant access.

Now the diagnostic that saves you an afternoon. If a plugin is showing you more than five Google reviews and it never asked you to sign in to your Google account, it is not reading them live from the Places API. It collected them once and is serving them from its own infrastructure. That is not necessarily a problem, and it is how most of the popular plugins work, but it changes what you are buying: you are paying a vendor to keep a copy of your reviews fresh, and the freshness schedule is a plan feature rather than a live lookup.

The cap gets all the attention and the sort order gets none, which is backwards, because the sort order is the part that actually embarrasses people.

Places returns reviews "sorted by relevance". Relevance is Google definition, not yours, and it is not the same as newest, or highest rated, or most useful to a buyer. A plugin reading from Places is showing five reviews that Google picked. If one of them is a three star from eighteen months ago about a delivery problem you fixed, that review is now on your homepage and there is no setting anywhere that removes it, because the plugin never received the other reviews in the first place.

This is the practical reason so many businesses end up on a paid tier. They did not want more reviews on the page. They wanted different ones, and control over selection is what the paid plan is really selling.

It is also worth being clear-eyed about what the five star rating does and does not do for a visitor. A rating is a fast credibility check: it tells somebody you are a real business that other people have used, and it does that in about half a second. What it cannot do is answer the specific objection in a buyer head at the moment they are hesitating, because nobody writes a Google review addressing whether your onboarding works for a team of twelve. That gap is not a volume problem and adding thirty more Google reviews does not close it. The difference between the two kinds of proof, and where each belongs on a page, is worked through on testimonial versus review.

Look at the three most installed Google review plugins in the WordPress repository and a pattern falls out immediately. Figures below are from each plugin own WordPress.org listing and each vendor own pricing page, checked August 2026. Confirm before you buy, because this category changes prices often.

Three independent vendors landing on exactly ten is not a coincidence and it is not a Google rule. Google gives you five through Places or effectively all of them through the Business Profile API. Ten is the number the market settled on for a free tier: generous enough to look like a real product on a small site, small enough that a business with sixty reviews feels the wall.

Trustindex is the one most people meet first, partly because it is enormous (their site says over 800,000 websites) and partly because the search term "trustindex google reviews plugin wordpress" is now its own query. Their paid ladder reads $65 a year for one domain, $125 a year for five domains, and $349 a year for unlimited domains, all listing unlimited widgets, unlimited views, and unlimited reviews, with a 30 day money back guarantee. For an agency running client sites, the per-domain axis is the one to model, not the headline price. We go through the rest of that comparison on the Trustindex alternative page.

If you are following a tutorial that tells you to enable "Places API" in the Google Cloud console and you cannot find it, the tutorial is out of date rather than wrong.

Google Maps Platform moved the legacy Places API, along with the JavaScript Places Service and the Android and iOS Places SDKs, to Legacy status on March 1, 2025. Google own legacy documentation defines what that means: "Legacy services are not available in new Cloud projects but remain fully supported for existing projects", and adds that while these services will be turned down in the coming years, "there is no date yet for when this will happen".

Two consequences that matter if you are setting this up in 2026. First, a Cloud project you create today cannot enable the old Places API at all, so any plugin whose instructions assume it will send you looking for a toggle that is not there. You want Places API (New). Second, an older site that has been running for years on a pre-2025 project keeps working, which is exactly why so many published guides still describe the old flow with confidence: they are accurate for the person who wrote them and useless for you.

Some plugins now ship both paths. Rich Showcase, for instance, records in its own changelog both a "New Google Places API integrated" release and a later option to use the old Places API for keys created before March 1, 2025. If you are choosing a plugin in 2026, checking that it supports Places API (New) is a more useful filter than counting layout templates.

The wider point for a WordPress site is that you have taken on a dependency with a moving floor. Google changed the API surface and the pricing model, plugin authors had to follow, and site owners found out when a widget went blank. An embed that does not read from a Google API at all has no exposure to that particular cycle, which is part of the same maintenance argument we make about WordPress testimonial plugins.

Scroll the feature comparison on almost any review plugin pricing page and you will find a filter that hides reviews under a chosen star rating, sitting in the paid column. Trustindex lists a negative reviews filter as a paid feature. It is a completely ordinary thing to sell and a lot of people buy the plan for it specifically.

It is worth knowing what the rule actually says before you switch it on, because the popular summary of it ("you cannot hide bad reviews") is wrong in a way that leads people to the wrong conclusion.

The FTC rule on consumer reviews and testimonials at 16 CFR 465.7 does not forbid a business from choosing which reviews to display. What it prohibits is materially misrepresenting, expressly or by implication, that the reviews shown represent most or all the reviews submitted, when reviews are being suppressed based on their ratings or their negative sentiment. The section also carves out suppression applied equally without regard to sentiment, for reasons like trade secrets, harassing or abusive content, personal information about others, discriminatory material, content that is clearly false or misleading, or a review the seller believes is counterfeit or wholly unrelated.

The uncomfortable structural detail is that a five-review Places widget is, by accident, the safest thing on this list. Nobody reads five relevance-sorted reviews as a complete archive. The moment you upgrade to the plan that lets you choose, you have acquired an editorial decision you did not have before. A curated wall of testimonials you collected sits in a cleaner position again, because a testimonial is understood to be selected marketing material, the way a case study is, rather than a representative sample of public opinion. The federal rules on all of this are collected in FTC testimonial rules, and the display-side detail is on using Google reviews on your website.

Everything above is about moving reviews that already exist. Plugins are display tools, and they are judged on layouts and load time because that is all the job contains. The part they cannot reach is upstream.

A Google review is a star rating and a short paragraph, written by somebody standing in a parking lot on their phone, about the thing that was most memorable in the moment. It is excellent for local credibility and it is not built to answer objections. No plugin can make it longer, no plugin can make it address your pricing page, and no plugin can turn it into video, because there is no video in a Google review to fetch. If your visitor needs to hear a customer like them describe what changed after they bought, that is a different artifact and it has to be requested.

Which is where most testimonial programs stall. The ask is uncomfortable, the customer means to reply and forgets, and chasing feels like begging. What moves the response rate is taking the work off them: an email asking would you mind writing us a testimonial hands a busy person a blank page and a request to compose marketing copy about you, while a link that opens three specific questions gets finished in about two minutes with no account to create. The mechanics are on collect testimonials, the questions that produce a usable answer are on testimonial form, and the wording of the request is in how to ask for a testimonial.

On placement inside WordPress, two things are worth doing deliberately. Keep the Google rating near your local trust signals, in the footer, on the contact page, near an address and a phone number, where a rating is the exact signal a visitor is checking for. Put the longer proof beside the button. A rotating slider is right for a tight strip on a long page, but on the page where somebody is deciding, a full Wall of Love does more work, because the sheer quantity is itself part of the argument. If you want the generic multi-source version rather than the WordPress-specific one, that is the review widget page, and the pure Google display case is the Google reviews widget page.

One performance note, since this is WordPress and everything ends up being a performance note. Review plugins commonly enqueue their stylesheet and script on every page of the site, including the pages with no reviews on them, so the cost is sitewide rather than local. The metric that usually breaks is not load time, it is layout shift, and the mechanism and fixes are in testimonial widgets and Core Web Vitals. If you build with a page builder, the builder adds constraints of its own, covered on the Elementor testimonial widget page and the Divi testimonial slider page.