Google has updated its Merchant Center documentation to confirm that product reviews can now be uploaded via the Merchant Center API. The help document previously stated explicitly that API support was not available for product review data sources. That line has been replaced with a straightforward instruction: "Add product reviews using API." It is a small documentation change with a meaningful operational implication for anyone running Shopping campaigns at any serious scale.
Why This Matters More Than It Looks
Product reviews in Merchant Center feed into the star ratings that appear on Shopping ads. Those ratings are not decorative. They influence click-through rate directly, and for Performance Max campaigns where Google controls ad placement and format selection, the quality of your feed signals - including review data - shapes how the system optimises.
Until now, getting product review data into Merchant Center required either a manual upload or a scheduled feed file. Both approaches have limitations. Manual uploads are not scalable if your catalogue or review volume changes frequently. Scheduled feed files work, but they introduce latency and add another file management dependency to an already complex feed stack.
API access changes the dynamic. You can now push review data programmatically, on your own trigger conditions, without waiting for a scheduled fetch cycle. For retailers with large catalogues, high review velocity, or seasonal peaks where new reviews accumulate quickly, that matters.
The Connection Between Review Freshness and Ad Performance
There is a meaningful difference between having product reviews in your Merchant Center account and having current, accurate product reviews there. A review dataset that was uploaded six weeks ago and has not been refreshed may be showing outdated ratings in your Shopping listings. If a product has received a wave of new positive reviews since the last feed upload, those are not appearing in your ads yet.
This is not a hypothetical edge case. For advertisers in categories where reviews move fast - consumer electronics, health products, kitchenware, anything that gets gifted seasonally - a stale review feed is a real gap between your actual product reputation and what Google is showing. API access closes that gap by allowing near real-time synchronisation.
From a bidding perspective, this has downstream consequences. Performance Max campaigns optimise toward conversion signals, but the assets and feed data surrounding those signals affect the quality of impressions the system generates. A product listing with a higher, more current star rating is a better asset. Keeping that data fresh is part of feed hygiene, not a nice-to-have.
What This Changes for Feed Management Strategy
If you are currently using a scheduled feed file for product reviews, the API route is worth evaluating - not because file feeds are broken, but because they require manual maintenance of a URL endpoint and are subject to whatever fetch frequency Merchant Center allows. API pushes are initiated by your system, which means you control timing.
For agencies managing multiple retailer accounts, this also opens the door to more consistent review data management across a client portfolio. Rather than tracking separate feed URLs per client and monitoring for fetch failures, a centralised API integration can handle review uploads across accounts with proper error handling built in. That reduces the operational overhead that tends to cause feed data to drift.
The practical starting point is to audit where your product review data currently sits and how it reaches Merchant Center. If you are relying on a platform-native integration or a third-party review aggregator that handles the upload, check whether they are planning to shift to the API method. If you manage feeds in-house, the API documentation is now updated and the capability is there to use.
Performance Max and the Role of Rich Feed Signals
Performance Max campaigns draw on everything in your feed when assembling Shopping placements. Product titles, descriptions, images, prices, availability, and review ratings are all signals the system uses when deciding how to represent a product and which queries to match against. Thin or outdated signals push the system toward lower-quality matching.
This is particularly relevant as Performance Max has expanded its Shopping inventory reach. The campaign type surfaces products across Search, Shopping, Display, and YouTube placements, adjusting format based on context. In each of those placements, social proof signals - ratings and review counts - carry weight with users deciding whether to click. Keeping those signals current is not separate from campaign management; it is part of it.
Advertisers running Performance Max for Shopping should think about feed quality as foundational to campaign performance. The more accurate and complete your product data, the better the system can do its job. Review data via the API is one more lever in that direction.
The Practical Steps Worth Taking Now
First, check your current review data in Merchant Center. Go to the product reviews section and look at when the data was last updated and whether the ratings shown match what your review platform is currently reporting. Any significant discrepancy is a gap worth closing.
Second, if you manage feeds via a developer or a feed management platform, flag the API change. The Merchant Center API documentation now confirms support for product review data sources, and any integration built before this change would have worked around that limitation. There may be a cleaner path available now.
Third, think about update frequency relative to your review volume. A retailer adding a handful of reviews per week does not need the same refresh cadence as one processing hundreds. Build your update logic around actual business need rather than defaulting to a daily scheduled file out of habit. The API gives you flexibility - use it based on what your data actually requires.