Implementing structured data correctly within BigCommerce can mean the difference between rich results that build shopper trust or underlying issues that dilute your SEO efforts. Review, AggregateRating, and Offer schema are each particularly prone to mistakes on ecommerce platforms.
With that in mind, the following guide will walk you through how to implement BigCommerce product schema safely, including what pitfalls to avoid and how to validate your work.
Why Review Schema Matters for Ecommerce
Search engines reward clear signals; by marking up products with Review and AggregateRating schema, you enable Google to display star ratings, review counts, and pricing in its search engine result pages (SERPs). These changes boost click-through rates and communicate credibility before a shopper even visits your site.
The challenge, however, comes from the fact that BigCommerce themes and third-party apps sometimes inject partial or duplicated schema. And if they are left unchecked, you risk conflicting markup, outdated pricing, or dangling reviews without any AggregateRating context.
Required vs. Optional Properties
At a minimum, you need to address the following BigCommerce product schema elements:
- Product: Name, Image, Description, SKU, Brand, Offers
- Offer: Price, PriceCurrency, Availability, URL
- AggregateRating (for Reviews): ratingValue and reviewCount
- Review: Author, datePublished, reviewBody, reviewRating
Other helpful (but not strictly necessary) schema types include BreadcrumbList and VideoObject.
Should You Use Snippets or Apps?
There are two main ways to inject BigCommerce structured data: theme snippets and applications.
Theme snippets are the best option for developers who have control over their Cornerstone or custom theme files. To use them, you’ll need to add schema as JSON-LD within product.html and category.html templates, and ensure your markup is tied directly to product objects in BigCommerce’s catalog.
Apps and plug-ins are the more “convenient” option, but many use a black box approach, meaning you may not know how they work or how JSON-LD is added. That can result in redundant schema that leads to duplicate product or offer objects on the same page.
Handling Data Freshness for Offers
BigCommerce prices, as well as your inventory, can shift quickly when you run promotions or sales. But once things cool off, it’s important to keep in mind that Google frequently flags stale price or availability fields.
To reduce the risk of such warnings, you’ll need to pull product, price, and value data directly from the theme context, use conditional logic for availability, and avoid hard-coding values and rely on dynamic population to stay compliant.
Common Pitfalls With AggregateRating
When implementing BigCommerce product schema for aggregateRating, you’ll want to avoid doing the following:
- Declaring AggregateRating without reviews
- Allowing conflicting rating values
- Hard-coding rating values into your schema
These mistakes, while simple, can nevertheless hurt your rankings and confuse Google. You may even be penalized for trying to declare aggregateRating without reviews.
Product JSON-LD Example for BigCommerce
Here is a look at a JSON-LD structured data example:
<script type=”application/ld+json”>
{
“@context”: “https://schema.org”,
“@type”: “Product”,
“name”: “{{product.title}}”,
“image”: [“{{getImage product.main_image ‘zoom’ (cdn ‘https:’)}}”],
“description”: “{{{stripHtml product.description}}}”,
“sku”: “{{product.sku}}”,
“brand”: {“@type”:”Brand”,”name”:”{{product.brand.name}}”},
“offers”: {
“@type”: “Offer”,
“priceCurrency”: “{{currency_selector.active_currency_code}}”,
“price”: “{{product.price.value}}”,
“availability”: “http://schema.org/{{#if product.stock.available}}InStock{{else}}OutOfStock{{/if}}”,
“url”: “{{product.url}}”
}
}
</script>
You can use the code above as a general template in which to add structured data relevant to your digital store.
Validation and Troubleshooting
After deployment, always run your pages through Google’s Rich Results test or the Schema Markup validator, making sure to focus on the following aspects:
- Warnings, such as “missing field”
- Duplicate product objects
- Price/availability mismatches
You can’t cut corners during troubleshooting; you must ensure that all of your structured data is accurate and functional before going live.
Acceptance Criteria for Success
With properly configured product schema, you should see your site meeting the following thresholds:
- Rich Results Test passes with zero critical errors
- No duplicate Product or AggregateRating entities
- Price and availability fields updating automatically with catalog changes
- No stale review warnings from Google
- Improved CRT from enhanced SERP snippets
If you aren’t seeing the kind of progress you hoped for, revisit the tips above until you achieve these points. And if you are unable to make any more noticeable gains, consider bringing in a team of pros to conduct a technical SEO audit of your digital store.
Frequently Asked Questions
Why Does Google Show Warnings Even When My Schema Is Correct?
In these cases, warnings are signs that optional fields, like “reviewBody,” are missing. While these omissions won’t disqualify your markup, filling them out can certainly strengthen your chances of earning Rich Results.
Do I Need Both JSON-LD and Microdata?
JSON-LD is Google’s preferred format, and that means you should remove or disable redundant microdata if an app is injecting it. That’s the danger of using apps, especially “black box” solutions that don’t reveal how they work or how they decide where to integrate structured data.
Any time you remove an app because it’s outdated or has gone unused, you’ll also need to check for left-behind markup or JavaScript.
Optimize BigCommerce Product Schema With Net Profit Marketing
Schema standards are constantly evolving, and that means Google may change requirements for Offer or Review markup while your BigCommerce theme continues to receive updates. To stay ahead, remember to periodically re-validate your key product pages, document your theme snippets so future devs know where schema lives, and audit third-party apps after every theme upgrade to prevent duplicate markup
If you need help getting started, Net Profit Marketing has your back. We offer BigCommerce audits and can identify opportunities to improve or optimize schema markup. Contact us today to get started.
Leave a Reply