Schema Governance for Ecommerce Sites

Schema issues usually come from conflicts across apps, themes, and platform defaults. This governance approach prevents regressions and keeps structured data consistent through changes.

What Schema Drift Looks Like

On ecommerce sites, schema drift usually appears in Product objects first. You might notice duplicate Product entities on the same PDP because the theme outputs one JSON-LD block and your review app injects another. The ecommerce platform may add a default snippet on top. 

Over time, these attributes get out of sync. One Product has an outdated title, and another has the wrong URL. One may be missing key attributes, like the brand or SKU. 

The offer data tends to drift next. One script might output the current price and availability information from your live catalog, while the other includes stale sale prices. 

That’s how you end up with conflicting offers, which are incredibly irritating for consumers. For example, one offer may say that an item is in stock and listed at $29.99, while another lists the same product for $34.99 and has an out-of-stock status. 

Unfortunately, making updates without an ecommerce schema checklist creates a cascade effect, which means that other elements are impacted, too. Review or aggregateRating objects can get jumbled in the chaos, resulting in different rating counts and averages. Search engines won’t be able to tell which is canonical, which means impacted pages are going to plummet in the rankings.

Drift can also appear in different template types. Product detail pages might get updated schema templates, but collection pages and search results keep older patterns. 

Here’s how duplication chaos typically occurs in Shopify:

• The theme outputs a Product container in product.liquid
• An SEO app injects enhanced Product markup via script tags
• A review app wraps ratings inside its own Product object

Search engines have to reconcile multiple representations of the same product. Sometimes they choose one. Sometimes they suppress rich results. Either way, your store loses much-needed authority. 

What you need is an ecommerce schema checklist for your digital store. Below, you’ll learn how to identify product schema conflicts that interfere with BigCommerce and Shopify SEO using a practical schema QA checklist. Our guide also includes JSON-LD ecommerce templates that enable you to make important changes at scale without cutting corners. 

Before shifting to our ecommerce schema checklist, it’s important to identify all of the places that the schema originates from. Only then can you effectively govern schema markup in a way that preserves the authority of your site. 

Where Schema Comes From

Here’s a common scenario that outlines how schema gets added to your store. 

You’ve recently installed a new review app, and visually, everything about your ecommerce site appears to be working as it did before the changes. However, two weeks later, you dip in the rankings and are appearing in fewer rich results. There are no warnings. 

Once you begin doing your due diligence, you check the page source and find that there are three different product objects and two different price values. The aggregateRating is attached to a different ID than the primary product. While that may seem like a simple mistake, it’s actually a governance failure.

On modern ecommerce stacks like Shopify and BigCommerce, schema usually comes from three places. The downside is that these sources don’t automatically coordinate by default, so you are left to pay the price. These sources are:

• Platform Defaults: Core platforms sometimes output baseline product, offer, and breadcrumb schema, which are typically linked to specific system fields 
• Theme Code: Theme developers add JSON-LD blocks directly in templates or theme settings, which map storefront elements to specific properties 
• Apps and Integrations: Many apps and plugins inject their own JSON-LD, which adds a third source of schema 

Conflicts happen when none of these sources is treated as the canonical owner for each template type. One team might adjust Product schema in the theme while another updates an app’s settings. Without strong governance, each layer can fix something locally while creating drift across your site. These challenges occur anytime you change your theme or install a new app. 

However, simply keeping your store as-is isn’t practical. You need to make sure the store is user-friendly and appealing to your target audience. You also need apps that help you collect data about traffic, the user experience, and sales. 

Using scalable templates and an ecommerce schema checklist helps you stop the bleeding. However, you also need technical SEO expertise. That’s why many ecommerce brands turn to third-party agencies to assist with schema markup. 

A technical SEO agency that understands the challenges facing ecommerce brands can protect your authority and ensure you are still eligible for rich results. 

Conflict Patterns and Detection

Thoroughly reviewing your BigCommerce schema (or Shopify schema) will help you identify repeatable trends. Simply debugging issues as they are uncovered is not practical or conducive to your long-term success. After all, it can be several weeks before you realize that specific product pages have dropped in the rankings. In the meantime, you could be losing thousands in sales. 

Recognizing patterns will help you be proactive. The most common patterns behind product schema conflicts are:

• Multiple product objects on a single product detail page, all describing the same item with slightly different information
• Product ID or URL values that don’t match the canonical URLs
• Offers attached to different product objects, each of which claims to be the authoritative source 

For reviews, you may see:

• An aggregateRating from the review app and another that is generated by a theme snippet, each with different values
• Standalone review objects that are not properly linked via aggregateRating
• Product variants each outputting their own rating objects 

Once again, an ecommerce schema checklist holds the key. You can implement different ecommerce schema checklists for specific tasks. When creating or customizing checklists to fit your workflows, treat schema QA like any other technical SEO regression test:

• Use a structured data testing tool to extract all JSON-LD from a page
• Count how many product, offer, and aggregateRating objects you see
• Check that there is only one canonical product object per PDP
• Ensure that everything else hangs off that object
• Run targeted sampling by template
• Compare what the schema says to what the page shows

Once you figure out which drift pattern is common in your stack, you can codify it into lightweight schema QA checklists. 

[Placeholder for conflict detection worksheet]

Governance Workflow

Whether you are building an SEO strategy for BigCommerce or Shopify, you must tackle the governance challenge head-on. Don’t treat schema like a one-off implementation project. Make it part of your ongoing technical SEO and release process. A practical schema governance workflow for ecommerce looks like this:

Ownership

Assign one person to be accountable for product, offer, and review schema across your entire store. Define who can change the schema logic in each layer. With one person overseeing everything and only a handful of authorized users making changes, it will be much easier to prevent drift. 

Canonical Source Per Template

For each template type, decide which component outputs the canonical product schema. You must also determine where offers come from and which tool will be the default authority for reviews and ratings. The goal is to prevent overlap. 

Change Control

Treat changes that impact the schema like any other technical upgrades. Create a ticket, identify the templates that will be impacted, and note where JSON-LD is generated. Perform a quick schema QA on staging before publishing your updates. 

QA Sampling

Maintain a small, fixed set of URLs per template type. Run through this set using your ecommerce schema checklist. You don’t need 100% coverage, but you do need consistency. 

Feedback and Iteration

When you find product schema conflicts or places where review schema collides, fix the canonical source. Next, update your governance sheet and refine your ecommerce schema checklist to better fit the needs of your store. 

The QA Checklist

Here are a few different QA checklists by template type to help you keep your schema under control. 

For product templates, you need the following:

• A single product container
• Stable ID
• Correct SKU
• One authoritative offer
• Matching price and currency
• Single aggregateRating

If you are preparing to launch an app or updated theme, you need a checklist that addresses the following:

• Will the update add JSON-LD?
• Does it output a full product container?
• Can we disable the injection?
• Does it modify offer logic?
• Will the change create a new product ID?

Use these basic concepts to build checklists for other technical SEO processes that could impact the authority and performance of your digital store. Our templates are also a valuable resource to jumpstart your process. 

[Placeholder for schema QA checklist by template]

When to Get Help

When an ecommerce schema checklist isn’t enough to overcome your markup challenges or regain authority, it’s time to bring in outside support. Net Profit Marketing serves B2B clients by providing expertise and technical guidance. 

Ready to learn more about our services and how we can help? Book a consultation today.