BigCommerce stores account for a quiet but growing share of Merchant Center suspensions. The platform feels well-integrated (Google Channel is native, the Content API connection is one click), so most owners assume any Shopping issue is on Google's side. It usually is not. Six BigCommerce-specific configuration choices cause almost every suspension we see on the platform, and each one is fixed in the control panel, not in Merchant Center.
This guide covers the six BigCommerce-specific suspension causes, the exact settings that resolve each one, the 7-step recovery workflow, and what the April 2026 AI verification layer added to the review process. If your account is suspended right now, start with step 1, run the free audit before appealing, and use the FAQ at the bottom to handle edge cases.
Before you appeal: run the free 60-second GMC audit against your BigCommerce storefront. It checks all 43 Merchant Center policy requirements and surfaces BigCommerce-specific issues (channel-price mismatch, default-domain verification, missing return-policy rendering) that often slip through a manual check. Appealing with one of those still active resets the cool-down clock.
The six BigCommerce-specific suspension causes
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 accidentally assigns it as default for the Google Channel, the prices Google receives diverge from the public storefront. Google flags the account as price mismatch even though the storefront price is correct. Fix: Channel Manager > Google Channel > Settings > Price List = Default.
2. Permanent-domain canonical 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 may discover product URLs on both. The Content API can then submit a permanent-domain URL as the canonical link, which Google rejects because it does not match the verified domain. Fix: Settings > Domain Names > select primary domain > tick "Redirect permanent domain to primary domain".
3. Channel-level currency override silently changing prices
BigCommerce multi-currency lets you display GBP on the EU storefront and USD on the US storefront. The Google Channel inherits the channel's currency, not the customer's IP. If the channel was configured during a multi-region test, the feed can end up exporting prices in the wrong currency. A USD 99.00 product submitted as GBP 99.00 produces a price mismatch on every product simultaneously. Fix: Storefronts > Currencies > confirm the primary channel currency matches the price tags on the storefront.
4. Default Help Centre template returning empty policy text
BigCommerce includes a Help Centre page 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 and flags the account for missing return policy. Fix: Storefront > Web Pages > Help Centre > edit each policy section so it contains the actual policy text, not the placeholder.
5. Customer-group pricing hiding real prices from Googlebot
BigCommerce can require a login to view prices on B2B stores. If the "Hide prices from guests" setting is on, Googlebot sees "Login for price" instead of a number. Without a visible price, Google cannot verify the feed price against the storefront, and the account is suspended for misrepresentation. Fix: either 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 (Stencil framework) generate Product schema automatically, but custom theme edits often delete or break the snippet without warning. Without valid Product schema on product pages, Google's structured-data check fails. This shows up as a "products disapproved" warning, escalates to account suspension after enough disapprovals. Fix: validate every product page in Google's Rich Results Test (search.google.com/test/rich-results) and restore the schema if missing.
The 7-step BigCommerce recovery workflow
Run the 43-point audit against your live storefront
Use the free GMC scan with the URL of your primary custom domain (not the permanent domain). The audit returns the exact issues Google's reviewer will see, so you can fix them before appealing rather than discovering them in the rejection email.
Confirm Channel Manager is on the Default Price List and correct currency
Channel Manager > Google Channel > Settings. Match the Price List and Currency to what the public storefront displays. Sync Status should show prices identical to the product pages.
Force the permanent domain redirect
Settings > Domain Names. The custom domain must be primary and the permanent domain (yourstore.mybigcommerce.com) must be set to redirect. If both are active, Googlebot indexes both, and the feed can submit either.
Re-verify the custom domain in Merchant Center
Merchant Center > Business Information > Website > Claim again. Use the HTML file upload method. Upload via Storefront > File Manager so the file ends up at the document root. Permission to write files in File Manager is required, so confirm your user role allows it.
Rewrite the Help Centre policies
Replace every placeholder block in Shipping Policy, Returns Policy, Privacy Policy and Contact Us with real text. Each policy must include specific values: a return window in days, a refund timeline, a contact email, and a physical or registered address. Empty policies fail both Google's manual review and the April 2026 AI verification layer.
Test every product URL in the Rich Results Test
Pick five products at random and run each through search.google.com/test/rich-results. Each should return valid Product schema with price, availability, brand and image. Fix the theme template (rather than individual products) if any fail.
Appeal with a specific list of what changed
The appeal text in Merchant Center is read by a human reviewer. Reference each fix you made by step number from your audit report. Generic appeals ("we fixed everything") are downranked. Specific appeals ("changed Channel Manager Price List from B2B to Default, rewrote three policy pages with the text now live at the URLs below") get faster reviews. See the full appeal template for the exact wording.
What the April 2026 AI verification added for BigCommerce stores
Google's April 2026 AI verification layer runs three checks before a Merchant Center account is approved or reinstated. BigCommerce stores tend to pass two and fail the third.
The first check, policy-page rendering, usually passes on BigCommerce because the Stencil framework renders policy pages server-side rather than client-side. The page reaches Googlebot with the policy text already in the HTML response. WooCommerce and Shopify stores using React-based themes fail this more often.
The second check, business-identity cross-reference against a public registry, usually passes because BigCommerce stores tend to be established companies with a registered business address. Sole-trader stores using a residential address fail this more often (and the fix is to add the business address to a registry the verification crawler can read).
The third check, WHOIS contact-information cross-reference, fails the most on BigCommerce. Many BigCommerce merchants buy domains through registrars that default to privacy protection (the WHOIS record shows "Domains By Proxy" instead of the merchant's name). When the AI cross-references the email and phone number on the contact page against WHOIS and finds privacy-masked values, the verification step fails. The fix is to either disable WHOIS privacy temporarily during the verification window or add an explicit "Registered business" block to the contact page that names the legal entity behind the domain.
Specific BigCommerce settings that map to GMC requirements
The 43 Merchant Center policy requirements (the same set the pre-appeal checklist covers) have specific BigCommerce equivalents. Use this map as a one-pass cleanup before the first appeal.
- GTIN policy, BigCommerce Products > Edit > Identity. The MPN, GTIN/UPC and Brand fields are exported in the Content API call. Empty values flag for missing GTIN requirements.
- Availability policy, Products > Edit > Inventory. The Track Inventory toggle must be on; otherwise BigCommerce exports availability as "in stock" on out-of-stock products.
- Price policy, covered above (Price List + Currency). Sale price requires the Calculated Price field, not a discount block, otherwise Google sees the base price.
- Shipping policy, Settings > Shipping > define at least one Shipping Zone covering the countries you submit products to. Empty Shipping Zones produce missing shipping policy warnings.
- Returns policy, Storefront > Web Pages > Help Centre > Returns. Must contain a return window in days, a refund timeline, and a return-shipping cost description.
- Contact information, Storefront > Web Pages > Contact Us. Must contain a contact email, a business address, and a phone number on the same page.
- HTTPS, Settings > SSL Certificates. BigCommerce-issued certificates auto-renew. Custom SSL on a custom domain expires silently; check the renewal date once per quarter.
Common BigCommerce mistakes during recovery
Three mistakes show up repeatedly when BigCommerce merchants try to fix a suspension without the audit report.
First, editing the wrong storefront. BigCommerce can have multiple channels (Stencil storefront, headless API channel, Facebook channel). The Google Channel inherits from the storefront set as default. Edits made on a non-default storefront do not change what Google sees. Confirm Channel Manager > Google Channel > Storefront before editing anything.
Second, fixing the home page and ignoring the policy URLs. Google's verifier visits each policy URL directly, not via the home page. The home page can be perfect while the Returns Policy URL still serves placeholder text.
Third, appealing too soon. BigCommerce's Sync Status takes between 2 and 4 hours to update after a Channel Manager configuration change, and the public Google Shopping listing takes 24 to 48 hours to reflect the new price. Submitting an appeal in the first 4 hours after a config change often means Google reviews the old price and the suspension stays in place. Wait 24 hours after the last config change before submitting.
Run the free 43-point audit on your BigCommerce store
One scan returns every policy violation Google is checking. BigCommerce-specific causes like channel-price mismatch and permanent-domain canonicals are detected automatically. Fix the report, then appeal once with confidence.
Start Free GMC AuditFrequently asked questions
Does BigCommerce have a native Google Merchant Center integration?
Yes. The Google Channel uses the Content API and inherits the prices, images, GTINs and availability flags from the BigCommerce control panel. The most common suspensions trace back to channel-specific overrides that disagree with what Googlebot sees on the public storefront.
Why does BigCommerce get suspended for misrepresentation even when the storefront looks fine?
Per-customer-group pricing, multi-currency, and channel-specific overrides can produce a feed price that diverges from the public price. Google evaluates the price visible to an unauthenticated visitor and compares it to the feed. Mismatches read as misrepresentation even when the visible price is correct.
Where in BigCommerce do I check the prices Google actually receives?
Channel Manager > Google Channel > Sync Status. Each product row shows the price submitted to Google. Cross-reference with Storefronts > Currencies and Customers > Customer Groups to find which override is sending the wrong value.
How do I fix a 'website not claimed' suspension on BigCommerce?
Set a custom domain as primary (Settings > Domain Names), then claim it in Merchant Center using the HTML file upload method via Storefront > File Manager. Permanent-domain (.mybigcommerce.com) URLs cannot be claimed.
Do BigCommerce stores need to pass the April 2026 AI verification layer?
Yes. The checks are platform-agnostic. BigCommerce usually passes policy-page rendering, often fails the WHOIS cross-reference because of domain privacy. Disable privacy temporarily during the verification window or name the legal entity on the contact page.
Can the gmcsuspension audit detect BigCommerce-specific issues?
Yes. The free 60-second audit runs all 43 policy checks against any BigCommerce storefront URL and detects channel-price mismatch, permanent-domain leakage, missing Help Centre policy text, missing Product schema and missing custom-domain verification.