CodeCanyon Star Rating - WordPress Plugin

CodeCanyon Star Rating for WordPress Setup Guide

CodeCanyon Star Rating is a practical tool for cases where a WordPress page needs more than decorative stars. It lets you collect visitor ratings, display the result, limit repeat votes, and, when appropriate, pass the aggregate rating into the page markup. This guide walks through how to configure the plugin after installation, which tabs to review first, where automatic placement works best, and where it makes more sense to insert the shortcode manually.

This article does not repeat the product's short description. The focus here is the working setup: preparing the site, choosing post types, configuring the scale and icons, deciding how results should be handled, checking the markup, applying safe styling, and quickly understanding why the rating did not appear or why voting behaves differently than expected.

The plugin belongs to the class of rating tools used for content pages, product pages, and custom post types. That is why this guide covers page assignments, voting limits, multi-factor ratings, top-rated content lists, and conflict troubleshooting with themes, cache, and manual shortcode placement.

What a Rating Solves on a WordPress Page

Ratings are useful for more than review blogs. They help show how well an article, product page, knowledge base entry, recipe, service listing, or tutorial meets visitor expectations. Unlike a full review system, a star rating is faster: the user does not need to write anything, and the site owner can gather feedback signals across dozens of pages more easily.

CodeCanyon Star Rating stores ratings for WordPress content: standard posts, pages, products, and custom post types if they are enabled in the settings. That is an important difference from simple widgets that only draw static stars. Here, the rating is tied to a specific WordPress entity, so you can display it next to the content, show a numeric value, account for vote count, and build a list of highly rated content through a shortcode.

In practice, the plugin solves several real-world tasks:

• Add a rating to the beginning or end of a page without manually editing the template.
• Let a user vote once or only a limited number of times.
• Display the final rating and total vote count on the public site.
• Show results in the admin post list so editors can spot weaker content.
• Use shortcodes for precise output of the rating block, numeric score, vote count, or a list of top pages.
• Add Schema.org markup if the page type and search engine policies support that use case.

At the same time, a rating does not replace full reviews. If you need written customer feedback, review moderation, admin replies, review images, and integration with WooCommerce product pages, you will need a separate review system. CodeCanyon Star Rating is stronger in a different area: it quickly adds compact voting to existing pages and gives you flexible control over how it is displayed.

The decision logic is simple: if you need a quick "did this help or not" signal for a specific page, a rating plugin is a good fit. If you need documented feedback with written reviews, authors, and moderation, look at review plugins instead.

Who This Plugin Fits Best, and When Another Approach Makes More Sense

Before installation, it helps to define the use case honestly. Ratings are often added "just in case," and then the site owner does not know how to use the data. Good configuration starts not with the star color, but with the answer to a basic question: which page is being rated, and what will you do with that signal?

Good Use Cases for CodeCanyon Star Rating

The plugin works well for sites with a lot of standalone content where the owner wants a quick way to measure audience response. That can include tutorials, reviews, recipes, knowledge base entries, product pages, roundups, service pages, catalogs, educational content, or custom post type entries. A rating is especially useful if the editor regularly updates older pages and wants to know which ones need improvement.

On a content site, you can enable automatic output after the article and show the result next to the icons. In a knowledge base, it is better to add a short explanation near the rating so users understand they are evaluating the usefulness of the article, not the site design as a whole. On a product or service catalog, it is important to decide in advance whether the rating will conflict with existing WooCommerce reviews or another review solution.

When a Rating May Be Unnecessary

A rating does not always improve a page. If the site gets little traffic, the first few ratings may look random and carry no statistical value. If the page covers legal, medical, financial, or otherwise critical instructions, a simple star rating may create the wrong impression about the reliability of the material. If the page already has a full review system, a second rating block can confuse users.

You should also be cautious with markup intended for rich results. Simply having a rating in the HTML does not guarantee stars in search. Search engines evaluate the page type, the correctness of the structured data, trust in the site, page accessibility, and policy compliance. So markup should be enabled not because of a promised SEO shortcut, but as careful technical markup for content that genuinely fits.

Who Will Work with the Settings

A simple setup is within reach for a WordPress administrator. They can install the ZIP file, open the Stellar menu in the admin area, choose post types, set the display position, and configure colors. For more complex cases, it is better to involve a developer or an experienced webmaster, for example when the rating must be inserted through a shortcode inside a page builder template, tied to a custom post type, validated in JSON-LD, or carefully styled with CSS to match the theme.

What to Check Before Installation and First Launch

Preparation is not just a formality. A rating affects the public side of the site, records user actions, and may inject markup into the HTML. If you enable everything at once on a live site, it becomes difficult to understand which setting controls the appearance, repeat-vote logic, or unexpected output on the wrong pages.

Check the WordPress Environment and Theme

The product page lists compatibility with modern WordPress versions and popular browsers, but on a real project, the specific setup matters: the theme, page builder, cache, JavaScript minification, optimization plugins, WooCommerce, and custom post types. Before installation, open the list of active plugins and note anything that affects content output: page builders, cache, lazy load, CSS/JS optimization, schema plugins, review plugins, and WooCommerce blocks.

If the site uses aggressive caching, make sure you already have a way to clear the page cache and CDN cache. The rating reacts to a user vote, while cache may continue to serve old HTML or an outdated result. That does not mean the plugin is incompatible with caching, but you should verify results in a normal window, in incognito mode, and after clearing cache.

Identify the Pages Where the Rating Actually Belongs

Do not enable the rating for every post type right away. Start with a single content type, such as blog posts or knowledge base pages. Then add products or custom post types only if there is a clear use case. This makes troubleshooting easier: if the block appears where it should not, you can focus on Post Types, Assignments, and the display position instead of auditing the entire site.

Create a Safe Test Page

Create or choose a test page that is easy to find and easy to roll back. It is the best place to verify the block position, scale, colors, vote limit, results, and shortcodes. If the site gets regular traffic, it is better to do the initial validation on a draft, a private test page, or a staging copy of the site. Once everything checks out, you can enable the rating on the public pages you actually want.

Decide How You Will Measure Success

A rating means very little without context. In a knowledge base, it may mean "this article helped." For reviews, it may measure content quality. For a service catalog, it may indicate trust in the description. For an online store, it is important not to mix product ratings with article ratings if the page already contains customer reviews. Write down this logic before configuration so the text next to the rating is clear to users.

Installation and Initial Validation in the Admin Area

CodeCanyon Star Rating installs like a standard WordPress ZIP plugin. The downloaded package may include documentation and a separate installable ZIP, so make sure you upload the plugin ZIP itself, not the full marketplace package. That is a common reason for the "archive could not be installed" error: WordPress expects a plugin structure, but receives a general package instead.

Installing Through WordPress

1. Open the WordPress admin area under a user account with administrator permissions.
2. Go to Plugins - Add New.
3. Click Upload Plugin and select the plugin ZIP file.
4. Start the installation with Install Now.
5. After installation, click Activate.
6. Open the settings through the Settings link under the plugin name or through the Stellar item in the left menu.

After activation, do not rush to enable every feature. First, verify that the settings page opens without errors, that the Stellar menu item appears, and that the settings tabs are available. Merkulove's documentation lists the tabs General, Results, Rich Snippet, Shortcode, Assignments, Custom CSS, Activation, Status, and Uninstall. The presence of these groups is a good sign that the plugin was installed correctly.

First Validation Without Risk

For the first test, choose a single post type and the After content position. That is a safe starting point: the block appears after the main content and rarely interferes with the heading, product layout, or above-the-fold area. Then open the test page in a separate window, submit a vote, refresh the page, and see whether the result appears.

Quick checkpoint after installation: the plugin is active, the Stellar menu item is available, the rating is visible on one test page, the vote is saved, and the value does not reset after reloading the page.

What Not to Do at the First Step

Do not enable markup, multi-factor voting, and complex assignments all at once. These features are useful, but each adds another layer of logic. If the base rating is not working yet, you will not know whether the problem comes from the display position, post type, cache, voting limit, markup, or a template conflict.

Configuring Display: Post Types, Position, Icons, and Description

The General tab controls where the rating appears and how users interact with the block. This is the main section to configure after installation. The important part here is not choosing "pretty stars," but creating the right relationship between the content, the user action, and the result.

Post Types and Scope

The Post Types setting selects the WordPress entities where the rating will be available. For a standard blog, posts are enough. For a knowledge base, you may need a custom post type if the documentation is handled by a separate plugin. For a store, products may make sense, but before enabling them, check how that interacts with native WooCommerce reviews.

The best starting point is one post type and one test page. After validation, you can expand the scope. If the rating is enabled for a custom post type, make sure the template actually outputs the main content through standard WordPress mechanisms. If the theme builds the page in a nonstandard way, the automatic position may fail, and that is where the shortcode becomes useful.

Display Position and Shortcode

The documentation lists several positions: before the title, after the title, before content, after content, and Shortcode [stellar]. For most sites, it is best to start with output after the content: users read the material first, then rate it. Output before the content can work on pages where the rating needs to act as immediate social proof, but it may distract from the heading.

Shortcode mode is useful when you want precise placement. For example, you can put the rating after a "Summary" block, inside a page builder template, in a separate product tab, or in a reusable knowledge base block. This approach is especially helpful when the automatic output gets duplicated because of the theme or builder.

Number of Rating Steps

The plugin lets you choose a scale from 1 to 12 steps. When you change the scale, existing ratings are recalculated to match the new system, so you should change this setting carefully on a live site. For most visitor ratings, 5 steps work best: the scale is familiar, easy to understand, and the result is easy to interpret. A longer scale can help with expert-oriented content where the audience understands finer distinctions, but it also makes the choice more complicated.

If you are unsure, stick with 5 steps. It is easier for users and easier to validate in markup, especially because the plugin documentation specifically notes the conversion of data to a 5-star system when working with rich snippets.

Icons, SVG, Size, and Spacing

Stellar supports icon selection from a built-in library and also lets you upload a custom SVG. That is useful if the site does not want classic stars. For example, recipes can keep stars, a knowledge base can use checkmarks or likes, and a service directory can use a more neutral symbol. But any custom icon still needs to be intuitive without explanation. If users do not understand what to click, the design is getting in the way of the data.

Icon size should be checked on mobile. The documentation notes that icons that are too small can make interaction harder on phones. In practical terms, that means do not chase minimalism too far. The rating should be noticeable, easy to tap, and not interfere with nearby buttons, links, or ad blocks.

Description Next to the Rating

The description field helps explain what the user is actually rating. For an article, that could be "Rate how helpful this guide was." For a product page, it might be "Rate this product description" if actual customer reviews are collected elsewhere. For a knowledge base, it could be "Did this guide help you solve your problem?" That kind of text reduces noise in the data because the visitor understands they are rating the specific content, not the entire website.

Validation After Saving

After changing the settings, click Save Changes, clear the page cache, open the test page in incognito mode, and verify four things: the block appears in the right place, the icons do not break the layout, the description reads clearly, and the vote persists after reload. If something goes wrong, revert to the previous position or temporarily switch to the shortcode.

Voting Results and Protection Against Repeat Ratings

The Results tab controls how the plugin stores, displays, and limits rating results. This is where mistakes are easy to make: a site owner enables everything at once, and the user ends up seeing too many numbers or does not understand why a second vote is rejected. A good configuration should be transparent for visitors and useful for editors.

What to Show the User

The plugin can show the current user's rating, the overall result, the vote count, and a tooltip with the numeric value. On a public page, the overall rating and vote count are usually enough. The current user's last rating is only worth showing where it adds value, such as in an account area or on a page visitors return to multiple times.

You can also hide the result until the user votes. That is useful if you want to reduce herd behavior, so users submit their own rating before seeing the average. For expert content and knowledge bases, that approach is often more honest. On product pages or roundup pages, visible social proof may be more useful, but then the vote count should also be easy to see.

Rounding and Partially Filled Icons

The rounding setting determines how the average score is translated into filled icons. If you round up, the result may look more optimistic than it really is. If you do not round, users will see partially filled icons, which is more accurate but visually more complex. For most content sites, the best balance is an exact numeric score next to the icons plus a clean visual display that does not inflate the rating.

Voting Limits

Stellar supports limiting the number of votes from a single IP address and session control. This is not absolute protection against manipulation, but it is a useful barrier against accidental repeat voting and simple attempts to change the result quickly. The documentation specifies a range for the IP-based voting limit. For a typical site, start with one vote and a clear message explaining that the limit has been reached.

It is important to understand the limits of this approach. An IP address does not always represent one person: an office, coffee shop, mobile carrier, or corporate network may share a single external address. So a strict limit can sometimes block legitimate visitors. If your audience often comes from shared networks, test the behavior with a small group first and use neutral messaging rather than accusatory wording.

Results in the Admin Area

Displaying results in the post list is useful for editors. They can see which pages receive low ratings, where there are too few votes, and which articles may need revision. For a content team, this can matter even more than public stars because the rating becomes an editorial signal. In the settings, you can choose the display format, such as count only or a combined count-and-result view.

Resetting Test Ratings

During setup, you will be voting yourself. The documentation describes a button for resetting rating data and warns that the reset is irreversible. Use it only after testing, and only if you clearly understand that you are deleting accumulated ratings. On a live site, it is safer to test settings on a dedicated page than to wipe real visitor votes.

Multi-Factor Ratings and the Scenarios Where They Actually Matter

A standard rating answers one question: how much the page was liked or how helpful it was. Multi-factor ratings are useful when a single score is too broad. In Stellar, you can enable multiple voting criteria, add labels and descriptions, and then control their display order. It is a strong feature, but it should only be used where the user understands each criterion clearly.

When to Enable Multiple Criteria

Multi-factor ratings work well for reviews, catalogs, recipes, tutorials, and roundups where the outcome depends on several aspects. For example, a service review might rate ease of use, speed, and support. A recipe might rate taste, difficulty, and ingredient availability. A knowledge base article might rate clarity, completeness, and freshness.

A poor use case is adding criteria just to make the block look more impressive. If visitors see five separate rating rows and do not understand the difference between them, they either will not vote at all or will assign random scores. In that case, the data becomes less useful than a simple single rating.

How to Design the Criteria

Each criterion should be short and specific. Avoid abstract labels like "quality" unless you explain what that means. Better options are "Clarity of the Guide," "Usefulness of the Example," "Accuracy of the Description," or "Product Usability." The description next to the criterion should explain exactly what is being rated. If the criteria depend on the page type, do not enable them globally for all content.

A Practical Workflow for a Multi-Factor Block

1. Choose one test page where a multi-factor rating genuinely adds value.
2. Enable Enable Multi voting.
3. Add 2-3 criteria through Add Vote, using clear labels and descriptions.
4. Set the order through Votes Order if reading order matters.
5. Save the settings and check the public output on desktop and mobile.
6. Vote on each criterion and make sure the result does not get mixed up with another block on the page.

If you need to display a specific criterion in a different part of the page, the documentation shows a shortcode like [stellar multi_vote _item_label="Taste"]. On a non-English site, the label can be localized to fit the context, but it still has to match the criterion name in the settings exactly. If the label does not match, the output may not find the correct item.

How to Avoid Overloading the Page

A multi-factor block takes up more space than a single row of stars. If the page already includes a form, recommendations, ads, product specs, and comments, the rating can get lost. In that case, it is usually better to keep one overall rating and reserve criteria-based voting only for pages where those distinctions actually help the user decide.

Shortcodes, Top Content Lists, and Manual Rating Placement

Shortcodes are what make the plugin flexible. They are useful not only for manually inserting the voting block, but also for showing the rating of a specific page, a list of top content, the sitewide average rating, or the vote count. The key is to use them intentionally: every shortcode should serve a specific purpose.

Manual Output of the Voting Block

If the automatic position does not fit, choose Shortcode [stellar] in the settings and place [stellar] where you want it on the page. This works well in the block editor, classic editor, page builder, or any template area that accepts shortcodes. Manual placement is especially useful when the block needs to appear after a summary section, next to a call to leave a rating, or inside a separate tab.

The shortcode [stellar id="10"] lets you display the voting block and result for a specific post or page somewhere else. Replace the sample value with the real post ID. You can find it in the WordPress post list by hovering over the title or in the edit URL. This is useful for summary pages where you want to show the rating of selected content items.

Top Page Lists

The documentation describes the shortcode [stellar top="10" for="page" cols="4"]. It outputs a list of items of the chosen type, with parameters controlling the count, post type, and number of columns. This is useful in a knowledge base, where you may want to show the highest-rated guides. In a blog, it can power a best-reviews widget. In a service catalog, it can highlight pages with strong user feedback.

Do not place a top-content list on every page. It can distract from the main action and add visual weight to the layout. It works better on a dedicated "Best Resources" page, in a knowledge base sidebar, or at the end of a topical section.

Averages and Standalone Numbers

The shortcodes [stellar overall="1"] and [stellar average="page"] help display the average rating across the site or for a specific post type. Additional shortcodes like [stellar-rating] and [stellar-count] output the numeric rating value and the vote count. That is useful if the page design needs the number separated from the icons or if you want the stats displayed in a dedicated block.

Testing Shortcodes

After inserting a shortcode, open the page as a normal visitor. If you see the shortcode text instead of the block, that location does not process shortcodes or they are disabled in that specific builder element. Try the standard WordPress shortcode block, a different builder element, or automatic placement. If the block appears twice, check whether both automatic output and manual insertion are enabled at the same time.

A practical rule: automatic placement is best for broad use, while a shortcode is best for precise control. Do not use both on the same page unless there is a clear reason to do so.

Assignments: How to Keep the Rating Off Pages Where It Gets in the Way

The Assignments tab gives you more precise targeting than a general post type selection. If you enable ratings for all posts or pages, the block may appear on internal content, landing pages, legal pages, contact pages, draft instructions, or builder templates where voting does not make sense. That is why assignments should be treated as a second filter after Post Types.

The logic is simple: first, choose the overall content type, then narrow it down by deciding which categories, individual pages, user roles, or devices should see the rating. This is especially useful on sites with multiple content formats. For example, a blog may contain news, reviews, and tutorials. Ratings may make sense for reviews and tutorials, but not necessarily for news. In a knowledge base, they may be useful for public articles but unnecessary for internal utility pages.

Categories and Individual Pages

If the site is built around categories, start there. It is easier to maintain: the editor places the content in the right category, and the rating appears automatically. Use individual pages for exceptions, for example when the rating should appear on one important landing page but not on every page-type page. This reduces the risk of the block appearing somewhere unexpected after the next publication.

Check not only the public URL, but also archive pages, listing cards, builder templates, and previews. Sometimes a theme outputs part of the content inside a content card, and the rating can end up there even though it does not belong. If that happens, disable the automatic position and use a manual shortcode only in the full entry.

User Roles and Devices

Role-based restrictions are useful during testing. For example, you can show the rating only to administrators or editors first, verify the appearance and logic, and then open it up to visitors. In public mode, use role restrictions carefully: if only logged-in users can see the rating, the data will reflect a small group rather than the audience as a whole.

Device restrictions can help if the block looks fine on desktop but takes up too much space on mobile. In most cases, though, it is better to adjust the size, spacing, and position than to hide the rating on phones entirely. If a large share of your audience comes from mobile devices, hiding the rating will distort the data.

How to Test Assignments Without Creating Chaos

1. Select one general post type in Post Types.
2. Add one rule in Assignments, such as a category or a specific page.
3. Check a page where the rating should be visible.
4. Check a similar page where the rating should be absent.
5. Clear the cache and repeat the test in incognito mode.
6. Only after that should you add the next rule.

Do not try to build a complex matrix of categories, roles, devices, and individual pages all at once. The more rules are enabled simultaneously, the harder it becomes to understand why the block appeared or disappeared. If the configuration gets too tangled, temporarily disable the extra assignments and go back to one simple rule.

How to Use Rating Results in Editorial Work

A rating becomes useful only when it drives decisions. If you simply show stars at the bottom of the page but never analyze weak content, the plugin loses much of its value. The admin-area results, numeric shortcodes, and top-page list can all be turned into a clear editorial workflow.

Signals for Updating Content

A low score does not always mean the article is bad. Sometimes users are unhappy with the product, the theme, an external service, or the fact that their task did not match the topic of the page. That is why ratings should be read in context: page traffic, time on page, comments, search queries, and the date of the last update all matter. But if a guide consistently gets low ratings and a meaningful number of votes, it is a strong candidate for revision.

Create a simple working list:

• Pages with many votes and a low average score should be reviewed first.
• Pages with high traffic and almost no votes should be checked to make sure the block is visible and the description text is clear.
• Pages with high ratings can be used as structural examples for similar content.
• Pages with a sharp rating change after an update should be checked to see whether the guide or an external service broke.

How Not to Overreact to a Small Sample

One or two ratings do not provide a reliable picture. Do not rewrite a page just because the first visitor left a low score. It is better to define a minimum vote threshold before a page enters the editorial review list. That threshold will vary by site, but the principle stays the same: the fewer the votes, the more cautious the conclusion.

The top-pages list created with [stellar top="10" for="page" cols="4"] is also better shown only after some data has accumulated. Otherwise, the "best content" page may feature entries that were rated highly by just one person. If your audience is small, use that list internally first and publish it only after checking the data.

Ratings as a Clue for Content Structure

If low ratings cluster around pages with the same structure, the issue may not be one specific article but the format itself. For example, users may be missing a "result check" section, examples, screenshots, or troubleshooting. In that case, ratings help you do more than fix one page. They help improve the template for future guides.

Editorial takeaway: use ratings as a signal to investigate, not as an automatic verdict. The best decision usually comes from comparing the score, user behavior, and the page content itself.

Rich Snippet Markup and Structured Data Validation

Rating markup is one of the most sensitive parts of the setup. Stellar includes a Rich Snippet tab where you can enable schema markup, choose a basic mode, or add advanced JSON-LD structure. But it is important not to confuse the technical ability to add markup with any guarantee that stars will appear in search results.

What Rating Markup Does

The markup tells a search engine that the page contains an aggregate rating. In Schema.org terms, that usually means properties such as AggregateRating, ratingValue, ratingCount, or reviewCount attached to the appropriate entity type. Stellar's documentation notes that the data can be converted to a 5-star system regardless of the rating scale used in the interface.

That is an important detail for sites that use a 10-step or 12-step interface. Users see one scale, but the search markup needs to be expressed in the standard format machines expect. So after enabling Rich Snippet, you should validate not only the visual output but also the machine-readable data.

When Markup Is Appropriate

Google does not support review snippets for every kind of page. The markup needs to match the content type and search engine guidelines. For example, aggregate ratings make sense for recipes, products, courses, books, apps, local businesses, and other supported entity types. For a standard informational article, stars may be technically present in the markup, but that does not mean the search engine will show a rich result.

If the page does not fit a supported type, do not promise yourself an SEO payoff. Enable markup only where it honestly describes the content on the page. If another SEO plugin or review plugin is already active, check whether the site is generating two competing markup blocks for the same entity.

Testing with Rich Results Test

1. Enable markup only on a test page or on a small set of suitable pages.
2. Open the public page URL where real votes and a result already exist.
3. Test the page in Rich Results Test.
4. Review not just the presence of a rating, but also the entity type, required fields, and warnings.
5. If there are critical errors, disable the advanced markup or correct the JSON-LD according to the documentation.
6. After making changes, clear the cache and run the test again.

If the test does not show a rich result, that is not always a plugin error. The page may not match a supported type, the markup may conflict with another plugin, the data may be hidden behind cache, or the search engine may decide not to show stars even when the markup is valid. The article should not promise guaranteed ranking gains: correct markup helps machines understand the data, but it does not replace content quality or site trust.

Advanced Markup and Code Caution

The documentation mentions Advanced Schema Markup and JSON-LD structures. This is an area for people who clearly understand what entity type the page represents. If you are not sure, do not paste random JSON-LD examples into the page. The wrong entity type is worse than no advanced markup at all because it creates misleading signals and makes troubleshooting harder.

Practical Example: A Rating for a Knowledge Base

Let us look at a concrete scenario. A site has a documentation section, and the owner wants to understand which articles help users and which ones need to be rewritten. The goal is a rating after the content, hidden results until the vote, repeat-vote limits, and a separate page listing the most useful articles.

Goal

Create a compact "Rate how helpful this guide was" block at the end of knowledge base articles, collect one vote per visitor, display the average result, and use a separate shortcode on a page that highlights the best resources.

Preparation

Before configuring anything, identify the knowledge base post type. If the articles are regular posts, use post. If a separate knowledge base plugin is installed, the type may be custom. Create a test article and make sure it is publicly accessible. Clear the page cache so changes appear immediately.

Configuration Steps

1. Open Stellar in the admin area.
2. On the General tab, select the required post type in Post Types.
3. Set the position to After content so the user reads the guide first.
4. Keep the scale at 5 steps unless there is a clear reason to use a longer one.
5. Adjust the icon size so the controls are easy to tap on mobile.
6. In the description field, enter a short text such as "Rate how helpful this guide was."
7. On the Results tab, enable the overall result and vote count after the icons.
8. Hide the result until voting if you want a more independent user response.
9. Set an IP-based voting limit and configure a neutral limit-exceeded message.
10. Save the settings with Save Changes.

Checking the Result

Open the test article in incognito mode. The block should appear after the content. Submit a rating, reload the page, and check whether the result was saved. Then open the post list in the admin area and see whether the result appears in the selected format. If hidden results are enabled until voting, test the page as a new visitor: before clicking, the average score should not influence the choice.

Top Guides List

Create a separate "Helpful Guides" page and insert the shortcode [stellar top="10" for="page" cols="2"], replacing page with the correct post type if your knowledge base uses a different one. After publishing, make sure the list outputs rated articles and that the column count does not break the layout on mobile.

A Cache-Related Detail

If the page still shows the old result after a vote, clear the page cache, optimization cache, and CDN cache. Then test again in a different browser or an incognito window. If the issue persists, temporarily disable JavaScript minification and file merging to rule out a conflict in vote handling.

Safe Styling and Localization Without Editing Plugin Files

The plugin lets you change colors, size, and icons through the settings. That is often enough. But sometimes the block needs a small adjustment to fit the theme, such as adding spacing, centering it, softening the description text, or reducing harsh contrast. You should not edit the plugin files directly: updates will overwrite the changes, and a mistake can break the public site.

Start with the Built-In Settings

Check Default Icon Color, Active icon color, Hover icon color, Icon size, Icon space, and Layout. These options are safer than CSS because the plugin applies them in the place it expects. CSS is best reserved for small refinements to the outer container when the built-in settings are not enough.

CSS for Clean Spacing and Alignment

If the block sits too close to the content or looks awkward at the end of the article, you can add a small CSS snippet through Appearance - Customize - Additional CSS or through the Custom CSS tab if that fits your setup. Before applying it, confirm the actual CSS class of the container in browser dev tools because the theme or plugin version may differ.

.mdp-stellar,
.stellar-rating {
  margin-top: 24px;
  margin-bottom: 24px;
  max-width: 100%;
}

.mdp-stellar .stellar-description,
.stellar-rating .stellar-description {
  margin-bottom: 10px;
  font-size: 0.95em;
  line-height: 1.5;
}

This example is intentionally small. It does not change voting logic, hide important elements, or create a difficult rollback path: remove the CSS, clear cache, and reload the page. If your site uses different classes, do not guess them. Open developer tools, inspect the rating container, and replace the selectors with the real ones.

Text Localization

The product page mentions a POT file for translations. That means the system strings can be localized through standard WordPress translation tools if you need to change the interface language. But the description text next to the rating is easier to set directly in the plugin settings, which lets the editor tailor the phrase to a specific use case without touching translation files.

When CSS Is Better Left Alone

Do not use CSS to hide warnings, limit messages, result elements, or disabled buttons. If the logic does not fit, change the settings instead. An element hidden with CSS may still work technically, but the user will have no idea what happened. Be especially careful with areas that display results or messages about exceeded voting limits.

If the Rating Does Not Appear, Does Not Save Votes, or Breaks the Output

Troubleshooting works best as a sequence: scope, output method, cache, voting limits, theme conflict, markup. Do not start by reinstalling the plugin. Most issues come from the display position, a duplicated shortcode, cache, or settings that are applied too broadly.

The Rating Block Does Not Appear on the Page

Symptom: the settings are saved, but there are no rating icons on the public page. First, check whether the page belongs to the selected Post Types. Then review the display position: if Shortcode [stellar] is selected, no automatic block will appear until you insert [stellar].

What to check: post type, page status, selected position, the Assignments tab, cache, and the theme template. If the page is built with a page builder and the main content is not rendered in the standard way, the automatic position may fail.

How to fix it: enable the correct post type, temporarily switch to After content, clear the cache, and test on a standard page without a complex builder. If the block appears there, use the shortcode in the right builder location.

The Rating Appears Twice

Symptom: the page shows two identical blocks, or the rating appears both automatically and in a manual location. The usual reason is that automatic output is enabled while a shortcode has also been inserted.

What to check: the position in General, the post content, the builder template, and reusable theme blocks. Sometimes a theme outputs the main content in multiple places, such as in both a card and the full post.

How to fix it: choose one method. For broad use, keep automatic placement and remove the manual shortcode. For precise placement, switch to shortcode mode and insert [stellar] only where the block is needed.

The Vote Is Not Accepted or the User Sees a Limit Message

Symptom: the user clicks the icons, but the vote does not change the result, or a limit-exceeded message appears. The cause may be expected behavior: the IP-based limit has already been reached, session control is enabled, or testing is happening from the same network.

What to check: Voting limit, Session control, the Limit exceeded message, testing in another browser, and testing from a different connection. If the site uses a shared office IP, multiple legitimate users may appear as one source.

How to fix it: for testing, temporarily raise the limit, then verify behavior in incognito mode and on another device. After validation, restore a stricter limit. Do not leave a permissive setup on a public site if the rating affects visible top-content lists.

The Result Does Not Update After Voting

Symptom: the vote is accepted, but the page still shows the old result or old vote count. A common cause is page cache, CDN caching, JavaScript minification, or script merging.

What to check: WordPress cache, hosting cache, CDN, optimizer settings, and exclusions for pages with interactive blocks. Also open the page in incognito mode and compare the result.

How to fix it: clear all caches, temporarily disable JavaScript merging, and check whether the plugin script is being delayed until the click handler no longer attaches in time. If everything works once optimization is disabled, turn options back on one at a time and find the conflict.

Rich Snippet Does Not Pass Validation

Symptom: Rich Results Test shows an error or does not recognize the rating. The cause may be an unsupported page type, incomplete data, a conflict with another SEO plugin, or an incorrect advanced JSON-LD structure.

What to check: whether Rich Snippet is enabled, whether the page has real votes, which entity type is specified, and whether a second schema block is being added by the theme or another SEO plugin. Check the raw HTML after clearing the cache.

How to fix it: disable advanced markup and start with the basic mode. If the page does not fit a supported type, do not try to force stars into search. For complex JSON-LD structures, rely on Google and Schema.org documentation, not random examples.

The Rating Styles Look Broken in the Theme

Symptom: the icons are too large, the block is pushed out of place, the colors do not match, or the spacing looks off. The usual reason is a CSS conflict with the theme, global builder styles, or a container that is too narrow.

What to check: icon size, icon spacing, selected layout, container width, theme CSS, and the mobile view. Temporarily change the position or insert the shortcode into a wider block.

How to fix it: first adjust size, color, and layout using the built-in settings. If needed, add a small CSS snippet in a safe location. If the block breaks only in one template, it is better to fix that specific container than to change the global settings for the whole site.

Limitations, Performance, and Compatibility with Other Plugins

Stellar is presented as a lightweight plugin built on Vanilla JavaScript without jQuery and with support for popular browsers. That is a solid technical baseline, but real-world performance depends on the theme, cache, the number of blocks on the page, and how often users interact with the rating. The plugin should be configured in a way that avoids unnecessary conflicts.

Cache and Interactivity

Any interactive rating lives at the boundary between a cached page and a live user action. The page HTML may be cached, but the vote still needs to be saved and the result updated. That is why, after setup, you should always test the page with caching enabled. If the result does not update, do not disable the entire site cache immediately. Start with cache exclusions, deferred script loading, and minification settings.

WooCommerce and Existing Reviews

The product page lists WooCommerce compatibility, but that does not mean the rating should automatically be enabled on products. WooCommerce already has its own review system and product rating. If you add a second rating, visitors may not understand which one matters. A better approach is to use Stellar for articles, guides, and landing pages while leaving product reviews to the store's native system. If you still want the rating on products, explain clearly in the description what is being rated, such as the usefulness of the description or a curated product roundup.

SEO Plugins and Duplicate Schema

Many sites already run SEO plugins that add Article, Product, Breadcrumb, Organization, and other markup. If Stellar adds AggregateRating while another plugin generates its own JSON-LD, you need to validate the final page as a whole. The conflict may not be caused by one plugin in isolation, but by two tools describing the same entity in different ways.

Custom Post Types and Page Builders

Custom post types are supported as long as they are available in the settings and correctly rendered by the theme. But page builders sometimes bypass the standard content flow. In that case, automatic output may not land in the right place. The shortcode solves most of these situations because you can place the block in a specific section yourself.

Voting Security

IP limits and session control reduce the risk of simple repeat voting, but they do not turn the plugin into a secure voting platform for contests, financial decisions, or legally significant outcomes. Do not use a public rating as the sole basis for important decisions. For content analytics and general user feedback, the plugin is capable enough, but strict voting requires a different architecture.

When CodeCanyon Star Rating Is the Right Choice

CodeCanyon Star Rating is a strong option if you need a manageable rating system for WordPress posts, pages, products, or custom post types rather than a full review platform. Its strengths include a flexible scale, icon selection, manual and automatic output, multi-factor ratings, voting limits, result display, and shortcodes for summary blocks.

Before rolling it out, configure one test scenario and verify the appearance, voting behavior, cache interaction, admin-area results, and structured data if you plan to use it. Do not enable markup and complex assignments across the whole site without testing. If the site already uses WooCommerce reviews or another review plugin, define the roles clearly in advance so visitors do not see two different ratings for the same entity.

If the plugin fits your use case after testing, you can get the WordPress version, install the ZIP file, and work through the setup steps from this guide. The safest path is to start with one test page, then one post type, and only after that expand it to the rest of the site.

Final pre-launch check: the rating appears in a clear location, users understand what they are rating, repeat votes are limited, the result updates with cache enabled, and the markup passes validation only where it truly belongs.