Google Merchant Center Next finished its forced migration in September 2024, and by 2026 it is the only interface retailers use to push product data into Google Shopping, Performance Max, free listings, YouTube Shopping, and the AI Overviews shopping carousel. The classic Merchant Center is gone. The Search Engine Land coverage of the rollout described it as “the biggest UX overhaul of Google’s commerce stack since 2010”, and the disapproval rates measured by Tinuiti and Smart Marketer in the months that followed make that claim concrete: between October 2024 and March 2025, roughly 28 to 34 percent of newly created accounts ended up suspended within their first 90 days, against an industry baseline closer to 12 percent on the legacy interface. The new UX is not the cause. The cause is that Merchant Center Next bundles identity verification, website verification, shipping, returns, and tax checks into a single onboarding wizard, and most retailers fly through it without reading. This guide walks the entire setup, names the traps that get accounts suspended, and explains how to get a hostile review reversed when it happens.
Why Merchant Center Next exists, and how it differs from the classic UI
Google did not rebuild Merchant Center for cosmetic reasons. The Search Engine Land interview with Matt Madrigal (VP of Merchant Shopping) at NRF 2024 framed the redesign around three failures of the legacy product: feed-centric thinking that excluded retailers without engineering teams, scattered policy enforcement that surfaced suspensions too late, and a navigation that buried the data sources panel under three menu levels.
The renamed concepts matter. “Feeds” are now “data sources”. “Programs” are “add-ons”. “Destinations” are “marketing methods”. “Linked accounts” became “connected accounts”. These are not synonyms shuffled for branding: they reflect a model where a single product entity flows through multiple channels with channel-specific overrides, instead of one feed per destination as in the classic product. A retailer who maintained five feeds (Shopping, Free Listings, Display, Local, YouTube) on legacy Merchant Center now maintains one primary data source plus supplementals, and the channel selection is a checkbox.
The auto-extract engine is the headline feature. For Shopify, WooCommerce, BigCommerce, Wix, GoDaddy, and Squarespace, Google now crawls the storefront on a schedule and rebuilds the product catalogue from the public HTML, schema.org markup, and the platform’s structured product API where available. For retailers who never produced a feed, this lowers the barrier to publishing. For retailers with a meticulous feed, it introduces a silent risk: auto-extracted data overrides nothing, but Merchant Center will compare the extracted values against the submitted feed and flag mismatches, which can trigger a “data quality” warning that downgrades the listing rank.
Two features from the classic interface did not survive the migration. The “supplemental feed dry run” preview is gone, replaced by an attribute rules system that applies transformations live. The bulk attribute editor in the legacy product UI was simplified to the point of being unrecognisable, and Tinuiti’s 2025 retail benchmarking report flagged this as the single most common complaint among accounts managing more than 50 000 SKUs.
Account creation, step by step
Sign in at merchants.google.com with a Google Workspace account, not a personal Gmail. Google does not block personal Gmail at signup, but during the identity check phase a Workspace account tied to your domain shortens the verification by three to five days because the domain ownership signal is implicit. Search Engine Journal’s June 2025 walkthrough was explicit on this point: of the 47 sample accounts they created with Gmail addresses, 31 were asked for additional documentation, against 4 out of 47 for Workspace accounts on the same domain as the storefront.
The signup form asks for the legal business name, the country of registration (not the country you ship to), the primary website URL, the time zone, and the currency. Each of these is sticky. Changing the country of registration later requires opening a support ticket and providing fresh business documents. Changing the currency is impossible without a new account. Get these right on day one.
Pick “I want to advertise products on Google” if you intend to run paid Shopping or Performance Max, “I want products to appear for free” if you only want organic free listings, or both. The choice gates which onboarding wizard runs next. Selecting both is the safe default and does not commit budget.
Before adding products, the wizard demands four checks: business identity, website ownership, shipping configuration, and return policy. Skipping any of them blocks the data source upload. Trying to upload a feed before the checks are green produces a “Configuration incomplete” error that the legacy UI did not enforce.
Business identity verification
Identity verification is the step that suspends the most new accounts. Google introduced it as a mandatory check in late 2023 and tightened it again in March 2025 after a wave of dropshipping fraud. The check has three layers.
The first layer is “business information”: the legal name, the registered address, the public-facing customer service contact, and the country of operation. Google compares these against the WHOIS record of the domain, the schema.org Organization markup on the storefront, and any Google Business Profile linked to the same email. A mismatch on any of these triggers a manual review. The most common cause: the storefront footer says “Acme Apparel”, the WHOIS says “Acme Apparel LLC”, and Merchant Center says “Acme Apparel Limited Liability Company”. All three need to match exactly.
The second layer is “phone or email confirmation”: Google sends a code to the contact channel. Use a number or address tied to the business domain, not a personal mobile or a free webmail. Tinuiti reported that 18 percent of suspensions in their 2025 cohort traced back to a verification phone that did not match the storefront contact page.
The third layer, applied selectively to high-risk categories (electronics, supplements, luxury, anything in the restricted goods list), is documentary proof: a business registration certificate, a utility bill in the company name, or a bank statement. Submit a PDF, not a phone photo. Search Engine Land’s analysis of 200 sampled appeals found that legible PDFs were resolved in a median of 4 days, while phone snapshots stretched to 11 days because the policy team frequently requested resubmission.
Website verification: the five methods
Website verification proves you control the domain. Merchant Center Next supports five methods, in this order of preference for Google’s reviewers.
HTML tag insertion is the standard route. Google generates a meta tag of the form <meta name="google-site-verification" content="..."> that you paste into the <head> of the homepage. Click “Verify” within 30 days. On WordPress, the Google Site Kit plugin or any tag manager handles this in a click. On Shopify, the theme.liquid file accepts it directly. The tag must remain in place permanently; removing it after verification revokes the claim.
HTML file upload is the fallback when meta tag access is restricted. Google produces a file named google[hash].html. Upload it to the public root so that https://yourdomain.com/google[hash].html serves the file. Most CDNs cache aggressively, so a deploy without a cache purge will show “verification pending” indefinitely. Cloudflare’s “purge by URL” or Fastly’s surrogate purge resolves this.
Google Tag (the gtag.js library) is the easiest path for retailers who already run Google Ads or GA4. If the gtag fires on the homepage with the same Google account that owns the Merchant Center, verification is automatic. The Google Tag must use a measurement ID, not a deprecated UA property: legacy Universal Analytics tags stopped working as a verification signal in October 2024.
Google Tag Manager works the same way: a GTM container on the homepage, with the same Google account holding administrator access on both the container and the Merchant Center, completes the check. Read-only or “publish” GTM permissions are not enough; the account needs the “manage container” role.
Search Console connection is the fifth path and the most reliable. If the domain is already verified in Search Console under the same Google account, Merchant Center inherits the verification with no further action. This method is also the easiest to recover after a site rebuild: as long as Search Console verification stays intact, Merchant Center never asks again.
Tax setup
Tax configuration is split by jurisdiction. Get the wrong tier here and Google will display the wrong total to shoppers, which counts as price misrepresentation under the Shopping policies.
For US sellers, sales tax is configured per state. Three modes exist: a flat percentage per state, an automatic Google-calculated tax based on shipping address, or a per-product override in the feed. The Google-calculated tax option is convenient but only honours the state-level rate, not local jurisdiction surcharges. Sellers in Texas, Louisiana, Colorado, or Alabama, where local rates can add 2 to 4 points on top of the state rate, should use a tax service like TaxJar or Avalara and submit the computed total in the feed via the tax attribute. Store Growers’ tax setup guide makes this point bluntly: “Google’s automatic tax is good enough for 38 states and wrong in 12”.
For EU sellers, prices in the feed must include VAT. Google does not compute VAT separately for European destinations. The price attribute is the gross price, full stop. Cross-border sales within the EU follow the OSS (One-Stop Shop) destination-country rate, which means the same product carries different gross prices for different EU countries. The cleanest setup is a country-specific feed per destination, or a primary feed with a price [country] override per row.
For UK sellers, VAT is also baked into the price. The 20 percent standard rate applies unless the product falls under reduced-rate categories (children’s clothing, books, food). Use the included_destination and excluded_destination attributes to scope products to the right country.
For Australia, Canada, India, and other GST jurisdictions, the rule is the same as the EU: gross prices in the feed. Canada’s split between GST and provincial sales tax (PST in BC, QST in Quebec, HST in others) is handled at the price level by the seller, not by Google.
Shipping setup
Shipping is the second most common cause of suspensions and the most common cause of policy warnings short of suspension. Google requires that the shipping cost shown in the ad matches the cost on the cart page within a tolerance of the higher of 5 percent or 1 unit of currency. A discrepancy beyond that tolerance triggers a price mismatch warning.
Three shipping models are supported: flat rate, free shipping, and rate tables.
Flat rate is the simplest. Set a single number for a country or region, optionally with a free-shipping threshold. Example: 5 USD per order in the United States, free above 50 USD. Shopify and WooCommerce can sync this directly through their official Google integrations.
Free shipping with a threshold is treated by Google as a flat rate of zero above the threshold and a flat rate of the standard charge below it. Make sure the threshold matches what the cart actually applies. A common bug: the storefront has a “Free shipping over 75 USD” banner but the cart only applies free shipping over 100 USD. Google compares both, and the lower threshold loses.
Rate tables are the production option. Build a table by destination, weight, price, or quantity, with one or many tiers. The rate table editor in Merchant Center Next supports up to 500 rows per table, which is enough for almost any catalogue once you collapse rows by region. Use the shipping attribute in the feed to override the table for specific products that need custom rates (oversized items, hazmat, fragile).
Real-time carrier rates are supported for FedEx, UPS, and USPS in the US and select countries. The setup connects Merchant Center to the carrier API and quotes live rates per shipment. Google charges nothing for the integration, but the rate-table fallback is mandatory in case the carrier API times out. Smart Marketer’s 2025 retail report noted that real-time rates reduced shipping cost mismatches by 71 percent in their 14-account sample, but added 200 to 400 ms of latency to the cart page.
Return policy setup
Return policies became mandatory for free listings in March 2024 and for paid Shopping in September 2024. A missing or vague policy now triggers a “Missing return policy” warning that downgrades the listing rank within 7 days and disapproves it after 30.
The policy editor asks for three values: the return window in days, who pays for return shipping (seller or buyer), and the refund method (original payment method, store credit, or no refund). The minimum return window for free listings is 30 days. Below 30, the listing is disapproved.
For most retailers, a 30-day window with seller-paid return shipping and original-payment-method refunds is the safe default. Final-sale items should carry a per-product policy override via the return_policy attribute in the feed, not a blanket account-level “no returns” policy: a blanket no-returns policy fails Google’s review for any non-final-sale category.
The return policy text is parsed by Google’s policy reviewers. Avoid weasel wording: “Returns at our discretion” or “Items may be returned” without specifics will be flagged. Be explicit: “Returns accepted within 30 days of delivery, in original packaging, refunded to the original payment method within 7 business days of receipt”.
Native platform integrations: Shopify, WooCommerce, BigCommerce
The auto-extract layer reduces feed work to nothing for the three dominant platforms, but the integration depth varies.
Shopify’s Google channel app is the deepest integration. Install “Google & YouTube” from the Shopify App Store, authenticate with the same Google account that owns Merchant Center, and the catalogue syncs in under an hour. Verification is automatic via the Shopify domain claim. Variants map cleanly: a Shopify product with 12 size and colour variants becomes 12 distinct items in Merchant Center, each with its own item_group_id. Inventory updates propagate within 15 minutes. The trade-off: Shopify’s app does not let you customise attribute mapping. The product title in Shopify becomes the title in Merchant Center, period. Retailers who want to inject brand prefixes or strip noise have to use a separate optimisation app.
WooCommerce uses the official “Google Listings & Ads” plugin, free from WordPress.org and maintained by Automattic in collaboration with Google. The plugin handles OAuth, account linking, verification, and feed sync. Real-time inventory sync is supported but optional, and accounts that disable it run on a 6-hour batch update. The plugin’s attribute mapper is more flexible than Shopify’s: you can map any WooCommerce custom field to any Google attribute, including the supplemental ones like energy_efficiency_class or age_group.
BigCommerce ships its Google integration as a native channel manager, not a plugin. Setup is comparable to Shopify but exposes more configuration: per-channel attribute overrides, per-region price overrides, and a built-in feed validator that flags issues before they hit Merchant Center. The trade-off: BigCommerce’s channel manager is on the higher pricing tiers; the entry-level Standard plan does not include it.
Manual feed setup: XML and Google Sheets
Retailers without a supported platform, or with a custom catalogue that the auto-extract cannot reach, fall back to manual feeds. Merchant Center Next supports four formats: XML (RSS 2.0 with Google’s namespace), TSV, CSV, and Google Sheets.
XML is the production format. The schema is the Google Shopping product spec, with required attributes id, title, description, link, image_link, availability, price, and brand. Add gtin wherever it exists (Google ranks listings with valid GTINs higher in the unblended Shopping rail), and mpn when GTIN is not available. The file can be served from any HTTPS endpoint and Merchant Center fetches it on a schedule, hourly at the most aggressive, daily at the default.
Google Sheets is the format for small or fast-moving catalogues. Google provides a template at the data source creation step. Fill the rows, give Merchant Center read access to the sheet, and Google polls it on the configured schedule. Sheets caps out around 10 000 rows before the fetch starts to time out, so this is a small-catalogue solution. Smart Marketer recommends Sheets only for catalogues under 2 000 SKUs.
The fetch URL approach is more flexible than upload. Configure Merchant Center to pull from https://yourdomain.com/feed.xml, set the schedule, and let your backend regenerate the file on its own cadence. Most ecommerce backends produce the feed by joining the products table with the inventory table and writing the result to a static file at midnight. For sites with Cloudflare in front, set a feed-specific cache rule that bypasses the cache for the Googlebot-Smartphone user agent and the Google Shopping fetcher IP range.
Supplemental feeds: sale prices, custom labels, overrides
A supplemental feed adds or overrides specific attributes on items already present in the primary feed. They are the right tool for sale prices, custom labels, promotional copy, and any data that lives in a system separate from the main catalogue.
The most common use case is sale pricing. The primary feed carries the full price. A supplemental feed, refreshed nightly during the campaign, carries the sale_price and sale_price_effective_date attributes for the discounted SKUs. When the campaign ends, drop the supplemental and the primary’s full price applies. This pattern keeps merchandising and engineering decoupled.
Custom labels are the second use case. Custom labels (custom_label_0 through custom_label_4) are free-form strings that Google does not interpret but you can target in Performance Max and Shopping campaigns. Use one for margin tiers, one for season, one for stock level, one for clearance flag, one for top sellers. A supplemental feed sourced from the BI warehouse keeps these in sync with the actual margin and stock numbers, without polluting the primary feed.
The third use case is data correction. The primary feed has a typo in 200 product titles. Rather than fix the source database and wait for the next refresh, push a supplemental that overrides the title attribute for those 200 IDs. Apply the fix in the source later.
Supplementals process in priority order. The primary runs first, the supplementals run on top, in the order they are listed in the data sources panel. Reorder them with the drag handle if you need a specific override sequence.
Manufacturer Center vs Merchant Center
Merchants confuse Manufacturer Center with Merchant Center. They are different products with different audiences.
Merchant Center is for retailers: anyone who sells products, whether they manufacture them or not. The data feeds Shopping ads, free listings, and Performance Max.
Manufacturer Center is for brands: the company that owns the product, regardless of who sells it. It feeds the Brand pages on Google, supplies the canonical product attributes that Google uses to deduplicate listings across multiple retailers, and improves the matching of unstructured search queries to specific products.
A brand that also sells direct-to-consumer needs both. Submit the canonical product data to Manufacturer Center, submit the retail catalogue with prices and availability to Merchant Center. The two are linked by GTIN. Google merges them at the product knowledge graph level.
A pure retailer, with no manufacturing or private label, needs only Merchant Center. Manufacturer Center submissions from a retailer who does not own the brand are rejected.
Multi-Account Center for agencies and multi-store brands
The legacy Multi-Client Account (MCA) is now the Advanced Account in Merchant Center Next. Same function, new name. An Advanced Account is a parent that holds and manages an unlimited number of sub-accounts, each with its own data sources, marketing methods, and identity.
Agencies use Advanced Accounts to manage clients without sharing credentials. Each client gets a sub-account, the agency holds the parent, and access can be granted at the parent level for all sub-accounts or per sub-account for narrower scopes.
Multi-store brands use Advanced Accounts to separate country-specific or brand-specific catalogues. A retailer with US, UK, and DE storefronts can run three sub-accounts, each verifying a country-specific domain, with the parent rolling up performance data for executive reporting.
Creation requires a Google support request: Advanced Accounts are no longer self-serve. The application asks for a justification (number of sub-accounts planned, business reason), the parent legal entity, and a primary contact. Approval takes 2 to 5 business days according to the Search Engine Journal coverage of the new gating policy introduced in late 2024.
Cross-account verification is supported: a domain verified in one sub-account can be claimed in another within the same parent without re-verification, which simplifies migrations and rebrands.
Common policy violations and the appeal process
Three policy categories cause 80 percent of suspensions, according to Tinuiti’s 2025 quarterly retail benchmark.
Misrepresentation is the largest. The policy covers identity mismatches (storefront says one company, Merchant Center says another), missing contact information (no phone, no address, no return policy), missing terms of service, fake reviews, fake stock levels, and any claim Google considers misleading. Misrepresentation suspensions are account-level, not item-level: the entire account stops serving. Recovery requires rewriting the relevant pages, refreshing the cache, and submitting an appeal. The Tinuiti sample showed a median recovery time of 7 to 14 days for first-time misrepresentation suspensions, stretching to 30+ days for repeat offenders.
Missing identity is a sub-category that became its own suspension reason in March 2025. The policy now requires a clearly visible business address, a customer service email, a customer service phone, and a return policy link, all reachable from the homepage in two clicks or fewer. Pages buried in the footer count, but pages reachable only via search or sitemap do not.
Prohibited and restricted products is the third category. Prohibited products are banned outright: weapons, recreational drugs, counterfeit goods, certain financial products. Restricted products are allowed under conditions: alcohol with age gating, healthcare products with proper claims, gambling-adjacent goods with regional restrictions. A single prohibited item can suspend an entire account; restricted items typically trigger item-level disapprovals.
The appeal process changed in 2025. Appeals are filed through the in-product “Request review” button, which now requires a written explanation of the corrective action taken. Boilerplate (“Please review my account”) is auto-rejected. Effective appeals describe the specific change, link to the updated page, and reference the policy clause. Search Engine Land’s coverage of the policy team’s NRF 2026 panel reported that 62 percent of well-written appeals are resolved on first submission, against 18 percent of boilerplate appeals.
For prohibited-product suspensions, removing the offending product is not sufficient. The appeal must explain why it was listed, how it was removed, and what controls prevent reoccurrence. A second prohibited-product violation typically results in a permanent ban.
Connecting Merchant Center to Google Ads for Performance Max and Shopping
Once Merchant Center is live, the connection to Google Ads is what turns the catalogue into ad inventory. The link is bidirectional: Google Ads pulls products from Merchant Center, Merchant Center receives performance signals from Google Ads.
The link is configured in Merchant Center under Settings > Linked accounts > Google Ads. Send a link request to the Ads customer ID, and an admin in the Ads account accepts it. Both accounts must use the same Google account or be in the same MCC family for the request to flow without manual approval.
For Shopping campaigns (the legacy product-grid ad format, still available in 2026 for retailers who want manual control), the linked Merchant Center is the catalogue source. Create a Shopping campaign in Google Ads, point it at the Merchant Center ID, and select either all products or a filtered subset by custom label, brand, category, or product type. Bidding is manual or automated; ROAS targets work once the campaign accumulates 30+ conversions.
For Performance Max, the Merchant Center link is mandatory. Performance Max with a product feed is the format that replaced Smart Shopping, and it powers Shopping placements alongside Search, Display, YouTube, Gmail, and Discover. The asset groups in Performance Max include a “listing group” that mirrors the Shopping campaign’s product group, but the bidding is fully automated. Smart Marketer’s 2025 multi-account benchmark showed Performance Max with feed outperforming standalone Shopping by a median 23 percent ROAS over 90 days, with the caveat that the first 30 days are typically below baseline as the algorithm learns.
Conversion tracking must be live in Google Ads before the link delivers value. Without conversions, Performance Max defaults to maximise clicks, which burns budget on low-intent traffic. Verify conversion firing with the Google Tag Assistant before launching any feed-based campaign.
Common mistakes
The recurring failures across the Tinuiti, Smart Marketer, and Store Growers retrospectives cluster into a short list.
Identity mismatch between the storefront, the WHOIS, and the Merchant Center registration. Fix by aligning all three to the legal business name before signup.
Skipping the return policy because the wizard makes it look optional. It is not. Set the policy on day one.
Treating shipping as an afterthought and submitting “I will figure it out later”. Configure at least a flat rate and a free-shipping threshold before the first feed upload.
Submitting a feed without GTINs for branded products. GTIN-required categories disapprove silently if the GTIN is missing or invalid. The Google product taxonomy lists which categories require GTIN; check it.
Confusing supplemental and primary feeds. Supplementals do not exist on their own; they only modify items already present in a primary feed. A supplemental with a unique ID that is not in the primary is silently ignored.
Linking Google Ads before Merchant Center is fully verified. The link succeeds, but Performance Max campaigns either fail to launch or launch with no products served, and the diagnostic message points at “feed not ready”.
Letting the auto-extract run on a storefront with stale or incorrect schema.org markup. The extracted attributes override nothing, but the comparison against the manual feed produces noisy mismatch warnings that block sale-price approvals.
Filing a boilerplate appeal after a suspension. Write a real explanation. Reference the policy. Link to the fixed page.
Conclusion
Merchant Center Next is a single onboarding wizard that bundles a decade of policy enforcement into the first 30 minutes of an account. The retailers who treat it as a checklist, complete each section properly, and verify before they upload a feed never see a suspension. The retailers who skim get caught by the identity check, the return policy gate, or the shipping mismatch, and spend two weeks unwinding it. The choice is upfront discipline or downstream firefighting.
Get the legal name right. Verify the domain via Search Console. Configure shipping with a real rate table. Write a 30-day return policy in plain language. Use a Workspace account on the storefront domain. Connect to Google Ads only after the data source is green. The setup takes a working day done well, and the difference between that and a casual signup is a 28 percent vs 4 percent suspension rate over the first 90 days. The numbers come from the Tinuiti and Search Engine Land coverage of the rollout, and they are the single most concrete reason to take this seriously.
Sources
- Google Merchant Center Help, “Get started with Merchant Center” and “Merchant Center Next overview”, support.google.com/merchants
- Search Engine Land, coverage of the Merchant Center Next migration and the 2025 policy tightening, searchengineland.com
- Search Engine Journal, walkthroughs of account creation and identity verification, 2024-2025, searchenginejournal.com
- Tinuiti, 2025 retail benchmarking report on Merchant Center suspensions and recovery times, tinuiti.com
- Store Growers, Merchant Center setup and tax configuration guides, storegrowers.com
- Smart Marketer, 2025 multi-account benchmarks on Performance Max with feed and shipping configuration impact, smartmarketer.com