WPRS Display Rating - WordPress Plugin

What the Rating Add-On Actually Solves

The core WP Rich Snippets plugin creates and displays review data: content type, rating, author, description, criteria, extra details, and the markup search engines may use for rich results. WPRS Display Rating adds a narrower layer: it outputs the rating in places where the standard review box may feel too heavy or out of place. Based on public descriptions, the add-on can display ratings by filtering content and excerpts inside the WordPress loop according to review type, and it also provides a shortcode for displaying the rating inside the loop.

In practice, this is useful when a site has more than a single review and instead runs an entire section of product cards, roundups, service directories, or post archives. Readers see more than just a title and an image - they also get a quick quality signal. For review-driven sites, that reduces friction: users can tell more quickly which post to open first, and the site owner gets a consistent visual language for ratings.

An important boundary: the add-on displays a rating, but it should not replace the review itself. If the page has no visible score, no review text, or no clear review subject, a single attractive star in a list does not solve the problem. More importantly, Google’s review guidelines require marked-up information to be available to users on the page. So Display Rating works best as a storefront for an existing rating, not as a way to hide review data in code.

Where a Rating Makes the Most Sense

The clearest use case is a review site where each post covers a specific product, service, recipe, app, place, or another item that can legitimately be rated. In a category archive, you can show a short star rating below the title, while the full post keeps the complete WP Rich Snippets review box with context and explanation. That way, users get a quick signal in the list and detailed reasoning after they click through.

Another scenario is a landing page with several internal content blocks. If the shortcode is available in your version, you can place it near a benefits section, comparison block, or solution area. The key is not to drop the same rating mechanically into every section. The rating should refer to a specific review subject, otherwise users will not know what exactly is being scored.

Where the Plugin May Be Unnecessary

This add-on is not worth installing on a site that does not use the WP Rich Snippets core plugin, or on a site that already relies on a modern full-featured review plugin with its own blocks, shortcodes, and JSON-LD. It can also be a questionable choice for projects that are only beginning to implement structured data: in that case, it is more useful to first build a correct review model, verify Google’s requirements, and make sure the theme does not break the base review box output.

If your goal is to collect user reviews, moderate them, prevent spam, or integrate with WooCommerce, WPRS Display Rating alone will not be enough. For those tasks, you need either other add-ons within the WP Rich Snippets ecosystem or a separate review system.

Who WPRS Display Rating Fits, and Who Should Take Another Route

The add-on is geared toward site owners who already publish rated content and already have WP Rich Snippets built into their editorial workflow. That could be a gadget review blog, a service rating site, a small product catalog, a curated list of local places, or an affiliate project where each post gets an editorial score. In that context, Display Rating solves a specific problem: how to show a compact rating outside the large review box.

A good candidate for installation is a site where the editor already understands which schema type is used in each post, where required fields are filled in, and how to validate the result. A poor candidate is a project where nobody is responsible for review quality and the rating is needed only as a decorative star. A visible rating without a transparent basis quickly undermines trust: visitors see a score, but they cannot tell where it came from.

A Good Fit

• WordPress review sites where WP Rich Snippets is already configured and used in posts.
• Editorial catalogs that need to show a rating in post lists, roundups, or category archives.
• Pages with custom layouts that need a compact rating display via shortcode, if it is available in the installed version.
• Projects where the owner is willing to validate structured data through Rich Results Test and Search Console.

May Not Be a Good Fit

• Sites without the base WP Rich Snippets plugin, because Display Rating is an add-on, not a standalone review system.
• Stores that need customer review collection, moderation, purchase verification, emails, and anti-spam tools.
• New projects where current support, modern editor blocks, and confirmed compatibility with the latest WordPress version matter more.
• Sites that already use another schema plugin and risk ending up with duplicate review markup.

Before installing it, answer one simple question: where does the rating you plan to display actually come from? If the answer is not tied to a real review on that same page, fix the content model first, not the star placement.

What to Check Before Installing It on WordPress

WPRS Display Rating has a dependency you cannot work around: it operates within the WP Rich Snippets context. So preparation includes more than standard backups - you also need to verify the main rich snippets system. If the base plugin already throws errors, fails to display the review box, or conflicts with the theme, the add-on will only make the problem more visible.

Public sources on WP Rich Snippets point to an older product with a mixed support history. That does not mean the add-on definitely will not work on your site, but it does mean testing should be stricter than usual. For a production project, the sensible path is this: start with a local copy or staging environment, then use a dedicated test post, then check the public-facing output, and only after that enable display on archives.

Minimum Checklist Before Uploading the ZIP File

• Create a backup of your files and database, or prepare a test copy of the site.
• Verify that the WP Rich Snippets core plugin is installed, active, and correctly displays a review on a test post.
• Open the list of active SEO and schema plugins so you do not end up with two independent sources of review markup on the same page.
• Check how the theme renders archives: full posts, excerpts, builder-based cards, or a custom template.
• Turn off aggressive optimization during testing: script combining, critical CSS, and HTML caching for the test page.
• Confirm that the user who will configure the plugin has access to plugin installation and settings.

Why Archives and Excerpts Matter

The Display Rating description is directly tied to output in content and excerpts inside the loop. In WordPress, the loop is the mechanism a theme uses to render post lists: the main blog page, category archives, search results, related posts, and some builder blocks. If the theme does not use the standard content or excerpt filters, the add-on may not appear where you expect it. That is not necessarily a plugin bug: the theme may be rendering its own cards directly, bypassing the standard path.

That is why it helps to open a category archive before installation and understand exactly what visitors see. If the cards include a normal post excerpt, the chances of correct output are higher. If the cards are assembled through a custom block, a builder template, or theme fields, you may need to use a shortcode or give up on displaying the rating in that location.

Installing the Add-On and Running an Initial Check

Installation works like any standard WordPress plugin: upload the ZIP file in the admin panel or use your hosting file manager if that is your normal process. WordPress documentation separately covers plugin uploads through Plugins, Add New, and Upload Plugin. But with an add-on, the order matters: first the base WP Rich Snippets plugin, then Display Rating.

Safe Installation Order

1. Open a test copy of the site or a prepared post that already contains a valid WP Rich Snippets review.
2. Go to Plugins and confirm that the base WP Rich Snippets plugin is active.
3. Upload the WPRS Display Rating ZIP file through Add New and Upload Plugin.
4. Click Install Now, then Activate.
5. Check whether the add-on appears in the list of active plugins and whether there are any PHP errors, a white screen, or a WordPress critical error message.
6. Open the test post on the front end and make sure the base review box has not disappeared.

Initial Validation Before Enabling Sitewide Output

Do not immediately enable automatic rating display across all archives. First, test one post and one category. If your version of the add-on has a dedicated settings page, look for it in the WP Rich Snippets menu or alongside the main plugin settings. Some third-party descriptions mention a Display Rating section in the Rich Snippets settings, but the exact menu label may differ in your build.

After activation, the main sign of success is that the site still shows the original review and does not introduce a new markup conflict. If the base review block disappears, an error shows up, or the rating begins displaying twice, disable the add-on and go back to checking theme compatibility, PHP version, and the main WP Rich Snippets plugin.

Configuring Rating Output in Lists, Excerpts, and via Shortcode

The real value of Display Rating appears after activation: you need to decide where the rating genuinely helps users. The add-on is described as supporting two directions: automatic output by filtering content and excerpts in the loop, and a shortcode for manual placement inside the loop. These are different methods, and there is no reason to mix them unless you have to.

Automatic Output in the Loop

Automatic mode is convenient for archives and post lists. If the theme outputs a standard excerpt, the rating may appear next to the summary text. If the theme outputs content inside the card, the add-on may process that content instead. In both cases, you should check the element order: title, image, excerpt, rating, and link button. The rating should not split a sentence, end up inside a button, or duplicate itself in every nested card.

Start with a single category that contains several posts with different review types. If the add-on filters ratings by review type, you need to confirm that it does not show a score where the review type is missing or does not match expectations. That protects the site from a situation where stars appear on ordinary articles that have no review data.

Output via Shortcode

A shortcode is useful when automatic output does not fit your setup - for example, when the theme assembles cards through a builder and you need to display the rating in a specific block. WordPress supports shortcodes as a safe way to insert dynamic output into content without putting PHP inside a post. But the exact Display Rating shortcode syntax is not confirmed by public documentation, so do not copy random variants from third-party articles. Look for it in the installed add-on settings, built-in help, or the original documentation that came with the archive.

If the shortcode is known, place it in a separate test post first, then in a Shortcode block in the editor or in a widget area. In the WordPress widget editor, you can place blocks in sidebars and other theme areas, but the final result depends on whether your theme supports that area and whether it preserves shortcode output.

Settings Worth Enabling Carefully

A short setup summary: enable one output method first, validate one page and one archive, and only then expand the scope. If you need the rating in multiple places, define a clear rule: where automatic mode is used, where shortcode is used, and where the rating is not shown at all.

How to Align the Visible Rating with Review Markup Requirements

A page rating is not just a visual detail. On review sites, it is often tied to structured data: Review, AggregateRating, ratingValue, ratingCount, or reviewCount. Google states that information marked up as a review or aggregate rating must be visible to users on the page, and the rating itself must refer to a specific item. That is why WPRS Display Rating is best configured through a logic of alignment: what is being rated, where users see the rating, and where they see the explanation.

If WP Rich Snippets generates the review markup, Display Rating can help make the score visible in the places where users scan the page. But it does not remove the need for validation. Rich results in search are never guaranteed even with correct markup: the search engine also considers page quality, compliance with guidelines, recrawl timing, and other signals.

What Must Match

• The item being rated in the page text and the item for which the markup is generated.
• The visible rating value and the value included in the structured data.
• The number of reviews or votes, if it is shown to users and used in the markup.
• The page type and the schema type that is eligible for review snippets under Google’s rules.
• The rating placement and its context: users should understand what the stars refer to.

How to Validate After Changing Settings

After enabling output, open the test post in incognito mode, inspect the raw HTML, and then check the URL in Rich Results Test. If the page is already in Search Console, watch the rich results reports and any issue messages. Do not try to solve every warning by simply displaying stars visually: some errors relate to the markup data itself, not to where the rating is placed.

Proper validation has two parts: users see a clear rating on the page, and the testing tool sees correct structured data without critical errors. One without the other does not produce a reliable result.

Practical Example: Showing the Rating in a Review Archive

Let’s walk through a specific task: you have a category called “Service Reviews,” each post contains a WP Rich Snippets review box, and the category page needs to show a short rating beneath each card title. The goal is to help readers compare posts quickly and click through to the full review without turning the archive into a cluttered table.

Goal

Get a clean star rating output in archive cards only for posts where the WP Rich Snippets review is filled out. Regular informational posts in the same theme should not receive an empty or random rating.

Preparation

• You have at least two test posts with correctly completed reviews and one post without a review for control testing.
• The WP Rich Snippets core plugin is active and displays the full review block on the post page.
• WPRS Display Rating is installed, but sitewide output has not yet been enabled for all sections.
• Page caching has been temporarily cleared or disabled for the test URL.

Steps

1. Open the add-on settings and find the mode responsible for rating output in content or excerpts inside the loop.
2. Enable output only for the location your theme archive actually uses. If you are unsure, start with the excerpt.
3. Save the settings using Save Changes or the equivalent button in your version.
4. Open the category archive in a new window and check three cards: two with reviews and one without.
5. If the rating appears on every post indiscriminately, go back to the review type settings or disable automatic mode for that archive.
6. Check one full post: the large review box should remain in place and should not be duplicated at the top of the content for no reason.

Expected Result

A compact rating appears in review post cards. It does not break the layout, does not overlap the title, does not appear on non-review content, and behaves consistently on both desktop and mobile widths. On the full post page, users see not only stars but also the context behind the score: description, criteria, reasoning, or another block created by WP Rich Snippets.

A Nuance That Often Gets in the Way

If the archive is built with a page builder or a non-standard template, the excerpt filter may not fire. In that case, do not rush into editing theme files. First, check whether the builder has a shortcode block, whether you can output the standard excerpt, or whether it makes more sense to keep the rating only on the full post page. Template edits are appropriate only through a child theme, and only if you know exactly which PHP template controls the card.

Compatibility with the Theme, Cache, and Other Schema Plugins

With rating plugins, the issue is rarely just the rating itself. More often, the conflict appears at the intersection: the theme renders a non-standard post list, the cache serves an older page version, the SEO plugin creates its own markup, and WP Rich Snippets adds another one. So after configuring Display Rating, you need to validate the environment, not just stop at “the stars appeared.”

Theme and Page Builder

A classic theme usually renders archives through the standard WordPress loop, so an add-on that filters content or excerpts has a better chance of working. Builders and modern block themes may use their own templates. In that case, the rating may fail to appear in the card, appear in an unexpected place, or display without styles. That is not a reason for heavy-handed edits, but for choosing a different output method: shortcode, a separate block, the standard excerpt, or no rating in that specific area.

Cache and Optimization

HTML cache may continue to show an old archive version even after you save the settings. CSS optimizers may hide the stars, change icon size, or break alignment. If the rating does not change after configuration, clear the page cache, CDN cache, and browser cache, then open the URL in a private window. If the rating appears correctly after disabling optimization, re-enable optimizations one by one and identify which one causes the conflict.

Duplicate Schema Markup

If Rank Math, Yoast SEO with schema extensions, Schema Pro, All In One Schema Rich Snippets, Review Schema, or another structured data plugin is active on the site at the same time, a single page may end up with multiple inconsistent review blocks. That is especially problematic when the visible rating is one thing but the code contains several different values. In that situation, choose one primary markup source for that page type. Display Rating can remain as a purely visual add-on to WP Rich Snippets, but it should not conflict with another system.

The safest model is simple: one page, one review subject, one primary source of review markup. Everything else should either avoid generating review schema or be used on different page types.