Shopify review stars in Google: what the markup needs and what it cannot promise
How star ratings reach Google for a Shopify product: Google's review and product snippet rules, what reviews apps print, and how to test.
6 min read
Contents · 7 sections
- What puts stars next to a Shopify product in Google?
- What are Google's rules for the reviews themselves?
- Does the self-serving review rule apply to a product page?
- What does a reviews app actually output?
- How do you check what your product page prints?
- When do stars not show even though the markup is valid?
- What to fix first
What puts stars next to a Shopify product in Google?
Two things have to be true on the same URL. The page must show customer reviews or an average rating to the shopper, and the page must carry structured data that describes those same reviews. When Google finds valid review or rating markup, its review snippet documentation says it "may" show a rich snippet with stars and summary information. The wording is permissive on purpose: valid markup makes a page eligible, and Google decides whether to display it.
For a product page the relevant feature is the product snippet. Its requirements are short. A Product needs a name, and one of review, aggregateRating or offers. The page can pass with offers alone, but the documentation notes that the Rich Results Test may then report a warning, because star ratings come from the other two. If stars are the goal, aggregateRating, review or both have to be present.
What are Google's rules for the reviews themselves?
The review snippet guidelines are where most Shopify stores go wrong, and they are worth reading in full. The ones that matter for a store:
- The reviews must be visible. The page has to make it obvious that it contains review content. If you mark up reviews, shoppers should be able to see the text and the rating. If you mark up an
AggregateRating, they should be able to see that aggregate rating on the page. - One specific item. Provide review information about a specific product, not about a category or a list of items. A collection page that says "4.8 stars across our range" is not what the feature is for.
- Several reviews need an aggregate. If you include multiple individual reviews, the guidelines say to include an aggregate rating of those reviews as well.
- No borrowed ratings. The guidelines say not to aggregate reviews or ratings from other websites.
- Nothing fake or undisclosed. Reviews that are not based on a genuine experience, or that were written in exchange for money, discounts, vouchers or free products without clear and prominent disclosure, do not belong on the page or in its markup.
- A valid reviewer name. The product snippet documentation gives "50% off on Black Friday" as an example of what is not a valid reviewer name, and "James Smith" as an example of what is.
Google also warns that a site violating the guidelines may face a manual action, which you can then fix and submit for reconsideration. That is the reason this article keeps repeating one rule: markup describes what is on the page and nothing else.
Does the self-serving review rule apply to a product page?
It is easy to over-read. The documentation's additional guidelines for self-serving reviews are written for review snippets about a local business or an organization: if the entity being reviewed controls the reviews about itself, its pages using LocalBusiness or another Organization type are ineligible for star reviews. Putting your store's own star rating on your homepage under Organization markup falls on the wrong side of that line.
Reviews of a specific product, nested inside Product markup on that product's page, are the case the product snippet documentation describes. Keep the two apart: put the ratings on the product they belong to, and do not add an organisation-level rating to the homepage.
What does a reviews app actually output?
This differs by app, theme and version, so do not assume. Some apps print their own JSON-LD, some write review data into Shopify metafields that your theme must print, and some render the review widget only after the page loads in the browser. Each of these has a different failure mode:
| What the app does | What to check |
|---|---|
Prints its own Product block with aggregateRating | Your theme may also print a Product block, so the page can carry two. Look for duplicates. |
| Writes ratings to metafields | Nothing appears in search until the theme prints them into the structured data. |
| Loads the widget with JavaScript | Google's product snippet documentation says dynamically generated Product markup can make Shopping crawls less frequent and less reliable. Prefer markup that is in the initial HTML. |
| Shows stars but prints no markup | Shoppers see stars; Google has nothing to parse. |
The decision between an app and theme code is its own topic, covered in theme customisation versus apps. The base Product markup your theme prints is covered in the product schema guide.
How do you check what your product page prints?
Five minutes, no tools beyond a browser:
- Open a product that has reviews and view the page source, not the inspector, which shows the page after scripts ran.
- Search for
application/ld+json. Count the blocks whose type isProduct. More than one is worth investigating. - In the
Productblock, look foraggregateRatingandreview. If neither is there, the app's data never reached the markup. - Compare with the page. The rating and count in the markup should match what a shopper sees, and the reviews should be on that page, not behind a link.
- Paste the URL into Google's Rich Results Test. It shows the product snippet items it parsed and any errors or warnings. Fix critical errors first; the documentation says non-critical issues are not needed for eligibility.
Then deploy to a few pages, and use the URL Inspection tool in Search Console to see how Google fetched the page. Google's own guidance is to allow time for recrawling: it can take several days after changes for Google to pick them up.
When do stars not show even though the markup is valid?
Often. The documentation says only that the feature "may" appear, and that the actual appearance in search results may differ from the test preview. Eligibility is necessary; it is not a promise. We do not know how often a valid page gets stars, and no source we have read gives a number, so we will not make one up.
What you can control is the list above: real reviews, visible on the page, for one product, with markup that matches. Check in Search Console after a few weeks and compare product pages that show stars with those that do not, looking for a pattern in the app, the template or the review count.
What to fix first
Start with one best-selling product that has real reviews. Check its source against the five steps above; if the rating is missing from the markup, fix the app setting or the theme snippet for that one template, then test it before touching the rest. That is usually an afternoon, not a project. If you would rather have someone read your store and tell you what the markup is doing across the catalogue, that is what the Store Teardown is for.