Google has quietly removed a significant automation limitation from Merchant Center: merchants can now upload and manage product reviews through the Merchant API. Until this documentation change, Google's Product Reviews guidance explicitly said API submissions were not supported, leaving merchants and review platforms dependent on other submission methods. The new API path makes Product Ratings substantially easier to operate programmatically, particularly for retailers managing large or frequently changing review datasets.
The change was reported by Anu Adegbola at Search Engine Land on September 18, 2026. Google's current Merchant API Product Reviews documentation confirms that reviews can now be created, retrieved, listed and deleted through the API, providing a full programmatic workflow rather than merely a new upload endpoint.
Product reviews can now become an automated data pipeline
The practical change is straightforward but important. Google's Merchant API exposes a Product Reviews resource and an accounts.productreviews.insert method that can create or update a review. Merchants first create or retrieve a review data source, then submit the review resource against that source. Google notes that an insert request overwrites the entire Product Review resource, so integrations need to include all required review details when updating an existing entry.
The API is not limited to sending new reviews. Google also documents accounts.productreviews.get for retrieving an individual review, productreviews.list for viewing reviews associated with the account, and accounts.productreviews.delete for removing a review. Together, those operations allow ecommerce systems and review platforms to synchronize review data with Merchant Center rather than treating Google as a separate file-upload destination.
That matters for merchants whose review inventories change constantly. A retailer collecting thousands of reviews across a large catalog can potentially connect its review database or review-management platform directly to Merchant Center, automate additions and updates, and remove obsolete entries without repeatedly generating and transferring static review files.
API access does not remove Product Ratings requirements
The new submission method should not be confused with automatic eligibility for Google's Product Ratings program. Google's documentation still requires participating accounts to be enrolled in Product Ratings, and Search Engine Land notes that merchants need at least 50 product reviews before applying. Google's revised workflow also clarifies that a Google agent reviews the application and enables the Merchant Center account for the program.
The Merchant API documentation lists additional prerequisites for programmatic review management. The account needs an active product review feed and enrollment in the Product Ratings program, and Google currently instructs developers seeking Product Reviews API access to submit an allowlisting request through the Shopping API support form. In other words, the API creates a new technical submission channel; it does not eliminate Google's onboarding, quality or policy controls.
The API supports more than simple star ratings
Product reviews are valuable to Google because they provide structured information behind the ratings shoppers see around products. Google's Product Ratings ecosystem can draw review information from merchants, review aggregators, review sites and Google users. The Merchant API turns merchant-supplied review data into a resource that can be managed with the same kinds of programmatic operations developers expect from modern commerce infrastructure.
That distinction is important for larger ecommerce organizations. A five-star number displayed in a dashboard is only the visible summary of a broader review record. Automated review pipelines need to preserve identifiers, review content, ratings, timestamps and product matching information accurately so Google can associate the review with the correct item. API automation reduces manual transfer work, but it also makes data quality and validation more important because errors can now propagate at software speed.
This is especially useful for review platforms and large catalogs
For a small merchant with a limited number of reviews, manual or scheduled file-based submission may remain perfectly adequate. The strongest benefit appears at scale. Marketplaces, large retailers, agencies and review technology providers can integrate Merchant Center review management into existing systems rather than maintaining a parallel export-and-upload process.
That can improve freshness as well as operational efficiency. When a review is added, corrected or removed in a merchant's source system, an API-based workflow can reflect the change in the Google submission pipeline without waiting for a manually prepared file. Developers can also retrieve and list review resources programmatically, making monitoring and reconciliation easier to incorporate into internal tools.
The change therefore fits a broader shift in commerce infrastructure toward machine-to-machine management. Product catalogs, inventory, promotions and other Merchant Center resources have increasingly moved into API-driven workflows. Reviews — an important trust and merchandising signal — can now participate in that same automation layer.
Google is also modernizing the Product Reviews documentation
Search Engine Land notes that the API addition arrived as part of a broader refresh of Google's Product Reviews guidance. Merchant Center navigation instructions have been updated for the current interface, with merchants directed through Products & store, Reviews, Product reviews and the product-review-source management area. Google has also shifted some terminology from “feed submission” toward “data source submission,” bringing the documentation closer to the language used throughout the newer Merchant Center architecture.
The revised guidance also adds instructions for products disapproved because of policy violations, including Healthcare and Medicine policies. Merchants are directed to resolve the underlying policy issue and then request a review of the affected products. Those changes are separate from API support, but together they indicate a broader cleanup of the Product Ratings workflow rather than a single isolated endpoint announcement.
What ecommerce teams should do now
Merchants already participating in Product Ratings should first determine whether API integration would actually improve their workflow. Teams with automated review collection, large catalogs or frequent review changes have the clearest reason to evaluate it. The technical starting point is Google's Product Reviews Merchant API guide, including its eligibility and allowlisting requirements, rather than simply switching off an existing review feed.
Developers should also account for the overwrite behavior of the insert operation and maintain reliable local mappings between Merchant Center data-source names and review records. An automation pipeline that sends incomplete updates can create new data-quality problems even while solving the manual-upload problem. Logging, validation and reconciliation should therefore be part of any production implementation.
For agencies and review platforms, the update is potentially more strategic. API support makes it easier to build review synchronization into a managed ecommerce stack, turning Merchant Center Product Ratings from a periodic feed task into an ongoing service. That can reduce operational overhead across multiple accounts once access and program requirements are satisfied.
A small documentation change with a meaningful automation payoff
This is not a new ranking system or a dramatic redesign of Google Shopping. Shoppers may never notice that the submission mechanism behind product ratings has changed. For ecommerce operations teams, however, the difference between “API not supported” and a documented create, read, list and delete workflow is substantial.
Google has effectively opened Product Reviews to the same kind of programmable management already expected elsewhere in modern commerce systems. The immediate opportunity is operational: fewer manual review-transfer steps, more scalable synchronization and better integration between review platforms and Merchant Center. For merchants handling reviews at volume, that quiet documentation update can translate into a much cleaner Product Ratings pipeline.