Ecommerce SEO

BigCommerce SEO: what the platform does and does not do

BigCommerce ships with canonicals, a sitemap, editable URLs and redirects. Where the platform stops, and the checklist for the parts a store owner must build.

By CartKernel · Published September 6, 2026

BigCommerce does a larger share of technical SEO out of the box than most hosted platforms, and the honest summary is that a store rarely loses rankings because of the platform. It loses them because the parts the platform cannot do, mainly content, information architecture and filter control, were never done. This piece separates the two so you know where to spend the effort.

What BigCommerce handles on its own

URL structure you control. In the URL structure settings you choose whether product URLs carry the category path or sit at the root as /product-name/, and whether category and brand URLs are short or descriptive. Root-level product URLs mean a product in several categories has one address, which removes the most common duplicate-content source on other platforms. Set this before importing the catalogue.
Canonical tags. Product, category and brand pages carry a self-referencing canonical from the theme, and a product reached through a category path resolves to the product URL you chose.
The XML sitemap. The store publishes one at /xmlsitemap.php, regenerated as products, categories, brands and pages change. Submit it in Search Console and confirm the counts match what you expect to be indexable.
Redirects. A redirect manager in the control panel supports single entries and bulk import, and the platform creates a redirect when you edit a product or category URL from the admin. Check the redirects list after any bulk URL change to confirm the entries are there.
Editable robots.txt. The file is exposed in the store settings, so you can disallow sort and search parameters without a developer.
Per-page search engine fields. Products, categories, brands and web pages each have a page title and meta description field. There is also a search keywords field, which search engines have not used for years; leave it empty rather than spend time on it.
Hosting and images. The store is served from a CDN with responsive image sizes generated automatically, so the baseline for speed is good before you customise anything.
Product markup in the default theme. The Cornerstone theme prints product markup with price and availability. Verify it with the Rich Results Test after any theme change, because customised templates often drop fields.
Channel integrations. The control panel connects to Merchant Center for Shopping and free listings, and the feed attributes it sends come from the same product fields you optimise for the page. Merchant Center setup covers what to check once the connection is live.

What it leaves to the store

Category content. A category has one description field. Where it renders, above or below the grid, depends on the theme, and page builder regions can add more. The platform gives you the field; it cannot tell you what to write. The answer to should collection pages have content is yes, and category page SEO explains what the content should be.

Sub-category structure. BigCommerce supports nested categories to any practical depth, with breadcrumbs generated from the tree. The decision about which nodes exist, and which combinations of attribute and category deserve a page of their own, is yours. Do sub-category pages help SEO explains how to decide.

Faceted search. On plans that include product filtering, shoppers can narrow a category by brand, price, rating and any attribute you enable. Each selection changes the URL. Confirm on a live filtered URL what the canonical and the robots meta say rather than assume it, because a customised theme can override the default. Then decide which facets are worth an indexable landing page and build those as real categories or pages with content. The method and the cleanup for a store that already has facet URLs indexed are in faceted navigation URLs indexed and faceted navigation SEO.

Brand pages. Every brand you assign to a product gets a page under /brands/. Out of the box it is a heading and a grid. Brand pages are among the easiest wins on a BigCommerce store because “brand plus category” is a query pattern with real intent, and a description plus links to the brand’s best categories takes an hour per brand.

Sort, search and pagination parameters. Sorting adds ?sort=, site search lives at /search.php and category pages paginate with ?page=. Sorting and search should be excluded from crawling in robots.txt; paginated pages should stay crawlable with self-referencing canonicals so deep products remain reachable. The products-per-page setting controls how deep pagination goes, and how many products per collection page discusses the trade-off.

Product content. Titles, descriptions, image alt text and the option to write a distinct meta description are all fields; supplier copy pasted into them ranks nowhere. Rewrite the products that carry revenue first.

Blogging and editorial content. The built-in blog covers posts, tags and authors, which is enough for buying guides and answers to shopper questions. Stores that need heavier editorial tooling sometimes run it elsewhere and connect it, and should an online store use subdomains explains why a subdirectory is preferable when you do.

International and multi-storefront. Multi-storefront lets one control panel run separate storefronts for regions or brands, each with its own domain and content. Hreflang between them is not generated for you; add it through the script manager or the theme, and keep the hreflang pairs in sync when URLs change.

Third-party scripts. The script manager makes it easy to add tags, chat widgets and review scripts, and each one costs load time on every page. Review the list every quarter and measure the product template with the Core Web Vitals checker.

Reading the page indexing report on a BigCommerce store

Once the sitemap is in Search Console, the page indexing report tells you what the platform defaults produced before you touched anything. Three patterns are worth looking for. A large count under “duplicate, Google chose a different canonical” usually means filtered or sorted URLs are being crawled and consolidated, which costs crawl budget even when it costs no rankings. “Crawled, currently not indexed” against brand pages or deep categories usually means those pages have a grid and nothing else. And “excluded by noindex” against pages you expected to rank means a theme setting or a per-page field is switched the wrong way. Each pattern maps to an item on the list below.

The checklist we run on a BigCommerce store

Confirm the URL structure setting matches the one you want for the life of the store, and if it does not, plan the change as a migration with a full redirect map.
Submit /xmlsitemap.php in Search Console and compare its counts with the page indexing report.
Open one product URL reached through a category and one reached directly; confirm both resolve to the same canonical.
Open one filtered category URL and one sorted URL; record the canonical and the robots meta on each.
Add sort and search parameters to robots.txt once the canonicals are confirmed.
Write category descriptions for the top twenty categories by revenue, and give brand pages a description and links.
Rewrite titles and descriptions on the products carrying most of the revenue.
Validate product markup on a live product page and fix any dropped fields.
List every script in the script manager, remove the ones nobody can justify, and measure the product template on mobile.
If the store runs multiple storefronts or languages, audit the hreflang pairs.

Where BigCommerce stores usually stand after the pass

The technical items on this list take a day or two on most stores because the platform has already done the heavy part. The content items take weeks, and they are where the rankings come from. A store with root-level product URLs, controlled facets and category pages that say something specific is in a strong position on this platform. A store with the defaults and no content is in the same position as a store on any other platform with the defaults and no content. The ecommerce SEO service is built around closing that second gap, and the canonical tag and crawl budget entries explain the two concepts most of the technical checks rely on.