Star Rating Plugins for Recipe and Affiliate Blogs
Reader ratings on blog posts are a different problem from business reviews, and the plugins that do them well are mostly free, mostly old, and mostly finished. This is a solved category, which makes the interesting questions the ones nobody asks: where star markup is still permitted on editorial content, how to stop the same person voting fifty times, and what a rating widget costs you on an archive page listing thirty posts.
This article covers those, and separates three things that get conflated constantly: reader ratings, business reviews and product reviews.
Verified August 2026. Structured data guidelines change; validate current behaviour with a live testing tool before relying on any markup claim.
Three things that are not the same
Reader ratings. Visitors rate your article. This is engagement signal, useful to you for knowing what lands, and mild social proof for the next reader. It is not a review of anything external, and on an ordinary article it will not produce a search snippet.
Business reviews. Customers rate your company. Valuable for conversion, and self-serving as structured data on your own site, which means no stars in search regardless of the plugin.
Product or item reviews. Someone rates a specific thing that is not you: a product you sell, a recipe you published, a course, a piece of software. This is the category where structured data still earns rich results, and the distinction is the entity being rated rather than who runs the site.
For a recipe blog, the useful consequence is specific: a rating on the recipe, handled by recipe-aware markup, is eligible. The same rating attached to a general article about the recipe is not. For an affiliate blog reviewing products, editorial review markup about the product is eligible; a reader rating of your article is not.
The 6 options compared
1. WP Recipe Maker ratings
For a recipe blog this is not one option among several, it is the correct answer, and general rating plugins are the wrong tool.
Recipe-specific plugins attach the rating to the recipe entity rather than to the post, which is what makes the structured data eligible in the first place. They also handle the rest of the recipe markup, ingredients, times, nutrition, in one coherent graph rather than leaving a rating plugin to bolt a rating onto a page that has no recipe schema for it to attach to. Using a general star rating plugin on a recipe site produces markup that is either ignored or actively conflicts with your recipe plugin’s output. The lesson generalises: where a purpose-built plugin exists for your content type, its ratings will be eligible in ways a general one cannot be.
- Rating attaches to: The recipe
- Stars possible: Yes
- Best for: Recipe blogs, without exception
- Watch out for: Do not add a second rating plugin
2. Rank Math review blocks
The right route for an affiliate or review blog, because the rating belongs to the product being reviewed rather than to your post.
An editorial review block lets you state that this article reviews a specific product and assigns it a score, which is eligible structured data because the reviewed entity is external to your site. It also lives inside the plugin already generating your page structured data, so there is one graph rather than two competing ones. That consolidation matters more than any feature difference: duplicate markup from an SEO plugin and a separate rating plugin is among the most common reasons a working rich result disappears without explanation. If your site reviews things, this is where the rating should live.
- Rating attaches to: The reviewed product
- Stars possible: Yes
- Best for: Affiliate and review publishers
- Watch out for: Running a second markup source alongside
3. kk Star Ratings
The long-standing free reader-rating plugin, and a good choice provided you want it for engagement rather than snippets.
It is small, it has been maintained for many years, and it does one thing without adding weight to your admin. Readers click stars, you see which posts resonate, and visitors get a mild signal that other people found the article useful. That is genuinely worth having on a content site. What it will not reliably deliver is stars in search results, because a reader rating of your own article is close to self-serving and articles are not among the eligible types anyway. Check whether its markup output can be disabled, and disable it if you are also running an SEO plugin, to keep one source of structured data per page.
- Rating attaches to: Your post
- Stars possible: Generally no
- Best for: Engagement signal, free
- Watch out for: Disable its markup if you run an SEO plugin
4. WP PostRatings
The veteran of the category, and the most configurable of the free reader-rating options.
Its appeal is control: rating scales, custom images, template functions for placing ratings anywhere in a theme, and options for how votes are counted and restricted. For a publisher who wants ratings integrated into a custom design rather than dropped in as a widget, that flexibility is the reason to choose it. It has also survived a very long time, which for a site nobody actively maintains is a real advantage. The interface is dated and the documentation assumes some comfort with template code. As with all reader ratings, treat it as an engagement feature and set your snippet expectations at zero.
- Rating attaches to: Your post
- Stars possible: Generally no
- Best for: Custom theme integration
- Watch out for: Template work expected
5. Yet Another Stars Rating
The option that distinguishes visitor votes from an author score, which is the most useful feature in this comparison.
Separating “the reviewer gave this 8 out of 10” from “readers rate this 4.2 stars” matters on a review blog, because those are different claims serving different purposes and only one of them can support review markup. Having both handled explicitly, rather than conflated into a single number, keeps your structured data honest and your presentation clearer. It offers multi-criteria ratings for scoring several attributes, ranking shortcodes, and reasonable control over where markup is emitted. As always, verify what it actually outputs against your SEO plugin so you are not producing two competing graphs on the same page.
- Rating attaches to: Author score or visitor votes
- Stars possible: For the reviewed item, on eligible pages
- Best for: Review blogs wanting both scores
- Watch out for: Coordinate markup with your SEO plugin
6. Comments as the rating system
The option that costs nothing and is often better, particularly for recipe sites.
A comment containing a real account of how something went is worth more than an anonymous click on a star, both to the next reader and to you. Recipe plugins already combine the two by attaching a rating to a comment, which solves vote integrity almost entirely, since leaving a comment is a much higher bar than clicking a star. For an affiliate blog, a handful of substantive comments does more for credibility than a rating widget averaging 4.7 from votes nobody can verify. Consider whether you want ratings because they are useful or because every site has them, and be honest about which.
- Rating attaches to: A comment, where supported
- Stars possible: Via the recipe or item plugin
- Best for: Genuine reader feedback
- Watch out for: Lower volume than one-click voting
Comparison table
| Option | Price | Rated entity | Stars possible | Best for |
|---|---|---|---|---|
| WP Recipe Maker | Free plus paid | The recipe | Yes | Recipe blogs |
| Rank Math review blocks | Free plus paid | The product | Yes | Affiliate publishers |
| kk Star Ratings | Free | Your post | No | Engagement signal |
| WP PostRatings | Free | Your post | No | Custom integration |
| Yet Another Stars Rating | Free plus paid | Either, separately | On eligible pages | Review blogs |
| Comments with ratings | Free | The item | Via item plugin | Genuine feedback |
Vote integrity and page speed
Two practical problems that decide whether a rating system is worth having, and neither appears on a feature grid.
- Cookie-based vote limits are trivially bypassed. Clearing cookies or opening a private window resets the restriction. It stops accidental double votes and nothing else, which is fine if you understand what you are getting.
- Address-based limits break on shared networks. Restricting by network address stops determined repeat voting but also blocks everybody in an office or on a mobile network after the first vote. Pick your failure mode deliberately.
- Requiring login is the only real protection, and on a public blog it will reduce voting to almost nothing. Reserve it for sites where readers already have accounts.
- Comment-attached ratings solve this best. Writing a comment is a high enough bar that manipulation stops being worthwhile, which is why recipe plugins adopted the pattern.
- Never display a rating from very few votes. An average of 5.0 from two votes is noise, and showing it invites suspicion rather than trust. Set a minimum before the widget appears.
- Assume the numbers are soft. Reader ratings are directional signal about which content resonates, not a measurement. Treat them accordingly and you will not be disappointed.
On performance, the specific problem is archive pages. A rating widget rendering on a listing of thirty posts means thirty widget instances, potentially thirty database lookups, and on some plugins additional scripts and requests. That is a measurable cost on the pages search engines crawl most and readers browse most. Display ratings on single posts only, and if you must show them on archives, confirm the plugin caches the values rather than querying per item.
Frequently asked questions
Will reader ratings give me stars in search?
On an ordinary article, no. Ratings on a recipe through a recipe plugin, or editorial review scores for an external product, are the cases that remain eligible.
Which plugin should a recipe blog use?
A recipe plugin with built-in ratings, so the rating attaches to the recipe entity. A general star rating plugin produces markup that is ignored or conflicts with your recipe schema.
How do I stop people voting repeatedly?
You mostly cannot without requiring login. Cookie limits stop accidents, address limits block shared networks, and comment-attached ratings raise the bar high enough to work.
Do rating widgets slow down my site?
On single posts, negligibly. On archive pages listing thirty items it is a real cost. Show ratings on single posts only unless the plugin caches archive values.
Can I run a rating plugin and an SEO plugin?
Yes, with only one emitting structured data. Two sources on a page is the most common reason a working rich result vanishes.
Is it worth showing an average from few votes?
No. Set a minimum vote count before the widget displays. A perfect score from two votes reads as unconvincing rather than impressive.
The verdict
For a recipe blog: your recipe plugin’s ratings, not a general one. The rating has to attach to the recipe for the markup to be eligible, and a second plugin only creates conflicts.
For an affiliate or review blog: your SEO plugin’s review blocks, which score the external product and keep structured data to a single source.
For engagement signal on ordinary articles: kk Star Ratings, free, with its markup disabled. Use it to learn what resonates, not to chase a snippet that will not appear.
Then set a minimum vote count and keep widgets off archive pages. A 5.0 from two votes persuades nobody, and thirty rating widgets on a listing page is a cost you pay on the pages that matter most.
