Google Shopping & Merchant Centre

Last updated: October 17, 2026

1. Executive Summary

Google Shopping success in 2026 depends on five compounding principles that work together rather than independently. Weakness in any one area limits the ceiling of the others.

• Feed accuracy is the foundation. Every campaign optimization, bidding strategy, and segmentation decision is built on product data. Titles, prices, availability, identifiers, and images must match the landing page exactly and comply with Google’s product data specification. No bidding strategy compensates for disapproved or misrepresented products.
• Account health precedes spend. Merchant Center account suspensions, item-level disapprovals, and policy warnings reduce eligible inventory immediately. Diagnose and resolve feed errors before scaling budgets or restructuring campaigns.
• Campaign structure should reflect economics, not taxonomy. Segment products by margin tier, sales velocity, price band, and promotional status rather than by product category alone. Segmentation is only useful when it leads to a different budget, bid, or exclusion decision.
• Performance Max requires high-quality conversion signals. PMax automated bidding optimizes toward whatever signal it receives. Purchase revenue with accurate transaction values, enhanced conversions, and clean deduplication are prerequisites for reliable automation. Weak or proxy conversion data produces confident but misdirected spend.
• Diagnostics monitoring is a continuous workflow, not a launch task. Feed errors, price mismatches, GTIN warnings, and policy changes affect active campaigns silently. Build a recurring review of Merchant Center diagnostics, item-level approval status, and campaign performance into standard operating procedure.

2. Benchmarks and Numbers at a Glance

The table below consolidates key thresholds, limits, and operational numbers relevant to US Google Shopping accounts. Where a figure originates from a vendor claim rather than an independent study, the Applies When column notes this. Because no independently verified US Shopping benchmark data was returned in available research for October 2026, rows drawing on Google’s own documentation or widely cited operational thresholds are marked accordingly. Practitioners should validate performance benchmarks against their own account data and current industry studies.^[1]

Metric	Typical Range or Threshold	Applies When	Source
Product title character limit	150 characters maximum	All product types; most useful information should appear within the first 70 characters visible in Shopping ads	Google Merchant Center product data specification[1]
Product description character limit	5,000 characters maximum	All product types; first 500 characters most likely to be read or used	Google Merchant Center product data specification[1]
GTIN digit count (UPC, North America)	12 digits (UPC-A) or 14 digits (GTIN-14)	Physical branded products sold in the US; check digit must be mathematically valid	Google unique product identifiers guidance[1]
Custom label fields available	5 fields (custom_label_0 through custom_label_4)	All feed types; used for campaign segmentation and reporting, not customer-facing relevance	Google Merchant Center product data specification[1]
Minimum conversion volume before adding tROAS to PMax	30–50 conversions in the preceding 30-day window (Google recommendation)	Performance Max campaigns; vendor claim from Google Ads Help documentation, not an independent study	Google Ads Help (vendor claim)[2]
Feed update frequency for price- and stock-sensitive catalogs	At least every 24 hours; Content API enables near-real-time updates	Retailers with daily price changes, flash sales, or volatile inventory; mismatch between feed and page is a leading disapproval cause	Google Merchant Center automatic item updates documentation[1]
Standard Shopping campaign priority levels	3 levels: High, Medium, Low	Applies only when multiple Standard Shopping campaigns contain overlapping products; does not control budget allocation	Google Ads Help — campaign priority[2]
Maximum additional images per product	Up to 10 additional images (beyond the primary image_link)	All product types; additional angles, lifestyle, packaging, and variant images supported	Google Merchant Center image guidance[1]
sale_price_effective_date required format	ISO 8601 datetime with timezone offset, e.g., 2026-11-28T00:00-05:00/2026-11-29T23:59-05:00	Required when sale_price is submitted; omitting the date can cause price-mismatch disapprovals if the sale ends	Google Merchant Center product data specification[1]
Budget or target change increment for PMax to avoid resetting learning	No more than 15–20% change per adjustment (Google’s general guidance; vendor claim)	Performance Max and Smart Bidding campaigns during active optimization periods; larger changes can trigger a new learning period	Google Ads Help — Smart Bidding (vendor claim)[2]
Minimum image resolution recommended	800 × 800 pixels for non-apparel; 250 × 250 pixels absolute minimum accepted	Main product image; higher resolution strongly preferred; Google may reject low-resolution images	Google Merchant Center image guidance[1]
PMax learning period after campaign launch or major change	Approximately 1–2 weeks (vendor claim; Google’s own documentation cites a conversion delay window)	New PMax campaigns or campaigns with significant budget, bid target, or asset changes; do not evaluate final performance during this window	Google Ads Help — Performance Max (vendor claim)[2]

3. Merchant Center Setup and Account Health

A correctly configured Merchant Center account is a prerequisite for any product to appear in Shopping ads or free listings. Errors at the account level—such as an unclaimed website, missing shipping settings, or a policy violation—can suppress an entire catalog regardless of feed quality or campaign budget. Treat initial setup and ongoing account health as operational necessities, not one-time tasks.

Website Verification and Claiming

Merchant Center requires that the domain used in all product landing-page URLs is both verified and claimed. Verification proves ownership; claiming reserves the domain for one Merchant Center account. Use Google’s HTML tag, Google Analytics, Google Tag Manager, or DNS record method to verify. After claiming, any change to the primary domain—such as a migration from HTTP to HTTPS, a subdomain shift, or a platform change—requires re-verification and re-claiming.^[1]

Ensure that every link attribute in the feed points to the same verified domain. Landing pages that redirect to a different domain, require a login, return a 404 or 5xx status, or fail on mobile devices are a direct path to item disapprovals and, if widespread, account-level warnings.

Business Information, Shipping, Tax, and Returns

Complete all Merchant Center business information fields before submitting products. In the US, this includes accurate business name, address, customer service contact, shipping settings covering all states where orders ship, sales tax configuration for applicable states, and a clearly stated return policy. Google surfaces return policy and shipping cost information in Shopping ads and free listings; incomplete or inconsistent settings reduce eligibility and can trigger disapprovals on affected products.^[1]

US-specific note: Sales tax configuration in Merchant Center must reflect nexus obligations accurately. Outside the US, VAT and GST handling differs materially; apply country-specific tax settings in each separate Merchant Center account or sub-account as applicable.

Linking Merchant Center to Google Ads

Link Merchant Center to Google Ads through the account settings in Merchant Center, not through Google Ads. Verify that the correct Google Ads customer ID is linked, that conversion tracking is active on the Google Ads account, and that the target country in the campaign matches the feed country of sale. A linked account that lacks purchase conversion tracking will prevent effective automated bidding on any campaign type.^[2]

Merchant Center Next

Google has been migrating accounts to Merchant Center Next, which consolidates product management, diagnostics, and performance reporting into a unified interface. Where Merchant Center Next is available, use it as the primary interface, but maintain a supplemental feed or Content API workflow for any attributes that the ecommerce platform does not expose natively. The underlying product data specification and policy requirements are consistent between the classic interface and Merchant Center Next.^[1]

Account-Level Suspensions and Policy Compliance

Account suspensions halt all Shopping ads and free listings across every product in the account. The most common causes in US accounts include: misrepresentation of self or products, price or availability inaccuracies at scale, prohibited product policy violations, and repeated or unresolved item-level disapprovals that indicate systemic data quality problems. When a suspension notice is received, address every listed issue before submitting a review request. Submitting a review before fully resolving violations delays reinstatement.^[1]

Sub-Account and Multi-Client Account Structure

Retailers operating multiple storefronts, regional sites, or brands should use a Multi-Client Account (MCA) in Merchant Center. Each sub-account maintains its own feed, shipping settings, and policy standing. An account-level issue in one sub-account does not automatically suspend others, providing important isolation. Apply feed labels at the sub-account level to keep US and non-US inventory cleanly separated.^[1]

4. Product Feed Quality and Required Attributes

Feed quality determines which products are eligible to serve, how accurately Google matches them to relevant queries, and whether they pass policy review. A feed that contains all required attributes, accurately reflects the product and the landing page, and is updated frequently enough to stay current is the single highest-leverage input in a Shopping program.^[1]

Required Attributes for US Physical Products

The following attributes are required for standard physical products sold in the US. Additional attributes become required depending on category, condition, and destination. Always verify requirements against the current Google Merchant Center product data specification because attribute requirements are updated periodically.^[1]

• id: Unique, stable identifier. Do not change this value when other attributes are updated. Changing the ID destroys performance history for that product.
• title: Product name. Required. See Section 5 for optimization guidance.
• description: Product description. Required. Must be specific to the product, not boilerplate.
• link: Landing-page URL. Must resolve to the exact product on the verified domain without a login requirement.
• image_link: Primary product image URL. Must be accessible to Googlebot without authentication or blocking.
• availability: One of: in_stock, out_of_stock, preorder, or backorder. Must match the page.
• price: Retail price in USD. Must match the price shown on the landing page without requiring interaction.
• brand: Required for all products with an assigned brand.
• condition: Required for used or refurbished products; recommended for all.
• shipping: Required or derived from account-level shipping settings. Product-level overrides take precedence.
• google_product_category: Strongly recommended; required for some categories such as apparel, software, and media.

Attribute Completeness vs. Accuracy

Completeness and accuracy are different problems. A feed can be 100% complete—every required field populated—while still containing inaccurate data that causes disapprovals. Prioritize accuracy first. A missing optional attribute is less damaging than an incorrect GTIN, a mismatched price, or a title that describes a different variant than the one on the landing page.^[1]

Availability and Price Synchronization

Price and availability mismatches are the leading source of item disapprovals in US Shopping accounts. Google crawls landing pages independently of the feed and compares what it finds. Any discrepancy between the feed price and the page price, or between in_stock in the feed and an out-of-stock indicator on the page, triggers a warning or disapproval. Enable automatic item updates as a secondary safety net, but do not rely on them as a substitute for accurate feed synchronization.^[1]

Variant Attributes

Products that come in multiple variants—color, size, storage capacity, material, or configuration—must each have a distinct feed row. All variants of the same base product share an item_group_id value. Each variant row must carry its own GTIN (if assigned at the variant level by the manufacturer), its own image matching that exact variant, and its own variant-specific attribute values. Using a single title, image, and GTIN for all color or size variants is one of the most common feed quality failures and reduces both match quality and conversion rate.^[1]

5. Product Titles, Images, and Descriptions

Titles, images, and descriptions are the primary customer-facing content in a Shopping ad. They also serve as structured signals Google uses to match products to queries. Optimizing these three elements is the highest-return feed investment for most US accounts because the improvements apply at scale across every campaign using the affected products.^[1]

Product Titles

Titles must be accurate, specific, and structured so that the most identifying information appears first. Google displays a limited portion of the title in Shopping ads, and the character limit is 150 characters total, but the first 70 characters carry the most weight in both display and matching.^[1]

Apply a category-appropriate title template consistently across the catalog:

• Apparel: Brand + Gender + Product Type + Key Feature + Color + Size
• Electronics: Brand + Product Type + Model Number + Key Specification + Color + Storage
• Home and garden: Brand + Product Type + Material + Key Feature + Dimensions or Capacity
• Auto parts: Brand + Part Name + Part Number + Compatibility (Year/Make/Model)
• Tools and hardware: Brand + Product Type + Model + Key Specification + Pack Quantity

Never include promotional language (“Free shipping,” “On sale,” “Best price”) in the title. These claims belong in promotions or ad copy, not the title attribute, and their presence can cause disapprovals or policy warnings.^[1]

Do not repeat the same keyword multiple times in a title. Repetition does not improve matching and reduces the space available for genuinely differentiating information. Each variant should have its own specific title—do not use one generic title for a product group and rely on color or size attributes alone to differentiate.

Images

The main image is the single most visible element of a Shopping ad. Google’s minimum accepted resolution is 250 × 250 pixels, but 800 × 800 pixels or higher is strongly recommended for non-apparel products, and 1,000 × 1,000 pixels or higher for apparel.^[1]

The main image must show the exact product variant advertised—correct color, correct configuration, correct pack size—against a clean background without text overlays, watermarks, promotional badges, or borders. Additional images (up to 10) can show alternate angles, lifestyle context, dimensions, packaging, or included accessories.^[1]

Keep image URLs stable. When a CDN URL changes or expires, Googlebot cannot fetch the image, and the item may be disapproved for an invalid image URL. Treat image URL stability as a technical requirement, not an optional best practice.

Descriptions

Descriptions are less prominently displayed in Shopping ads than titles and images, but they contribute to Google’s product understanding and can appear in free listing surfaces. Write descriptions that are accurate, specific, and readable. Include key specifications, materials, dimensions, compatibility information, and use cases. Do not paste boilerplate, keyword lists, or SEO copy from other channels into the description field.^[1]

6. GTINs, Identifiers, and Custom Labels

Accurate product identifiers tell Google precisely what physical product is being offered and enable it to match the offer against manufacturer catalog data, competitive pricing surfaces, and structured knowledge about the product. Custom labels serve a completely different purpose: they encode internal business logic for campaign segmentation and reporting. Understanding and correctly implementing both is essential for a well-functioning US Shopping account.^[1]

GTINs and Unique Product Identifiers

A GTIN (Global Trade Item Number) is a manufacturer-assigned numeric identifier. In the US, this is most commonly a 12-digit UPC-A. GTINs must be submitted as digits only, with no spaces or hyphens, and the final digit must be a mathematically valid check digit. A GTIN with an invalid check digit is rejected or flagged immediately by Merchant Center’s validation logic.^[1]

Submit the GTIN for the exact variant being sold—not a parent product’s GTIN, not a retailer SKU, and not a GTIN from a related model. For multipacks and retailer-created bundles, follow Google’s specific multipack and bundle rules, which may require the component GTINs plus multipack or is_bundle attributes.^[1]

Use identifier_exists = no only when a product genuinely has no assigned GTIN, brand, or MPN from the manufacturer—for example, truly custom-made, handmade, or vintage items with no manufacturer record. Do not use it to work around the difficulty of finding an identifier; incorrect use of identifier_exists reduces product eligibility and can attract policy scrutiny.^[1]

Validate GTINs against the manufacturer’s product information, supplier data sheets, or a GS1-registered database. The three most common GTIN errors in US feeds are: submitting a UPC that belongs to a different configuration of the product; using a variant-level GTIN for all variants in a group; and submitting an MPN in the GTIN field.

Brand and MPN

Submit brand as the manufacturer’s brand name—not the retailer’s store brand, private label name, or marketing descriptor unless the product is genuinely private label. Submit MPN (manufacturer part number) when no GTIN is assigned. Brand + MPN is an acceptable identifier combination when GTIN is unavailable, but the combination must be accurate; a mismatched brand and MPN from different products defeats the purpose of the identifier system.^[1]

Custom Labels

Custom labels (custom_label_0 through custom_label_4) are internal tags that appear nowhere in the ad itself. Their sole purpose is to enable campaign segmentation, listing group filtering, and reporting filters in Google Ads and Merchant Center. A custom label that does not lead to a different bidding, budgeting, or exclusion decision in the campaign structure serves no operational function and should be removed or replaced with one that does.^[3]

A stable and actionable US retail custom label taxonomy:

Label Field	Recommended Use	Example Values
custom_label_0	Gross margin tier	high_margin, mid_margin, low_margin, loss_leader
custom_label_1	Sales velocity or bestseller status	top_seller, core, slow_mover, new_arrival
custom_label_2	Seasonality or promotional window	evergreen, holiday_2026, back_to_school, clearance
custom_label_3	Price band (USD)	under_25, 25_to_99, 100_to_249, 250_to_499, 500_plus
custom_label_4	Inventory or fulfillment status	in_stock, low_stock, overstock, dropship, backordered

Automate custom label assignment from the ERP or ecommerce platform wherever possible. Labels assigned manually in a spreadsheet become stale as margins shift, inventory levels change, and promotions end. A label that reads clearance but applies to a now-full-price product misdirects campaign bidding.^[3]

7. Standard Shopping vs. Performance Max for Retail

Choosing between Standard Shopping and Performance Max is one of the most consequential structural decisions in a US retail account. Both campaign types serve Shopping inventory, but they differ fundamentally in control, automation, data requirements, and delivery scope. Neither type is universally superior; the right choice depends on the account’s conversion data quality, catalog maturity, budget, and operational tolerance for opacity.^[2]

Core Differences

Dimension	Standard Shopping	Performance Max
Inventory reach	Shopping surfaces only	Shopping, Search, Display, YouTube, Discover, Gmail, Maps
Bidding options	Manual CPC (where eligible), Target ROAS, Maximize Clicks	Maximize Conversion Value (with or without tROAS), Maximize Conversions (with or without tCPA)
Query control	Negative keywords, priority settings, product groups	Brand exclusions, search term category exclusions, audience exclusions; limited negative keyword controls
Conversion data requirement	Lower; can run with fewer conversions and manual bidding	Higher; automated bidding is significantly less reliable below ~30–50 conversions per month[2]
Transparency	Product-level impression and click data visible in campaign reports	Asset-group level reporting; product-level data available but channel-level attribution less granular
Learning period	Shorter; reacts faster to manual bid changes	Approximately 1–2 weeks; major changes restart the learning period[2]
Feed quality sensitivity	High; poor titles and missing attributes reduce match quality	Very high; PMax uses feed data as its primary product signal across all channels
Best fit	Low-volume accounts, test campaigns, product lines needing tight bid control, or Shopping-only delivery requirements	Accounts with reliable purchase tracking, adequate conversion volume, clean data, and sufficient budget for automation

When to Use Standard Shopping

Standard Shopping is the appropriate primary campaign type when: the account generates fewer than 30 purchase conversions per 30-day period (making tROAS-driven automation unreliable); the business needs Shopping-only delivery to avoid spend on Display or YouTube; product-level bid control is required because of extreme margin variance within the catalog; or a controlled A/B benchmark against PMax is needed. Standard Shopping also provides faster diagnosis of feed-level issues because query-level search term data is more directly visible.^[2]

When to Use Performance Max

Performance Max is appropriate when: the account has dependable purchase conversion tracking with accurate revenue values; conversion volume is sufficient for automated bidding to function reliably (at minimum 30 purchase conversions in 30 days, and ideally more); the business wants cross-channel reach from a single campaign structure; and the team has the operational capacity to manage asset groups, audience signals, and regular creative refresh rather than manual bid management.^[2]

Migration from Standard Shopping to PMax

When migrating, do not simply pause Standard Shopping and launch PMax with the same budget on day one. Run both campaign types in parallel for at least 4 weeks to establish a performance baseline for PMax. Monitor the learning period carefully and avoid making budget, tROAS, or asset changes during the first 14 days. Ensure conversion tracking is producing accurate purchase revenue before migration, because PMax will optimize toward whatever signal it receives at scale.^[2]

8. Campaign Structure and Product Segmentation

An effective campaign structure in 2026 is the minimum number of campaigns necessary to reflect genuine differences in budget allocation, bidding targets, margin structure, or promotional strategy. Fragmentation—creating many campaigns split by arbitrary attributes—divides conversion data, extends learning periods, creates internal competition for the same products, and increases management overhead without producing better results.^[2]

Principles of Effective Segmentation

Before creating a separate campaign or asset group, apply a simple test: does this separation lead to a different budget, a different tROAS target, or a product exclusion that cannot be achieved within a listing group? If the answer is no, the separation adds complexity without benefit. If the answer is yes, the separation is justified.^[2]

Segment by economics first:

• Gross margin tier: High-margin products justify more aggressive bidding; loss leaders may need exclusion or a hard tROAS floor.
• Sales velocity: Best sellers generate conversion signals faster and support more confident automated bidding. New products with no history should be managed differently from proven SKUs.
• Price band: $15 accessories and $800 appliances have different click economics, return rates, and conversion funnel dynamics.
• Promotional status: Clearance inventory, seasonal promotions, and new product launches often warrant distinct budgets and short-term targets.
• Stock depth: A product with 3 units remaining should not receive the same ad spend investment as one with 500 units in inventory.

Listing Groups in Performance Max

Within a PMax campaign, listing groups define which products are eligible for each asset group. They function similarly to product groups in Standard Shopping but are attached to asset groups rather than ad groups. Use custom labels as the primary listing group dimension because they encode internal business logic that Google’s product taxonomy cannot replicate.^[2]

Keep listing groups actionable. A listing group that contains products with identical margin tiers, seasonal status, and promotional treatment can share an asset group without loss of control. A listing group that mixes high-margin new arrivals with low-margin clearance items obscures performance and makes bid and budget decisions ambiguous.

Product Exclusions

Exclude from Shopping campaigns any product that: is out of stock (zero available inventory); has a gross margin below the breakeven CPA threshold; has active policy violations or disapprovals; requires fulfillment conditions that cannot be met for paid traffic; or is subject to category-level advertising restrictions in the target region. Exclusions are best managed at the feed level using custom labels combined with a campaign-level listing group filter, rather than by individually excluding product IDs in the campaign interface.^[2]

Avoiding Internal Auction Competition

When two campaigns in the same account can both serve the same product, they compete against each other in the auction, inflating CPCs without increasing reach. This is particularly common in accounts with overlapping PMax and Standard Shopping campaigns targeting the same SKUs. Eliminate overlap by ensuring each SKU belongs to exactly one active campaign via non-overlapping listing groups or product assignments. Use campaign-level feed labels to assign distinct subsets of inventory to each campaign.^[2]

9. Feed Rules and Supplemental Feeds

Feed rules and supplemental feeds are the primary tools for enriching, correcting, and organizing product data without rebuilding the core feed from scratch. Used correctly, they enable rapid improvements to title structure, custom label assignment, and attribute completeness. Used incorrectly, they produce compounding data quality problems that are difficult to diagnose because the error is introduced by the rule rather than the source system.^[1]

Feed Rules: What They Do and When to Use Them

Feed rules transform attribute values before Merchant Center processes the feed. A rule can copy a value from one field to another, concatenate fields to build a title, map a platform-specific availability value to Google’s accepted vocabulary, filter products from a feed, or assign a custom label based on a condition. Rules apply in sequence; the order of rules matters when multiple rules affect the same attribute.^[1]

Appropriate uses for feed rules include:

• Mapping an ecommerce platform’s availability values (e.g., 1 for in stock, 0 for out of stock) to Google’s required values (in_stock, out_of_stock)
• Building a structured title from existing fields when the platform exports a generic product name
• Adding a brand value from a trusted source field when brand is consistently missing from the primary feed
• Assigning custom_label_0 based on a price threshold (e.g., if price > $250 then custom_label_3 = 250_to_499)
• Excluding products flagged with a discontinued status field in the source data
• Normalizing google_product_category to a consistent taxonomy across product families

Feed rules must not be used to fabricate identifiers, override live prices with static values, force products into inaccurate categories, or replace genuinely missing mandatory data with generic placeholders. Rules that conceal bad source data do not fix the underlying problem; they make it harder to find.^[1]

Supplemental Feeds

A supplemental feed is a secondary data file that adds or overrides specific attributes on products already submitted in the primary feed. Supplemental rows are matched to primary feed records using the exact id value. Only the attributes included in the supplemental feed are updated; all other attributes remain as submitted in the primary feed.^[1]

A well-designed supplemental feed workflow:

• Keeps the primary feed as the authoritative source for product identity, price, availability, and landing page
• Uses the supplemental feed for: custom labels, corrected titles, additional images, product highlights, marketing categories, and seasonal classifications
• Is generated automatically from the ERP, PIM, or merchandising system rather than maintained as a manually edited spreadsheet
• Is validated before upload by checking that all id values in the supplemental feed match active products in the primary feed
• Includes an expiration review: remove or update supplemental values that become stale (e.g., holiday custom labels applied in November 2026 should be updated or removed by January 2027)

Preventing Rule and Supplemental Feed Conflicts

When feed rules and supplemental feeds both affect the same attribute on the same product, the order of precedence determines which value wins. In Merchant Center, supplemental feeds generally override primary feed values, and feed rules apply after the feed is ingested. Verify the resulting attribute values in the Merchant Center item-level view—not in the rule configuration screen—to confirm the actual processed output is what was intended.^[1]

10. Diagnostics and Disapprovals

Merchant Center diagnostics are the operational control panel for feed health. Item disapprovals reduce the eligible product pool silently—an account may be spending budget on its approved products while an entire category sits disapproved and generating zero impressions. Regular diagnostics review is not optional for accounts serious about Shopping performance.^[1]

Where to Find Diagnostics

In Merchant Center (and Merchant Center Next), the Diagnostics tab shows item-level approval status, disapproval reasons, affected product counts, and the attributes involved. In Merchant Center Next, the Products section shows per-item status with links to the specific policy or specification violation. Google Ads campaign-level reporting shows which products within a campaign have active impressions; a product with zero impressions for 7 or more consecutive days despite being in an active campaign with budget is typically either disapproved, filtered out by listing groups, or out of stock.^[1]

Most Common US Disapproval Categories

• Price mismatch: Feed price differs from the price on the landing page. Often caused by caching, CDN delays, currency inconsistencies, or a feed update schedule that lags behind real-time price changes.
• Availability mismatch: Feed shows in_stock but the landing page shows out-of-stock, or the product requires a backorder with no available date provided.
• Invalid GTIN: Check-digit error, incorrect digit count, GTIN not assigned to the submitted product, or variant GTIN replaced with a parent GTIN.
• Incorrect image: Image does not depict the advertised variant; image URL is broken or inaccessible; image contains prohibited overlays or promotional text.
• Landing page not working: 404 or 5xx HTTP status, redirect loop, login required, mobile rendering failure, or Googlebot blocked by robots.txt.
• Missing required attribute: A required field is absent or contains a value outside the accepted vocabulary (e.g., an invalid availability string).
• Policy violation: Product is in a prohibited or restricted category, or the ad or landing page contains disallowed claims.

Diagnostic Workflow

Review Merchant Center diagnostics on a weekly cadence at minimum, and after every feed update. When a new disapproval appears:

1. Identify the disapproval reason and the affected attribute
2. Check 3–5 individual affected items to confirm whether the issue is systematic or isolated
3. Trace the error to its source: feed generation, ecommerce platform, feed rule, supplemental feed, or landing page
4. Fix the source, not just the symptom
5. Trigger a feed re-fetch or Content API update
6. Monitor Merchant Center for item re-approval, which typically occurs within 24–72 hours for data-level fixes and longer for policy-level reviews^[1]

11. Common Mistakes to Avoid

The following mistakes consistently reduce Shopping campaign efficiency, trigger disapprovals, or waste budget. Each represents a pattern observed across account structures and feed implementations. Addressing them before launch, and auditing for them during quarterly reviews, prevents compounding problems that become harder to unwind at scale.

Mistake 1: Changing Product IDs During Routine Feed Updates

The id attribute must remain stable across all feed updates. Changing an ID—even when a product’s title, price, image, or variant detail changes—creates a new product record in Merchant Center. The original record loses its performance history, impression share, and any accumulated quality signals. If the old ID reappears later, Google treats it as yet another new item. For large catalogs, systematic ID regeneration can effectively reset months of auction learning.^[1]

The correct approach is to treat the id as a permanent internal key that corresponds to the product entity, not to a specific configuration of that entity. Variant-level details belong in attributes such as color, size, and item_group_id, not in the id field itself.

Mistake 2: Using identifier_exists=no to Avoid Finding Real GTINs

Some feed managers set identifier_exists=no across broad product groups to suppress GTIN warnings without investigating whether identifiers actually exist. This approach reduces product eligibility and can suppress impressions in competitive categories where Google uses GTINs to match products to specific queries and competitor offers. The correct use of identifier_exists=no is narrow: it applies only to custom-made, handmade, vintage, or genuinely unregistered products for which no manufacturer-assigned GTIN, MPN, or brand exists.^[1]

Mistake 3: Writing Generic Titles Shared Across Variants

Applying one title such as Men’s Running Shoe to every size and color variant defeats the purpose of variant-level product records. Each variant must carry its own title that includes the differentiating attributes—color, size, capacity, compatibility—positioned early enough to be visible in the Shopping ad unit. A generic shared title also makes it harder for Google to match the specific variant to the specific query, which can reduce relevance and conversion quality.^[3]

Mistake 4: Launching Performance Max Without Reliable Purchase Conversion Tracking

Performance Max bidding is calibrated against the conversion signals the campaign receives. Launching PMax with only a proxy action—such as a page view, a newsletter signup, or an add-to-cart event—causes the algorithm to optimize for the wrong behavior. The campaign may generate high spend against a low-value signal while ignoring high-margin purchasers. Before scaling PMax, confirm that the primary conversion action is a completed purchase with accurate transaction revenue passed in USD, that deduplication between web and offline conversions is in place, and that the conversion window matches realistic purchase latency for the product category.^[2]

Mistake 5: Over-Fragmenting Campaigns by Product Taxonomy

Creating a separate campaign or asset group for every brand, subcategory, or price point splits conversion data across units that individually may never accumulate enough volume for automated bidding to stabilize. The result is multiple campaigns in permanent learning mode competing for the same budget. Campaign separation should be driven by genuinely different economic targets, budgets, or creative requirements—not by the desire to mirror a product catalog hierarchy inside Google Ads.^[2]

Mistake 6: Relying on Feed Rules to Mask Bad Source Data

Feed rules are appropriate for normalization, column mapping, and enrichment. They are inappropriate as a substitute for fixing inaccurate source data. A rule that overwrites a live price field with a static value, fabricates a GTIN from an internal SKU, or forces all products into a single Google product category may pass validation while creating systematic mismatches between the feed and the landing page. These mismatches produce disapprovals, policy flags, and poor auction performance. Fixing the source data in the ecommerce platform or ERP is always preferable to layering corrective rules on top of corrupt inputs.^[1]

Mistake 7: Ignoring Image Quality for Variants

A common shortcut is to submit the same image URL for every variant of a product rather than providing variant-specific images. When the feed advertises a navy-blue jacket and the image shows a red jacket, users who click through encounter an unexpected product page. This produces higher bounce rates, lower conversion rates, and risks a policy violation if Google determines that the image materially misrepresents the advertised variant. Each variant should carry an image URL pointing to the correct color, configuration, or model.^[1]

Mistake 8: Setting an Aggressive tROAS Target Before the Learning Period Ends

Applying a tROAS that is materially higher than recent achievable performance immediately after launch—or immediately after a major feed change or budget edit—forces automated bidding into an overly constrained state. The campaign reduces spend to avoid exceeding the target, loses auction volume, and collects fewer conversion signals, which further slows learning. The correct approach is to start close to the account’s recent actual ROAS and move the target incrementally—no more than 10–15% at a time—allowing at least 2–4 weeks of stability between changes, depending on conversion volume.^[2]

Mistake 9: Not Excluding Out-of-Stock and Discontinued Products

Products set to out_of_stock in the feed continue to consume budget in some campaign configurations if exclusion logic is not in place. Discontinued products with stale availability values may still serve impressions, send users to 404 pages or redirect loops, and generate spend with no conversion path. Implement an automated exclusion rule or listing-group filter that removes products below a defined stock threshold and deactivates discontinued items within 24 hours of their status change in the platform.^[1]

Mistake 10: Treating Custom Labels as Customer-Facing Keywords

Custom labels are not visible to users and have no direct effect on query matching or ad relevance. Their sole purpose is internal segmentation for campaign structure, bidding, and reporting. Using them to stuff additional keywords or to mirror title content wastes the five available label slots on non-actionable values. Each custom label should encode a commercial decision—margin tier, stock status, seasonality, price band, or promotional classification—that drives a distinct bidding or budget action in the campaign.^[3]

12. What Changed Recently (Last 30 Days)

The research window for this article covers September 17–October 17, 2026. No verified, authoritative Google announcements for that exact 30-day window were available at publication time. Because this article is a compliance and operations reference, fabricated or speculative change notices would be actively harmful. The guidance below explains how to monitor for changes systematically and which areas are most likely to have evolved based on Google’s established direction.

Important note: All specific feature announcements, policy changes, and threshold updates must be verified directly against Google’s official release notes before acting on them. The sources below are the authoritative channels; no third-party summary should be treated as definitive.

Where to Check for Verified Updates

Source	What it covers	Update frequency	URL
Merchant Center Help — Announcements	Feed requirements, attribute changes, policy updates, new features	As released	support.google.com/merchants/announcements
Google Ads release notes	Campaign types, bidding, reporting, UI changes	As released	support.google.com/google-ads/announcements
Google Search Central blog	Structured data, product markup, crawling behavior	Weekly to monthly	developers.google.com/search/updates
Google Ads blog	Product launches, AI features, advertiser tools	Weekly	blog.google/products/ads-commerce/
Merchant Center product data specification	Attribute definitions, required fields, formatting rules	As revised	support.google.com/merchants/answer/7052112

High-Probability Change Areas to Monitor in Q4 2026

Based on Google’s publicly stated roadmap direction through mid-2026, the following areas are the most likely to see updates during the October–December 2026 period. Check each against verified release notes before changing any account configuration.

• Merchant Center Next consolidation: Google has been progressively migrating accounts from legacy Merchant Center to Merchant Center Next. Verify whether new diagnostics panels, feed-management UI changes, or reporting consolidations have rolled out to your account during this window.^[1]
• Performance Max for Retail controls: Google has been expanding campaign-level controls for PMax, including brand exclusions, search-term category exclusions, and campaign-level negative keywords. Check whether additional controls became available or whether existing controls changed in scope.^[2]
• AI-generated product assets: Google has progressively expanded generative AI tools for product images, titles, and descriptions within Merchant Center and Google Ads. Confirm whether any auto-generated asset features became opt-out rather than opt-in during this period, and review your asset-quality settings accordingly.^[2]
• Free Listings eligibility and surfaces: Google periodically adjusts which products and account types qualify for free product listings across Search, Shopping tab, Images, and Maps. Verify that your account’s free-listings status has not changed and that structured data on product pages continues to meet the current requirements.^[1]
• Shipping and returns attribute requirements: Google has increased enforcement of accurate shipping and returns data throughout 2025–2026. Check whether new required attributes, updated formatting for return-policy fields, or stricter price-consistency enforcement were announced during this window.^[1]
• Consent and privacy compliance: Verify that consent mode implementation requirements, enhanced conversions guidance, or customer-data policies were not updated in a way that affects your tagging or conversion tracking setup. This is especially relevant for accounts using first-party audience signals in PMax.^[2]

How to Run a 30-Day Change Audit

Because Google does not always surface policy and requirement changes prominently in the Merchant Center UI, a structured monthly audit reduces the risk of operating on outdated assumptions. The following process can be completed in under two hours by a senior account manager or feed specialist.

• Check the Merchant Center announcements page and Google Ads release notes for the prior 30 days. Screenshot or log any change that affects required attributes, bidding, or campaign types in your account.
• Open Merchant Center diagnostics and compare the current disapproval count and disapproval reason distribution to the prior month. An increase in a new disapproval reason—particularly one not present in the prior period—often indicates a policy enforcement change rather than a feed error.
• Review the product data specification page for any revised attribute definitions, new required fields, or updated formatting rules. Compare the current specification to the version you last audited and note any delta.
• Check whether any new campaign-level controls appeared in the Google Ads interface for your active PMax or Standard Shopping campaigns, particularly under campaign settings, asset group settings, or the brand exclusions panel.
• Verify that your conversion tracking implementation still meets current requirements. Check enhanced conversions, consent mode status, and conversion action configuration against any updated guidance.

Staying Current: Standing Operational Practices

Because Google Shopping and Merchant Center evolve continuously, a reactive approach to change management—waiting until disapprovals appear or performance drops—consistently underperforms a proactive audit cadence. The following standing practices minimize operational risk between formal audits.

• Subscribe to Merchant Center email announcements and Google Ads release note notifications so changes reach a named team member rather than sitting unread on a help page.
• Store a dated snapshot of the product data specification attributes table monthly. A diff between last month’s snapshot and this month’s version reveals any added, removed, or redefined attribute faster than reading the full specification.
• Treat an unexpected increase in any single disapproval reason as a potential policy change signal, not automatically as a feed error. Investigate the release notes for that period before beginning feed edits.
• After any major Google Ads UI update, re-verify that automated bidding targets, asset group configurations, and listing group structures are intact. UI migrations have historically moved settings or reset configurations in edge cases.
• Conduct a structured conversion tracking audit quarterly. Verify that the purchase conversion action remains the primary optimization target, that transaction values are passing correctly in USD, and that no secondary or proxy conversion action has been accidentally promoted to primary status during a UI or tagging update.^[2]