Discussion starter: an ecommerce SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- eCommerce SEO
- Structured Data
Is product structured data still worth maintaining when Merchant Center feeds already give Google price, availability and shipping?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
The short answer is yes for most merchants, but for different reasons than a few years ago, and not every property is worth maintaining. The feed is the main data source for Shopping ads and free listings. Product markup now does three other jobs. It lets Google check the feed against your landing pages. It feeds automatic corrections to your Merchant Center data. And it supports the organic product results (merchant listings and product snippets) that come from crawling your pages.
The deciding factor is accuracy, not coverage. Correct, minimal markup is cheap and useful. Extensive markup that drifts out of sync with the page and the feed can do more harm than good, because Google uses it to verify and even overwrite the feed. So the practical move is usually to trim the markup to what you can keep accurate, not to remove it.
What Google says about using both
Google’s product structured data documentation says that providing both on-page structured data and a Merchant Center feed maximises your eligibility for product experiences. It also says this helps Google understand and verify your data. The same page notes that product snippets may use pricing from your feed when the structured data on the page does not include it. In other words, Google treats the two sources as complementary, not interchangeable.
The part many merchants miss is Merchant Center’s automatic item updates. Google’s help page says these read the structured data and other product data on your store’s pages. They can update price, availability and condition in Shopping ads and free listings when those values differ from your feed. Google says the automations should already be turned on in your account, and that they may not work for products whose price or availability changes more than once a day.
Important distinction:
Structured data is not a passive extra that Google may or may not read. With automatic item updates on, the values your pages expose can change what Shopping ads and free listings show. That makes markup accuracy a paid-media issue as well as an SEO one.
Which data source does which job
Source Main role What goes wrong when it is inaccurate Merchant Center feed (or Content API) Primary product data for Shopping ads, free listings and newer Google shopping surfaces Disapprovals, suspended items, wrong prices shown in ads Product structured data on the page Verification of the feed, automatic item updates, organic merchant listings and product snippets Mismatch warnings, feed values “corrected” to the wrong number, invalid items in Search Console reports Merchant Center or Search Console shipping and returns settings Account-wide shipping and return policies Wrong delivery or return information shown across many products at once Organisation-level return policy markup Fallback policy information, useful for sites without Merchant Center Overridden by stronger sources, so errors are often invisible The return policy documentation sets an explicit order of precedence, strongest first: Content API return settings, then settings in Merchant Center or Search Console, then product-level merchant listing markup, then organisation-level markup. If you manage returns in Merchant Center, product-level return markup is mostly redundant for Google. That is one of the clearest places to cut maintenance. Shipping has equivalent settings in Merchant Center. Check the current shipping documentation for its precedence before removing shipping markup, rather than assuming it matches returns.
The markup that earns its maintenance
- Core offer data:
name,image, and anOfferwithprice,priceCurrencyandavailability. Every Offer needs a price for merchant listing eligibility. For discontinued items, changeavailabilitytohttps://schema.org/Discontinued; do not remove the price and leave the Offer in place. - Identifiers:
gtin,brandandmpnwhere they exist. They help Google match your page to the same product in your feed and elsewhere. - Condition:
itemCondition, especially if you sell refurbished or used stock, since automatic item updates read it. - Variants:
ProductGroupmarkup if you sell sizes or colours, so variant pages and the parent product are understood together. - Reviews and ratings: only when they are genuine, first-party and visible on the page. Stale or unrelated rating markup is a policy risk.
- Shipping and returns: keep them in Merchant Center or Search Console settings if you can. Use organisation-level markup as a fallback if you have no Merchant Center account.
On Shopify, WooCommerce and most mainstream platforms, the theme or an app generates most of this. The build cost is close to zero. The real cost is keeping the markup, the visible page and the feed in agreement when prices change, sales start, stock runs out or a theme update changes the template.
Where the markup actively causes problems
Markup is most likely to cause trouble when it is generated separately from the price the shopper sees. Common causes are:
- full-page caching that serves yesterday’s JSON-LD with today’s visible price
- prices injected by JavaScript after the markup was rendered server-side
- sale prices handled in the feed but not in the template
- multi-currency or tax-inclusive and tax-exclusive display that differs from the feed’s currency and tax treatment
Hypothetical example:
An outdoor gear retailer runs a weekend sale. The feed carries the sale price through a supplemental feed. The product template’s JSON-LD sits in a page cache for 48 hours and still shows the regular price. The visible price is correct because a script updates it. Merchant Center crawls the landing page, sees a markup price that differs from the feed and flags a mismatch. Depending on what its extractors trust, it may update or limit the item. The fix is not deleting the markup. The fix is generating the markup from the same price source and cache rules as the visible price.
Removing the markup does not make this verification go away. Google’s help page says automatic item updates use “advanced data extractors” on your HTML as well as structured data. Without markup, Google is just guessing from less reliable signals.
When the calculation changes
Situation What I would do Why Standard retailer with a Merchant Center feed Keep minimal, accurate product markup. Move shipping and returns to account settings. Verification, automatic updates and organic product results all depend on it Retailer without Merchant Center Markup is essential, including organisation-level return policy It is the main way Google learns your product data from your site B2B catalogue with “request a quote” pricing No Offer without a price. Consider whether product snippet markup (reviews) fits Offers without a price are not eligible for merchant listings Editorial review site Review-focused product snippet markup, not merchant listing markup You are not selling, so feed logic does not apply Headless or heavily cached build with frequent price changes Fix how markup is generated first. Treat the markup and the feed as one data pipeline Mismatches are most likely here, and automatic updates may not keep up One more consideration is non-Google consumers: Bing, price comparison crawlers and AI shopping assistants. Some may parse on-page markup, but public documentation on how much AI assistants rely on it is thin. Google’s own agentic shopping work, including the Universal Commerce Protocol and Merchant Center conversational attributes, is built on Merchant Center data. That suggests feed quality is the bigger long-term investment. Markup is the verification layer beside it, not the thing to over-engineer.
Evidence worth inspecting before changing anything
- Merchant Center diagnostics: look for price or availability mismatch issues between feed and landing page, and for any notices about automatic item updates. A steady trickle of mismatches means your markup and feed come from different sources.
- Search Console enhancement reports: merchant listings and product snippets. Look for invalid items and missing-field warnings, and check whether the valid count tracks your live catalogue.
- Performance report search appearance: if product result appearances are shown for your property, compare clicks from them with your standard web results. That tells you how much organic product exposure you would put at risk.
- A sample audit: for 100 to 200 products across templates, compare the markup, the visible page and the feed for price, availability and currency on the same day.
One fast check to run this week
Run the sample audit above on a day when a promotion is live, because sales are when these sources drift apart. Metric: the share of sampled products where markup, visible price and feed all agree. A reasonable target is near-total agreement, with any mismatch traced to a named cause (cache, script, currency, sale logic). Time window: one promotion cycle. Next step: if agreement is high, trim redundant properties and leave the rest alone. If it is low, fix the pipeline so markup and feed come from one source before worrying about anything else in the markup.
My position: keep product structured data, keep it small and make it exactly match the page. Let Merchant Center or Search Console settings carry the policy data they now override anyway. The maintenance you save by trimming is real. The risk from removing the markup entirely is also real, and harder to see until a price mismatch reaches your ads.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
- Core offer data:
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.