BigCommerce · Hosted ecommerce

BigCommerce SEO audit: the issues built into BigCommerce — and how to fix them

A BigCommerce SEO audit checks your store across search, AI visibility, accessibility and security — with a fix for each issue we find.

A hosted platform built more SEO-friendly than most — flexible URLs and built-in structured data — but its faceted search and multi-category catalogs still need crawl discipline.

How does BigCommerce's architecture shape your SEO?

BigCommerce is hosted like Shopify but gives you far more SEO control: you can set custom URL structures (no forced path prefix), it emits Product structured data out of the box, and it serves the catalog server-side over Akamai's CDN. The themes use the Stencil framework, and the platform also supports a fully headless setup via its Storefront and GraphQL APIs. The recurring issues are catalog-shaped rather than platform-limitation-shaped: refinement/faceted URLs, products living in multiple category paths, and thin or duplicated category pages.

Reference: BigCommerce SEO docs →

What issues show up most on BigCommerce sites?

Why these happen on BigCommerce

Specific to how BigCommerce is built — not generic checklist advice.

SEO

Faceted search refinement URLs

BigCommerce's product filtering generates refinement URLs that, left uncontrolled, get crawled as endless variants of a category. Use the platform's faceted-search SEO controls and canonicals so only the clean category URL is indexed.

SEO

Products in multiple categories

When a product belongs to several categories, BigCommerce can expose it under multiple URL paths. Confirm canonicals resolve every variant to one product URL so ranking signals don't split.

AEO

Headless setups lose default SEO scaffolding

Going headless with the Storefront/GraphQL API means you're now responsible for the meta tags, canonicals, and JSON-LD that the stock Stencil theme provided automatically. Many headless BigCommerce builds ship with missing or incomplete Product schema — verify it in the rendered output.

Full fix guide →

Fixes written for BigCommerce

We catalog 182 BigCommerce fixes — exact steps for BigCommerce's admin and theme, each with a link to the official docs.

Catalog coverageSEO

Audit your XML sitemap and internal linking so that every product and category page is discoverable and crawlable by Google — not hidden behind JavaScript, pagination, or missing links.

On BigCommerce
  1. 1BigCommerce auto-generates a sitemap at yourstore.com/xmlsitemap.php. Submit this URL in Google Search Console › Indexing › Sitemaps.
  2. 2Admin › Storefront › Search Engine Optimization: confirm 'Enable XML Sitemap' is checked.
  3. 3Admin › Products › View: export your product list (Export button) and compare the count to what Google Search Console reports as indexed.
  4. 4Admin › Storefront › Navigation: ensure every category is linked in the navigation. Uncategorised products are still in the sitemap but may receive fewer internal links — assign them to categories.
  5. 5Check Admin › Products › Categories for any category set to 'Visible: No' — hidden categories and their products are not indexed.
  6. 6Use the URL Inspection tool in Google Search Console to test individual product URLs and confirm they are crawlable.
Code · Generic HTMLhtml
<!-- CORRECT: Standard crawlable link -->
<a href="/products/blue-running-shoes">Blue Running Shoes</a>

<!-- WRONG: JavaScript-only — Googlebot cannot follow this -->
<span onclick="navigate('/products/blue-running-shoes')">Blue Running Shoes</span>

Standard crawlable product link — use plain <a href> tags, never JavaScript-only click handlers, for navigation links that Google must follow.

BigCommerce docs →
Cwv clsSEO

Eliminate unexpected layout shifts by reserving space for every image, video, embed, and dynamically injected element so nothing jumps when the page loads.

On BigCommerce
  1. 1Images: In Storefront → My Themes → Edit Theme Files, open templates/components/products/product-view.html (and card.html for listing pages). Add width and height attributes to every <img> tag. BigCommerce's Stencil framework provides {{getImageSrcset}} helpers; use {{image width=800 height=800}} to output sized images with explicit dimensions.
  2. 2Theme CSS: In assets/scss/settings/foundation/images/_settings.scss, ensure img { max-width: 100%; height: auto; } is present so explicit width/height attributes work correctly with responsive layouts.
  3. 3Banner / promo: In Marketing → Banners, avoid rotating hero banners injected via JavaScript without a reserved container. In your theme's homepage template (templates/pages/home.html), wrap the banner region in a container with a fixed aspect-ratio or min-height.
  4. 4Fonts: In assets/scss/settings/global/color-and-type/_settings.scss, locate @font-face declarations and add font-display: optional;.
  5. 5Apps: For review or chat apps installed from the BigCommerce App Marketplace, wrap their embed scripts in a sized container div in the relevant template file.
  6. 6Verify: Check PageSpeed Insights on your storefront URLs; CLS should be < 0.1 on both mobile and desktop.
Code · Generic HTMLhtml
<!-- CORRECT: explicit width and height prevent layout shift -->
<img
  src="/images/product-red-sneaker.jpg"
  alt="Red canvas sneaker, side view"
  width="800"
  height="800"
  loading="lazy"
>

Always declare width and height on every img element. The browser uses these to reserve space before the image file downloads.

BigCommerce docs →
Cwv inpSEO

Reduce Interaction to Next Paint (INP) to under 200 ms by breaking up long JavaScript tasks, deferring non-critical third-party scripts, and lightening event handlers so the page feels fast and responsive after every tap or click.

On BigCommerce
  1. 1Go to Storefront → Script Manager. Review every installed script. For non-critical scripts (chat, affiliate pixels, review widgets), change their 'Load Method' to 'Defer' or move their 'Placement' to 'Footer'.
  2. 2In Storefront → My Themes → Advanced → Edit Theme Files, open templates/layout/base.html and find any hard-coded `<script>` tags. Add `defer` or `async` attributes to non-critical ones.
  3. 3Remove or disable BigCommerce apps that inject frontend JavaScript but are no longer actively used (Apps → My Apps).
  4. 4For custom JavaScript in assets/js/, refactor event handlers on cart, search, and navigation interactions to yield back to the browser using `setTimeout` or `scheduler.yield()` between heavy steps.
  5. 5Use BigCommerce's built-in Lighthouse integration (Storefront → Optimize) or PageSpeed Insights to measure INP before and after changes.
BigCommerce docs →
Cwv lcpSEO

Reduce Largest Contentful Paint (LCP) to under 2.5 seconds by serving the hero image in a next-gen format (WebP/AVIF), preloading it, and eliminating render-blocking resources.

On BigCommerce
  1. 1IDENTIFY LCP IMAGE: Run PageSpeed Insights on your storefront. The LCP is usually the hero carousel image configured under Storefront › Home Page Carousel or a theme banner.
  2. 2CONVERT TO WEBP: BigCommerce's Akamai Image Manager automatically serves WebP/AVIF to supported browsers when you upload standard images — no action needed if you are on a current plan. Confirm by inspecting the hero image URL for a format parameter.
  3. 3UPLOAD OPTIMISED SOURCE: Even with auto-conversion, upload the highest-quality but appropriately-sized source JPEG/PNG (max 1920px wide) via Storefront › Image Manager so the CDN has a good original to compress.
  4. 4PRELOAD: Go to Storefront › My Themes › Edit Theme Files (or use Stencil CLI). Open templates/layout/base.html. In <head>, add: <link rel='preload' as='image' href='{hero image CDN URL}' fetchpriority='high'>. For dynamic images use the Handlebars variable that outputs your carousel image.
  5. 5DEFER JS: In base.html, add 'defer' to non-essential third-party <script> tags. Move analytics and chat widgets to the bottom of <body> or wrap in a setTimeout.
  6. 6NO LAZY-LOAD: Find the carousel/hero img tag in templates/components/ and ensure it has loading='eager' fetchpriority='high'.
  7. 7VERIFY: Re-run PageSpeed Insights; monitor Core Web Vitals in Google Search Console.
Code · Generic HTMLhtml
<!-- Step 1: Preload the LCP hero image -->
<link
  rel="preload"
  as="image"
  href="/images/hero-banner.webp"
  imagesrcset="/images/hero-banner-400.webp 400w,
               /images/hero-banner-800.webp 800w,
               /images/hero-banner-1500.webp 1500w"
  imagesizes="100vw"
  fetchpriority="high"
>

<!-- Step 2: Hero <img> tag — eager, high priority, no lazy-load -->
<img
  src="/images/hero-banner-1500.webp"
  srcset="/images/hero-banner-400.webp 400w,
          /images/hero-banner-800.webp 800w,
          /images/hero-banner-1500.webp 1500w"
  sizes="100vw"
  alt="[Descriptive alt text for your hero image]"
  width="1500"
  height="600"
  loading="eager"
  fetchpriority="high"
>

Add inside <head>, immediately after <meta charset>. Replace the href with your actual hero image CDN URL.

BigCommerce docs →

Browse all 182 BigCommerce fixes →

BigCommerce on the open web

0.1% of the crawled web runs BigCommerce

17,168
live BigCommerce sites
#6
of 6 ecommerce platforms
0.1%
share of all crawled sites

Losing share — -5.2% over the last 6 monthly crawls

Source: HTTP Archive — a real-Chrome crawl of 15.5M origins (2026-09-01). Share of all crawled sites, not just ecommerce.

Based on 5 BigCommerce sites swept on SEOLZ

vs all-platform average

Avg SEO79
≈ average
Avg AEO20
-21 below average
Avg WCAG89
≈ average
Avg Security66
-6 below average
Avg GEO50
≈ average
Avg Composite64
-4 below average

BigCommerce sites score near the all-platform average. AEO is the most common area for improvement.

Data as of July 2026 · SEOLZ audits

Every scan checks all six pillars

You can't rank what AI can't read. SEO, AEO, and GEO tell you where you rank; WCAG, OWASP, and Lifecycle determine whether search and AI can read and trust you at all. SEOLZ scores all six as one system.

🔍
SEO

Your catalog pages may be invisible to Google right now and you'd have no way to know. Indexability gaps, canonical conflicts, and faceted navigation issues silently kill organic traffic — we surface every one and tell you which to fix first.

Learn how to fix SEO issues →
✨
Answer Engine (AEO)

When someone asks ChatGPT to recommend a product in your category, is your store in the answer? Often it isn't. We check the structured data, page structure, and brand signals that help search and AI understand your products and describe them accurately — and we measure whether they actually cite you, or a competitor.

Learn how to fix Answer Engine (AEO) issues →
🌐
AI Visibility (GEO)

AI search is eating traditional organic traffic. We track your actual brand mentions across ChatGPT, Perplexity, and other AI engines — and tell you what's pushing you down in the results.

Learn how to fix AI Visibility (GEO) issues →
♿
Accessibility (WCAG)

Ecommerce stores are among the most frequent recipients of ADA accessibility demand letters. We run WCAG 2.1 AA checks across your catalog, surface the barriers that most often appear in demand letters, and track each one through to a verified fix.

Learn how to fix Accessibility (WCAG) issues →
🛡️
Security (OWASP)

A missing security header exposes your customers, and a compromised or flagged site loses search visibility fast. We check the server configuration, HTTPS setup, and email authentication issues that erode trust — before they become an incident.

Learn how to fix Security (OWASP) issues →
⏳
Site Lifecycle

SSL expires. Plugin versions fall behind. GTM containers go unverified. These aren't hypothetical risks — they're the operational failures that cause outages, ranking drops, and security incidents. We catch them before they happen.

Learn how to fix Site Lifecycle issues →

Start free. Upgrade when ready.

Scout
Free
1 site · 50 pages/audit · monthly audits
6-pillar welcome scan
  • ✓Composite + pillar scores
  • ✓Issue counts
  • ✓Recurring five-pillar re-scan
  • ✓Free forever
Start free
Starter
$49/mo
1 site · 500 pages/audit · weekly audits
All 6 pillars
  • ✓Every finding across all 6 pillars, with step-by-step fixes for your platform
  • ✓Template fixes: fix it once, clear it on every page built from that template
  • ✓Fix tracking: mark it fixed and the next audit confirms it
  • ✓Email alerts for score drops, new security issues, and SSL / domain expiry
  • ✓Report builder with PDF, HTML and Markdown export
  • ✓GTM & tracking audit, plus Search Console topic gaps
Choose Starter

Questions about BigCommerce audits

Does SEOLZ work with BigCommerce?+

Yes — we crawl your live BigCommerce storefront, whether it's a standard Stencil theme or a headless build, and write fixes for the BigCommerce admin and theme.

Is BigCommerce good for SEO?+

Technically it's one of the more SEO-capable hosted platforms — flexible URLs, built-in Product schema, and a fast CDN. The issues we typically find are catalog-management ones: faceted URLs and multi-category duplicates, not platform limitations.

What changes if my BigCommerce store is headless?+

You inherit responsibility for everything the Stencil theme did automatically — meta, canonicals, structured data, and performance. We check the rendered frontend, so we catch the gaps a headless build commonly introduces.

See what's holding back your BigCommerce site

Free scan, no credit card, results in minutes. We've got you.

Scan My BigCommerce Site Free