Generate Merchant Center-ready product data with required Google fields, source-backed copy, review states, and feed validation. Central starts from the product data you have, verifies the facts, and prepares the output with review states before it ships.
The Merchant Center error you've seen before. Title too long. GTIN missing. Wattage value doesn't match the landing page. Promotional language in the title. Central catches the same checks Google runs — in your record, before submission.
Title hype, price drift, missing identifiers, category mapping, image dimensions — all enforced in the canonical record, so the Merchant Center diagnostics report stays empty.
The 12 required Google Merchant attributes — plus the common recommended ones — checked against your verified record, with the source that backed each value and the readiness state per field.
Title length, GTIN format, image resolution, category taxonomy, identifier_exists, condition, availability — every check Google runs at submission time, run first in Central.
Same shape as the Merchant Center submission flow you already know — but every check runs in Central first, against the verified record, before Google ever sees it.
Paste a shop URL, upload a CSV, or connect a catalog. Central maps your fields to Google's expected attributes and shows which ones are filled and which are missing.
Title length, GTIN format, image resolution, category taxonomy, promotional language — every Merchant Center rule runs locally. Disapprovals surface here, not at submission.
Channel Studio drafts titles, descriptions, highlights, and attributes from verified facts. Merchant values stay in control for prices, stock, identifiers, URLs.
Merchant Center-ready XML or CSV. Schedule re-exports, push by URL, or sync directly. Review states ride along, so unsupported claims never enter the feed.
The same Le Creuset SKU. Sparse import on the left. The Google Merchant Center XML feed entry on the right — required fields filled, characters counted, identifiers validated, one claim held.
<?xml version="1.0" encoding="UTF-8"?> <feed channel="Google Merchant Center"> <item> <g:id>SIG-RND-26-CER</g:id> <title>Le Creuset Signature Round Dutch Oven, Cast Iron, 26 cm, 5.3 L, Cerise</title> <description>Enameled cast iron, oven-safe to 260 °C, induction-compatible.</description> <link>https://shop.le-creuset.eu/p/sig-rnd-26-cer</link> <g:image_link>/products/signature-round-26.jpg</g:image_link> <g:brand>Le Creuset</g:brand> <g:gtin>0024147210504</g:gtin> <g:price>379.00 EUR</g:price> <g:availability>in_stock</g:availability> <g:condition>new</g:condition> <g:google_product_category>630</g:google_product_category> <g:product_highlight>Enameled cast iron, oven-safe to 260 °C</g:product_highlight> <g:product_highlight>5.3 L capacity, induction-compatible</g:product_highlight> <g:product_highlight>Lifetime manufacturer warranty</g:product_highlight> <g:product_highlight>Available in 21 colors</g:product_highlight> <!-- Central adds structured product_detail Google's optional --> <g:product_detail> <g:section_name>Material</g:section_name> <g:attribute_name>Construction</g:attribute_name> <g:attribute_value>Enameled cast iron</g:attribute_value> </g:product_detail> <g:product_detail> <g:section_name>Dimensions</g:section_name> <g:attribute_name>Capacity</g:attribute_name> <g:attribute_value>5.3 L</g:attribute_value> </g:product_detail> <g:product_detail> <g:section_name>Performance</g:section_name> <g:attribute_name>Max oven temperature</g:attribute_name> <g:attribute_value>260 °C</g:attribute_value> </g:product_detail> <g:product_detail> <g:section_name>Compatibility</g:section_name> <g:attribute_name>Heat sources</g:attribute_name> <g:attribute_value>Induction, gas, electric, ceramic, halogen</g:attribute_value> </g:product_detail> <!-- "Pro-grade performance" held — no source --> <g:review_state>ready</g:review_state> </item> </feed>
Google Shopping, Free Listings, Performance Max, Microsoft Shopping — all consume the same verified facts, shaped to each destination's character limits and field rules.
The same Merchant Center feed powers Shopping ads. Add bidding, audiences, and campaign assets in Ads — copy stays grounded in the record.
See Shopping setupSame feed, no spend — surface across Google Search, Images, and Lens. Required attributes overlap with Shopping; Central fills both at once.
See Free ListingsPMax pulls from Merchant Center plus asset inputs. Verified record powers the feed; Channel Studio drafts the asset variations.
See PMax inputsMicrosoft Shopping reads the same verified record with different character limits and policy rules. One adaptation, no rewrites.
See Bing setupCentral prepares and publishes Google Merchant Center output from verified product records. Platform review, account settings, and destination policies still apply — Google approves the feed.
Start with a shop URL, product URLs, a CSV, supplier files, or existing catalog data. Central uses what you already have and shows what is missing for Google Merchant Center.
Central drafts copy from verified facts. Unsupported claims stay hidden or marked for review until evidence or a merchant decision supports them.
Identifiers, URLs, prices, stock, availability, account settings, shipping values, and other commercial invariants. Central validates and formats them while keeping merchant-sourced values intact.
Yes. The same verified product record supports Google MC, Bing MC, ChatGPT Shopping, Perplexity, plus custom CSV / XML / JSON feeds, storefront copy, product widgets, Schema.org, and JSON-LD.
The output view shows required fields, source evidence, confidence, conflicts, blocked claims, and review decisions before anything ships. The Merchant Center diagnostics report stays empty.