Google Search Console for BigCommerce: The Complete SEO Guide

BigCommerce gives you a fast, well-structured storefront out of the box, but it does not tell you how Google actually sees your store. That gap is where Google Search Console (GSC) earns its place in your toolkit. It is the only free source of first-party data on which queries surface your products, which category pages are indexed, and which URLs Google is quietly skipping.

The challenge is that most GSC advice is written for blogs and generic websites. BigCommerce has its own URL conventions, its own automatic sitemap, and its own habits around faceted navigation, product variants, and out-of-stock items. If you treat your store like a content site, you will misread the reports and chase the wrong fixes.

This guide is a practical playbook for BigCommerce merchants. We will connect and verify your store, understand BigCommerce URL structure, submit and monitor the sitemap, diagnose the indexing issues that are specific to the platform, and then use GSC's reports to find revenue-driving opportunities you would otherwise miss. Every step includes the actual clicks in both the BigCommerce admin and GSC.

Connecting and verifying your BigCommerce store in GSC

Before any data appears, Google needs proof that you own the domain. BigCommerce supports every verification method GSC offers, so pick the one that matches how your store is set up.

Start by choosing a property type in Search Console. A Domain property covers every subdomain and both http and https, which is the most complete option but requires DNS access. A URL-prefix property covers only the exact address you enter (for example https://www.yourstore.com/) and supports more verification methods. For most merchants, a Domain property is the better long-term choice because it consolidates everything in one place.

Method 1: DNS verification (best for Domain properties)

1. In GSC, click Add property, choose Domain, and enter your root domain (yourstore.com).
2. Google shows a TXT record. Copy it.
3. Log in to wherever your DNS is managed. If you bought your domain through BigCommerce, this lives under Settings to Domain names. If you use Cloudflare, GoDaddy, or another registrar, go there instead.
4. Add a new TXT record at the root (@) and paste the value.
5. Wait for the record to propagate (often minutes, sometimes hours), then click Verify in GSC.

Method 2: HTML file upload (URL-prefix only)

BigCommerce does not give you raw access to the web root, so the HTML file method is awkward on the platform. You generally cannot drop a file at yourstore.com/googleXXXX.html the way you would on traditional hosting. Skip this method unless you have a custom setup that exposes file uploads; use DNS, the HTML tag, or GA4 instead.

Method 3: HTML meta tag

1. In GSC, choose the HTML tag option and copy the <meta> tag.
2. In BigCommerce admin, go to Storefront to Script Manager.
3. Click Create a Script, set Location to Head, Pages to All pages, and Script type to Script.
4. Paste the meta tag, save, then click Verify in GSC.

Method 4: Google Analytics (GA4)

If you already run GA4 on your store, this is the fastest route. In BigCommerce, GA4 is added under Settings to Web Analytics to Google Analytics. As long as the GA4 property uses the same Google account and you have edit access, GSC can verify ownership through it. Choose the Google Analytics option in GSC and click Verify.

Whichever method you use, do not remove it later. Google re-checks verification periodically, and deleting the record or tag will revoke access.

Understanding BigCommerce URL structure and the automatic sitemap

To read GSC correctly you need to know what BigCommerce URLs look like by default. The platform uses clean, readable paths:

| URL type | Typical BigCommerce pattern | Notes | |----------|-----------------------------|-------| | Product | /product-name/ | Flat by default, not nested under category | | Category | /category-name/ | Can be nested: /parent/child/ | | Brand | /brands/brand-name/ | Generated automatically | | Faceted/filtered | /category/?Color=Blue | Query parameters appended | | Search | /search.php?search_query=... | Internal search | | Cart/account | /cart.php, /account.php | Should not be indexed |

The important detail: by default BigCommerce product URLs are flat, living at the root rather than inside their category path. This avoids a lot of duplicate-content trouble, but some stores change the URL structure setting to include the category path, which reintroduces it. Check Settings to URL structure to see how yours is configured.

BigCommerce also generates an XML sitemap automatically at yourstore.com/xmlsitemap.php. You do not build it manually; the platform keeps it updated as you add and remove products and categories. It includes products, categories, brands, web pages, and blog posts that are visible and set to be included. Visit that URL in a browser to confirm it loads and lists current products. For more on how sitemaps should be structured, see our XML sitemap guide for Search Console.

Submitting your sitemap to GSC

Even though Google can discover the sitemap on its own, submitting it explicitly speeds up discovery and gives you a dedicated report.

1. In GSC, open Indexing to Sitemaps from the left menu.
2. In the Add a new sitemap field, enter xmlsitemap.php (GSC prepends your domain automatically).
3. Click Submit.
4. Refresh after a day or two. The status should read Success, with a count of discovered URLs.

If the status shows Couldn't fetch, first open yourstore.com/xmlsitemap.php directly. If it loads fine in your browser, the error is usually a temporary fetch issue; wait and let GSC retry. Compare the Discovered URLs number against your roughly known product and category count. A large gap suggests products are excluded somewhere in BigCommerce, often because they are hidden, out of stock with the wrong visibility setting, or assigned to no category.

BigCommerce-specific indexing issues to watch

This is where most BigCommerce SEO problems hide. The Pages report (under Indexing to Pages) splits your URLs into indexed and not-indexed buckets with a reason for each exclusion. Here are the patterns that show up repeatedly on BigCommerce stores and how to read them.

Faceted and filtered category URLs

When shoppers filter a category by color, size, or price, BigCommerce appends query parameters (?Color=Blue&Size=Large). Each combination is a unique URL, and Google can discover thousands of these crawlable variations. You will see them in the Pages report grouped under reasons like Alternate page with proper canonical tag, Crawled - currently not indexed, or Duplicate, Google chose different canonical.

In most cases this is fine and expected: BigCommerce points faceted URLs back to the clean category page with a canonical tag, so Google consolidates them. The problem is crawl budget. If Google spends its time on filter combinations, it crawls your real products less often. Confirm faceted pages carry a canonical to the base category, and if your category has heavy faceting, consider limiting indexable filters. To audit which parameterized URLs Google is actually visiting, filter the Pages report and the Performance report with the regex examples below.

Product variant URLs

BigCommerce variants (a shirt in three colors) usually share one product URL, which is the clean approach. But some themes or apps generate variant-specific URLs or anchor links. If you see near-duplicate product URLs in the not-indexed report under a duplicate-canonical reason, check whether a variant is generating its own crawlable address. The fix is to ensure all variants resolve to the single canonical product URL.

Out-of-stock products

BigCommerce lets you choose what happens when a product sells out: keep it visible, hide it, or redirect. Each choice has an SEO consequence. If out-of-stock products are hidden, their URLs return a 404 or get removed from the sitemap, and you will eventually see Not found (404) in the Pages report. If you regularly restock, hiding products throws away the ranking equity those pages built. A better pattern for restockable items is to keep the page live, show stock status, and suggest alternatives. Reserve removal (with a 301 redirect to the parent category) for products that are gone for good. For a deeper walk-through of these exclusion reasons, see our guide to index coverage errors in Search Console.

Duplicate content from category paths

If your store includes the category path in product URLs, the same product can be reachable from multiple category paths, creating duplicate URLs. BigCommerce handles this with canonicals, but it is worth verifying. In the Pages report, watch for Duplicate without user-selected canonical or Duplicate, Google chose different canonical affecting product pages. If you see this, the cleanest fix is switching to flat product URLs under Settings to URL structure, then ensuring old paths 301-redirect to the new ones.

Useful GSC page regex (RE2) for BigCommerce

GSC's Performance and Pages reports let you filter URLs with Custom (regex) matching, using the RE2 syntax. These copy-paste patterns isolate the parts of a BigCommerce store you care about. To use them in the Performance report, click + New to Page to Custom (regex) and paste.

Match only category and brand pages (exclude products and filters):

^https://www\.yourstore\.com/(brands/)?[^/?]+/$

Match faceted/filtered URLs (anything with a query parameter):

\?.+=

Match internal search result pages:

/search\.php

Match a specific category and all its filtered variants:

^https://www\.yourstore\.com/mens-shoes/

Exclude non-content system pages from a report (cart, account, checkout):

^(?!.*(cart|account|checkout|login)\.php).*$

Match likely product pages (single-segment paths that are not known system pages):

^https://www\.yourstore\.com/[^/?]+/$

Replace www.yourstore.com with your domain, and remember RE2 requires escaping dots and the ? character. Combine these with the date comparison feature to see how a section trends over time.

Tracking category vs product performance

One of the most useful things you can do in GSC is separate how your category pages perform from your product pages, because they serve different intent. Category pages tend to capture broad, higher-volume queries ("running shoes"), while product pages capture specific, high-intent ones ("brand model size 10").

1. Open Performance to Search results.
2. Click + New to Page and choose Custom (regex).
3. Paste the category regex above to see clicks, impressions, average position, and CTR for categories only.
4. Note the totals, then swap in the product regex to compare.

If categories pull strong impressions but weak CTR, your titles and meta descriptions are the lever; rewrite them in BigCommerce under each category's SEO settings. If products earn impressions but rank on page two, that is a content and internal-linking opportunity. This kind of segmented analysis is the foundation of our broader ecommerce SEO with Search Console workflow, and the same regex approach works on other platforms too, as covered in our GSC guide for Shopify.

Finding striking-distance queries

Striking-distance queries are searches where you already rank on the edge of page one (roughly positions 8 to 20) but are not yet getting meaningful clicks. These are your fastest wins because Google already considers you relevant; you just need a nudge.

1. In Performance to Search results, set the date range to the last 3 months.
2. Enable the Average position metric.
3. Click the Queries tab and sort, or export to a spreadsheet and filter for positions between 8 and 20 with a healthy impression count.
4. For each query, identify the ranking URL (use the Pages tab or click the query to filter).

On a BigCommerce store, the fix usually means strengthening the page that ranks: add the query phrasing to the product or category description, expand thin category copy, add internal links from related products, and make sure the title tag leads with the term. Re-check positions after a few weeks. Our dedicated walkthrough on striking-distance keywords in Search Console covers the prioritization math in more depth.

Checking product rich results

Rich results (the star ratings, price, and availability that can appear under your listing) make BigCommerce product pages more clickable. BigCommerce themes typically include Product structured data, but it is worth verifying that Google can read it and is not flagging errors.

1. In GSC, scroll to the Enhancements section of the left menu. If Google has detected product markup, you will see a Products (or Merchant listings) report.
2. Open it to review Valid, Valid with warnings, and Invalid items. Common warnings include a missing aggregateRating, brand, or availability field.
3. For any specific URL, paste it into Google's Rich Results Test to see exactly which fields are present and which are missing.

Many warnings come from optional fields that your theme does not populate, such as review ratings if you have no reviews yet, or brand if products are not assigned a brand in BigCommerce. Fixing these is often a matter of completing product data in the admin or enabling reviews. For the full set of eligible result types and how to troubleshoot them, see our guide to rich results in Search Console.

Putting it into a routine

GSC rewards consistency, not heroics. A simple monthly rhythm keeps a BigCommerce store healthy: confirm the sitemap still reads Success, scan the Pages report for new not-indexed reasons, compare category and product performance, pull a fresh striking-distance list, and check the product enhancements report for new warnings. Most months this takes under an hour and surfaces a handful of concrete, revenue-relevant tasks.

If turning that GSC data into prioritized, ready-to-write content briefs sounds like the slow part, that is exactly what Search Console Tools automates. Connect with Google sign-in (free, OAuth, read-only) and it turns your real query and page data into briefs you can hand straight to a writer.

Frequently Asked Questions

How do I verify a BigCommerce store in Google Search Console?

The most reliable method is a Domain property verified with a DNS TXT record added at your registrar, which covers your whole domain. If you cannot edit DNS, use the HTML meta tag through BigCommerce's Script Manager (Storefront to Script Manager, set to the Head on all pages) or verify through an existing GA4 property. Avoid the HTML file upload method, since BigCommerce does not expose the web root.

What is the BigCommerce sitemap URL and how do I submit it?

BigCommerce automatically generates and maintains an XML sitemap at yourstore.com/xmlsitemap.php. To submit it, open Indexing to Sitemaps in GSC, enter xmlsitemap.php, and click Submit. After a day or two the status should read Success with a count of discovered URLs.

Why are my BigCommerce product pages not indexed?

The most common reasons in the Pages report are duplicate canonicals from category-path URLs, products hidden or 404ing after going out of stock, thin product content marked "Crawled - currently not indexed," and crawl budget being absorbed by faceted filter URLs. Open Indexing to Pages, read the reason next to each excluded URL, and fix the underlying cause, usually canonicals, visibility settings, or content depth.

Should I let Google index filtered category URLs on BigCommerce?

Generally no. Faceted URLs with query parameters create near-infinite duplicate variations, so it is better to let BigCommerce canonical them back to the clean category page, which it does by default. Heavy faceting still wastes crawl budget, so audit which parameterized URLs Google actually visits using a regex filter and limit indexable filters where possible.

How do I separate category and product performance in GSC?

Use the Performance report's Custom (regex) page filter. Apply a regex that matches single-segment category paths to view categories only, then swap in a product regex to compare clicks, impressions, position, and CTR. This reveals whether your wins are coming from broad category terms or specific product queries, which determines where to focus optimization.

Do BigCommerce product pages support rich results?

Yes. Most BigCommerce themes output Product structured data that can produce price, availability, and review-rating rich results. Check the Products or Merchant listings report under Enhancements in GSC, validate individual URLs with the Rich Results Test, and resolve warnings by completing product fields like brand and enabling reviews in the BigCommerce admin.