Step by Step Bigcommerce Search Engine Optimization Help

BigCommerce ships with strong SEO foundations, but a default install leaves several technical levers unpulled. This is a step-by-step technical SEO walkthrough for BigCommerce store owners — the platform-specific configuration that controls how search engines crawl, deduplicate, and index your catalog. It complements broader on-page guidance in our BigCommerce SEO for beginners guide and our work implementing publisher and structured-data markup. For hands-on help, see our ecommerce SEO services.

Editorial note (updated 2026): BigCommerce relocated its robots.txt editor. The current path is Settings › General › Storefront Robots.txt — not the older “Tools” tab some legacy tutorials reference. Theme file edits now live under Storefront › My Themes › Edit Theme Files. Steps below use the current interface.

Step 1: Reference Your Sitemap in robots.txt

BigCommerce auto-generates an XML sitemap at /xmlsitemap.php and you should submit it directly in Google Search Console and Bing Webmaster Tools. Additionally, declare it in robots.txt so any compliant crawler can find it:

1. Open Settings › General › Storefront Robots.txt.
2. Below the existing entries, add on its own line: Sitemap: https://yourdomain.com/xmlsitemap.php
3. Save, then confirm by loading https://yourdomain.com/robots.txt.

Step 2: Block Crawl-Wasting and Thin URLs

Crawl budget and index bloat are real problems for large catalogs. Internal search results, faceted/filtered combinations, cart, checkout, and account pages add thousands of near-duplicate or zero-value URLs. In the same robots.txt editor, disallow the paths that have no organic value, for example:

• Disallow: /cart.php
• Disallow: /checkout
• Disallow: /account.php
• Disallow: /search.php (your internal search results path)

Confirm exact paths against your own storefront before disallowing — a wrong rule can deindex real pages. Robots.txt controls crawling, not indexing of already-known URLs; for pages that must be removed from the index, use a noindex meta tag or remove them.

Step 3: Get Canonical Tags and Faceted Navigation Right

Duplicate content is the most common technical SEO failure on ecommerce sites. BigCommerce automatically adds rel="canonical" tags so product-variant URLs (different size/color query strings) consolidate to one ranking URL — do not strip these out with custom theme edits. If you run BigCommerce's faceted (filtered) search, configure which facets generate crawlable links versus which are JavaScript-only; allowing every price/brand/size combination to be a crawlable, indexable URL is the fastest way to bury your real category pages under millions of thin permutations.

Step 4: Handle URL Changes With 301 Redirects

Every time you change a product or category URL, rankings and inbound links point at the old address. BigCommerce offers to auto-create a 301 redirect when you edit a URL — always accept it. You can also manage redirects in bulk under Settings › 301 Redirects. After a redesign or replatform, audit for 404s in Google Search Console's Pages report and map each broken URL to its closest live equivalent. Never let a 404 sit on a page that has earned links.

Step 5: The Powered-By Footer Link (Mostly Obsolete)

Correction to older guidance (updated 2026): earlier versions of this article had merchants edit the %%GLOBAL_PoweredBy%% snippet to nofollow a forced BigCommerce credit link. Current BigCommerce Stencil themes no longer require an outbound credit link, so this step is unnecessary for most stores. Only if a customized legacy theme still hard-codes an outbound link in footer.html should you edit it (Edit Theme Files) to remove it or add rel="nofollow" — and verify the link genuinely exists first.

Step 6: Structured Data for Rich Results

Product schema (price, availability, review rating) drives rich snippets that materially lift click-through from search. Many modern BigCommerce themes include Product structured data out of the box; validate it with Google's Rich Results Test. If your theme lacks it or you want Organization, Breadcrumb, and FAQ markup, add JSON-LD via the script manager or theme templates and re-test after every theme update.

Step 7: Page Speed and Core Web Vitals

Page experience is a ranking signal. On BigCommerce, the practical wins are: stay on a current Stencil theme, prune unused apps (each injects JavaScript), serve compressed imagery, and minimize render-blocking marketing scripts. Monitor the Core Web Vitals report in Search Console and re-check after adding any new app.

Step 8: Monitor Continuously

Technical SEO is not a one-time setup. After every catalog import, theme update, or app install, recheck Search Console for new crawl errors, coverage drops, manual actions, and Core Web Vitals regressions. A monthly review catches most problems before they cost rankings.

A Repeatable Technical SEO Audit Checklist

Run this list after any significant change (theme update, large import, app install) and at least quarterly otherwise. It catches the regressions that silently erode rankings:

1. Indexation: In Search Console's Pages report, does the number of indexed pages roughly match your real product/category/content count? A sudden spike usually means faceted or parameter URLs leaked into the index; a drop means pages were noindexed or are 404ing.
2. Crawl errors: Review server errors (5xx) and not-found (404) lists. Map every 404 that has inbound links or historic traffic to a 301.
3. Canonical integrity: Spot-check product variants and ensure they canonicalize to the main product URL, not to themselves.
4. Sitemap health: Confirm /xmlsitemap.php returns 200, contains your live URLs, and excludes redirected or noindexed ones, and that Search Console reports it as read successfully.
5. Robots.txt: Re-verify your disallow rules did not accidentally block a real section, and the Sitemap: line is still present.
6. Structured data: Run a key product URL through the Rich Results Test; theme updates frequently break or duplicate JSON-LD.
7. Core Web Vitals: Check the report for new “poor” URLs after any app addition.
8. HTTPS and mixed content: Ensure every resource loads over HTTPS — a single http:// asset can flag a page as insecure.

Technical SEO FAQ

Will robots.txt remove a page from Google? No. Robots.txt blocks crawling; a URL Google already knows can still appear (often without a description). To remove a page from the index use a noindex meta tag (and let it be crawled so Google can see the tag) or remove the page and 301 it.

Are BigCommerce's automatic canonicals enough? For standard variant deduplication, generally yes. Faceted/filtered URLs and custom parameter pages still need deliberate handling — that is where most large catalogs leak.

Do I need to resubmit the sitemap after changes? BigCommerce regenerates it automatically and Google recrawls submitted sitemaps periodically; a manual resubmission after a major catalog change just speeds things up.

Worked through methodically, these steps remove the crawl waste, duplication, and indexing leaks that hold back otherwise well-built BigCommerce stores. For a managed program, our BigCommerce experts handle technical SEO, development, and ongoing optimization. Visit our site to talk to the team.