WPRS Compare - WordPress Plugin

A Guide to Setting Up WPRS Compare for Comparison Tables in WordPress

WPRS Compare is useful not as a standalone table builder, but as an extension to the WP Rich Snippets ecosystem. It helps you display product or service comparisons in a table format when your site already uses reviews, ratings, and structured data. In this guide, we will cover how to approach installation, where to find the related WP Rich Snippets settings, how to prepare comparison data, how to insert the table with a shortcode, and how to verify the result on the page.

This guide is written for a review site owner, an affiliate content editor, a webmaster, and a developer maintaining an older project built on WP Rich Snippets. It does not cover purchasing, licensing, or workaround methods for obtaining the plugin. The goal here is different - to safely determine whether the add-on fits your page, which dependencies to check in advance, and what to do if the comparison table does not appear.

There is very little public documentation specifically for WPRS Compare, so some of the recommendations here rely on confirmed information about WP Rich Snippets, WordPress shortcodes, Google's structured data, and standard safe WordPress practices. Where the exact add-on screen could not be verified, I state the steps conditionally: check the menu item, tab, or shortcode available in your installed version.

What the Comparison Add-On Is Meant to Do

The main purpose of WPRS Compare is to give the reader more than a single review box. It provides a quick way to compare several items side by side. This is useful on pages where the visitor already understands the product or service category, but still cannot see the difference between the available options: one service is cheaper, another is stronger on features, a third is better for beginners, and a fourth stands out for support.

In a standard article, comparison often falls apart into long paragraphs. The reader has to keep the price, rating, pros, cons, key features, and review link for each option in mind. A table solves that problem: rows become criteria, columns become the compared options, and the final choice becomes visible without rereading the entire page.

What matters for WPRS Compare is that the add-on is tied to WP Rich Snippets. That means it should be treated not as a universal table editor for any kind of data, but as a tool for sites where the comparison is built around reviews, ratings, descriptions, and other fields already used in rich snippet markup. If you simply need a schedule table, a price list, or a CSV catalog, a dedicated table plugin will usually be the better choice.

Where This Format Works Best

A comparison table works especially well on decision pages: the best tools for a specific job, a roundup of WordPress plugins, a hosting comparison, an email marketing services comparison, software selection, or an article comparing plans or feature sets. In every case, the reader is not looking for a nice-looking block. They are trying to reduce uncertainty: what to choose, and why.

• A review blog can combine several separate review posts into one decision page.
• An affiliate site can show differences in rating, core features, and primary call to action.
• A service directory can compare offers using a few clear criteria.
• A content project can use the table as navigation to deeper reviews.

If the page is about a single product and does not compare it to alternatives, WPRS Compare may be unnecessary. In that case, a standard WP Rich Snippets block, a pros and cons list, and a clean call to action are often enough.

How WPRS Compare Fits Into WP Rich Snippets

WPRS Compare is an add-on, so it should not be evaluated separately from the main plugin. The base WP Rich Snippets plugin handles the review metaboxes, the choice of structured data type, review box output, and fields such as description, criteria, author, image, link, and extra details. The Compare add-on extends that system with comparison output.

That dependency determines the correct workflow. First, make sure the main WP Rich Snippets plugin is installed, activated, and correctly displaying data on a standard review page. Only then does it make sense to enable WPRS Compare and build a table. Otherwise, the add-on may be technically active, but the table will remain empty because it has nothing to compare.

What the Sources Confirm, and What You Need to Verify Yourself

Publicly available sources confirm a few important things: WPRS Compare belongs to the WP Rich Snippets ecosystem, works as an add-on, is intended for comparison tables, and uses a shortcode-based output flow. It is also confirmed that WP Rich Snippets works through settings, post editor metaboxes, and a set of add-ons.

What could not be reliably confirmed is the full list of settings specific to the Compare add-on: the names of all fields, the exact shortcode syntax, the limit on how many items can be compared, and current compatibility with modern versions of WordPress. For that reason, this guide will not invent a shortcode. The practical rule is this: use the exact shortcode and parameters from your installed plugin version, and use this article as a map for setup, validation, and troubleshooting.

Why This Is Not a Replacement for a Modern Schema Plugin

In public reviews, WP Rich Snippets is often described as a capable but aging product. That does not mean WPRS Compare is automatically broken on your site. It does mean you should check the environment, PHP compatibility, theme behavior, caching, markup, and editor behavior more carefully before rolling it out. For a new project with no existing dependency on WP Rich Snippets, it may be more practical to choose a modern, actively maintained tool instead.

The practical takeaway: WPRS Compare makes the most sense on a site that is already built around WP Rich Snippets and just needs a careful way to add comparisons to existing reviews, not to move the entire project to a new schema system.

Who This Format Is For, and Who Should Choose Something Else

The comparison add-on is not useful for every site. It works best when your data has a repeatable structure: several products, the same criteria, ratings, short verdicts, and links to detailed reviews. If every piece of content is unique and the criteria keep changing, the table quickly turns into manual editorial labor.

A Good Fit

WPRS Compare is worth considering if your site already has a series of reviews with similar fields. For example, you may rate plugins by ease of use, speed, settings, support, and price, then want to show a shortlist on one page. In that scenario, the comparison does not duplicate the content. It turns scattered reviews into a navigational layer.

• You already have WP Rich Snippets installed and in use.
• Your content uses identical or closely aligned evaluation criteria.
• The user needs to compare several options before opening a full review.
• You are willing to validate structured data not only visually, but also with Google tools.
• Your theme displays wide tables properly on both desktop and mobile screens.

When It May Not Be the Best Choice

If you need a modern table with filters, CSV import, advanced sorting, large datasets, or live WooCommerce product comparison, WPRS Compare may not be the right tool. It sits closer to the review and schema ecosystem than to full-scale table builders.

You should also be more careful on sites with heavy caching, JavaScript optimization, or non-standard page builders. The shortcode may render in an unexpected place, and the table styles may conflict with the theme's global typography.

What to Check Before Installing on a Live Site

Preparation matters because the WP Rich Snippets ecosystem is older and the add-on depends on the main plugin. Do not start on a live page that is already receiving search traffic. First test the plugin on a site copy, a staging environment, or at least a non-public test post.

Basic WordPress Environment

Make sure you have administrator access, the ability to install ZIP plugins, and permission to disable conflicting extensions. If the site is managed by a client, hosting provider, or agency, align on a maintenance window in advance. A comparison table can affect more than the content itself - it may also affect styles, caching, minification, schema markup, and editor behavior.

• Create a backup of both files and database before installation.
• Make sure the main WP Rich Snippets plugin is already active and available in the admin panel.
• Open one existing review post and confirm that the Schema metabox is available.
• Check that a normal review box appears correctly on the front end of the site.
• Temporarily disable aggressive CSS/JS optimization if it breaks the appearance of tables.

Data for the Future Comparison

Comparisons work poorly when the data is incomplete. Imagine two products have a rating, price, and pros, while a third only has a description filled in. The table will end up with empty gaps, and the reader will stop trusting the block. Before enabling WPRS Compare, bring your review posts into a consistent structure.

Prepare a list of criteria that actually help people choose: overall score, intended use, strongest point, limitation, target audience, license type, review link, and action button. Do not try to surface everything available in the post. A comparison table should be more compact than a full review.

The Risk of Outdated Markup

Structured data does not guarantee enhanced search presentation. Google uses structured data to understand the page and may show rich results only when its rules, content quality requirements, and supported markup types all line up. So after configuring WPRS Compare, check not only how the table looks, but also whether the data validates correctly in Rich Results Test or Search Console reports.

Installation and Initial Activation Without Unnecessary Risk

Installing the add-on in WordPress is usually done through a ZIP file. The exact source of the archive depends on your legitimate distribution, but the process in the admin panel is the same: open the plugin upload screen, upload the ZIP, install it, and activate it. It is important not to mix that up with purchase or license setup. What matters here is the installation file you already have.

Recommended Order of Actions

1. Open the WordPress admin panel using an administrator account.
2. Go to Plugins - Add New - Upload Plugin.
3. Upload the ZIP file for the main WP Rich Snippets plugin if it is not installed yet.
4. Activate the main plugin and verify that its menu or settings now appear in the admin panel.
5. Then upload the WPRS Compare ZIP file the same way.
6. Click Activate and check whether the add-on appears in the WP Rich Snippets extensions list or related settings.

If the site throws a critical error after activation, do not immediately try to turn the plugin back on. Roll back the change through your hosting panel, file manager, or WordPress recovery mode. Then check the PHP error log and environment compatibility. With older plugins, this is a normal part of troubleshooting, not a reason to modify WordPress core.

The First Check After Activation

After installation, do not jump straight to a live article. Create a test post or open a draft where you can safely check the Schema metabox, fill review fields, and test the shortcode output. In the block editor, use the Shortcode block for the shortcode. In the classic editor, insert the shortcode where you want it in the content.

Quick check: if a simple test shortcode from your version of WPRS Compare renders as plain shortcode text instead of a table, the problem is not design-related. WordPress did not process the shortcode, it was inserted in the wrong context, or the add-on did not register the shortcode handler.

Configuring the Data: What to Fill In Before Displaying the Comparison Table

The quality of the table depends on the source reviews. WPRS Compare should not be used to compensate for poorly filled-out posts. If every item uses different fields, different rating scales, and different description logic, the table may look visually aligned but still be weak in substance. Start with data structure, not color settings.

The Review Post Framework

Open the post that will be part of the comparison and find the WP Rich Snippets settings block. In known WP Rich Snippets examples, the plugin shows a Schema metabox where you choose the markup type and fill in the fields. In a review scenario, the important pieces are usually the item title, description, criteria, rating, author, and the extra tabs that handle details, price, image, or link.

Not all of those fields must appear in the comparison table. But if the table relies on review data, every compared value should be filled in the same way. Use one set of criteria across the entire review series. For example, if the first product uses Ease of use, Features, and Support as criteria, do not switch to different labels for the second product without a clear reason.

A Typical Field Set for a Review Table

• Product or service name, so the column makes sense without extra context.
• A short purpose statement, so the reader immediately sees who the option is for.
• An overall score or rating, if WP Rich Snippets uses one.
• A standout strength that helps separate one option from another.
• A limitation or cautious note, so the comparison does not read like advertising.
• A link to the full review, if the table is being used as navigation.

Display Settings and Block Placement

WP Rich Snippets reviews often mention a Display tab where the review box output is configured. For WPRS Compare, that matters indirectly: if the base review box already appears in an awkward place, the comparison table may clash with it visually. Decide in advance where the table should sit: before the detailed reviews, after the introductory explanation, before the conclusion, or inside a dedicated comparison block.

If your version includes settings for the Compare add-on, start with conservative values. Do not enable every decorative element, image, and button at once. First get a correct table working with core data, then add styling and extra columns. This sequence makes it easier to identify which setting broke the output if the problem appears after a save.

The Shortcode as the Output Point

Public sources indicate that the Compare add-on can be used through a shortcode. But the exact syntax is not confirmed in the available public sources, so do not copy random examples from third-party pages. Open the documentation for your version, the list of available shortcodes in the admin panel, or the plugin's own hints.

In the WordPress block editor, the official Shortcode block is appropriate for inserting shortcodes, and its advanced settings let you add a custom CSS class. That is useful if you want to limit future CSS changes to a single comparison block instead of affecting every table on the site.

Planning Your Criteria Before Creating a Comparison Table

Before using WPRS Compare on a live page, it helps to design the comparison criteria separately. That may sound like editorial work, but it is exactly what determines whether the table will actually help the reader. Technically, you can output many fields, but a good comparison is built around 5 to 7 parameters that answer the real selection question.

Start with the page audience. A beginner needs simple distinctions: who the product is for, how hard it is to get started, whether there is a clear limitation, and where to go next. A technical user cares more about compatibility, scalability, integration type, data format, and support risk. If you mix those two layers into one table, it becomes long and loses clarity.

How to Choose Table Rows

A table row should represent a criterion the reader actually uses to compare options. If a row does not affect the choice, it belongs in the full review instead. For example, an identical field like "WordPress plugin" adds no value if all options are already plugins. But a row like "Best for" is useful because it separates real scenarios: beginner, agency, store, developer, content project.

Every criterion should mean the same thing across all columns. You cannot write "good for beginners" in one column, "has lots of settings" in another, and "budget-friendly" in the third. That is not a comparison, it is a set of disconnected notes. Bring the values to a single type: complexity level, main advantage, primary risk, recommended use case, link to the full review.

A Practical Workflow

1. List every field already filled in across the WP Rich Snippets review posts.
2. Mark the fields that exist for all compared items.
3. Remove criteria that do not influence the user's decision.
4. Shorten long wording into compact values that make sense inside a table cell.
5. Check that each row helps distinguish the options instead of repeating the article introduction.

How to Keep the Table from Turning Into an Ad Block

A comparison table earns trust only when a strength is paired with a limitation. For each option, add a careful field: who it may not be right for, where manual setup is required, which risk should be checked, or which dependency matters. That does not reduce the value of the page. On the contrary, it shows the reader that the comparison was built to support a decision, not to push a single option.

If the table is used in affiliate content, separate the editorial conclusion from the commercial link. Do not turn every cell into a button. It is better to provide a short verdict and keep the action in a separate row or in the detailed review. That way the comparison table remains a reference and navigation block rather than a stack of promotional labels.

Final Check Before Publishing

After filling in the criteria, open the page and read only the table without looking at the rest of the article. If the table does not make the differences between the options clear, go back to the data. If it is clear but too long, split it into two: a quick decision table near the top and a more detailed comparison lower on the page. WPRS Compare works best when it shortens the path to a decision instead of turning the entire review into a table.

For older content, it helps to keep a separate editorial document listing which criteria are used across the review series, what each row is called, and what counts as an acceptable value. This makes it easier to preserve a consistent structure when different authors add new reviews. As a result, WPRS Compare gets cleaner data, and the reader sees a stable comparison logic across the whole category.

How to Use WPRS Compare in a Real Article

Imagine a review page where you are comparing several WordPress plugins for the same task. Each plugin has its own review post with a rating, a short verdict, pros, and a link to the detailed article. The goal is to place a table near the top of the page so the reader can quickly narrow the choice to 2 or 3 options worth reading in depth.

The Goal of the Scenario

You want a compact comparison block right after the introduction, but before the long descriptions of each product. The table should not show every field. It should show only the information that influences the decision: name, who it is for, overall rating, strongest point, limitation, and a review link.

Preparation

Before inserting the shortcode, open each review post and confirm that the fields are filled out using the same logic. If a product has no rating, it is better to leave it out of the table temporarily or fill in the data honestly. Empty cells are not always a technical error, but they do reduce trust in the comparison.

Steps

1. Create or open the page where the comparison will be displayed.
2. Write a short introductory paragraph explaining what is being compared and by which criteria.
3. Add a Shortcode block where the table should appear.
4. Insert the exact WPRS Compare shortcode from your plugin version.
5. If the shortcode supports parameters for selecting posts or criteria, include only the items you actually need.
6. Save the page as a draft and open the preview in a new tab.
7. Check the table on desktop, tablet width, and a mobile screen.

Expected Result

On the front end of the site, you should see a table with the compared options displayed side by side and the criteria readable without horizontal confusion. If the table is too wide, do not rush to shrink the font size. First reduce the number of columns or move some details into the full reviews.

A Common Detail That Causes Problems

A comparison page may look fine in the administrator preview but still break for a regular visitor because of cache, minification, or theme styles. Check the result in a private browser window and after clearing the cache. If the site uses a separate mobile cache, verify the mobile view separately.

Practical Ways to Use It on a Review Site

This section exists not to stretch the feature list, but to help you choose the right scenario. WPRS Compare works best when the table solves a specific editorial problem. Below are several scenarios based on the confirmed role of the add-on: displaying a comparison table for items connected to WP Rich Snippets review data.

A Selection Page for Beginners

If the audience does not know the category well, the table should stay short. Do not show ten technical criteria. Highlight purpose, difficulty level, strongest point, and one cautious note. That format helps users avoid getting lost in the details.

Checking the result is simple: ask an editor who did not write the article to choose a suitable option based only on the table. If they are forced to read every full review, the table is too weak or the criteria were chosen poorly.

A Page for Experienced Users

For a technical audience, you can show more criteria: compatibility with the required use case, integration type, limitations, presence of user reviews, and the ability to fine-tune the setup. But even here, the table should not become a wall of text. It is better to keep 5 to 7 strong criteria than to create dozens of rows with tiny text.

Navigation Across a Review Series

If you have several detailed articles, the comparison table can act as a navigation block. The user sees a short comparison, picks 1 or 2 options, and moves to the separate reviews. In this scenario, the link to the full article and a clear takeaway for each product are both important.

Editorial Quality Control

The table quickly reveals where a review series is missing data. If one column is weaker than the others, that is a signal to improve the review post, not the design. Use WPRS Compare as a check on editorial discipline: same criteria, same level of depth, same honesty about limitations.

How to Check the Visual Result and Structured Data After Publishing

Post-publication validation should happen on two layers. The first layer is visual: does the table appear, are the rows readable, do the links work, and does the mobile view hold up. The second layer is technical: did any structured data errors appear, and does the review markup conflict with the theme or another SEO plugin.

Visual Checks

• Open the page in a private browser window to see it the way a normal visitor would.
• Make sure the shortcode is not showing as plain text.
• Compare the desktop and mobile versions, especially for wide tables.
• Click the links inside the table and confirm that they go where they should.
• Check text contrast, because the theme styles may override the table colors.

Markup Checks

Google recommends testing structured data with Rich Results Test and monitoring Search Console reports. That matters even more with WPRS Compare: the table may look fine to the user while the underlying review markup still contains warnings or errors. Do not assume that clean table output means search enhancements are guaranteed.

Rich result is not a guaranteed visual bonus. It is the result of a search engine understanding supported markup and deciding the page is eligible for enhanced display. That is why you should look at the tool's actual messages, not just whether stars or ratings appear on the page.

Checks After Updates

After updating WordPress, the theme, the cache plugin, or the SEO plugin, open the comparison page again. Old shortcodes and older styles usually break not immediately after installation, but after a neighboring change. Add the comparison page to your manual post-maintenance checklist.

A good practice is to keep one hidden test page with the same shortcode and the same data types. If the live page starts behaving strangely, compare it with the test page. That makes it much faster to tell whether the problem is specific content, a page template, cache, or the overall behavior of the add-on.

Safe CSS Adjustments for Your Theme

The exact CSS classes used by WPRS Compare are not confirmed in public sources, so it would be risky to write a snippet that pretends to know the internal structure of the plugin. Instead, use a safe outside-in approach: add your own class to the shortcode block or the page container and style only what appears inside it. That does not modify plugin files and is easy to roll back.

Where to Apply It

In the block editor, select the Shortcode block, open the advanced settings, and add a class such as wprs-compare-wrap. If you use the classic editor, you can wrap the shortcode in a container using an HTML block or a theme template, but do not edit the plugin core.

The code below solves a narrow problem: it adds horizontal scrolling for a table that is too wide and slightly improves cell readability. It is based on safe WordPress CSS practice, not on an undocumented WPRS Compare API.

.wprs-compare-wrap {
  overflow-x: auto;
  -webkit-overflow-scrolling: touch;
}

.wprs-compare-wrap table {
  width: 100%;
  min-width: 760px;
  border-collapse: collapse;
}

.wprs-compare-wrap th,
.wprs-compare-wrap td {
  padding: 12px 14px;
  vertical-align: top;
}

Add this CSS through a child theme, Additional CSS in the Appearance settings, or a trusted snippets plugin. After saving, open the page at a mobile width. If the table scrolls horizontally and no longer breaks the overall layout, the job is done. To roll it back, remove the class from the block or delete the CSS.

Do not set global styles for all table tags if the site contains other tables. Scope the change to the container of the specific comparison block.

If the Comparison Table Does Not Appear or Looks Wrong

WPRS Compare is best diagnosed in a chain: is the main plugin installed, is the add-on active, did the shortcode process correctly, is there data to compare, and are the theme or cache getting in the way. That order is faster than randomly enabling and disabling every plugin one by one.

The Shortcode Appears as Plain Text

Symptom: the page shows the shortcode string instead of a table. Possible causes include an inactive add-on, a typo in the shortcode, insertion into an unsupported field, or shortcode processing being disabled in that specific theme context.

What to Check

• Make sure the main WP Rich Snippets plugin is active.
• Confirm that WPRS Compare is active and not disabled because of an error.
• Copy the shortcode again from your installed plugin version, not from a third-party article.
• Insert it into normal post content using the Shortcode block, not into an arbitrary theme field.

If the shortcode works in a normal test post but not inside a theme template block, the issue is the output location. Roll back the template insertion and use a standard content block instead.

The Table Is Empty or Missing Items

Symptom: the table container appears, but some columns or rows are empty. Most often, the cause is the source review data: different criteria, incomplete fields, incorrect post selection, or a missing relationship between the compared items.

Open each post that should be part of the comparison and check the Schema metabox. Fill in the same fields, save the posts, and clear the cache. If the table uses shortcode parameters to select posts, verify the identifiers or slug values passed into the shortcode.

The Table Styles Break the Mobile View

Symptom: the table extends beyond the screen, squeezes the columns until they are unreadable, or overlaps nearby content. The cause is usually a table that is too wide, global theme styles, or missing horizontal scroll behavior.

First reduce the number of columns. If the content still needs to remain wide, add a horizontally scrollable container using the CSS from the previous section. Do not reduce the font to a microscopic size - that will hurt readability and accessibility.

The Table Disappears or Stays Outdated After Cache Is Enabled

Symptom: the administrator sees updated data, but the visitor sees an old table or an empty block. The cause may be page cache, object cache, CDN, or JavaScript/CSS optimization.

Clear the page cache, CDN cache, and optimizer cache. Then open the page in a private window. If the issue disappears, add the comparison page to your manual post-edit checklist. If it does not, temporarily disable CSS/JS minification and check for a conflict with the theme.

Rich Results Test Shows Warnings

Symptom: the table looks fine, but the structured data validation tool shows errors or warnings. The cause may be incomplete review markup fields, conflicting schema markup from the theme or another SEO plugin, or a mismatch between the visible page content and the data in the markup.

Do not try to hide the issue with styles. Open the specific elements flagged by the tool and fill in the missing fields in WP Rich Snippets. If two systems are outputting review schema at the same time, temporarily disable one of them on a test page and compare the result.

Limitations and Cautious Decisions for Older Projects

WPRS Compare is best introduced as a targeted improvement, not as the foundation of a new site architecture. If the project already has dozens of review pages on WP Rich Snippets, the add-on can provide a quick win in navigation and usability. If the project is only now being launched, it is worth comparing it against more actively maintained alternatives.

The main limitation is the small amount of current public documentation. When a product does not have a fresh official knowledge base, every WordPress or PHP update needs more careful validation. A legacy plugin may continue to work on a specific site, but still require stricter testing.

When It Is Better Not to Touch a Live Page

Do not roll out WPRS Compare immediately on a page that brings in leads, sales, or search traffic. First create a copy of the page and test the shortcode, the table, the mobile view, cache behavior, structured data, and link behavior. If everything is stable, move the solution to the live page during a low-traffic period.

When Migration Should Be Considered

If you need regular updates, active support, modern schema types, data import, interactive sorting, and fine-grained design control, migrating to another tool may make more sense than extending an older WP Rich Snippets setup. In that case, WPRS Compare can remain in place for older content, while new pages are built on a different system.

When WPRS Compare Is the Right Choice

WPRS Compare is worth using if you already have a site built on WP Rich Snippets, filled-out review posts, and a clear goal: displaying a clean comparison table for several products or services. In that case, the add-on helps turn a set of separate reviews into a decision page where the reader can spot the differences faster and move to the right article.

Before rolling it out, verify the dependency on the main plugin, prepare matching fields, insert the shortcode into a test page, check the table at mobile width, and run the page through structured data validation tools. If everything is stable, you can download the ZIP archive and test it on a site copy or a non-public page.

If you are building a new project and need active support, large table import, a modern review builder, or WooCommerce comparison, do not lock yourself into WPRS Compare just because of the name. Define the working scenario first, then choose the tool. An older add-on can be a good fit for preserving an existing WPRS workflow, but it does not have to be the best solution for every new comparison page.