Google is sunsetting the Content API, with a required migration to the Merchant API by August 18, 2026.
Feedonomics will migrate customers with Google feeds to the Merchant API before the transition date — no action is required from customers.
For other merchants, failure to migrate in time can disrupt product data, reduce visibility, and impact Google Shopping performance.
The Merchant API introduces a more scalable and flexible way to manage product data across Google.
Google is updating how product data connects to Merchant Center, ushering in a new API with an improved design for faster product rollouts, easier updates, and new features.
As a result of this update, the Content API for Shopping is being phased out, and merchants must transition to the Merchant API by August 18, 2026. This change affects how product data is submitted, updated, and maintained across Google Shopping.
For teams using Feedonomics, the transition is already underway. Rest assured, product data continues to flow without disruption as migrations are completed in the background.
For those not using Feedonomics, now is the time to understand what’s changing and how to approach the transition efficiently.
If you’re interested in learning how to get more out of your ad spend, check out our webinar as well.
What is Google’s Merchant API and why is it replacing Content API?
Google’s Merchant API replaces the Content API as the primary way to manage product data in Merchant Center. Feedonomics supports this transition by helping merchants migrate and maintain product data without disruption.
At a high level, the Merchant API serves the same purpose. Merchants can still programmatically send product information—titles, pricing, availability—to Google Shopping.
What’s changed is how that system is structured:
A more modular, resource-based design
Improved support for automation
Emphasis on further scalability
Support for larger catalogs and complexity across channels
If you want a quick overview of how Google is thinking about these changes and where the platform is heading, this walkthrough highlights some of the newer capabilities:
At a high level, the Merchant API builds on what the Content API already handled, while expanding into areas like AI-assisted content creation through Product Studio, more flexible data source management, real-time inventory updates, and expanded reporting insights.
A more structured way to manage product data.
One of the more practical changes with the Merchant API is how product data is organized.
With the Content API, product data often moved through multiple layers: primary feeds, supplemental feeds, and rules inside Merchant Center. Each layer could influence the final output.
With the Merchant API, product data is handled through clearly defined resources, and updates are made more explicitly. That creates a more consistent path between your source data and what appears in Google Shopping.
For most teams, this shows up as:
More predictable updates
Clearer ownership of product attributes
Fewer surprises when changes are made
Why Google is changing how it handles product data.
The shift with the Merchant API aligns with how important product data has become to performance.
Google depends on accurate, well-structured data to determine which products appear in listings and ads. As catalogs grow and update more frequently, older systems become harder to maintain at scale.
The Merchant API provides a foundation that better supports:
Frequent updates
Larger catalogs
More automated workflows
For merchants, that generally translates into more stable listings and a system that keeps up with how fast ecommerce moves.
What happens if merchants don’t migrate in time?
The migration itself is manageable, but it touches several parts of your data flow. Failure to migrate in time can result in a few issues:
1. Product data can fall out of sync.
When the connection to Merchant Center breaks, updates stop flowing as expected.
A price change might not reflect in Google. Inventory updates can lag behind. Those gaps quickly create inconsistencies between your site and your listings.
What sellers can do:
Start by mapping how your product data currently reaches Merchant Center. Look for dependencies that might not be immediately obvious.
How Feedonomics helps:
Feedonomics maintains those data flows during migration, so updates continue without interruption.
2. Listing performance declines when data becomes inconsistent.
Google Shopping performance is closely tied to data accuracy.
When product data becomes inconsistent, listings can lose visibility or run into approval issues.
What sellers can do:
Monitor listings during migration and spot-check key attributes like price and availability.
How Feedonomics helps:
Feedonomics continuously validates and optimizes product data to keep listings aligned with Google’s requirements.
3. Migration coordination gets messy.
Even a straightforward API change tends to involve multiple systems.
Engineering, ecommerce, and marketing teams all have a role in making sure data flows correctly and updates are tested. Failing to migrate in time can result in a scrambled effort and mistakes that have a ripple effect across your product data and related pages and listings.
What sellers can do:
Treat migration as a cross-functional project and involve multiple teams and stakeholders. That usually leads to fewer issues during rollout.
How Feedonomics helps:
Feedonomics manages the integration layer, reducing the amount of internal coordination required.
How to know if you need to migrate to Merchant API.
Migrating to Merchant API is only necessary if you’re currently using Content API. Follow these steps to learn what your data source is, and how to complete your migration if it’s required.
Check if you’re using the Content API by opening Google Merchant Center. Go to Settings, then click Data Sources and review your “Source.” Migration is necessary if your source says "Content API."
If necessary, follow Google’s developer guide to complete the migration from Content API to Merchant API. Feedonomics customers do not need to take action, as Feedonomics handles migration for them. If any action is required, Feedonomics will notify them.
Once the new API is in place, validate that products sync correctly, attributes map cleanly, and listings remain active.
Where the Merchant API fits into product data optimization.
The Merchant API introduces new ways to improve product data within Google’s ecosystem.
Features like AI-generated content, enhanced data source management, and deeper reporting give merchants more tools to refine how listings perform on Google Shopping.
Where, the Merchant API focuses on improving individual listings within Google, Feedonomics focuses on how product data is structured, optimized, and delivered across the entire catalog and across multiple channels.
Feedonomics helps ecommerce teams:
Transform and structure large product catalogs
Apply advanced rules to improve search relevance
Align product data with the requirements of each channel
Syndicate data across marketplaces, ad platforms, and social channels
These two approaches work even better together.
Google provides more intelligence within its platform, and Feedonomics ensures the underlying data is clean, consistent, and ready to perform across every destination.
Google requires merchants to migrate from the Content API to the Merchant API by August 18, 2026. After this date, the Content API will no longer support product data updates, which means listings may stop syncing correctly with Merchant Center.
The Merchant API allows merchants to programmatically manage product listings, including attributes like pricing, availability, and titles within Google Merchant Center. It also introduces better capabilities for updating data more efficiently and integrating with automation and reporting tools.
The Merchant API replaces the Content API with a more modular, resource-based structure. It supports more efficient updates, better scalability for large catalogs, and improved handling of product data across multiple sources. In practice, this means a more consistent and flexible way to manage product listings in Google Shopping.
Yes, if migration is handled incorrectly. Product data accuracy directly impacts visibility and eligibility in Google Shopping. During migration, inconsistencies in attributes like price or availability can lead to disapprovals or reduced exposure, which can affect campaign performance.
Yes. Feedonomics manages the full migration process, including API integration, data transformation, and ongoing optimization. This allows ecommerce teams to maintain consistent product data and performance while transitioning to the Merchant API.
