Easy BigCommerce SEO Fixes: Quick Wins You Can Ship This Week

Q: Is BigCommerce SEO-friendly out of the box?

More than most platforms. BigCommerce ships with clean URLs, automatic XML sitemap, customizable robots.txt, server-side rendering, and Product schema in the Cornerstone theme. The gaps appear in custom Stencil themes, multi-storefront setups, and faceted-navigation configurations.

Q: What's the difference between /products/* and /p/* URLs in BigCommerce?

BigCommerce supports both. /products/ is the legacy long form; /p/ - is the shorter modern form. If both resolve on your store, you have duplicate content. Pick one pattern, redirect the other. The long form usually performs better for SEO because of richer URL semantics.

Q: How do I add structured data on BigCommerce?

The Cornerstone theme emits Product schema by default. For custom themes, add JSON-LD blocks to product-view.html, category.html, and base.html. Most BigCommerce stores need to add BreadcrumbList, FAQPage on product pages with FAQs, and Review schema on stores with native reviews.

Q: Should I use Google Shopping with BigCommerce?

If you sell physical products and your margins support paid traffic, yes. BigCommerce has a native Google Shopping integration that pushes product feeds to Merchant Center. Even if you don't run paid ads, having products in Merchant Center helps with the free shopping listings now powered by the Shopping graph.

IN THIS ARTICLE

1. Run a baseline audit before you change anything 2. Duplicate category URLs from /categories/* and /c/*3. Faceted navigation creating thin / duplicate pages 4. Stencil theme not emitting full Product schema 5. Default product titles missing brand and category 6. Robots.txt not blocking /checkout and /account What to ship next, after the easy wins Common questions about BigCommerce SEO fixes Is BigCommerce SEO-friendly out of the box?What's the difference between /products/* and /p/* URLs in BigCommerce?How do I add structured data on BigCommerce?Should I use Google Shopping with BigCommerce?

Every BigCommerce merchant has a backlog of "I should fix that someday" SEO issues. This post is the shortlist: the easy, ship-today wins that recover the most traffic per hour of effort.

Nothing here needs a developer, an agency, or a paid app. Most fixes take less than 30 minutes each. If you do all five in one afternoon, expect a measurable lift in Search Console impressions within two weeks.

Skip the long read: run a free RankCart audit on your store and we'll tell you which of these fixes apply, ranked by missed-revenue impact.

1. Run a baseline audit before you change anything

You can't measure improvement without a starting line. Run a free RankCart audit, screenshot the score and the issue count, and save it. That's your baseline. Re-audit after each fix so you know which one moved the needle.

This is the only step that's not "shipping a fix" — but it's the one that makes every subsequent step measurable. Skip it and you'll spend the next quarter unsure whether your work actually helped.

2. Duplicate category URLs from /categories/* and /c/*

BigCommerce supports both legacy /categories/ URLs and shorter /c/- URLs. If both resolve, Google sees duplicate content. Same for products with /products/* and /p/*.

Quick fix: Decide on one canonical URL pattern in Storefront → Web Pages → URL settings. Set canonical tags consistently, and 301-redirect the secondary pattern. RankCart flags every duplicate path pair.

Filters like /c/shoes?attr_color=red&attr_size=10 generate thousands of crawlable URL combinations, all near-duplicate. Crawl budget collapses on a large catalog.

Quick fix: Use the Faceted Search settings to exclude facets from indexable URLs, or block filter parameters in robots.txt. For facets that should rank (e.g. /shoes/red), build them as standalone category pages with unique copy.

4. Stencil theme not emitting full Product schema

BigCommerce's Cornerstone theme emits Product schema with offers and reviews. Custom Stencil themes often strip this during development, especially after a designer-led refresh.

Quick fix: Audit the rendered HTML for