Product pages send Google no product data
The product page shows the price and Add to cart, but Google gets no product data from it. Usually the template skips WooCommerce's product summary.
The symptom
Nothing you can see. The product page has a title, a price and an Add to cart button, and customers buy from it. What is missing is in the page source: the block of structured data that tells Google “this page is a product, it costs this much, it is in stock”.
WooCommerce prints that data while it builds the product summary—the part of the product page with the title, price and short description. A product page template that places those elements one by one, without the summary, still looks complete, but WooCommerce never prints the data. That happens with templates from page builders, with a theme’s own product template, and with a block theme template from which the Product Summary block was removed.
In a sample of 221 WooCommerce stores from Poland, the UK and the US, checked in October 2026, about one in eight had product pages with no product data at all—in Poland, almost one in three. Most of them were built with an Elementor product template.
What it costs
- Google cannot show the page as a product. Price, availability and other product details in search results come from this data. Without it the page can still appear in search, but as an ordinary page.
- Merchant listings lose the page as a source. Google uses the same data to match product pages with what it shows in its shopping results.
- No promise attached. Data on the page does not guarantee any rich result; Google decides what to show. What the data does is give Google the answer in the form it asks for.
Source: Google Search Central, Product structured data.
How to check it yourself
- Paste the address of a product page into Google’s Rich Results
Test. When the data is there, it finds Product
snippets or Merchant listings. The Schema Markup Validator
lists a
Productfor the same page. - Or open the product page as a visitor, choose View page source and search for
application/ld+jsonand then for"Product". A block with breadcrumbs or the website name alone is not product data. - Check a few products from different categories: a template can be assigned to some categories only.
How to fix it
- Block theme: go to Appearance → Editor → Templates → Single Product. If the template has neither a Product Summary block nor an Excerpt block, add the Product Summary block back where the product details are, and save.
- Page builder or a theme’s own product template: ask its author or your developer to keep
WooCommerce’s product summary in the template (the
woocommerce_single_product_summaryaction), or to print the product data another way. - A broken block: if the page has a JSON-LD block that is not valid JSON, find the plugin or the code snippet that prints it and fix it there—Google discards the whole block.
- Clear your page cache and test the page again.
When it’s a false alarm
- The data is added by JavaScript, for example through Google Tag Manager, and the Rich Results Test, which runs JavaScript, finds product snippets or merchant listings. Google reads it after rendering the page; Merchlint reads only what the server sends. Hide the finding.
- The product pages are not meant for search, and the store asks search engines not to index them. Then settle that decision first: see Your store asks Google not to show it.
How Merchlint finds it
During an audit Merchlint opens up to three of your product pages from your own server, at their public address and without your login, the way a visitor or Google opens them. It picks published products that are in stock and sold best in the last 90 days (the newest ones, if nothing sold), from different top-level categories, and one variable product if the store has one. These are the only requests the plugin makes, and they go only to your own store.
On each page it reads every JSON-LD block and the microdata, from WooCommerce or any other plugin. A page with no product node—or with product data only inside a block that is not valid JSON—is a finding. One finding per store: the fix is usually one template. When the template is a block template without the Product Summary or Excerpt block, or a theme template that skips the summary, the finding names it.
When a page cannot be read—the store is in “Coming soon” mode, the site asks search engines not to
index it, the page answers with an error, does not answer, or returns something other than that
product’s page—Merchlint says so instead of reporting a problem. Developers can turn the requests off
with the merchlint_open_product_pages filter.
Confidence: F—fact from the page. Merchlint reads the same HTML that Google gets, before any JavaScript runs.
New in version 0.3.10. This check runs in the free version, with no cap.
Doesn't match what you see in your store? Email us—we read every message. contact@merchlint.com