BigCommerce SEO: Built-in Capabilities Deep Dive

BigCommerce renders every storefront page server-side by default, generates Product schema without a plugin, and canonicalizes filtered category pages automatically. Nothing here requires an app to be installed first.

The one place that native depth stops is structured data beyond the product page, breadcrumb and FAQ schema both need a template edit.

This guide covers everything BigCommerce does on its own, and exactly how to configure and verify each piece.

Key Takeaways

• BigCommerce renders storefronts through true server-side rendering via its Stencil and Handlebars framework, not a crawler-specific workaround, every visitor gets the same real HTML a search engine sees.
• Canonical tags apply automatically, and faceted navigation canonicalizes to base category pages by default. This solves one of ecommerce’s most common duplicate-content problems without any configuration.
• 301 redirects generate automatically when a product or category URL changes, and a manual redirect tool covers everything else.
• Robots.txt is directly editable with no support ticket required, a real advantage over platforms that gate this behind their support team.
• The honest gap: native structured data covers Product schema well and stops there. Breadcrumb, FAQ, and review schema all require a template edit or a marketplace app.
• Sitemap index files are handled automatically at scale, BigCommerce splits large catalogs into product, category, brand, page, and blog sub-sitemaps once the 50,000 URL ceiling is reached, confirmed in BigCommerce’s own developer documentation.
• IndexNow is not native, confirmed by BigCommerce’s own marketplace hosting dedicated third-party apps to fill exactly this gap. A quick app install closes it in minutes.

What BigCommerce Handles Natively

BigCommerce automates the infrastructure-level SEO work well: crawl access, sitemaps, URL structure, redirects, and page rendering.

It leaves richer structured data, breadcrumb and FAQ schema specifically, as a deliberate task rather than an automatic default.

The sections below cover each capability in the order that matters most when setting up or auditing a store.

Editing robots.txt Without a Developer

Robots.txt is a plain-text file at your site root that tells search engines which parts of your store they may or may not crawl.

Several hosted platforms lock this behind a support ticket. BigCommerce gives you direct access.

Where to find it

1. Log in to your BigCommerce control panel
2. Go to Settings, then General
3. Scroll to Storefront Robots.txt

If a tutorial tells you to look under a Tools tab or Store Setup, it is describing an older version of the control panel. The current location is Settings, then General.

What to actually put in it

The default file is permissive, everything is crawlable. Two changes are worth making on most stores:

Block faceted navigation parameter URLs. If your category pages use filters (size, color, price range) that generate URL parameters like ?size=medium&color=blue, these create near-duplicate pages that waste crawl budget. Add a Disallow rule targeting your filter parameter pattern.

Add your sitemap reference. On its own line, add:

Sitemap: https://yourdomain.com/sitemap.xml

How to verify it worked

Save your changes, then visit https://yourdomain.com/robots.txt directly in a browser. Confirm the file loads and reflects exactly what you entered.

Test one blocked URL pattern using Google Search Console’s URL Inspection tool to confirm Google respects the rule.

The one real risk

Incorrect Disallow rules can remove entire sections of your site from search results. Before saving a broad rule, test it narrowly first, block one specific URL pattern, confirm it behaves as expected, then expand.

How the Automatic Sitemap Actually Works

BigCommerce generates and maintains an XML sitemap without any manual setup. It updates as products, categories, and content pages are added, changed, or removed.

Finding and submitting it

Your sitemap lives at yourstore.com/sitemap.xml. To get full value from it:

1. Go to Google Search Console and add your property if you have not already
2. In the left menu, click Sitemaps
3. Enter sitemap.xml and click Submit
4. Repeat for Bing Webmaster Tools if you use it

What actually gets included

Products, categories, and content pages (blog posts, custom pages) are all covered automatically. You do not need to regenerate it after adding new products, this happens on its own.

The maintenance task this still requires

Review the sitemap monthly, particularly after a bulk product import, a large category restructure, or removing discontinued products in bulk.

Open the sitemap URL directly and spot-check that recently added products appear and recently removed ones do not linger.

This is the one place automation can lag slightly behind a large, fast-moving catalog change.

What Happens at Large Catalog Scale

A single XML sitemap has a hard technical ceiling of 50,000 URLs. BigCommerce handles this automatically once your catalog crosses that line: it splits the sitemap into a proper sitemap index, a master file pointing to several smaller, specialized sub-sitemaps organized by content type, products, categories, brands, static pages, and blog posts each get their own file.

This is confirmed directly in BigCommerce’s own developer documentation, which uses the term sitemap index as part of how the platform serves this structure.

You do not configure this, it activates on its own once your catalog needs it.

Why BigCommerce URLs Do Not Need Fixing

This is one of the platform’s clearest, most underreported strengths.

Every product and category URL is fully editable, and there is no mandatory prefix segment forced onto the structure by default, unlike some competing platforms.

How to edit a URL

1. Open any product or category in the control panel
2. Find the Search Engine Optimization or URL field on that page’s edit screen
3. Edit the slug directly: lowercase, hyphenated, descriptive
4. Save

What good practice looks like here

Keep URLs shallow and readable. A product URL like yourstore.com/blue-running-shoes outperforms a deeply nested, parameter-heavy alternative for both users and crawlers.

Category names carry real weight here too, since they appear in the URL, in breadcrumbs, and in navigation simultaneously, so getting the category name right once pays off across all three.

What happens when you change a URL later

Covered in full in the next section, but the short version: BigCommerce handles the redirect for you automatically.

Automatic 301 Redirects: What Triggers Them and What Does Not

When a product or category URL changes, BigCommerce automatically creates a 301 redirect from the old URL to the new one.

This closes one of the most common sources of broken links and lost rankings after a site restructure.

What triggers the automatic redirect

Renaming a product’s URL slug, renaming a category’s URL slug. The redirect fires without any manual step from you.

What does not trigger it, and needs a manual redirect

Deleting a product or category largely (rather than renaming it), consolidating two pages into one, or moving content that was never a BigCommerce-native URL in the first place (migrating from another platform, for example).

How to add a manual redirect

1. Go to Settings in your control panel
2. Find the 301 Redirects tool
3. Enter the old URL path and the new destination
4. Save

Checking your redirect health

Periodically, run your site through a crawler (Screaming Frog’s free tier handles up to 500 URLs, sufficient for most small to mid-sized catalogs) and look for 404 status codes on URLs that used to work. Any you find are candidates for a manual redirect using the tool above.

True Server-Side Rendering: What This Actually Means for Your Store

This is the single sharpest technical differentiator covered in this guide, and it is actually underreported.

The distinction that matters

Some platforms serve a fully assembled page to search engine crawlers specifically, a technique called dynamic rendering, while regular visitors receive a page that gets built client-side by JavaScript after the initial load.

This works for crawlability but does not improve the actual experience for a real visitor.

BigCommerce’s storefront runs on the Stencil framework, built on Handlebars templating. Pages render server-side by default, for every request, from every visitor and every crawler alike. There is no separate crawler-specific path.

Why this matters practically

A crawler indexing your product page sees exactly what a customer’s browser receives. There is no risk of a mismatch between what Google indexes and what a shopper experiences, a real, if less common, problem on platforms relying on client-side rendering with a crawler workaround layered on top.

What this means for customization

If you or a developer are editing Stencil theme files, you have granular, direct control over the HTML output, the heading structure, and where structured data markup gets injected, since Handlebars cleanly separates template logic from the final rendered output. This is the foundation the next several sections build on.

Controlling Indexation Page by Page

Every page on your store needs an explicit indexing decision, either the default (index and follow, letting search engines list it normally) or an explicit noindex for thin, duplicate, or internal-only content.

Where to set this

1. Open the page (product, category, or content page) in the control panel
2. Find the page’s Search Engine Optimization settings section
3. Look for the indexing or noindex option
4. Apply it where appropriate

Pages worth noindexing deliberately

Internal search results pages, thin filtered category views that duplicate a fuller category page, and any staging or test content that accidentally went live. Leaving these indexed by default dilutes your site’s overall quality signal without adding any real search value.

Verifying it worked

Use Google Search Console’s URL Inspection tool on a page you noindexed. It should confirm the noindex directive is being read correctly. Give it a few days after your first crawl for the change to reflect in actual search results.

Getting Heading Structure Right in a Stencil Theme

Headings tell both users and search engines how a page is organized. BigCommerce’s Stencil framework makes correct implementation simple for a developer, but nothing in the day-to-day content editor prevents a skipped heading level or a duplicate H1 if you are not paying attention.

The structure to aim for

One H1 per page, typically the product name or page title. H2 for major sections beneath it (Description, Specifications, Reviews). H3 for subsections within those, without skipping from H2 directly to H4.

How to check your current heading structure

Right-click any page element and choose Inspect (in Chrome or a similar browser) to view the underlying HTML tag.

Confirm the heading tags follow a clean, nested order. If you or a developer are editing Stencil theme template files directly, this is the point to build the correct hierarchy into the template itself so every page inherits it automatically, rather than checking page by page.

The auditing tool worth using

Screaming Frog’s free tier (up to 500 URLs) includes a heading tag report that flags multiple H1s or skipped levels across your whole crawled site in one pass, faster than manually inspecting individual pages.

Building Internal Links That Actually Support SEO

Internal links are the strongest signal you fully control for telling search engines what a page is about and how important it is relative to the rest of your site. BigCommerce does not automate this, it is built through your native blog and landing page tools deliberately.

How to add an internal link

1. While editing a blog post or a content page, highlight the relevant text
2. Use the editor’s link tool
3. Select or paste the destination product or category URL
4. Repeat consistently

Where this pays off most

Blog posts linking to the specific products they mention. Category pages linking to actually related categories, not every category in your navigation. Product pages linking to complementary products a customer is likely to also want.

Finding pages with no internal links pointing to them

A general site crawl tool (Screaming Frog again covers this) can identify orphaned pages, ones with zero or very few internal links, so you can deliberately connect them from somewhere relevant rather than leaving them to be found only through your site’s main navigation.

Structured Data: What Generates Automatically and What You Have to Add

This is BigCommerce’s real, honest gap, and it is worth understanding precisely rather than in vague terms.

What generates automatically, no setup required

Product schema activates the moment a product exists in your catalog. It includes price, availability, SKU, brand, and, when product reviews are enabled on that product, review aggregate data (average rating and review count).

This is the single most impactful schema type for an ecommerce store, since it is what powers the price and star-rating rich results shoppers see directly in search listings, and BigCommerce covers it without any manual work.

What does not generate automatically

Breadcrumb schema (the BreadcrumbList markup matching your visible navigation trail), FAQ schema (for expandable FAQ rich results), and review schema specifically as a standalone markup type distinct from the aggregate data folded into Product schema.

Adding Breadcrumb Schema, Step by Step

The visible breadcrumb trail already exists by default in Stencil themes, showing a customer’s path through your category structure.

The matching JSON-LD is not automatic, but the data it needs is already sitting in your theme’s context, waiting to be used.

Step 1: Get into your theme files safely.

1. Go to Storefront, then My Themes
2. Find your live theme and make a copy of it first, never edit a live theme directly
3. On the copy, click the three-dot menu
4. Select Edit Theme Files

Page Builder, the default drag-and-drop editor, does not expose file-level editing. This is why the copy-first step matters, it lets you test changes safely before applying them to your live storefront.

Step 2: Open the base layout template. Inside the theme file editor, find the base layout file (typically under templates/layout/base.html in a Stencil theme built on the Cornerstone framework).

Step 3: Add the JSON-LD block using the breadcrumbs context object. BigCommerce’s Stencil framework exposes a breadcrumbs object as part of its standard page context, confirmed in BigCommerce’s own Theme Object Reference.

Add a script block like this inside your base template, looping through it with Handlebars’ {{#each}} helper:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {{#each breadcrumbs}}
    {
      "@type": "ListItem",
      "position": {{@index}},
      "name": "{{this.label}}",
      "item": "{{this.url}}"
    }{{#unless @last}},{{/unless}}
    {{/each}}
  ]
}
</script>

Step 4: Verify the exact property names before deploying. The example above uses this.label and this.url, the standard pattern for breadcrumb objects, but confirm the exact field names against BigCommerce’s current Theme Object Reference in the developer docs before publishing, since object structures can shift slightly between Stencil versions.

Step 5: Preview, then apply. Use the theme copy’s preview link to check the page renders correctly and the script tag appears in the page source.

Once confirmed, apply the theme copy to make it live.

Adding FAQ Schema, Step by Step

FAQ schema needs to be added to specific pages that actually contain expandable FAQ content, not site-wide.

Step 1: Identify where your FAQ content lives. This is typically a specific product page, category page, or custom content page with a genuine question-and-answer section.

Step 2: Follow the same theme copy and file access process as above (Storefront, My Themes, copy your theme, Edit Theme Files).

Step 3: Add the JSON-LD block to the relevant page template. For a static FAQ section, the markup looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Your first FAQ question here",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The direct answer to that question here."
      }
    },
    {
      "@type": "Question",
      "name": "Your second FAQ question here",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The direct answer to that question here."
      }
    }
  ]
}
</script>

Step 4: Keep the markup in sync with the visible content. Google’s structured data guidelines require the schema to match what a visitor actually sees on the page.

If you edit the visible FAQ text later, update this block to match, or the rich result risks being flagged or ignored during a future review.

Step 5: Verify with the Rich Results Test (covered below) before considering the job done.

If you do not have developer access to edit theme files directly, a marketplace schema app can generate this without touching template code, at the cost of an added subscription.

Adding Dedicated Review Schema

For stores wanting standalone review rich results beyond what Product schema’s aggregate rating already covers, Yotpo and Stamped are both established review platforms with BigCommerce marketplace listings that generate this markup automatically as part of their review collection functionality.

How to install either one:

1. Go to Apps in your BigCommerce control panel
2. Click Marketplace
3. Search for Yotpo or Stamped
4. Click Install, then follow the app’s own connection wizard to link it to your storefront

Both apps handle the schema generation internally once connected, no template editing required. Neither is a heavy install, both are worth evaluating if reviews are a significant part of your conversion strategy.

Verifying Any Structured Data, Automatic or Added

Run individual URLs through the Rich Results Test after any change. It confirms exactly which schema types Google detects and flags any missing required fields.

.Test a product page, a page with your new breadcrumb markup, and a page with your new FAQ markup separately, each one validates independently.

The Breadcrumb Trail vs the Breadcrumb Schema

Worth stating as its own point because the two are easy to conflate. The visible breadcrumb navigation (Home, then Category, then Product) is a native, default part of Stencil themes, customers see it without any setup.

The structured data markup that lets search engines display that same trail in search results is a separate thing largely and requires the template edit described above. Having one does not mean you have the other.

Automatic Duplicate Content Prevention on Filtered Pages

Faceted navigation, letting a shopper filter a category page by size, color, price range, or brand, is one of the most common sources of duplicate content in ecommerce. Each filter combination can generate its own URL, and search engines can end up indexing dozens of near-identical variations of the same category.

BigCommerce canonicalizes faceted navigation to the base category page by default. A shopper filtering by blue, running shoes, and under $100 still gets the filtered results they want, but the canonical tag on that filtered view points back to the main category page, telling search engines which version is the one to index.

This requires no configuration. It is a structural advantage worth weighing directly alongside the broader BigCommerce vs Shopify decision, since the same duplicate-content risk on other platforms, including WooCommerce, often depends on plugin configuration rather than working correctly by default.

IndexNow Is Not Native, and Here Is the Real Fix

IndexNow is a protocol that pushes participating search engines, Bing, Yandex, and others, to recrawl a URL the moment it changes, instead of waiting for their next scheduled crawl. Google does not participate in IndexNow on any platform.

BigCommerce does not support IndexNow natively. This is confirmed, not a guess, BigCommerce’s own marketplace hosts a dedicated category of third-party IndexNow integrations specifically because the platform does not ping search engines on its own when content changes.

How to add it:

1. Go to Apps, then Marketplace in your control panel
2. Search IndexNow
3. Review the available integrations and install the one that fits your needs
4. Most connect with no manual configuration, detecting product and page changes automatically and pinging IndexNow’s participating search engines in the background

This is a minor gap relative to BigCommerce’s other native strengths. Bing and secondary engines still index your changes through normal crawling, IndexNow only makes that faster, and it has no effect on Google indexing regardless of which platform you use.

How This Compares to Shopify and WooCommerce

Capability	BigCommerce	Shopify	WooCommerce
True server-side rendering	Yes, via Stencil	Yes	Depends on hosting and theme
Automatic canonicals on faceted navigation	Yes, by default	Yes	Depends on plugin configuration
Native Product schema	Yes, strong	Yes	Via plugin
Native breadcrumb schema	No, requires a template edit	Partial, theme-dependent	Via plugin
Direct robots.txt editing	Yes, no support ticket needed	Yes	Yes, file-level access

Shopify matches BigCommerce closely on the infrastructure fundamentals. The clearer gap sits with WooCommerce, where the same capability often exists but depends largely on which plugins are installed and correctly configured, a real difference in reliability even when the underlying feature is technically available on all three platforms.

FAQ’s