BigCommerce Currency Mismatch: Troubleshooting Incorrect Currency in Google Search Snippets

Solving Persistent Incorrect Currency Display in Google SERP for BigCommerce Stores

Even with meticulous BigCommerce store configurations, merchants sometimes encounter frustrating discrepancies, such as Google Search Engine Results Pages (SERP) displaying incorrect currency symbols in product snippets. This community insight delves into a specific case where a BigCommerce store, strictly configured for HKD, found NT$/TWD persisting in Google's search results.

The Problem: HKD Configured, TWD Displayed on Google

The original poster, Jimmy Fung, outlined a clear scenario: their BigCommerce store was set exclusively to Hong Kong Dollar (HKD) as the sole transactional and display currency. Despite this, Google SERP snippets for most products continued to show New Taiwan Dollar (NT$/TWD). Crucially, Jimmy had already performed several critical checks:

• Store Currencies: TWD was deleted, and HKD was the only active currency under Settings > Currencies.
• Schema Markup: Google's Rich Results Test confirmed that priceCurrency correctly outputted "HKD".
• HTML Source: Local inspection of the front-end page source revealed no instances of NT$ or TWD.
• Sitemaps: The XML sitemap was re-submitted, and pages were re-crawled.

These initial checks confirmed that the issue was not originating from the immediate BigCommerce store settings or its direct output.

Expert Solutions and Troubleshooting Steps

The community's replies provided comprehensive troubleshooting strategies, highlighting that such issues often stem from external factors or Google's interpretation beyond the immediate website code:

1. Investigate Google Merchant Center (GMC) and Product Feeds

Several experts, including Sri Vathson and eCommerce Bros, emphasized checking Google Merchant Center. This is a common culprit for currency discrepancies, especially if:

• An old Taiwan/TWD product feed or supplemental feed is still active.
• Automatic currency conversion is enabled in GMC, potentially overriding site settings.

Merchants should review their GMC settings and all connected product-feed apps for any legacy data or misconfigurations.

2. Leverage Google Search Console (GSC)

Sri Vathson recommended using GSC's URL Inspection tool. Specifically, the "View Crawled Page" feature allows merchants to see exactly what Googlebot rendered and received, which might differ from a local browser view due to IP-based content delivery or caching.

3. Check Canonical and Hreflang Tags

Incorrect canonical or hreflang tags could point to an old Taiwanese storefront, subdomain, parameterised URL, or translated product page that still contains TWD currency information. Ensuring these tags correctly reference the HKD version of the store is vital for SEO.

4. Examine Theme Scripts, APIs, GTM, and Caching

The possibility of dynamic content delivery was raised. Theme scripts, APIs, Google Tag Manager (GTM) tags, third-party currency apps, or CDN/cache behavior might serve different content based on a user's IP location or cookies. This could inadvertently expose TWD data to Googlebot if it crawls from a location associated with TWD.

5. Enhance Currency Symbol Clarity

Tony McCreath suggested that Google sometimes "guesses" currency based on visible content. Adding more explicit currency symbols, such as "HK$" instead of just "$", can help Google (and visitors) unequivocally identify the currency, especially when multiple currencies share the same basic symbol.

6. Request Re-indexing and Escalate to Google

After implementing fixes, requesting indexing for a few representative product URLs in GSC is recommended. It's important to note that Google controls when snippets are regenerated, so immediate updates are not guaranteed. If all internal and external checks yield no solution, escalating the issue to Google Search support with screenshots and Search Console crawl evidence is the next step.

Key Takeaway for BigCommerce Merchants

This thread highlights that while BigCommerce provides robust currency management, issues with Google SERP display often require a broader investigation involving Google's own services (Merchant Center, Search Console), potential legacy data, and dynamic content delivery mechanisms. A systematic approach, starting with external Google data sources, is crucial for resolving such complex currency display discrepancies.