Google Merchant Center in 2026: Set Up a Product Feed and Fix Errors

Google Merchant Center receives an online store’s product data and makes it available across Google’s shopping surfaces. The data tells Google each item’s title, image, price, availability, brand, variant, shipping terms and landing page. An approved feed may support free listings, Shopping campaigns and retail Performance Max. Poor data can restrict visibility, disapprove individual products or create account-level problems.

Merchant Center cannot repair an unprepared store. A perfect XML file will not compensate for broken product pages, stale prices, hidden delivery charges, missing returns information or an unusable checkout. Feed requirements should therefore be planned during online store development rather than one day before advertising begins.

Merchant Center and product feeds

Merchant Center is the account where a business verifies its store, adds product sources, configures shipping and returns, reviews issues and links Google Ads. A product feed is a structured source containing one item for each product or purchasable variant.

Google compares at least three layers:

1. data sent through a feed or API;
2. information displayed on the product landing page;
3. account settings and policies.

If the feed says UAH 1,999, the page says UAH 2,199 and checkout charges UAH 2,399, the difference is not a cosmetic data error. It is a poor customer experience. Every layer should use one authoritative catalogue.

What changed in the 2026 specification

Google updates the product data specification regularly. Its 14 April 2026 update introduced new product-level shipping fields including handling_cutoff_time and minimum_order_value, plus the optional video_link attribute. Video serving and policy or quality validation began on 30 June 2026.

Google also announced a 500×500-pixel minimum resolution for primary and additional product images. Warnings started in 2026, with enforcement scheduled for 31 January 2027. Stores should replace weak images before the deadline rather than waiting for catalogue disapprovals.

Do not copy an attribute list from an old plugin tutorial. Check the current specification for the target country, product category and destination before a large import.

Prepare the store first

Before adding products, confirm that:

• the domain works over HTTPS;
• product URLs open without login;
• price, currency and availability are visible;
• the item can be added to cart and purchased;
• seller and contact information are accessible;
• payment, shipping, returns and privacy terms are genuine;
• checkout has no hidden mandatory fees;
• required crawlers are not blocked;
• the mobile flow works;
• page and product-data languages match.

If the business itself is still being prepared, use the online-store launch plan before submitting the catalogue. Fixing fulfilment and policies before review is cheaper than rebuilding them after a warning.

Initial account setup

Interface labels may change, but the underlying sequence is stable:

1. create the account with a controlled business email;
2. enter accurate business and address information;
3. verify and claim the domain;
4. choose selling countries and languages;
5. configure shipping cost and delivery time;
6. add the returns policy;
7. select a product-data source;
8. upload a small representative test group;
9. resolve critical issues;
10. link Google Ads after the catalogue is stable.

Do not share one password with a whole team. Use roles and separate access. The business should retain ownership even when an agency manages implementation.

Ways to submit product data

A daily manual CSV is unreliable when stock and price change hourly. Synchronisation should run before data becomes stale. A successful plugin sync is not proof of a good feed; inspect the submitted output.

Core attributes

Requirements vary by country and category, but the practical core includes:

Technical attribute names and supported values must be submitted in English. Free-form content such as title and description should use the same language as the feed and landing page.

Keep the product ID stable

The id should not change when price, copy or imagery changes. Otherwise Google treats the record as a new item, loses continuity and has to process it again.

A good ID is:

• unique within the account and source;
• independent of export row order;
• free of random timestamps;
• retained during a CMS migration;
• distinct for separately purchasable variants.

Use a catalogue key or SKU, but do not replace it when marketing renames a product.

Write useful product titles

Titles help match products to demand. They must remain accurate and readable.

A practical pattern is:

product type + brand + model + key attribute + colour/size

Example: Nike Air Max 90 Women's Trainers, White, Size 38.

Avoid “buy cheap,” shipping promises, phone numbers, excessive capitals, emoji and synonym lists. Place decisive details early without repeating the same word. A feed title can be more structured than a short H1, but it must not contradict the landing page.

Product descriptions

Explain what the item is, who it is for and which verified features matter. Include material, purpose, compatibility, package contents, dimensions and important usage conditions. Do not repeat shipping copy in every description when dedicated settings exist.

Avoid:

• generic marketing with no specifications;
• keyword lists;
• unsupported “number one” claims;
• data belonging to another model;
• unnecessary HTML;
• mixed languages in one record.

The landing page should substantiate the feed. Use the high-converting product-page checklist to align content, structured data and checkout.

GTIN, MPN and identifier_exists

GTIN is an official global identifier such as an EAN. If a manufacturer assigned one, submit the genuine code. Never invent a number or use a store SKU as a barcode.

A branded product without a GTIN may need brand and mpn. A genuinely unique item with no manufacturer identifiers should follow the specification for identifier_exists. Do not set it to false across the catalogue simply to suppress missing-data errors.

Store identifiers in the main catalogue or ERP rather than entering them manually into an advertising plugin.

Variants: colour, size and material

Every purchasable variant may need its own record, id, price, stock, URL and image. Variants from the same base product use a common item_group_id.

The URL should open the correct variant or make it immediately selectable. An ad for a blue medium jacket must not land on an unavailable red extra-large version.

Product imagery

The primary image must show the item represented by that record. Use sufficient resolution, accurate colour, appropriate framing and a clean background where suitable. Variant records should use the corresponding image.

Avoid on the main image:

• promotional copy or calls to action;
• price, discount and delivery badges;
• logo watermarks;
• borders and decorative padding;
• placeholders;
• another product;
• an excessively small subject.

Use additional_image_link for angles, detail and contextual usage. The 2026 video_link option can enrich a listing, but video does not replace strong still images.

Price, sale price and availability

price must match the page and checkout for the selected variant. Use sale_price and the appropriate dates for a genuine promotion rather than overwriting the normal price without context.

Availability must reflect reality:

• in_stock — available to order;
• out_of_stock — not currently purchasable;
• preorder — a genuine pre-order with clear terms;
• backorder — delayed fulfilment where supported.

Do not mark every product as in stock if managers later cancel the order. Repeated cancellations damage both advertising economics and customer trust.

Shipping, returns and minimum orders

Settings must reflect actual countries, carriers, delivery times and rates. Free shipping thresholds, regional exclusions and oversize surcharges should be represented accurately.

The 2026 specification added product-level controls including handling_cutoff_time and minimum_order_value. Use account-level rules for normal cases and item-level values for genuine exceptions.

The returns policy must be visible on the website and consistent with Merchant Center. Never promise conditions that operations cannot honour.

Structured data and automatic updates

Product/Offer structured data helps Google read page price, currency, availability and condition. Markup must match visible content rather than presenting a hidden, more attractive offer.

Merchant Center automations can update price, sale price, availability and condition based on the landing page. This is a safety net for temporary mismatches, not a substitute for a reliable feed. If automations continually correct thousands of items, investigate the catalogue source, caching, time zones and mapping.

Accurate structured data also supports SEO services, although markup alone never guarantees a rich result or product impression.

Free listings and paid campaigns

Approved items may be eligible for free exposure on supported Google surfaces. Eligibility does not guarantee traffic; visibility depends on the programme, country, demand, relevance, competition and data quality.

For paid promotion, link Merchant Center to Google Ads and use the catalogue in Standard Shopping or retail Performance Max. Professional Google Ads management should test the feed, purchase conversion, value, budget and margin rather than merely creating a campaign.

Prepare the feed for Performance Max

Product data influences what can serve, for which demand and with which details. Before launch:

• clear critical disapprovals;
• segment products by category, margin, season and priority;
• use custom_label for business groupings;
• exclude products that cannot be fulfilled reliably;
• validate purchase, value and currency;
• build asset groups around coherent product sets;
• align budget with expected order economics.

The campaign framework is covered in the Performance Max setup guide. Automation cannot compensate for unreliable inventory.

Ecommerce measurement

Merchant Center provides status and performance information, but the business needs the full journey:

impression → click → view_item → add_to_cart → begin_checkout → purchase → revenue → refund

Send transaction ID, value, currency and item data with each purchase. Do not duplicate one order through both GA4 and a separate tag without a deliberate setup. The foundation is explained in the Google Analytics 4 guide.

Measure margin, cancellations, refunds and new-versus-returning customers, not only platform ROAS.

Common Merchant Center issues

Price mismatch

Typical causes include cache, wrong variant selection, tax handling, geolocation, currency conversion, expired sales and conflicting structured data. Test the landing page while logged out and in the target region.

Availability mismatch

The feed says in_stock while the page or schema says out_of_stock. Establish one inventory source and synchronise the CMS, ERP, cache and export.

Missing or invalid GTIN

Do not generate one. Obtain the manufacturer data, correct the format or submit the appropriate identifier combination for that product type.

Image issues

Replace overlays, watermarks, tiny files and unrelated images. Confirm that Googlebot-image can access a stable URL without a 403 response.

Landing page not working

Check 404 and 5xx responses, timeouts, redirects, country blocks, cookie walls and login requirements. The URL must open a specific purchasable product, not a homepage or generic category.

Policy or account issue

An item disapproval and an account suspension are different levels. Review business identity, contact details, checkout, payment, shipping, returns and offer accuracy—not just the XML row.

Use the Needs attention workflow

1. Separate account-level and product-level issues.
2. Remove priority filters to see every issue.
3. Export examples and affected-item counts.
4. Identify a shared rule, category, language, template or source.
5. Fix the system rather than ten rows manually.
6. refresh the source and allow it to process;
7. request review only after the live issue is resolved.

Google distinguishes warnings from disapprovals. A warning can limit performance; a disapproved item stops serving. Repeated review requests are not a replacement for a real fix.

Quality control before campaign launch

Select 20–30 representative products: best sellers, discounted items, variants, expensive products, items without GTIN, out-of-stock products and pre-orders. Compare feed, page, schema and checkout.

Check:

• stable ID;
• accurate title and description;
• working URL and canonical;
• matching image;
• real price and availability;
• brand and GTIN/MPN;
• variant and item group;
• shipping and returns;
• mobile purchase;
• purchase measurement.

Budget for feed, analytics and landing-page work as well as media. The complete cost framework is covered in Google Ads cost in 2026.

Weekly operating routine

• review account-level issues;
• inspect new disapprovals and warnings;
• track the approved-product rate;
• find products receiving no impressions;
• sample prices and stock;
• inspect import errors;
• review products with spend but no sales;
• incorporate cancellations and refunds;
• monitor plugin or API releases;
• record changes in a log.

Large catalogues need alerts, logging and an assigned owner. A problem found a week late may already have stopped a priority category from selling.

Launch checklist

Store

• Domain is verified and HTTPS works.
• Seller and contact information are available.
• Payment, delivery and returns terms are genuine.
• Checkout works on desktop and mobile.
• Page, cart and checkout show consistent prices.

Feed

• IDs remain stable.
• Titles describe the exact products.
• GTIN, MPN and brand are genuine.
• Variants share the right item_group_id.
• Images meet requirements and match variants.
• Sync frequency matches catalogue changes.

Account and campaigns

• Country, language, currency and shipping align.
• No critical account-level issue remains.
• A representative sample was manually checked.
• Purchase includes value and currency.
• Products are segmented by business priority.
• Budget, margin and target ROAS are defined.

Conclusion

Merchant Center performance begins with a truthful catalogue, not the “link Google Ads” button. Stable IDs, accurate copy, valid identifiers, relevant images and synchronised prices and stock create the foundation for free listings and product ads.

Start with a representative test group, correct systemic causes, verify the journey through revenue and only then scale the catalogue and budget. For a store, feed and campaign audit, contact BB STUDIO.