Free Google Reviews Plugins That Work Without an API Key
Setting up a Google reviews plugin often stops at the same place: it asks for a Places API key, and getting one means creating a cloud project, enabling an API and attaching a billing account. For a plumber who wanted six reviews on a homepage, that is where the project ends.
Several plugins avoid the requirement entirely by fetching reviews through their own service. That is convenient and it introduces a different dependency. This article explains why the key requirement exists, which plugins need one and which do not, how stale the reviews get either way, and where the genuine risk in this category sits.
Verified August 2026. Platform terms and API pricing change; confirm current requirements before relying on any specific behaviour.
Why the API key question exists
Google review data is available through an official interface, and using it requires identifying yourself.
A key identifies who is making the request. That lets the provider apply quotas, enforce terms and bill usage. It is a normal arrangement for any commercial data interface and not an obstacle placed in your way specifically.
The billing account is the real deterrent. Free monthly usage allowances are generous enough that a small business displaying reviews would rarely pay anything, but attaching a card to a cloud account feels like a commitment, and the console is intimidating to somebody who has never seen one.
The official interface also limits what you get. Typically a small number of the most recent reviews per location rather than the full history, which surprises businesses expecting all two hundred of theirs to appear.
Plugins that do not ask for a key have not found a loophole. They are making the request themselves, with their own credentials, and passing the result to your site. That is why they charge, and it is also why your access depends on their service continuing to exist.
The 6 options compared
1. Trustindex
Handles the fetching through its own service, so no key is required from you. $65, $125 and $349 a year, unlimited views, with a limited free tier.
Setup is a matter of finding your business and connecting it, with no cloud console involved at any point. Reviews are then cached on your own site rather than fetched per visitor, which is better for performance and means a temporary problem at the source does not empty your review section. Because the vendor is doing the fetching under its own arrangements, the dependency is on them: their access, their terms, their continued operation. At $65 a year with no metering that is a reasonable trade for most small businesses, and the wide platform coverage means the same plugin handles your other review sources too.
- API key needed: No
- Reviews cached locally: Yes
- Best for: Businesses wanting setup without a cloud console
- Watch out for: Access depends on the vendor
2. Widgets for Google Reviews
A long-standing free option with a usable free tier, popular precisely because it removes the setup obstacle.
For a business that wants a handful of reviews displayed on one page without spending anything, this is frequently the shortest path. The free tier covers basic display, and paid tiers add layouts, multiple locations and more control over refresh behaviour. Check specifically how often reviews update on the free tier, because that is the usual limitation and stale reviews are the most common complaint about free plugins in this category. Also confirm whether it renders server-side or in the browser, since that decides whether your page caching helps and whether the widget arrives with the page or after it.
- API key needed: No
- Reviews cached locally: Check the tier
- Best for: Free display on a single page
- Watch out for: Refresh frequency on the free tier
3. Smash Balloon Reviews
The engineering-led option, where the connection is handled for you and the caching is the reason to choose it.
Reviews are fetched on a schedule and stored locally, so pages serve content that is already present rather than waiting on an external request, and an outage at the source leaves your reviews visible. This vendor’s whole product line is built on that pattern and it shows in the reliability. Connection is handled through their own authorisation flow rather than by making you generate credentials, which removes the obstacle without leaving you guessing about how the data arrives. It is a paid product and worth comparing against the flat-priced alternative on platform coverage, since this one focuses on the major sources rather than aiming for breadth.
- API key needed: No, handled by their flow
- Reviews cached locally: Yes, scheduled
- Best for: Reliability and page speed
- Watch out for: Fewer platforms than the widest option
4. Plugins that require your own key
The route with the fewest intermediaries, and the one to prefer if you are technically comfortable.
When the plugin uses your key, the data comes to your site under your own arrangement with the provider. Nothing sits between you and the source, so there is no vendor whose service ending removes your reviews, and no third party whose terms you are relying on. Free usage allowances mean a small business displaying reviews would rarely pay anything, and you can see exactly what is being requested. The costs are the console setup, which takes twenty minutes the first time and feels worse than it is, and remembering to restrict the key so it cannot be used from other sites. For a developer configuring a client site, this is usually the more durable choice.
- API key needed: Yes, yours
- Reviews cached locally: Usually, plugin dependent
- Best for: Developers and durable client setups
- Watch out for: Restrict the key to your domain
5. Elfsight Reviews
No key required, with the fetching and rendering both handled externally. Free at 200 widget views a month, Basic from around $6 a month for 5,000 views.
Setup is the fastest here and the widgets are the best looking, which is a real advantage for somebody who wants a presentable review section immediately. The architecture is the trade: the widget loads from their service on every pageview, which is why views can be metered and why your page caching cannot help. That also means two dependencies rather than one, since both the review data and the rendering come from outside your site. For a low-traffic business page it is a perfectly reasonable choice. For anything with meaningful traffic, the metering and the performance profile both argue against it.
- API key needed: No
- Reviews cached locally: No, rendered externally
- Best for: Fast setup on a low-traffic page
- Watch out for: Metered views and no caching benefit
6. Copying the reviews by hand
The option nobody sells and plenty of businesses should take.
Take your six best reviews, paste them into the page as text with the reviewer’s first name and a link to your public profile, and you are done. No key, no plugin, no service, no request, nothing that can break. The objection is that it does not update, which matters less than it sounds for a business with a stable set of good reviews: the ones that persuade are specific accounts of real jobs, and those do not go out of date monthly. Refresh the selection when you next edit the page. Be honest in the presentation, link to the full profile so visitors can see everything, and never quote selectively in a way that misrepresents your rating.
- API key needed: No
- Reviews cached locally: They are the page
- Best for: Small sites with a stable set of reviews
- Watch out for: Update it, and link to the real profile
Comparison table
| Option | Key required | Price | Cached locally | Dependency |
|---|---|---|---|---|
| Trustindex | No | $65/yr | Yes | The vendor |
| Widgets for Google Reviews | No | Free plus paid | Tier dependent | The vendor |
| Smash Balloon Reviews | No | Paid | Yes | The vendor |
| Bring your own key | Yes | Usually free usage | Usually | You and the provider |
| Elfsight Reviews | No | From about $6/mo | No | The vendor, per view |
| Manual copy | No | Free | Not applicable | None |
Staleness, refresh rates and terms
Two practical issues decide whether an embedded review display stays useful, and one risk deserves stating plainly.
- Nothing updates in real time, and that is correct. Every sensible plugin caches, because fetching per visitor is slow and wasteful. Daily or weekly refresh is normal and entirely adequate for reviews.
- Free tiers refresh least often. Weekly or monthly is common, which means a new five-star review may not appear for some time. Check this before assuming a free plugin is equivalent.
- Only a few reviews are usually available. The official interface returns a small selection rather than your full history, so a business with two hundred reviews will still display five. That is a limit of the source, not the plugin.
- Deleted reviews can linger. A cached copy of a review removed at the source may keep showing until the next refresh, which is worth knowing if somebody asks you to take one down.
- Avoid anything that scrapes. A plugin obtaining reviews by reading public pages rather than through an official interface is operating against platform terms, and that arrangement tends to break without warning.
- Do not filter the display to flatter. Showing only five-star reviews while your profile averages three is misleading regardless of how the data was obtained, and several plugins offer exactly that setting.
The general principle worth carrying away: your reviews live on the platform, and anything on your website is a copy whose continued existence depends on somebody else. Collecting first-party reviews alongside is the only way to own social proof outright, and it costs nothing.
Frequently asked questions
Why do some plugins need an API key and others do not?
Those that do not are making the request with their own credentials and passing the result to you. That is why they charge, and why your access depends on their service.
Does using my own key cost money?
Rarely for a small business displaying reviews, since free monthly allowances are generous. The obstacle is the billing account and console setup, not the bill.
Why does my plugin only show five reviews?
The official interface returns a small selection rather than your full history. That is a limit of the source, and no plugin can retrieve reviews it is not given.
How often do embedded reviews update?
Daily or weekly on paid tiers, sometimes monthly on free ones. Real-time updating does not and should not exist, because fetching per visitor is slow.
Are scraped review plugins risky?
Yes. Obtaining reviews by reading public pages rather than through an official interface breaks platform terms and tends to stop working without notice.
What is the most reliable long-term setup?
Your own key with a plugin that caches locally, or manual copies for a small site. Both remove the vendor from between you and your social proof.
The verdict
If the console is what is stopping you, Trustindex at $65 a year removes it entirely, caches reviews locally so pages stay fast, and covers your other review platforms with the same licence.
If you are technically comfortable, use your own key. Twenty minutes of console setup buys you an arrangement with no vendor in the middle, and the usage is almost certainly free at your volume.
For a small site with six good reviews, copy them into the page. Nothing to break, nothing to pay, nothing to refresh except your own judgement about which ones to show. Link to the full profile and keep it honest.
Avoid anything that scrapes, and collect first-party reviews alongside whatever you choose. Embedded reviews are always a copy of something you do not own, and the free plugins that let customers review you directly are the only way to fix that.
