BigCommerce stores feel like they should not get suspended on Google Merchant Center. The Google Channel is native, the Content API connection is one click, and the platform handles a lot of feed plumbing automatically. That is exactly why most BigCommerce suspensions catch owners by surprise: the failure modes are all in the BigCommerce settings, not in Merchant Center.
Six BigCommerce-specific configuration choices cause almost every suspension we see on the platform. Each one is fixed in the control panel, not in Merchant Center. Here is the list, with the exact path to each setting.
1. Google Channel inheriting the wrong Price List
BigCommerce supports multiple Price Lists per channel. When a developer creates a B2B-only price list and assigns it as default for the Google Channel, the prices Google receives diverge from the public storefront. Google then flags the account as price mismatch even though the storefront price looks correct.
Fix: Channel Manager > Google Channel > Settings > Price List = Default.
2. Permanent-domain canonicals leaking into the feed
Every BigCommerce store ships with a permanent domain in the form yourstore.mybigcommerce.com. If the custom domain is set as primary but the permanent domain remains active, Googlebot can discover product URLs on both. The Content API may then submit a permanent-domain URL as the canonical link, which Google rejects.
Fix: Settings > Domain Names > select primary > tick 'Redirect permanent domain to primary domain'.
3. Channel-level currency override
BigCommerce multi-currency lets you display GBP on one storefront and USD on another. The Google Channel inherits the channel's currency. If the channel was configured during a multi-region test, the feed can end up exporting prices in the wrong currency.
Fix: Storefronts > Currencies. Confirm the primary channel currency matches the price tags on the storefront.
4. Default Help Centre returning empty policy text
BigCommerce includes a Help Centre out of the box, but the default template often contains placeholder text rather than actual return-policy and shipping-policy content. The page renders successfully (HTTP 200), so the merchant never notices, but Google's policy crawler sees an empty page.
Fix: Storefront > Web Pages > Help Centre > edit each policy section so it contains real policy text.
5. Customer-group pricing hiding real prices from Googlebot
B2B stores sometimes require login to view prices. With that setting on, Googlebot sees 'Login for price' instead of a number. Without a visible price, Google cannot verify the feed price against the storefront.
Fix: disable guest hiding for the products submitted to Google, or remove those products from the Google Channel feed.
6. Missing Product schema after a Stencil theme update
BigCommerce themes generate Product schema automatically, but custom edits often delete the snippet without warning. Without valid Product schema on product pages, Google's structured-data check fails.
Fix: validate every product page in Google's Rich Results Test and restore the schema if missing.
The April 2026 AI verification adds one more failure mode
Google's AI verification layer now cross-references the contact page email and phone number against the WHOIS record. Many BigCommerce merchants buy domains through registrars that default to privacy protection. When the AI finds 'Domains By Proxy' in WHOIS, verification fails.
Fix: disable WHOIS privacy temporarily during the verification window, or add an explicit 'Registered business' block to the contact page that names the legal entity.
Full guide and the 43-point audit
The full BigCommerce recovery workflow (7 steps, with the exact appeal text), plus how it interacts with Performance Max suspensions, is in the BigCommerce GMC Suspended fix guide.
If you want to know which of these six are currently triggering on your store before submitting an appeal, the free 43-point audit at gmcsuspension.com runs in about 60 seconds and surfaces every Merchant Center policy issue on the public storefront. No signup, instant results.
Top comments (0)