Open the page source on almost any BigCommerce product page, and there’s already a Product schema block sitting in the head. That’s the part everyone knows. What’s less obvious is how little that block actually contains. A name, an image, one price, and not much else. It passes validation. It just doesn’t do the job it’s supposed to do.
SearchPilot’s controlled A/B tests on review schema alone found a 20% traffic lift from adding one missing field. It highlights how much opportunity can be missed when default BigCommerce schema markup isn’t fully implemented across a catalog.
What the Default Theme Schema Actually Contains
Stencil templates generate a Product object automatically on every product page. That’s genuinely useful, nobody starts from a blank slate. But “automatic” and “complete” aren’t the same thing. The default output rarely includes aggregateRating, often skips brand and gtin, and handles offers as a single static price rather than a proper range.
On a catalog with a few hundred SKUs and real variant complexity, it turns into a coverage problem. Some pages become eligible for enhanced listings, while others sitting right beside them don’t.
Four Common Problems With Out-of-the-Box Schema
Missing Ratings Field
No aggregateRating = no stars. Regardless of how many real reviews exist on the page. This is one of the most common reasons a product with strong reviews still shows a plain blue link in search.
One Price Standing In for Several Variants
A product with five colors and three sizes needs AggregateOffer with a genuine low-to-high range. Default markup usually grabs whichever variant loaded first and calls it done. When that number doesn’t match what’s visible on the page, Google treats it as a mismatch and tends to drop the markup rather than guess.
Fixes That Don’t Survive a Theme Update
Someone edits the JSON-LD by hand, adds the missing fields, and ships it. A theme update lands a few weeks later, the template quietly reverts, and nothing immediately flags the change in Search Console.
Two Apps Writing Two Product Schemas on One Page
Review widgets and SEO plugins frequently inject their own Product object instead of extending the theme’s. Two Product schemas on one page can create conflicting signals, making it harder for Google to determine which markup to trust.
{
“@context”: “https://schema.org”,
“@type”: “Product”,
“name”: “Example Product Name”,
“image”: “https://example.com/images/product.jpg”,
“sku”: “EX-1001”,
“brand”: {
“@type”: “Brand”,
“name”: “Your Company Name”
},
“aggregateRating”: {
“@type”: “AggregateRating”,
“ratingValue”: “4.6”,
“reviewCount”: “128”
},
“offers”: {
“@type”: “AggregateOffer”,
“priceCurrency”: “USD”,
“lowPrice”: “24.99”,
“highPrice”: “39.99”,
“offerCount”: “3”,
“availability”: “https://schema.org/InStock”
}
}
What Incomplete Schema Costs a Store Today
Complete structured data now correlates with roughly 4.2x better odds of appearing in Google Shopping results. That used to just mean losing out on stars. Now, with AI Overviews and shopping assistants pulling directly from structured data to decide what to recommend, a thin Product schema can reduce a product’s chances of appearing in AI-generated shopping experiences or enhanced search features.
On a platform like BigCommerce, where themes, apps, and custom Stencil work all touch the same fields, solid Ecommerce schema takes more than installing a theme and moving on – it needs someone checking that ratings, pricing, and availability all line up the same way across every page, not just the ones that got manual attention early on.
Catalogs with real volume tend to do better with schema that regenerates automatically as inventory and reviews change, rather than markup that only gets touched when someone remembers to.
How to Audit and Fix It
Pull the live JSON-LD, check it against required and recommended fields, confirm the schema price matches the page price. Add aggregateRating, brand, and a real AggregateOffer range for variant products. That’s most of the distance between markup that validates and markup that actually earns the rich result.
Final Thoughts
Default BigCommerce schema markup was never designed to be a finished product. It’s a starting point that a lot of stores mistake for the whole job. The gap between what’s there and what actually earns rich results is smaller than it looks, but someone has to go find it.
Common Questions
Does BigCommerce add schema markup automatically?
Yes, but the default block usually covers only name, image, and price. Ratings, brand, and full offer data are typically missing.
Why aren’t star ratings showing up in search for my products?
Missing aggregateRating is almost always the cause, even when real reviews are visible on the page itself.
Can a review app cause my schema to stop working?
Yes, if it adds its own Product object without disabling the theme’s default one – the two can conflict and cancel each other out.
Does BigCommerce schema update when I change a price?
Not reliably. Cached or static JSON-LD can lag behind live pricing, particularly on variant-heavy pages.
How do I know if a theme update broke my schema?
Check Search Console’s structured data reports after any update, reverted templates usually show up there before they show up in lost rich results.
Madeline Miller love to writes articles about gaming, coding, and pop culture.
