A catalog with a performance signal on every product
Google reads your products from the feed. Feedance sends a complete, valid feed plus the signals Google does not have on its own.
Google Product ReviewChannel · Marketing toolsFeedance builds your Google Product Review feed and adds product-level labels for score, 4T segment, price position and broken sizes, so every product carries its own performance signal.
Google reads your products from the feed. Feedance sends a complete, valid feed plus the signals Google does not have on its own.
The Google Product Reviews feed is a structured XML data source that lets merchants, review platforms, or reviews aggregators submit third-party product reviews to Google so they can be aggregated into Product Ratings -- the star rating and review count shown on Shopping ads and free product listings. It is a distinct program from a Google Merchant Center shopping/product feed: a product feed describes what you sell (title, price, availability, GTIN), while a product reviews feed describes what customers said about it (review text, rating, reviewer, timestamp). Google's own developer documentation names this format the "Product Review Feed" and publishes a dedicated XML schema (currently version 2.4) for it, separate from the shopping feed specification.
You can supply this feed either directly through Google Merchant Center or via a Google-supported reviews aggregator that submits reviews to Google on your behalf.
Google's Product Ratings program states its purpose plainly: it lets you "display aggregated reviews for your products to customers shopping on Google," with ratings shown as 1-to-5 stars alongside the total review count in both paid Shopping ads and free product listings. Retailers use this because shoppers weigh star ratings heavily before clicking through, and a listing with visible product ratings stands out next to competitors that show none.
But the program has a hard eligibility gate: Google requires a minimum of 50 reviews across all of your products before any product ratings will display on Shopping or Google Ads -- below that threshold, submitting a feed doesn't yet produce visible stars, no matter how well-formed the file is. Feedance keeps your review data source current so that once you clear that threshold, your aggregated ratings reflect your actual, up-to-date review volume rather than a stale one-time export.
It's worth separating two things Google documents independently, since they're easy to conflate. The XML product reviews feed covered on this page feeds Google's Product Ratings program: aggregated stars and review counts surfaced specifically on Google Shopping ads and free product listings, sourced from a feed you submit to Merchant Center or through an aggregator. Separately, Google Search can also show review-snippet rich results in organic search listings, but those are driven by Review/AggregateRating schema.org structured data markup embedded in your own webpage's HTML -- a page-level mechanism governed by Google Search's structured data guidelines, not by this feed format. A merchant can run one, both, or neither; they use different data formats, different submission paths, and surface in different places, so a product reviews XML feed alone does not create organic review-snippet rich results, and structured data markup alone does not populate Shopping-ad star ratings.
The product reviews feed must be a validated XML file. Google's schema (currently version 2.4, published at google.com/shopping/reviews/schema/product/2.4/product_reviews.xsd) defines a single root <feed> element containing, in order: an optional <aggregator> element, a required <publisher> element, an optional <reviews> container holding your individual <review> entries, and an optional <deleted_reviews> container for retracting previously submitted reviews by ID.
You can validate a feed before submitting it with a standard XML schema validator, for example:
xmllint --schema http://www.google.com/shopping/reviews/schema/product/2.4/product_reviews.xsd --noout file.xml
Once validated, Google accepts the file through Merchant Center in three ways: a scheduled fetch from a URL you host beginning with http://, https://, or sftp:// (Google's recommended method); an upload pushed directly via SFTP or Google Cloud Storage; or a one-off manual upload from your computer. Individual files must stay under 4 GB, and if you split your catalog of reviews across multiple XML files, they can be packaged into a single .zip containing up to 5,000 files, also capped at 4 GB total.
The table below lists the core elements of Google's product review feed schema, using Google's own element names exactly as documented and shown in Google's official sample feed.
| Field | Required | Format | Notes |
|---|---|---|---|
review_id | Yes | Non-empty string, unique and permanent | Mandatory for every review since July 8, 2024; reviews submitted without one fail processing entirely |
reviewer / name | Yes | Non-empty string | The reviewer's display name or alias; supports an is_anonymous attribute |
review_timestamp | Yes | ISO 8601 date-time, e.g. 2014-04-21T11:07:07-06:00 | When the review was originally written |
content | Yes | Non-empty string | The full body text of the review |
review_url | Yes | HTTP(S) URL, with a type attribute of singleton or group | Links back to where the review is published |
ratings / overall | Yes | Decimal, with min/max attributes defining the scale (commonly 1-5) | The overall numeric score given by the reviewer |
products / product_url | Yes | HTTP(S) URL | Links the review to the live page of the product being reviewed |
product_ids (gtins, mpns, skus, brands) | Recommended | Strings; GTIN is the strongest identifier, MPN must be paired with brand | Used to match the review to the corresponding product in your Merchant Center catalog; reviews Google can't match to a product will not be used |
title | Optional | Non-empty string | Review headline |
pros / cons | Optional | Sequence of pro/con string elements | Specific reviewer-written positives and negatives; Google discourages boilerplate text like "pro:" unless the reviewer wrote it themselves |
is_verified_purchase / is_incentivized_review | Optional | Boolean | Disclosure flags; incentivized reviews must be marked as such under Google's Product Ratings policies |
collection_method | Optional | unsolicited or post_fulfillment | How the review was gathered |
review_id are mapped to Google's required elements, and product identifiers (GTIN preferred, or brand + MPN / SKU) are attached under product_ids so Google can match each review to the right catalog item.Google's stated requirement is to "send your full reviews data source at least once a month, or more frequently if possible" -- monthly is the documented floor for maintaining program eligibility, not a recommended target. Since new reviews only count toward your ratings once they're present in a submitted feed, stores that collect reviews continuously benefit from updating weekly or even daily so recent feedback reflects in your star rating without a month-long lag. Feedance can run the export on a fixed recurring schedule so a stale feed never becomes the reason product ratings stop serving.
Merchant Center's Product Reviews Diagnostics sorts every submitted review into one of three states: Ready to serve (processed successfully with all recommended identifiers), Needs review (processed but missing recommended values), or Disapproved (failed to process and won't display until fixed). The table below lists specific errors and warnings Google documents in that diagnostics view.
| Error / warning | Category | Cause |
|---|---|---|
| Missing review_id | Disapproved (error) | Every review has required a permanent, unique review_id since July 8, 2024; reviews without one fail processing outright |
| Missing content, rating, or timestamp | Disapproved (error) | One of the required review-level elements (content, ratings/overall, review_timestamp) is absent |
| Incorrect time stamp | Disapproved (error) | review_timestamp isn't valid ISO 8601 |
| Invalid XML character / start tag / value; parsing failed; wrong top-level XML tag | Disapproved (error) | The file itself is malformed XML or doesn't start with the required <feed> root element |
| Unsupported collection method, rating, or tags | Disapproved (error) | A value falls outside what the schema allows -- for example a collection_method other than unsolicited or post_fulfillment |
| Missing product_id / product_url | Needs review (warning) | No usable identifier links the review to a product; Google can't match it to your catalog |
| Missing reviewer name / review_url | Needs review (warning) | A recommended but non-blocking element is absent |
| Comment contains URL / unsupported comment characters | Needs review (warning) | Review text includes content Google flags as promotional or malformed |
Separately, reviews that pass structurally can still be excluded on quality or policy grounds -- Google's Product Ratings policies remove reviews written by employees or anyone with a vested interest, spam or gibberish text, undisclosed incentivized reviews, and content that is offensive, illegal, or primarily AI-generated.
Always include a stable review_id. It must be permanent and unique per review -- reusing or omitting it causes outright processing failure, not just a warning.
Send GTINs whenever you have them. Google's own schema documentation calls GTIN the strongest match between a review and a catalog product; brand + MPN or SKU are fallbacks, but unmatched reviews are simply not used.
Disclose incentivized reviews honestly. Set is_incentivized_review accurately rather than omitting it -- undisclosed incentivization is a documented policy violation, not just a missing optional field.
Write real pros and cons, not boilerplate. Google explicitly discourages generic "pro:"/"con:" filler and rewards substantive, specific reviewer-written detail.
Submit more often than the monthly floor. Monthly is the minimum required cadence to stay eligible, not a target -- fresher submissions mean recent reviews count toward your visible rating sooner.
Validate before you submit. Running the file through an XML schema validator against Google's published .xsd catches structural errors before they show up as Disapproved items in Merchant Center.
Track your 50-review threshold. If you're near the eligibility line, prioritize collecting the reviews you're missing over polishing feed formatting -- ratings simply won't display below 50 total reviews regardless of feed quality.
What format does Google's product reviews feed use?
XML, validated against Google's published schema (currently version 2.4), with a root <feed> element.
Is this the same as my Google Merchant Center shopping feed?
No. A shopping/product feed describes your catalog (price, availability, GTIN); the product reviews feed is a separate XML format carrying reviewer, rating and review-text data, submitted through its own section of Merchant Center.
How many reviews do I need before ratings show up?
Google requires a minimum of 50 reviews across all your products before product ratings will display on Shopping ads or free listings.
How often must I submit the feed?
At least once a month to remain eligible; more frequent submissions are recommended so recent reviews count sooner.
Do I have to submit directly, or can someone do it for me?
Either -- you can submit directly through Merchant Center, or use a Google-supported reviews aggregator that submits on your behalf.
What happens if a review is missing a review_id?
Since July 8, 2024, review_id is mandatory; reviews without one fail processing and won't be used.
Does this feed create the review-snippet stars I sometimes see in organic Google Search results?
No. Those come from separate schema.org Review/AggregateRating structured data markup on your own webpages -- this XML feed powers Product Ratings on Shopping ads and free listings instead.
The Google Product Reviews feed lets merchants and review platforms send product reviews to Google for its Product Ratings program. The reviews are combined into a star rating and review count that appear on Shopping ads and free product listings, helping shoppers judge products before they click.
The reviews feed is separate from the regular Merchant Center product feed. A product feed describes what you sell, such as title, price and availability, while the reviews feed describes what customers said: rating, review text, reviewer, date and the product identifiers that link each review to the right item.
Reviews are submitted as an XML file following Google's Product Review Feed schema, either directly through Google Merchant Center or through a Google-supported reviews aggregator that sends them on the merchant's behalf. Ratings only start to appear once enough reviews have been collected across the catalog, so the feed alone does not guarantee visible stars.
Matching is where feed quality matters most. Reviews must point to the correct products through GTINs, SKUs, brand or product URLs, or Google cannot attach them to listings. Regular updates that add new reviews and remove invalid ones keep ratings accurate. Product Ratings are also different from review snippets in organic search, which come from structured data on the merchant's own pages.
Connect your feed and GA4. We show Product Score, 4T, Price War and Broken Size on your own catalog.