Review Plugins With Valid Schema After Google’s Rich-Snippet Crackdowns
A great many WordPress review plugins still emit structured data that will never produce a star rating in search results. Not because the markup is malformed, but because it describes something search engines stopped rewarding: a business publishing reviews about itself.
The plugins are not necessarily lying. Their markup is technically valid, a testing tool will parse it, and the rich result simply never appears. This article explains which review markup still earns stars, why self-serving reviews are the rule most plugins ignore, and how to test what your site actually emits rather than trusting a feature list.
Verified August 2026. Structured data guidelines change; validate against current documentation and a live testing tool before relying on any behaviour described here.
What changed, and what still works
Two shifts matter, and confusing them is why so much advice in this area is wrong.
Self-serving review markup stopped producing stars. Reviews about your own organisation or a service you provide, marked up on your own website, are treated as self-serving and do not generate a rich result. This is the single most important rule and the one most review plugins were built before.
The list of eligible types narrowed. Review snippets are supported for a defined set of things: products, books, recipes, films, software applications, courses and a handful of others. A local business page is not on the list for its own reviews, whatever your plugin outputs.
What still works reliably is customer reviews of a product on that product page, ratings on a recipe, ratings on a course, and reviews of software or books. In each case the reviewed thing is distinct from the publisher, and the reviews come from people other than the seller.
The practical test is simple: is the entity being reviewed the same as the entity publishing the page? If yes, stars are off the table. That single question resolves nearly every case people find confusing.
The 6 options compared
1. Site Reviews
The free first-party option with the most control over what it emits, which is what matters here.
Because reviews are stored as content in your own database and assigned to specific pages, you can attach them to the right entity rather than dumping business reviews onto every page with markup attached. That distinction decides eligibility: reviews of a product on that product page are legitimate, and the same reviews of your company on your homepage are not. Its schema output is configurable, which means you can switch it off where it would be self-serving and keep it where it is valid. Whatever the settings say, run the page through a testing tool and see what is detected, because the gap between configuration and output is where problems live.
- Emits review schema: Yes, configurable
- Eligible for stars: On product and item pages
- Best for: Control over what gets marked up
- Watch out for: Self-serving markup if left on everywhere
2. WooCommerce product reviews
The case where review markup is unambiguously legitimate, and the reason store owners see stars while service businesses do not.
A customer review of a specific product, displayed on that product page, marked up as product review data, is exactly the pattern the guidelines contemplate. The reviewed entity is the product, the reviewers are customers rather than the seller, and the aggregate rating is backed by individual reviews visible on the page. Core WooCommerce handles this correctly without additional plugins, which is worth knowing before buying a review plugin to solve a problem you do not have. Where stores go wrong is bolting on a second review plugin that also emits markup, producing conflicting structured data on the same page and a rich result that disappears entirely.
- Emits review schema: Yes, as product reviews
- Eligible for stars: Yes
- Best for: Stores, using the built-in system
- Watch out for: Duplicate markup from a second plugin
3. Rank Math and SEO plugin review blocks
The route most publishers should take, because the SEO plugin already owns your structured data and adding a second source causes conflicts.
Modern SEO plugins include review and rating blocks intended for editorial content: a product review article, a software comparison, a book review. Used on genuine review content about something other than your own business, that markup is eligible and works. The reason to prefer this over a dedicated plugin is consolidation. Your SEO plugin is already emitting page-level structured data, and a separate review plugin adding its own creates duplicate or contradictory graphs that are hard to debug and frequently suppress the rich result altogether. One source of structured data per page is the rule worth following.
- Emits review schema: Yes, editorial reviews
- Eligible for stars: When reviewing something external
- Best for: Publishers reviewing products or software
- Watch out for: Do not run a second markup source
4. kk Star Ratings and reader rating plugins
Reader ratings on your own articles, which is a different thing again and where expectations need managing.
Letting readers rate a post is a legitimate engagement feature, and plugins that do it are lightweight and long-established. What they generally cannot do is produce stars in search results, because an article rated by its own readers on its own site is close to the self-serving case, and articles are not among the types eligible for review snippets in the first place. Some of these plugins still emit markup implying otherwise. Use them because reader ratings are useful signal for you and mild social proof for visitors, not because of a snippet that is not coming. On a recipe or a course, a purpose-built plugin for that content type is the correct route.
- Emits review schema: Often, and often ineligible
- Eligible for stars: Generally no
- Best for: Engagement signal on articles
- Watch out for: Markup that will never produce a result
5. Trustindex and embedded review widgets
Display tools for reviews that live elsewhere, where the schema answer is short. $65, $125 and $349 a year, unlimited views.
Reviews fetched from an external platform belong to that platform, and marking them up as your own review data is both ineffective and a misrepresentation of whose content it is. Any plugin offering to add structured data to embedded third-party reviews is offering something you should decline. There is also a mechanical issue: widgets that render reviews with JavaScript after page load may not present the content in a form that is reliably crawled at all. Use embedded widgets for what they genuinely deliver, which is credibility for human visitors, and leave the structured data question to first-party content on eligible page types.
- Emits review schema: Should not, for borrowed reviews
- Eligible for stars: No
- Best for: Human-facing credibility
- Watch out for: Any offer to mark up third-party reviews
6. No review markup at all
The correct configuration for most service businesses, and an unpopular thing to say in this category.
If you are a law firm, a clinic, an agency or a tradesperson, reviews of your business on your own site will not produce stars, and emitting markup that claims otherwise achieves nothing while adding a source of structured data errors to your reports. Turn it off. Display the reviews prominently for human visitors, where they raise conversion regardless of any snippet, and let your business structured data describe the business rather than its rating. Where you want stars in search results for a service business, the route is your profile on the review platforms themselves, which is a different project from anything a plugin does on your website.
- Emits review schema: None
- Eligible for stars: Not applicable
- Best for: Service businesses reviewing themselves
- Watch out for: Plugins that enable markup by default
Comparison table
| Option | Reviewed entity | Self-serving | Stars possible | Recommended use |
|---|---|---|---|---|
| Site Reviews | Configurable | Depends on page | On item pages | Collection, markup selectively |
| WooCommerce reviews | The product | No | Yes | Stores, built in |
| SEO plugin review blocks | External item | No | Yes | Editorial reviews |
| Reader rating plugins | Your article | Effectively yes | No | Engagement only |
| Embedded widgets | Platform content | Not yours | No | Human credibility |
| No markup | Not applicable | Not applicable | No | Most service businesses |
Testing before you trust it
Plugin feature lists and actual output disagree often enough that testing is not optional. Five checks catch nearly everything.
- Run the live URL through a rich results testing tool. Not the plugin preview, the actual page. Check what type is detected and whether the tool reports the page as eligible for a review snippet or merely as containing valid markup.
- Look for more than one source of markup. An SEO plugin, a review plugin and a theme all emitting structured data on the same page is the most common cause of a rich result vanishing. One source per page.
- Check the aggregate has reviews behind it. A summary rating marked up with no individual reviews visible on the page is the pattern most likely to be discounted, and several plugins do exactly this.
- Verify the reviewed item is not you. Open the markup and read the item being reviewed. If it is your own organisation, stars are not available regardless of what else is correct.
- Watch the enhancement reports in search console over weeks. Validation says the markup parses; the reports tell you whether search engines are acting on it, and that is the only answer that matters.
On aggregate ratings specifically: they are legitimate where they summarise real reviews of an eligible item that are present on the page. They are not a shortcut for displaying a number you calculated elsewhere. If the individual reviews are not on the page, do not mark up the average.
Frequently asked questions
Why does my review plugin not produce stars?
Almost always because the reviews are about your own business on your own site, which counts as self-serving. The markup is valid and the snippet is unavailable.
Which review markup still works?
Customer reviews of a product on its product page, and editorial reviews of something external such as software, a book or a course. The reviewed thing must not be you.
Can I mark up embedded Google reviews?
No. They are another platform’s content, marking them as yours misrepresents that, and it will not produce a rich result in any case.
Is an aggregate rating on its own allowed?
Only when it summarises reviews of an eligible item that are visible on the same page. An average with nothing behind it is the pattern most likely to be ignored.
Should I run a review plugin and an SEO plugin together?
Only with one of them emitting structured data. Two sources on the same page is the most common reason a working rich result suddenly disappears.
How do service businesses get stars in search?
Through their profiles on the review platforms themselves, not through markup on their own website. That is a different project from anything a plugin controls.
The verdict
Ask one question: is the reviewed thing the same as the site publishing the page? If yes, stars are unavailable and any markup claiming otherwise is decoration. That resolves nearly every case.
For stores, use the built-in WooCommerce reviews, which mark up the product rather than the seller and are eligible without any additional plugin.
For publishers reviewing external things, use your SEO plugin’s review blocks, so structured data has exactly one source on the page.
And for most service businesses, turn review markup off entirely. Display the reviews for human visitors, where they raise conversion regardless of snippets, and stop generating structured data errors chasing a rich result that is not available to you.
