Google requires seven mandatory attributes on every product — id, title, description, link, image_link, price, and availability — plus conditional attributes like brand, GTIN, and condition that become required the moment they apply to your product. On top of the classic spec, 2026 added a new video attribute, a higher minimum image resolution, product-level shipping controls, and mandatory disclosure rules for AI-generated titles and descriptions. Missing any required attribute means the product won’t serve, full stop — no partial credit.
Your Merchant Center feed is no longer a background task you fill out once and forget. It’s the data layer that decides whether you show up in Google Shopping, free listings, Search, Images, and increasingly, Google’s AI-driven shopping surfaces. This guide breaks down every attribute that matters in 2026, what’s new this year, and the mistakes that quietly cost merchants visibility.
Why Feed Quality Matters More in 2026 Than Ever Before
Product feeds now power far more than Shopping ads and free listings — they’re the raw material Google’s AI systems use to recommend, compare, and even transact on your behalf, which makes incomplete data a direct revenue problem.
Also Read: Startup Marketing Budget: A Founder’s Guide to Spending Smart
Google is investing heavily in AI-driven shopping experiences, and every one of those experiences depends on structured product data. If your feed is thin, your products simply don’t have enough signal to be matched, recommended, or surfaced — no algorithm can fix a missing attribute. Feed quality has effectively become a core part of ecommerce SEO: giving Google the most complete and accurate product data possible so its systems can match your products to the right shopper, on the right surface, at the right moment.
The Seven Mandatory Attributes (Miss One, Lose the Product)
Every product you submit needs id, title, description, link, image_link, price, and availability — these seven apply universally, with no exceptions by category.
| Attribute | Limit / Format | Why It’s Non-Negotiable |
| id | Up to 50 characters, stable | Google keys your product’s entire history to this value |
| title | Up to 150 characters | The first thing a shopper sees; drives match quality |
| description | Up to 5,000 characters, plain text | Feeds relevance-matching and AI Mode comparisons |
| link | Valid, mobile-friendly URL | A broken or redirected link causes disapproval |
| image_link | Meets resolution rules | Low-quality or unclear images hurt CTR and can trigger disapproval |
| price | Matches your site exactly | Mismatched pricing is one of the most common disapproval causes |
| availability | in_stock, out_of_stock, preorder, etc. | Prevents shoppers from clicking through to a dead listing |
Keep your product ID stable across every channel you sell on, not just Merchant Center — changing it frequently breaks historical performance tracking and can cause data loss in your reporting. For titles, resist the urge to stuff in every keyword you can think of. A title built around brand, product type, and the one or two features shoppers actually search for consistently outperforms a keyword-crammed one.
Conditional Attributes: Where Most Disapprovals Actually Happen
Attributes like brand, GTIN, MPN, condition, color, size, gender, and age group aren’t universally required, but they become mandatory the moment they apply to your product category — and this is where most feed errors originate.
Brand matters because both shoppers and Google’s matching systems rely on it heavily; resellers need to make sure the brand field reflects the actual manufacturer, not the reseller’s own name. GTIN (the standardized barcode — UPC, EAN, ISBN) is how Google verifies and matches products against real-world catalogs; if your product has an official GTIN and you leave it out, you lose impressions you’re otherwise entitled to. MPN steps in only when no GTIN exists, and needs to be verified against your supplier’s records to avoid indexing problems.
Apparel and variant-heavy categories carry extra weight here. Color, size, gender, and age group all help Google filter and categorize correctly, and inconsistency between your feed and your actual website is one of the most common — and most avoidable — sources of disapproval. A “Large” shirt listed as “L” in the feed while the website says “Large” is a small inconsistency that Google will flag and that can meaningfully suppress visibility until it’s fixed.
What’s New in the 2026 Merchant Center Specification
The 2026 update introduced a new video_link attribute, raised the minimum product image resolution to 500×500 pixels, added product-level shipping controls, and expanded loyalty program attributes — with enforcement dates staggered across the year.
Video Link (video_link)
Merchants can now submit product videos directly through the new video_link attribute. <cite index=”25-1″>The attribute began generating technical validation warnings in April 2026, and full policy and quality validation started once serving eligibility opened in the following months</cite>. A policy or quality issue on the video itself doesn’t take down the underlying product offer — it just stops that video specifically from serving.
Higher Image Resolution Requirements
Google raised the minimum resolution requirement for both the image_link and additional_image_link attributes to 500 by 500 pixels. <cite index=”20-1″>Warnings for images that don’t meet this updated minimum began appearing in Merchant Center in April 2026, with full enforcement scheduled for January 31, 2027</cite>. In the meantime, Google has started automatically optimizing some undersized images using high-resolution near-duplicates or AI upscaling, which prevents disapproval without any action from the merchant — though these optimized images get flagged with a warning in the Needs Attention section so you can still replace them with a genuine high-resolution original if you choose to.
Product-Level Shipping Controls
Two shipping sub-attributes moved from account-wide settings down to the individual product level: handling_cutoff_time, which sets a daily deadline for processing orders on a per-product basis, and minimum_order_value, which specifies a required minimum spend for a specific product or supplier relationship rather than applying one blanket rule across your entire catalog. Two related attributes, loyalty_program_label and loyalty_tier_label, also sit under shipping for merchants running tiered loyalty benefits, letting you reflect member-specific perks directly in the feed.
AI-Generated Content Disclosure
This is one of the most consequential changes for any merchant using AI tools to write titles or descriptions. If generative AI created your product title, you’re required to submit it through the structured_title attribute instead of the standard title attribute, using two sub-attributes: digital_source_type, set to the value “trained_algorithmic_media,” and content, which holds the actual AI-generated text. The identical pattern applies to descriptions through the structured_description attribute. Google also asks merchants not to strip embedded IPTC metadata tags — such as DigitalSourceType — from AI-generated images produced by tools like Product Studio, since those tags communicate the same disclosure for visual content. Skipping this disclosure when your content genuinely is AI-generated risks disapprovals and policy flags, so if you’re using an AI feed optimizer, confirm it outputs structured_title and structured_description correctly rather than writing into the plain title and description fields.
Feeding the Age of AI Shopping and Agentic Commerce
Google is rolling out a wave of new “conversational” attributes designed for AI Mode and agentic shopping experiences, and feed richness is becoming a direct eligibility requirement for these surfaces, not just a ranking factor.
Beyond the core spec, Google has signaled a much larger shift: dozens of new attributes aimed at helping AI systems understand, compare, and recommend products in natural conversation, going well beyond the traditional title-description-GTIN trio. These enhancements — richer titles, longer descriptions, complete commercial terms like return policies and delivery windows, multiple quality images — are increasingly framed not as nice-to-haves but as entry requirements for Google’s emerging AI-driven retail experiences, including a virtual shopping agent that answers product questions directly using your submitted feed data. For merchants, the practical takeaway is straightforward: a thin feed that scrapes by on the seven mandatory fields will simply be invisible to these newer surfaces, even if it technically passes validation.
Merchant Center Next: How You Actually Submit This Data
Merchant Center Next supports multiple ways to connect your catalog — including automatic website crawling from clean structured data — and Google is actively pushing merchants toward reading product data directly from well-marked-up landing pages instead of relying solely on manually maintained feed files.
If your product pages carry clean schema.org markup, Google can pull baseline product data automatically through website crawling, reducing (though not eliminating) manual feed maintenance. This matters for a second reason too: it’s also worth knowing that the older Content API for Shopping is being sunset, with the newer Merchant API v1 as its replacement — if you’re on an older integration, migrating before the cutover avoids a disruptive scramble later.
Feed Management Best Practices for 2026
Automate updates wherever possible, audit your feed on a fixed schedule, keep titles natural rather than keyword-stuffed, and mirror your website’s structured data with what you submit to Merchant Center.
- Automate real-time updates. Managing pricing and stock manually across a large catalog invites mismatches. For stores with frequent price changes, push multiple feed updates a day rather than one.
- Schedule regular feed audits. Weekly or monthly reviews catch Merchant Center warnings before they snowball into widespread disapprovals, and give you a chance to archive discontinued or seasonal products before they clutter your active feed.
- Write titles and descriptions for people, not just crawlers. Include brand, product type, and one or two genuinely relevant features — natural language consistently outperforms keyword stuffing in both click-through rate and Google’s own quality signals.
- Match structured data on-site to your feed. JSON-LD product schema on your website that mirrors your Merchant Center submission builds consistency, which reduces disapprovals and improves eligibility for free listing placements.
- Use custom labels strategically. Grouping products by margin, season, or bestseller status makes it far easier to manage bids and campaign budgets at scale, especially across large catalogs.
Common Pitfalls That Quietly Cost Visibility
Inconsistent pricing, generic titles, missing GTINs, incomplete shipping or tax data, and unresolved Merchant Center warnings are the five mistakes that account for the vast majority of feed-related visibility loss.
A price mismatch between your Merchant Center feed and your live website is one of the fastest ways to trigger disapproval, and shoppers notice the discrepancy just as quickly as Google does. Generic titles like “Men’s Shirt” — with no brand, style, or distinguishing detail — simply don’t carry enough signal to rank well against more descriptive competitors. Leaving out a GTIN your product actually has means forfeiting impressions Google would otherwise grant you, since GTINs are core to how products get verified and matched. Missing shipping or tax information can inflate bounce rates once shoppers hit checkout and encounter costs they weren’t shown upfront. And perhaps most avoidable of all: letting flagged errors sit unresolved in Merchant Center for weeks doesn’t just suppress the specific affected products — it drags down how Google evaluates your feed’s overall reliability.
Frequently Asked Questions
What happens if I submit AI-generated titles through the regular title attribute instead of structured_title? You risk a policy violation, since Google specifically requires the structured_title attribute with a digital_source_type disclosure for any title created using generative AI — using the standard title field for AI-written content can lead to warnings or disapprovals.
Do I need to update every product’s image to 500×500 pixels immediately? Not immediately — warnings began appearing in April 2026, but full enforcement isn’t scheduled until January 31, 2027, giving merchants a runway to fix images before disapprovals kick in.
Is handling_cutoff_time required for every product? No, it’s an optional product-level attribute. It’s most valuable if you compete on delivery speed and want to differentiate cutoff times by product or supplier rather than applying one account-wide setting.
Can a product pass every required attribute check and still perform poorly? Yes. Passing validation only confirms the seven mandatory fields are present — attributes like brand, GTIN, and detailed descriptions live outside that minimum bar, and a feed that skips them will validate fine while still underperforming.
Should I be worried about the Content API for Shopping sunset? Only if your current integration still relies on it. Google has been moving merchants toward Merchant API v1, and planning that migration ahead of the shutdown avoids losing feed functionality unexpectedly.
