Ecommerce Website Development in Pune: Product Schema for Shopify and WooCommerce, and Why Duplicate or Wrong Markup Costs You Rich Results
Product schema is a block of structured data (usually JSON-LD) on each product page that tells Google the product's name, image, price, currency and availability in a form a machine can read. If it is correct, present in the page's initial HTML and consistent with what shoppers see, your product pages can become eligible for richer Google results. If it is missing, duplicated by a theme and two apps, or out of date, the best case is that nothing happens and the worst is warnings in Search Console and listings that do not appear. Good ecommerce website development in Pune treats this markup as part of the build, not as a plugin installed at the end.
This article is for store owners and marketing managers on Shopify or WooCommerce who have heard "add schema" from an SEO vendor and want to know what that actually means, what to check on their own store and what to ask a developer. It covers what product markup is, the difference between product snippets and merchant listings, required and recommended properties, variants, where Shopify and WooCommerce get their markup from, why duplicates appear, how to audit a store step by step, a worked example and questions for your agency. Facts come from Google Search Central's product, merchant listing, product snippet and product variants documentation, read in October 2026. Google changes these pages and its eligibility rules, so verify before you commit to a scope. Where I describe general practice, or rely on community reports rather than official documentation, I say so. The worked example is hypothetical and no real client is described. This article does not cover payments, shipping rates or tax.
What product schema is, and what it is not
Structured data is extra information added to a page, in a standard vocabulary from Schema.org, so search engines do not have to guess what the page is about. For a product page, the vocabulary's Product type carries the name, images, brand, identifiers and an Offer with the price, currency and availability.
It is not a ranking trick. Google's product documentation describes it as the way to make a page eligible for enhanced presentations, such as price and availability, ratings, shipping and return information in results. Eligible does not mean guaranteed: Google decides what to show. And it is not a substitute for the page itself. The marked-up facts must match the facts a shopper sees. If the page says ₹1,499 and the markup says ₹1,299, you have created a mismatch, not an advantage.
Think of schema as a second copy of the product's key facts, written for a machine. Like any second copy, it goes out of date unless it is generated from the same source as the first.
Product snippets versus merchant listings
Google's documentation distinguishes two things, and the difference matters for a store.
- Product snippets are for product pages where people cannot buy directly, such as review sites. They support review-related options.
- Merchant listings are for pages where a shopper can buy from you. They support richer product details, including shipping and return information.
The two overlap: Google says meeting the required properties for merchant listings also makes a page eligible for product snippets, and the more properties you provide, the more enhancements a page can qualify for. Google also says providing both page markup and a Google Merchant Center feed maximises eligibility, and that some experiences combine the two; for example, product snippets may use price from your feed if the page lacks it. Our article on Google Merchant Center for Indian stores covers the feed side.
For an online store, you are normally aiming at merchant listings eligibility.
The properties that matter
From Google's merchant listing documentation, the required properties for a Product are:
name: the product name.image: one or more image URLs that Google can crawl and index.offers: a nestedOffer. Merchant listings need anOffer, not anAggregateOffer, because the merchant must be the seller.priceinside the offer: the active price, greater than zero.priceCurrency: a three-letter ISO 4217 code. For Indian stores, that isINR.
Recommended properties include:
availability: one value such asInStockorPreOrder.- Shipping and returns. Google recommends defining a global shipping policy and a merchant return policy at the
Organizationlevel, and using offer-level details only to override them. This is easier to maintain than repeating it on thousands of products, and it keeps the markup aligned with your actual policy pages. Our article on legal and trust pages for an Indian online store explains how to write those policy pages themselves. priceValidUntil,validFrom,validThrough: used for sale timing. Google's page warns that a pastpriceValidUntilmay stop the listing from displaying, so a value copied into the template and never updated can actively hurt.itemCondition,url: useful where relevant.- Identifiers and descriptive fields:
description,brand,sku, GTIN properties,mpn,category,color,size,materialandpatternhelp Google match your product. The documentation says to use at most one brand name and onesku. aggregateRatingandreview: governed by Google's review snippet guidelines. Reviews are an area where honesty and rules matter more than markup; our article on building a trustworthy product review system covers it.
For product snippets, the requirements are lighter: name, plus at least one of review, aggregateRating or offers. Because the Rich Results Test may warn if offers is present without a review or rating, expect some non-critical warnings; Google says non-critical issues are worth fixing but are not required for eligibility.
Guidelines that catch stores out
Several rules from Google's pages deserve to be written into your build specification.
Only purchase pages. Google states that only pages where a shopper can purchase a product are eligible for merchant listing experiences.
One product per page. Product markup suits pages about a single product or variants of the same product. Category and listing pages are not a good fit; Google recommends putting markup on product pages instead. This is a common mistake with themes that add Product markup for every item on a collection page.
Markup in the initial HTML. Google's documentation recommends placing Product markup in the initial HTML. Markup generated by JavaScript after the page loads can make Shopping crawls less frequent and less reliable. If your store injects schema through a script or tag manager, that is worth questioning.
One currency per URL. Offer each currency at its own URL.
Prices that are real. A zero price is not valid for merchant listings, and markup should reflect the active price.
Policies must be real. Shipping and return markup should describe policies you actually follow.
Variants: sizes, colours and the ProductGroup
Most stores sell variants: a kurta in four sizes and three colours, a protein powder in two flavours. Google's variant documentation explains how to tell it which products are variations of one parent.
ProductGrouprepresents the parent product. Common properties, such as brand, can be set once on the group.variesBylists the aspects that vary. Google's documentation listscolor,size,suggestedAge,suggestedGender,materialandpattern.hasVariantnests each variant'sProductentry under the group, or each variant points back withisVariantOf.productGroupIDis the parent SKU, and each variant needs its own unique identifier such asskuorgtin.- Each variant should be selectable through its own distinct URL, usually with a query parameter, and that URL should show the correct image, price and availability and let the shopper add that variant to the cart.
This is where default store setups often fall short. If a size dropdown changes the price with JavaScript but the URL never changes, Google sees one product page and one price. If your catalogue is large, variant markup is a design decision that should be made with the theme developer, not left to a plugin. Our article on WooCommerce variation galleries covers a neighbouring problem, and our guide to preparing product catalogue data explains why clean identifiers and attributes matter before any markup is written.
Where your store's markup actually comes from
On both platforms, markup can come from several places at once. That is the root of most problems.
Shopify
Shopify product pages commonly get markup from:
- The theme. Many themes output product JSON-LD themselves. I could not confirm from official documentation how every theme does it, so check your own theme's code.
- A manually added snippet a developer inserted in the past.
- An SEO app that injects its own schema.
- A reviews app that adds
aggregateRatingandreview. - Another integration, such as a loyalty or marketplace app.
Merchant community threads, which are reports from users rather than official documentation, describe cases of duplicate Product blocks where a theme and an SEO app or a reviews app both output markup, sometimes with different fields in each. Some of those threads also report that the fix was to switch off the app's JSON-LD option, such as a setting in a reviews app, or to remove the conflicting app. One commenter argued that Google simply picks the better data set and ignores the other, while another warned that duplicates can cause errors or ignored data; neither is an official Google statement. The practical conclusion: check, do not assume.
WooCommerce
WooCommerce core adds product structured data to product pages, and an SEO plugin, a theme or a reviews plugin may add more. I could not load WooCommerce's own documentation page for this when I researched it, so confirm what your version outputs by viewing the rendered source or running the Rich Results Test, and read your plugins' settings for schema options. The risk pattern is the same: more than one source writing a Product block, each slightly different.
Custom-built stores
In a custom build, markup is generated from your product database in a template. That is the cleanest setup, because the price in the markup and the price on the page come from one source. The risks are different: a template bug can affect every product at once.
Why duplicates and wrong markup do harm
The mechanics, based on Google's guidance and common sense rather than any published penalty:
- Conflicting values. Two
Productblocks with different prices or availability give Google a reason to distrust both. - Missing required fields. A block missing
priceorpriceCurrencymakes the page ineligible for merchant listings. - Stale data. An expired
priceValidUntilcan stop the listing from displaying, per Google's documentation. - JavaScript-injected markup that Google's crawl handles less reliably.
- Markup on the wrong pages, such as collection pages with dozens of
Productblocks. - Markup that does not match the page, which can attract a manual action under Google's structured data guidelines. Treat that as a risk to avoid rather than a likely outcome.
None of this is dramatic on a day-to-day basis. It shows up as flat impressions on product pages, warnings in Search Console and listings that never gain the enhancements competitors have.
A step-by-step audit of your own store
You can do the first four steps without a developer.
- Pick five product pages: a simple product, a variant product, a product on sale, an out-of-stock product and a bundle if you sell one.
- Run each through Google's Rich Results Test. Google's documentation names it as the tool to validate markup and fix critical errors. Note how many
Productitems it finds. More than one per page is a red flag. - View the page source and search for
application/ld+json. For each block, note what produced it, using the theme files and app list as clues. Do this on a copy of the theme, not the live one, if you plan to edit. - Compare the markup to the page. Price, currency, availability, name and image should match what a shopper sees. Test a sale price and a sold-out product specifically.
- Check Search Console. Google's documentation points to the Merchant listings report for pages where shoppers can buy, the Product snippets report for other product pages, and the rich result status report to track valid and invalid items. Look for patterns, not single errors.
- Use the URL Inspection tool to confirm Google can fetch the page and see the markup, and that the page is not blocked by robots.txt, a noindex tag or a login.
- Fix at the source. Decide which component owns the markup, switch off the duplicates, and then re-test.
- Submit and monitor. Keep your sitemap current and watch the reports after the fix; changes can take time to be reflected.
Do not delete a block before understanding what it contributes. One block may carry the core product data while another supplies ratings. Removing the wrong one can make the warning vanish while removing valid information.
A worked example (hypothetical)
Take a Pune home-decor store on Shopify. The figures are illustrative and not from a real client.
What the audit found:
- The theme output a
Productblock with name, image, price and availability. - An SEO app added a second
Productblock that includedpriceValidUntilset to a date in the past. - A reviews app added a third block with
aggregateRating. - Collection pages carried a list of
Productitems from the theme. - Shipping and return policy were not marked up anywhere, although the store had clear policy pages.
- Size and colour variants changed the price through JavaScript without changing the URL.
The fix plan:
- Decide the theme should own the core
Productblock, and switch off the SEO app's product schema. - Keep the reviews app's rating data, but confirm in its settings whether it adds a separate
Productblock or merges; configure it so only one product entity is output. If it cannot, ask the app's support for the supported method. - Remove
Productmarkup from collection pages, per Google's one-product-per-page guidance. - Remove the stale
priceValidUntil, or generate it from the actual sale end date. - Add an organisation-level shipping and returns policy that matches the policy pages.
- Give each colour variant its own URL parameter and make the selected variant load the right image, price and availability.
- Re-test five pages in the Rich Results Test, then watch Search Console for a month.
What was not promised: a ranking uplift, a rich result, or a traffic number. The work removes causes of warnings and makes eligibility possible; whether Google shows enhancements is Google's decision.
What ordering of work makes sense
If your budget is limited, here is the order I would take on a typical store:
- Make the core
Productblock correct and singular on every product page. - Fix price, currency and availability accuracy, including sold-out and sale states.
- Remove markup from non-product pages.
- Add organisation-level shipping and return policies.
- Add identifiers such as brand, SKU and GTIN where you have genuine values.
- Handle variants properly with distinct URLs and
ProductGroup. - Add review markup only when your review system meets Google's guidelines.
- Connect a Merchant Center feed and keep it consistent with the page.
Each step is independently testable, which is what you want in a maintenance agreement.
Questions to ask an ecommerce website development company in Pune
- Which component outputs our
Productmarkup: the theme, a plugin or an app? - How many
Productitems does the Rich Results Test find on a typical product page? - Is the markup in the initial HTML, or injected by JavaScript?
- How are sale prices, sold-out items and variants represented?
- Do category pages carry product markup, and should they?
- Where are our shipping and returns policies marked up, and do they match the real policies?
- What happens to the markup when we install a new SEO or reviews app?
- Which Search Console reports will you monitor, and how often?
- Who is responsible for fixing markup errors after a theme update?
- Will you document the markup source so a future developer can find it?
If your products have sizes and colours, also read our guide to product variants, size charts and fit guides, which covers how variants should be described in your markup and feeds.
Working with Govindani Infotech
Govindani Infotech is a web design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. If your product pages show warnings in Search Console or you suspect two plugins are fighting over your markup, we can audit a sample of pages, trace each block to its source and tell you plainly what to change and in what order.
Our ecommerce service page describes how we build and maintain Shopify and WooCommerce stores, our SEO service page explains where structured data sits alongside content and technical work, and our website creation work covers custom builds where markup is generated from the product database. For the general picture of schema beyond products, see our guide to structured data and schema markup. To talk it over, use the contact page or message us on WhatsApp.
Out-of-stock products raise their own markup and page questions, covered in back-in-stock and wishlist alerts.
Frequently Asked Questions
What is product schema on an ecommerce website?
It is structured data, usually JSON-LD, that describes a product's name, images, price, currency and availability in a form search engines can read. Google uses it to decide whether a product page is eligible for enhancements such as price, availability and shipping or return information in results.
Does product schema improve my Google ranking?
Google's documentation describes structured data as making pages eligible for enhanced presentation, not as a ranking boost, and eligibility does not guarantee that Google shows an enhancement. The practical benefit is accurate, machine-readable product facts, and avoiding errors that stop your listings qualifying.
Why does Search Console show duplicate or invalid product markup on my store?
Often because more than one source writes markup, for example a theme plus an SEO app or a reviews app. Community reports on Shopify describe exactly this pattern. Use the Rich Results Test to count the Product items per page, trace each to its source and keep one owner for the core block.
Should I put product schema on collection or category pages?
Google's documentation says product rich results suit pages focused on a single product or its variants, and that category and listing pages are not a good fit; it recommends putting markup on the product pages instead.
Do I need to mark up each size and colour variant?
If you sell variants, Google recommends marking the parent as a ProductGroup and each variant as a Product with its own identifier, and each variant should be selectable through its own URL that shows the right image, price and availability. If your variants change only through JavaScript on one URL, that needs to be addressed in the build.
Sources:
- https://developers.google.com/search/docs/appearance/structured-data/product
- https://developers.google.com/search/docs/appearance/structured-data/merchant-listing
- https://developers.google.com/search/docs/appearance/structured-data/product-snippet
- https://developers.google.com/search/docs/appearance/structured-data/product-variants
- https://community.shopify.com/t/removing-of-duplicate-schema/359409 (community discussion, not official documentation)