First-Party Review Collection vs Embedding Google Reviews
There are two ways to put reviews on a website, and they look almost identical to a visitor. One collects reviews on your own site, into your own database. The other displays reviews that live somewhere else, borrowed through an interface you do not control.
The difference only becomes visible on the day the embed stops working, and by then you have nothing. This article sets out who actually owns the review in each model, what happens when a borrowed feed goes away, which of the two can legitimately produce star ratings in search results, and why running both is usually the right answer.
Verified August 2026. Structured data policies and platform terms change; verify current rules before relying on any specific markup behaviour.
Who owns the review
A first-party review is yours. A customer submits it through a form on your site, it is stored in your database, and you can export it, display it however you like, move it to a new website and keep it forever. The relationship is between you and the customer, with nobody in the middle.
An embedded review is borrowed. It lives with the platform where the customer left it. Your site fetches and displays a copy. You cannot edit it, you cannot export it in any meaningful sense, and if access ends, so does the display.
That last scenario is not theoretical. Access to a platform’s reviews depends on their terms continuing to allow it, on the plugin vendor maintaining the integration, and on your own account remaining in good standing. Any of the three can change. When one does, a page that was full of social proof becomes an empty box, usually noticed weeks later.
The counterweight is credibility. A review on a major platform carries weight precisely because you could not have written it. A testimonial on your own site is easy to fake and everybody knows it, which is why first-party reviews are more valuable when they are visibly collected from verified customers.
The 6 options compared
1. Site Reviews
The strongest free first-party option, and the natural starting point if ownership is your priority.
Reviews are submitted through a form on your site and stored as content in your own database, which means they are yours to export, migrate and display as you choose. Moderation, verified-customer flags, replies and per-page assignment are all present, so a review can be attached to a specific service or product page rather than dumped into one testimonials list. Because the reviews are real submissions from identifiable customers rather than marketing copy, they are also the kind of content that can legitimately support structured data in the contexts where that is still permitted. The trade-off is effort: nobody hands you reviews, you have to ask, and the asking is the work.
- Ownership: Yours, in your database
- Survives a vendor change: Yes
- Best for: Building an asset you keep
- Watch out for: You have to collect them yourself
2. Trustindex
The most straightforward way to display reviews you already have elsewhere. $65, $125 and $349 a year, with unlimited widget views rather than metered display.
Unlimited views matters more than it sounds, because the main alternative pricing model in this category meters how many times your widget is seen, which puts a variable cost on your own traffic. A flat annual price removes that entirely. It aggregates reviews from the major platforms, offers a wide range of display layouts, and handles the technical side of fetching and caching. What you are buying is presentation of borrowed content: the reviews remain the platform’s, the display depends on this vendor continuing to maintain the integrations, and you have no export worth the name. Good at its job, and its job is display rather than ownership.
- Ownership: Borrowed from the platform
- Survives a vendor change: No
- Best for: Displaying existing platform reviews
- Watch out for: Nothing to export if it ends
3. Elfsight Reviews
Polished widgets on a metered model that deserves close attention. Free at 200 widget views a month, with Basic from around $6 a month for 5,000 views.
The design quality is genuinely good and the setup is the easiest here. The pricing model is the thing to understand: a view is counted every time the widget loads, so the cost is a function of your traffic. Two hundred views a month is a handful of visitors, and a moderately busy page can consume 5,000 views quickly. That makes it inexpensive for a small site and unpredictable for a growing one, in a way flat-priced alternatives are not. There is also a performance consideration, since the widget loads from an external service. Fine for a low-traffic site that values appearance; model the cost against your actual pageviews before committing anything larger.
- Ownership: Borrowed from the platform
- Survives a vendor change: No
- Best for: Small sites wanting polished widgets
- Watch out for: Metered views make cost track traffic
4. WP Customer Reviews
The long-standing free first-party option, and a reminder that this problem was solved a long time ago.
It collects reviews on your pages, stores them in your database and displays them with moderation, which is the whole requirement for many small businesses. Its longevity is a genuine feature: a plugin maintained across many years of WordPress releases is a safer dependency than a newer product, particularly for a site nobody watches closely. The interface is dated and the display options are plainer than the commercial widgets, so if presentation is a priority you will be adding styling yourself. Check its current structured data behaviour rather than assuming, since the rules about what markup may legitimately produce stars have tightened considerably and older plugins do not always reflect that.
- Ownership: Yours, in your database
- Survives a vendor change: Yes
- Best for: Simple free first-party collection
- Watch out for: Verify its current schema behaviour
5. Smash Balloon Reviews
The display option with the best engineering, from a vendor whose whole business is embedding third-party content well.
Its caching approach is the reason to prefer it over lighter embed plugins: reviews are fetched periodically and served from your own site rather than requiring a live external request on every pageview, which is better for both speed and reliability. If the external service is briefly unavailable, your page still shows reviews. The plugin is a known quantity with a long maintenance record and support that answers. What it cannot change is the fundamental position: these are still borrowed reviews, still dependent on continued platform access, and still not an asset you can take with you. It is the best version of the display approach rather than an escape from its limitations.
- Ownership: Borrowed from the platform
- Survives a vendor change: No
- Best for: Embedding with good caching and performance
- Watch out for: Still dependent on platform access
6. Running both, deliberately
The arrangement most businesses should actually adopt, once the trade-off is understood.
Embedded platform reviews provide credibility that a testimonial on your own site cannot, because a visitor knows you did not write them. First-party reviews provide an asset you own, a longer and more detailed body of content, and the material that can support structured data where it is permitted. Using both means the borrowed feed disappearing is an inconvenience rather than a loss. The practical arrangement is to show platform reviews prominently as proof, collect first-party reviews continuously in the background, and place each on the pages where it does most work. Ask for both in the same follow-up message, since a customer willing to write one is usually willing to write the other.
- Ownership: Mixed, by design
- Survives a vendor change: Partly, which is the point
- Best for: Almost every business
- Watch out for: Two systems to maintain
Comparison table
| Option | Model | Price | You own the data | Exportable |
|---|---|---|---|---|
| Site Reviews | First party | Free | Yes | Yes |
| Trustindex | Embed | $65/yr | No | No |
| Elfsight Reviews | Embed | From $6/mo | No | No |
| WP Customer Reviews | First party | Free | Yes | Yes |
| Smash Balloon Reviews | Embed | Paid tiers | No | No |
| Both together | Mixed | Free plus embed | Partly | Partly |
Which reviews may legitimately produce stars
This is where the two models diverge in a way that has real consequences, and where a great many plugins still behave as though nothing changed.
- Self-serving review markup does not earn stars. Reviews about your own business, placed on your own site, marked up as review data, are treated as self-serving and will not produce star ratings in search results. Plenty of plugins still emit it.
- Reviews of products you sell are different. Customer reviews of a specific product on that product page remain legitimate structured data, which is why store review plugins behave differently from business review plugins.
- Do not mark up embedded platform reviews. Reviews fetched from another site are that site’s content, and marking them up as your own review data is both ineffective and a misrepresentation.
- An aggregate rating needs individual reviews behind it. A summary score marked up without the underlying reviews visible on the page is exactly the pattern search engines look for and discount.
- Test before you trust any of it. Run the page through a structured data testing tool and see what is actually detected. Plugin marketing claims and validator output frequently disagree.
- Stars are not the only reason to have reviews. Reviews increase conversion on the page whether or not they produce a search snippet, and that value is unaffected by any of the above.
On duplicate content, the worry is usually overstated. Displaying platform reviews on your site alongside first-party ones is not a penalty risk in any meaningful sense; the reviews are short, attributed, and serve a clear purpose for the visitor. What matters more is that the page does not become a wall of repetitive text with nothing else on it.
Frequently asked questions
Should I collect reviews on my site or just embed them?
Both. Embedded platform reviews carry credibility you cannot manufacture; first-party reviews are an asset you keep if the embed ever stops working.
What happens if the review plugin stops working?
With embedded reviews, the display empties and you have nothing to migrate. With first-party reviews, the content is in your database and any other plugin can show it.
Will reviews on my site give me stars in search?
Not for reviews about your own business, which count as self-serving. Customer reviews of specific products on product pages remain legitimate structured data.
Is displaying platform reviews duplicate content?
Not in any way that causes practical harm. They are short, attributed and useful to visitors. Just do not build a page that is nothing but repeated review text.
What is the cheapest way to display existing reviews?
Trustindex from $65 a year with unlimited views, which avoids the metered-view model where your cost rises with your own traffic.
How do I get customers to leave first-party reviews?
Ask everybody, shortly after the work is done, with a direct link. Offer the platform option and your own form in the same message, and never filter who gets asked.
The verdict
Run both, and understand which one is an asset. Embedded platform reviews are credibility you are borrowing. First-party reviews are content you own, and only one of the two survives a plugin, an integration or an account going away.
For collection: Site Reviews, free, stored in your own database, with moderation and per-page assignment so a review lands where it does most work.
For display: Trustindex at $65 a year, whose unlimited views avoid a model that charges you more as your traffic grows, or Smash Balloon if caching and page speed are the priority.
And do not buy a review plugin for the stars. Reviews about your own business will not produce them, whatever the marketing says. Reviews raise conversion on the page regardless, which was always the better reason to collect them.
