Google Shopping Feed Requirements 2026: What Every Product Page Must Have

Google Shopping — now integrated across Google Search, Google Images, and the Shopping tab — drives significant paid and free traffic for ecommerce stores. But products that don't meet Google Merchant Center's data quality requirements get disapproved and don't show up. Understanding exactly what Google requires (and what it recommends) determines how much of your catalog qualifies for Shopping listings.

Required Attributes for All Products

These attributes are mandatory. Products missing any of these will be disapproved:

id

A unique identifier for the product in your feed. Use your internal SKU or product ID. Once set, never change this — Merchant Center uses it to match your feed entries to existing listings.

title

The product name as it appears in Shopping listings. Maximum 150 characters (keep it under 70 for best display). Include brand, product type, and key attributes (color, size, material) in this order: Brand + Product Type + Attributes. Example: Nike Air Zoom Pegasus 41 — Men's Road Running Shoe, Wide, White/Black.

Bad title: Shoe - Nike - White. Too vague, missing model, missing attributes Google uses for matching.

description

Up to 5,000 characters. The first 160-200 characters appear in the listing. Include the product's key selling points, materials, and intended use. Don't include promotional language ("best," "sale," "free shipping") — that violates Merchant Center policy.

link

The canonical URL of the product page on your site. Must be crawlable by Google. Must match the domain verified in Merchant Center. Must use HTTPS.

image_link

The URL of the main product image. Requirements that get products disapproved:

• Minimum size: 100×100 pixels (250×250 for apparel). Recommended: 800×800+
• Must show the product clearly against a clean (white preferred) background
• No watermarks, overlaid text, or promotional graphics
• Must be the main product without packaging (exceptions for food/beverage)
• Must be publicly accessible (no auth, no robots.txt block)

availability

One of four accepted values:

• in_stock — available for purchase
• out_of_stock — not currently available
• preorder — available for preorder with a future availability date
• backorder — can be ordered but will ship later

This must match what your product page actually shows. Sending in_stock when the product page says "sold out" is a policy violation.

price

The product's current price with currency code: 29.99 USD. Must match the price visible on the product page within a small tolerance. Price mismatches are the most common reason for Merchant Center disapprovals.

brand

Required for all products except custom/handmade items (use "handmade" as brand for those). Must be the brand that manufactures the product, not your store name.

Strongly Recommended Attributes

These aren't required for all products but significantly improve eligibility for Shopping ads and free listings:

gtin (Global Trade Item Number)

UPC (US), EAN (Europe), ISBN (books), JAN (Japan). For products you manufacture yourself: set identifier_exists: false. For reselling branded products: the GTIN is almost always required. Products without GTINs have lower ad eligibility and quality scores. Google uses GTINs to match your listing against other sellers of the same product for comparison shopping.

mpn (Manufacturer Part Number)

Required when GTIN isn't available for products that have one. Use the manufacturer's official part number.

condition

One of: new, refurbished, used. If omitted, Google assumes new. Required if the product is not new.

product_type

Your internal category taxonomy: Clothing > Shoes > Running Shoes. Not the Google product category (that's google_product_category, a separate attribute). Used for bidding segmentation in Shopping campaigns.

google_product_category

Google's standardized taxonomy category. Pick the most specific matching category from Google's taxonomy file. Correct categorization improves ad targeting accuracy and eligibility.

Apparel-Specific Required Attributes

For clothing, shoes, and accessories:

• gender: male, female, unisex
• age_group: newborn, infant, toddler, kids, adult
• color: primary color(s) of the product
• size: the product's size (required for clothing; recommended for shoes)

For variants (a t-shirt available in S/M/L/XL in 5 colors), each variant needs its own feed entry with a unique ID, the appropriate size/color, and a product page URL that loads that specific variant (or uses URL parameters with a canonical to the main product).

Common Disapproval Reasons

Issue	Impact	Fix
Price mismatch (feed vs page)	Disapproval	Sync feed on every price change
Image too small (<100×100)	Disapproval	Upload higher-res images
Missing GTIN (branded product)	Limited eligibility	Add GTINs to product database
Availability mismatch	Disapproval	Sync inventory in real time
Promotional text in title/description	Policy violation	Remove sale/promo language
Image with watermark/text overlay	Disapproval	Re-shoot or remove text
Missing brand for branded products	Disapproval	Add brand attribute
Title too short (under 20 chars)	Quality score reduction	Add model, color, attributes

Automated Feed Solutions

Managing feed attributes manually doesn't scale. The standard approach:

• Shopify: Google & YouTube app (official Google channel) syncs your product catalog automatically. For advanced attribute management, DataFeedWatch or Feedonomics.
• WooCommerce: WPML Product Feed for WooCommerce, Feedonomics, or the Google Listings & Ads plugin (official).
• BigCommerce: Native Google Shopping integration in channel manager.
• Custom: Generate feed as XML (RSS 2.0 with Google Merchant extensions) or CSV, host publicly, submit URL to Merchant Center. Re-fetch frequency: every 24 hours.

Product Page Schema and Merchant Center

There's an important connection between your product page's structured data (schema.org Product markup) and Google Shopping. Google can extract product data directly from Product schema on your pages — but this supplements your feed, it doesn't replace it. For structured product listings with price and availability, a submitted Merchant Center feed is the authoritative source; schema.org markup is a secondary signal.

However, schema.org Product markup with correct Offer data (price, priceCurrency, availability) does influence Shopping eligibility for free listings. If you can't maintain a feed, getting your product schema right is the next best option.

StoreVitals' Product Schema Validator checks your product pages for Offer.price, Offer.priceCurrency, Offer.availability, and AggregateRating — the same fields Merchant Center pulls from structured data. Run it on any product page to see what Google is extracting before you troubleshoot in Merchant Center.