Google Shopping Stars. The PLA Playbook

Where stars actually appear

Three different Google features put stars next to a product or a store, and each reads a different source.

The practical consequence: a merchant who wants stars in all three places needs a product reviews feed (or an aggregator that sends one), a store-level review source, and clean on-page markup. They share the same underlying reviews but are three separate pieces of plumbing. The on-page half is covered in depth in the review schema and rich results handbook; this guide concentrates on the feed side, which is where Shopping stars live.

Qualifying for Product Ratings

Google offers two routes into the programme. If you already use a reviews platform that appears on Google's list of supported aggregators, that platform can submit your reviews through its own integration with Google, outside Merchant Center. If you don't, you register interest in Product Ratings, and once your account is enabled you upload a product reviews data source under Products, then Product reviews, in Merchant Center. The file follows Google's XML product review feed schema.

The account rules catch people out. The domains in each review's product_url must match the domain registered in your Merchant Center account, and you need a standalone Merchant Center account or sub-account with administrative access. A multi-client account will not do. Agencies that manage several brands from one MCA should plan for this before promising stars to a client.

The onboarding review is real. Google specialists check the data source for quality and policy compliance before it goes live. While that runs, a direct-feed merchant sees an "inactive" eligibility status, which is expected and not a rejection. Merchants who share reviews only through an aggregator get no eligibility panel at all; the confirmation is simply seeing stars on the ads.

The content policies decide which reviews survive. Google's Product Ratings policies prohibit reviews primarily generated by an automated program or AI, reviews from employees or anyone with a vested interest, and low-quality or off-topic reviews. Incentivised reviews are allowed only if the incentive does not depend on sentiment, and you must flag them with the is_incentivized_review attribute. Retailers are expected to share all their reviews, not a selected subset. If your collection flow gates unhappy customers away from the review form, you have a policy problem, not a volume problem. The wider rules on incentives are in incentivising reviews without breaking platform policy.

A 90-day plan to reach the 50-review floor

Fifty reviews across the catalogue is a low bar for an established store and a real one for a new brand or a store that has never asked. The floor counts reviews in the feed, so the job is steady collection from real buyers, not a burst. The plan below assumes a store starting from close to zero and a post-purchase request as the main engine. For the mechanics of the request itself, see how to ask customers for reviews.

If your order volume makes 50 reviews in 90 days unrealistic, don't pad the feed. Low-volume stores are better served by making the reviews they do have visible on the PDP and in search while collection catches up. Social proof for a new store with no reviews covers the interim options.

Schema, feeds and what each one does

Three markup rules matter most for product pages. The rating you mark up must be readily visible to the user on that page, so a hidden AggregateRating with no visible stars or reviews breaks the guideline. AggregateRating needs ratingValue and at least one of ratingCount or reviewCount. And Google's guidelines say not to aggregate reviews or ratings from other websites, which means a Trustpilot or Google Business score displayed on your PDP should not be folded into your product's AggregateRating. The minimum honest shape looks like this:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Jute Tote Bag",
  "gtin13": "0000000000000",
  "brand": { "@type": "Brand", "name": "Your Brand" },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": 4.6,
    "reviewCount": 58
  }
}

The numbers in that snippet are placeholders. The rule that matters is that they are computed from the reviews shown on that page, and that the aggregate is omitted entirely when a product has no rated reviews rather than padded. For the fuller field list, see aggregate-rating schema and rich snippets.

Where a UGC and reviews platform fits

It is worth being exact about what a platform does and does not handle, because "we have a reviews app" is the most common false assumption behind missing Shopping stars.

What Idukki does today. On Shopify, Idukki can send a post-purchase review request triggered by the order or its fulfilment status (in transit, out for delivery or delivered), with a configurable delay, linking to a hosted form that accepts photos and video. Review requests are off by default and need both the merchant's opt-in and Idukki's approval before any shopper is emailed. Reviews land in a moderation inbox alongside imported sources, and the Product Rating Stars theme block renders stars on the PDP and can emit Product, AggregateRating and Review JSON-LD from those reviews, omitting the aggregate when nothing is rated. Details are on the reviews page.

What it does not do for you. Idukki is not on Google's list of supported Product Ratings aggregators, and it does not push anything to Google. It can generate a product reviews feed in Google's XML schema (version 2.4) from the approved, rated, product-tagged reviews collected on your store; you switch the feed on, add its URL as a data source in Merchant Center, and Google fetches it. Imported Google, Trustpilot, TripAdvisor and Feefo reviews are left out, and so are Judge.me reviews, because Judge.me submits those to Google itself. You still need Product Ratings approval and the 50-review floor.

The combination that works. Google's supported list includes several Shopify review apps, Judge.me among them, alongside Bazaarvoice, PowerReviews, Trustpilot, Yotpo, Okendo, Loox, Stamped, Reviews.io and Feefo. Idukki can connect a Judge.me account and import its product reviews, with their photos and video, auto-tagged to the matching products. That lets Judge.me handle the Google submission while the same reviews power shoppable galleries on site. Whatever the pairing, make sure only one system is the source of truth for the feed so reviews are not submitted twice.

Recovering disappeared stars

Stars that were live and then vanish almost always trace to one of a handful of causes, most of them mechanical. Google's own troubleshooting guidance names incomplete onboarding, data source errors or a feed that stopped processing, a mismatched domain, and reviews that are eligible but not matching. Work through the list below before you assume a penalty.

Migrations deserve their own checklist. A replatform changes URLs, sometimes product IDs, and occasionally GTIN mappings on variants. Export your reviews with their product identifiers before the move, map old URLs to new ones in the reviews feed, and keep the monthly upload running through the cutover. The wider migration sequence is in the replatforming UGC migration playbook.

Freshness keeps you eligible. Each monthly upload must contain updated reviews, so a store whose collection has stalled can drift out of the programme even with a large historical count. See why fresh reviews win.