--- url: 'https://www.wpconsults.com/de/google-merchant-center-requirements-2026/' language: 'de' title: 'Google Merchant Center’s 2026 Feed Rules: What WooCommerce Stores Must Fix Before the Deadlines' author: name: 'Abdullah Nouman' url: 'https://www.wpconsults.com/de/author/nouman/' date: '2026-07-06T20:56:27-05:00' modified: '2026-07-07T00:25:32-05:00' type: 'post' categories: - 'eCommerce SEO' image: 'https://www.wpconsults.com/wp-content/uploads/2026/07/google-merchant-center-requirements-2026-featured-hero-7657.avif' published: true --- # Google Merchant Center’s 2026 Feed Rules: What WooCommerce Stores Must Fix Before the Deadlines Google changed the Merchant Center product data specification in April 2026, and this round is not cosmetic: product images get a hard minimum size, product videos become a real feed attribute, and shipping data moves down to the product level. On top of that, the API your feed plugin talks to is being replaced this August. If you run a WooCommerce store, most of this is fixable in an afternoon once you know what actually changed and which date matters for each item. That is what this guide covers, with every deadline verified against Google’s own announcements. ## Wichtigste Erkenntnisse - Product images below 500×500 pixels have triggered warnings since April 14, 2026; enforcement (disapprovals) starts January 31, 2027 - The new video_link attribute went live for serving and policy validation on June 30, 2026; video errors block the video, not the product - Shipping data moved to the product level: handling cutoff time, minimum order value, and loyalty shipping labels per product - Google is retiring the legacy Content API in August 2026; keeping the Google for WooCommerce extension updated is what carries you through - A video or image warning sits in the same “Needs attention” queue as a disapproval, so check it even when sales look normal Inhaltsverzeichnis - What changed in the 2026 Merchant Center product data specification - The 500×500 image minimum: the one with a disapproval deadline - The video_link attribute: live since June 30, 2026 - Product-level shipping data: optional, but it fixes a real WooCommerce problem - The Merchant API migration: the August 2026 deadline behind the scenes - The order to fix things in a WooCommerce store - So, how urgent are the 2026 Merchant Center changes really? ## What changed in the 2026 Merchant Center product data specification Google revises the product data spec every year, but most years the changes are new optional attributes nobody is forced to touch. The [2026 update](https://support.google.com/merchants/answer/16989427), announced April 14, is different because one change carries a disapproval deadline and another rewires how your product data reaches Google at all. Here is Google’s own announcement, which is worth reading in full since it is short and every date in this article comes from it. ![Google's Merchant Center product data specification update 2026 help page announcing the new requirements and dates](https://www.wpconsults.com/wp-content/uploads/2026/07/google-merchant-center-product-data-specification-update-202-7659.avif)Google’s Merchant Center product data specification update 2026 page in the Merchant Center Help Center, the primary source for every deadline below. | Change | Warning starts | Enforcement | Who needs to act | | --- | --- | --- | --- | | 500×500 px minimum for image_link and additional_image_link | April 14, 2026 | January 31, 2027 | Any store with old or small product photos | | video_link attribute (product videos in the feed) | Technical errors from April 14, 2026 | Serving + policy validation from June 30, 2026 | Optional; stores with product videos | | Product-level shipping: handling_cutoff_time, minimum_order_value, loyalty labels | Live April 14, 2026 | Optional, no deadline | Stores whose shipping reality varies per product | | Content API for Shopping retired, replaced by Merchant API | Ongoing | August 2026 | Everyone syncing via a plugin or custom code | The four 2026 Merchant Center changes side by side, with the date warnings began, the date each is enforced, and who actually has to do something. ![Timeline of the 2026 Google Merchant Center requirements deadlines: April image warnings, June 30 video_link, August API cutoff, January 31 2027 image disapprovals](https://www.wpconsults.com/wp-content/uploads/2026/07/google-merchant-center-2026-requirements-deadline-timeline-7666.avif)The four 2026 Merchant Center dates on one timeline, from the April image warnings to the January 2027 disapproval deadline. ## The 500×500 image minimum: the one with a disapproval deadline The minimum resolution for **every product image, including additional images, rises to 500×500 pixels** across all categories and marketing methods. Warnings have been running in Merchant Center since April 14, 2026, and enforcement begins January 31, 2027, at which point undersized images can take the listing down with them. Google says it will auto-optimize some smaller images to keep products serving, and those get flagged in the Needs attention section too. I would not lean on that safety net; an upscaled thumbnail sells the product about as well as you would expect, and Google choosing your product imagery for you is not a position a store wants to be in. To find what is affected: Merchant Center, then Products, then Needs attention, click View history and look for **“Image too small for upcoming enforcement”**. In WooCommerce, the usual offenders are old products whose only photo was uploaded years ago, variation images pulled from small swatches, and feeds configured to send a thumbnail size instead of the full image. Check what your feed plugin actually sends; the fix is often changing one image-size setting, not reshooting your catalog. ![Google Merchant Center Needs attention dashboard showing a feed not syncing alert and an image too small warning under the 2026 requirements](https://www.wpconsults.com/wp-content/uploads/2026/07/google-merchant-center-2026-needs-attention-feed-dashboard-7665.avif)In the Needs attention queue, a feed that has stopped syncing and an image too small warning sit in the same list, which is why a silent break is easy to miss. ## The video_link attribute: live since June 30, 2026 Product videos are now a first-class feed attribute. You could submit [video_link](https://support.google.com/merchants/answer/15216925) from April 14, but June 30 is when submitted videos became eligible to serve and when Google started policy and quality validation on them. The failure mode is gentle, which is why it is easy to ignore: a video that fails validation stops the video from showing, not the product. Still, if you have product videos sitting on YouTube or your CDN already, wiring them into the feed is cheap enhancement work, and video-carrying listings get more surface area in Google’s shopping experiences. Check the Needs attention section for video warnings after you add them. ## Product-level shipping data: optional, but it fixes a real WooCommerce problem The 2026 spec adds **handling_cutoff_time** (the daily order-processing deadline), **minimum_order_value**, and loyalty shipping labels as per-product attributes, mirroring what was previously account-level only. This matters because account-level shipping settings lie for a lot of stores. A store shipping most items same-day but its bulky products in 3 days had to pick one story; now the bulky items can carry their own cutoff and the delivery estimates shoppers see stay honest. Nothing forces you to adopt these, but if your delivery estimates in Shopping have always been slightly wrong for a subset of products, this is the mechanism that fixes it. ## The Merchant API migration: the August 2026 deadline behind the scenes The Content API for Shopping, which is how most feed plugins have talked to Merchant Center for a decade, is being retired in favor of the Merchant API; Google already shut down the API’s beta version in February 2026 and the legacy API’s sunset lands in August 2026. If you sync WooCommerce with the official [Google for WooCommerce](https://woocommerce.com/document/google-for-woocommerce/) extension, the migration ships inside plugin updates, and WooCommerce’s guidance is to be on the current version by early August. So the action item is unglamorous: **keep the extension updated**, and if your store pins plugin versions or someone built a custom Content API integration, treat this as a real deadline, because a feed that stops syncing does not disapprove products, it silently stops updating prices and stock. That failure mode is worse than a disapproval; you find out from angry customers, not from a dashboard warning. ## The order to fix things in a WooCommerce store Merchant Center 2026 compliance, in the order that de-risks fastest 1. Update the Google for WooCommerce extension (or audit your custom API integration) 2. Pull the “Image too small” warning list from Needs attention 3. Fix undersized images: feed image-size setting first, then real replacements 4. Add product-level shipping data where your estimates have been wrong 5. Wire existing product videos into video_link and watch for warnings Work top to bottom: the API migration can silently break the whole feed, images carry the only disapproval deadline, and the last two are enhancements. The ordering logic is simple: fix the things that can break your feed before the things that improve it. The API migration and the image minimum are the two with teeth; shipping attributes and video are upside once the floor is safe. One connection worth making: this compliance work is also the foundation for where feeds are heading. The same clean, complete product data that satisfies these 2026 rules is what agentic shopping surfaces read, which I covered in my breakdown of the [Universal Commerce Protocol and product feeds](https://www.wpconsults.com/de/universal-commerce-protokoll-produkt-feed-seo/), and richer structured data compounds it further, per my guide to [product schema for AI shopping agents](https://www.wpconsults.com/de/produkt-schema-ai-shopping-agents/). ## So, how urgent are the 2026 Merchant Center changes really? If this were my store, I would treat the extension update as this week’s job and the image audit as this month’s, then relax. The January 31, 2027 image enforcement sounds far away, but image fixes on a big catalog are slow, manual work, and warnings have already been accumulating since April; a 2,000-SKU store does not clear that list in a weekend. The rest is opportunity rather than obligation. Product-level shipping and video_link reward stores that keep their feed honest and rich, and most competitors will do neither until something breaks. Yes, that is a boring edge; boring edges are the ones still working a year later. ### Want Your Product Feed Checked Against the 2026 Rules? Zögern Sie nicht [kontaktieren Sie uns](https://www.wpconsults.com/de/arbeit-mit-wpconsults/) oder [E-Mail](mailto:info.wpconsults@gmail.com) for a feed and Merchant Center review. Remember, a compliant, complete feed is the groundwork for everything your store does in Google Shopping and beyond.