> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/reviews/storefront-and-display/count-only-rated-reviews-in-star-averages.md).

# Count only rated reviews in star averages

Keep reviews without a star rating, such as imported text-only reviews, out of your star averages and counts, and show rating and review counts separately on your storefront.

Some reviews don't have a star rating. This is common when you import reviews from a platform that only collected written reviews. By default, Roadmap includes every published review in the count beside your stars, so a batch of text-only reviews can make your ratings look out of step with your review list.

The **Star ratings** setting lets you count only reviews that have a star rating. Text-only reviews still appear on your product pages. They just don't affect the stars.

### Change which reviews count

{% stepper %}
{% step %}

#### Open your review settings

In Roadmap, go to **Reviews**, open the **Actions** menu and click **Settings**.
{% endstep %}

{% step %}

#### Choose an option under Star ratings

The **Star ratings** card has two options:

* **All reviews**: the default. The review count beside the stars includes every published review, including reviews without a star rating.
* **Only reviews with a star rating**: reviews without a star rating show as written reviews only. They don't count toward star averages, the review count beside the stars, or the star rating Google shows in search results.

Select **Only reviews with a star rating**, then save.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FmhfttQuacfnlYT5IAecq%2FScreenshot%202026-11-17%20at%201.13.04%E2%80%AFPM.png?alt=media&amp;token=be701306-88a3-4305-b082-69efebd708d0" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### What changes on your storefront

With **Only reviews with a star rating** selected:

* **Reviews without a rating show as written reviews only**, with no stars. This is how unrated reviews always display.
* **Star averages and the counts beside them** only include reviews that have a star rating. This applies to the review badge, the review summary in the PDP review block, and the star rating Google shows in search results.
* **Products whose reviews are all unrated don't show a star rating**, but their written reviews still appear on the product page.
* **New reviews collected through Roadmap** keep the normal 1 to 5 star rating and count toward the average.

For example, a product with one 5-star review and three text-only reviews shows a 5-star average based on one rating. All four reviews still appear in the review list.

### Show rating and review counts separately

When some reviews are unrated, "Based on 2 reviews" can look odd above a list of 10 reviews. You can change the text to show both counts, for example "Based on 2 ratings and 10 reviews".

In **Edit Review Widgets**, the variables are listed under each text field. Click a snippet to add it.

**PDP Block**: the **Headline** and **Review summary with 1 or more reviews** fields.

* **Product title** (`_product_title_`): the title of the product the block sits on, e.g. Brain Wave.
* **Review count** (`_review_count_`): the number of reviews with a star rating, e.g. 24.
* **Average rating** (`_avg_rating_`): the average of all star ratings on the product, e.g. 4.6.
* **Total review count** (`_total_review_count_`): the number of all reviews, including ones left without a star rating, e.g. 31.

So a summary of `Based on _review_count_ ratings and _total_review_count_ reviews` renders as "Based on 2 ratings and 10 reviews".

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FfrZOLVkTbAbd8DUUDcbP%2FScreenshot%202026-11-17%20at%201.08.35%E2%80%AFPM.png?alt=media&amp;token=5f742a25-e459-4f46-805a-8b43284c3805" alt="" width="563"><figcaption></figcaption></figure>

**Review Badge**: the **Text** field uses `{{ n }}` for **Review count** and `{{ total_n }}` for **Total review count**. For example, `{{ average_rating_1_decimal }} ({{ n }} ratings, {{ total_n }} reviews)`.

If every review in your store has a star rating, **Review count** and **Total review count** are the same, and nothing changes on your storefront.

### Related guides

* [Edit your PDP review block](https://docs.roadmap.so/reviews/storefront-and-display/edit-your-pdp-review-block.md)
* [Edit your review badge](https://docs.roadmap.so/reviews/storefront-and-display/edit-your-review-badge.md)
* [Import reviews to Roadmap with CSV template](https://docs.roadmap.so/reviews/migration-to-roadmap/import-reviews-to-roadmap-with-csv-template.md)
* [The top reviews product metafield](https://docs.roadmap.so/reviews/storefront-and-display/the-top-reviews-product-metafield.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.roadmap.so/reviews/storefront-and-display/count-only-rated-reviews-in-star-averages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
