Google Merchant API 2026: Content API Shuts Down

On August 18, 2026, Google draws a line: on that day the Content API for Shopping is permanently shut down (Google for Developers). Anyone who submits product data programmatically to Google Merchant Center must have switched to the new Merchant API by then - otherwise product listings can quietly drop out of Google Shopping and Performance Max campaigns. In parallel, Google is tightening the feed rules in 2026: a higher minimum image resolution, new shipping attributes at the product level and a new video attribute. This guide sorts out the dates, explains what really breaks for your online shop, and shows how to set up your feeds for the future now.

What Happens in Google Merchant Center in 2026

In 2026 two changes run in parallel in Merchant Center, and they are often confused. The first is a technical switch: the old Content API for Shopping is replaced by the new Merchant API. The second is a content-level tightening of the feed rules: Google raises the minimum image resolution, introduces new shipping attributes at the product level and launches a video attribute. The two topics affect different people in a business - the API concerns development or the feed tool, the feed rules concern marketing and product maintenance - but they point to the same goal: staying visible in Google Shopping.

An important distinction: the Content API shutdown only affects programmatic integrations. Anyone who maintains products exclusively via manual file upload, a scheduled fetch or a Google Sheet is not directly affected by the API switch (Google Merchant Center). The new feed rules, by contrast, apply to all feeds, regardless of how the data reaches Merchant Center. It is exactly this distinction that decides how urgent your action is.

The Content API for Shopping Ends on August 18, 2026

For years the Content API for Shopping was the standard interface for automatically submitting product data, prices, availability and stock information to Merchant Center. Google is retiring exactly this interface on August 18, 2026 (Google for Developers). Applications that keep calling the Content API after that will no longer receive responses - there is no transition period beyond this date (Google for Developers). One intermediate step has already passed: the beta version of the new interface, Merchant API v1beta, was discontinued back on February 28, 2026, so the stable v1 version has been authoritative since then (Google for Developers).

For a shop that relies on the API, a missed switch essentially means the data flow breaks: prices and stock are no longer updated, new items no longer appear, sold-out products stay visible online - and in case of doubt the affected offers are disapproved. Because around 76 percent of retail search advertising budgets go to Google Shopping (scubemarketing), such a break hits the paid channel at a sensitive spot. The tricky part is that the outage need not show immediately: as long as the last submitted feed state sits in Merchant Center, ads appear to keep running - until outdated prices and stock trigger complaints and the offers gradually drop out of the results. The risk is therefore not theoretical but directly tied to revenue.

• Product synchronization: without an active API connection, new and changed items no longer reach Merchant Center automatically.
• Prices and availability: real-time or minute-by-minute updates stop as soon as the interface no longer responds.
• Custom middleware: self-developed connectors and older plugins built on the Content API must be ported to the Merchant API.
• Reporting and diagnostics: the programmatic retrieval of status and error data will also run through the new interface in future.

Merchant API: What the New Interface Does Better

The Merchant API is not just a successor with a new name but a modular system of several sub-APIs - for products, inventory, accounts, data sources and reporting, for example. This structure makes it possible to connect only the areas a shop really needs. For businesses whose ads run through Google Ads, it is also relevant that Google is gradually bringing the Merchant API into the scripting and automation world of Google Ads. Anyone still working with self-built scripts on the old interface today should put this dependency on the list early, because otherwise it only surfaces shortly before the deadline.

New Feed Rules 2026: Images, Shipping and Video

Independently of the API, Google updated the product data specification effective April 14, 2026 (Google Merchant Center). These changes affect every feed - including those maintained via Google Sheet or manually. At their core they cover three areas: higher requirements for product images, more control over shipping at the product level and a new attribute for product videos. Anyone who adjusts their feed structure early avoids warnings and later disapprovals.

Minimum Image Resolution 500 x 500: Images Decide Visibility

The most noticeable change concerns product images. Google is raising the minimum resolution for images submitted in the feed to 500 x 500 pixels across all product categories. Warnings for this appear in Merchant Center from April 14, 2026, and binding enforcement begins on January 31, 2027 (Google Merchant Center). There is time until then, but the scale of the topic is often underestimated: around 65 percent of all product disapprovals in Merchant Center are due to image-related issues (Productsup). The image is therefore not a cosmetic detail but a central reason for disapproval.

The distinction between requirement and recommendation matters. The 500 x 500 pixels are the future floor; recommended, however, are images of around 1500 x 1500 pixels or more, to achieve a high-quality effect across all ad formats - from the small Shopping thumbnail to large-scale display (Google Merchant Center). Google also states that it will automatically upscale some images that are too small to avoid immediate disapproval (Google Merchant Center). You should not rely on this stopgap, though, because upscaled images tend to lose sharpness.

Shipping at the Product Level: Using the New Attributes Correctly

The second block of the specification update expands shipping control at the product level. Instead of only storing blanket shipping rules for the whole account, conditions can now be mapped more finely per item. For this, Google introduces several new attributes effective April 14, 2026 (Google Merchant Center):

• Handling cutoff time: a daily time by which an order is still accepted for same-day shipping - helpful for keeping delivery promises realistic.
• Minimum order value: the amount from which an item can be ordered and shipped - relevant for assortments with a minimum purchase.
• Loyalty details (loyalty program label and loyalty tier label): two new sub-attributes in the shipping field that let you indicate a loyalty program's shipping benefits per product and tier.

These fields sound like detail work but act directly on the purchase decision: a visibly realistic delivery date and transparent shipping conditions tend to reduce cart abandonment. The prerequisite is that the data comes correctly from the inventory system. Anyone who already controls shipping and pricing logic from the ERP should connect this source cleanly - just as is the case with customer-specific prices from the ERP.

Video Link: The New Product Video Attribute

As a third innovation, Google introduces the optional attribute for a product video link. Submission is possible from April 14, 2026, and from June 30, 2026 the videos are also served and Google begins the associated quality and policy checks (Google Merchant Center). A faulty video then prevents the video from serving but does not impair the actual product offer (Google Merchant Center).

For products that need explanation this is an opportunity: a short video showing size, material or use can support the purchase decision without users having to leave the product page. Because the attribute is optional, there is no obligation - but there is an early advantage for everyone who already has suitable videos or can produce them affordably.

Migration Roadmap: Switch Safely in Five Steps

Whether a technical switch or pure feed maintenance - a structured approach prevents last-minute rush before the deadline. The following steps have proven themselves in practice:

1. Inventory of connections: first clarify how your product data reaches Merchant Center today - via API, through a feed tool, via Google Sheet or manually. Only API connections require migration.
2. Check the data source: verify that inventory management, PIM system or shop deliver the new fields cleanly - especially images of sufficient size and the shipping details.
3. Switch to the Merchant API: port your own connectors to version v1 or check whether your shop system or feed service already handles the switch.
4. Update feed attributes: raise images to at least 500 x 500, better 1500 x 1500 pixels, and add the new shipping and video attributes where they fit.
5. Test and monitor: check the feed in the Merchant Center diagnostics, fix warnings early and keep the dates until August 18, 2026 in view.

Set Up Your Feeds for the Future Now

The Content API shutdown and the new feed rules coincide in 2026 - which makes this the right moment to tidy up the entire data path to Google Shopping once and for all. Instead of treating both fronts separately, it pays to think of connection, data quality and feed maintenance as one system. This is exactly where XICTRON's Google Merchant Center integration comes in.

The earlier the switch is in place and the more cleanly the feed attributes are maintained, the smaller the risk that ads stand still shortly before or after August 18, 2026. We review your current connection, plan the migration and set up the new feed rules together. Talk to our team to build your roadmap for Merchant Center 2026.