How to Fix Missing Product and Article Schema (JSON-LD)
Your product pages (URLs containing /product/, /products/ or /shop/) and your blog or news posts do not declare what they are in structured data, so search engines and AI assistants have to guess the price, stock status, author and publish date. By the end of this guide, each of those page types will output a JSON-LD block typed as Product, Article or BlogPosting, with the properties Google actually uses, and you will have validated it.

Why it matters
Product markup with offers, availability and ratings makes pages eligible for price, stock and star snippets in Google Search, and for free merchant listings in the Shopping tab. Article markup with author and dates helps Google show the correct byline and date and attribute your content. AI answer engines and shopping assistants parse the same JSON-LD to quote prices and cite authors, so unmarked pages are easier to misread or skip.
This audit fails when half or more of your product and article pages have no Product, Article or BlogPosting JSON-LD.
What you need
Step-by-step fix
Find which pages are missing the markup
Open a sample product page and a sample blog post, then view the source (Ctrl+U / Cmd+Option+U) and search for application/ld+json. Check the @type values, including any inside an @graph array. The audit only counts JSON-LD: a page passes if it has a type containing Product, Article or BlogPosting (so NewsArticle, TechArticle and ProductGroup also count).
Microdata or RDFa alone will not pass.
Turn on built-in schema if your platform has it
Many platforms already generate this markup once a setting or extension is enabled. Check this before writing code, because duplicate Product blocks with conflicting prices cause errors.
- WordPress posts: Yoast SEO or Rank Math outputs Article/BlogPosting automatically.
- WooCommerce: Product JSON-LD is built in, unless your theme strips it.
- Shopify and Wix: product and blog templates usually include it already.
If the platform's output is present and valid, go straight to the final validation step.
Add Product JSON-LD to the product template
Place one script block in the product page template and fill it from your product data, not hard-coded values. Google requires name plus at least one of offers, review or aggregateRating. org/InStock`.
Only include aggregateRating if the reviews are actually visible on the page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Blue Ceramic Mug",
"image": ["https://example.com/images/blue-mug-1x1.jpg", "https://example.com/images/blue-mug-4x3.jpg"],
"description": "12 oz stoneware mug, dishwasher safe.",
"sku": "EC-MUG-BLU",
"gtin13": "0123456789012",
"brand": { "@type": "Brand", "name": "Example Co" },
"offers": {
"@type": "Offer",
"url": "https://example.com/products/blue-mug",
"price": "18.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.7",
"reviewCount": "38"
}
}
</script>Add Article or BlogPosting JSON-LD to post templates
Use BlogPosting for blog posts, NewsArticle for news, and Article for everything else. Include headline, image, datePublished and dateModified in ISO 8601 format with a timezone. For author, use a Person with name and a url pointing to the author's bio page.
The dates must match the dates shown on the page, and dateModified should only change when the content meaningfully changes.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Brew Pour-Over Coffee at Home",
"image": ["https://example.com/images/pour-over-16x9.jpg"],
"datePublished": "2026-01-14T08:00:00+00:00",
"dateModified": "2026-02-03T10:30:00+00:00",
"author": [{
"@type": "Person",
"name": "Jane Doe",
"url": "https://example.com/authors/jane-doe"
}],
"publisher": {
"@type": "Organization",
"name": "Example Co",
"logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
},
"mainEntityOfPage": "https://example.com/blog/pour-over-guide"
}
</script>Generate the markup dynamically in templates
Output values from your data layer so every page gets correct, current markup. Escape the values properly: serialising with a JSON encoder avoids broken quotes in product names. The example below shows a Shopify Liquid product template.
For other platforms, see the platform notes.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": {{ product.title | json }},
"image": {{ product.featured_image | image_url: width: 1200 | prepend: 'https:' | json }},
"sku": {{ product.selected_or_first_available_variant.sku | json }},
"brand": { "@type": "Brand", "name": {{ product.vendor | json }} },
"offers": {
"@type": "Offer",
"url": {{ request.origin | append: product.url | json }},
"price": {{ product.selected_or_first_available_variant.price | divided_by: 100.0 | json }},
"priceCurrency": {{ cart.currency.iso_code | json }},
"availability": "https://schema.org/{% if product.available %}InStock{% else %}OutOfStock{% endif %}"
}
}
</script>Handle /shop/ listing pages and non-product URLs
The audit treats every URL containing /product/, /products/ or /shop/ as a product page. That includes category and archive pages such as /shop/mugs/. A site passes as long as fewer than half of these pages lack the markup.
Do not paste a fake single Product onto a category page. Instead, either make sure your individual product pages, which usually outnumber listings, are marked up, or add an ItemList whose items are Product entries that match the products visible on the page.
Validate, deploy and monitor
Paste a live URL into Google's Rich Results Test. Product pages should show Product snippets and/or Merchant listings, and posts should show Article, with no red errors. org-level issues.
After deploying, open Google Search Console and watch Enhancements > Product snippets, Merchant listings and Shopping tab listings for errors as Google recrawls. Finally, re-run this audit.
Platform-specific notes
WordPress / WooCommerce
Yoast SEO and Rank Math add Article/BlogPosting to posts inside an @graph array, which counts. WooCommerce outputs Product JSON-LD on single product pages by default. If it is missing, check whether your theme or a 'performance' plugin removes woocommerce_structured_data. Rank Math Pro and Yoast WooCommerce SEO add brand, GTIN and better offer data.
Shopify
Product URLs use /products/, which the audit checks. Dawn and most Online Store 2.0 themes output {{ product | structured_data }} and {{ article | structured_data }} in the main-product and main-article sections. Older or custom themes may lack it. Edit them in Online Store > Themes > Edit code. Avoid stacking a schema app on top of theme markup, because that creates duplicate Product blocks.
Wix
Wix Stores product pages and Wix Blog posts generate Product and BlogPosting JSON-LD automatically. To add properties such as GTIN or brand, go to the SEO settings for the page type (Dashboard > Marketing & SEO > SEO > SEO Settings > Product pages > Edit > Structured data markup). Static pages built as 'product pages' without Wix Stores need custom markup added in Page settings > SEO > Advanced SEO > Structured data markup.
Webflow
Webflow generates no Product or Article schema. Open the CMS Collection template page, go to Page settings > Custom code > Inside <head> tag, paste the JSON-LD and insert CMS fields with the '+ Add field' button. Webflow Ecommerce product templates need the same treatment, using the product price and SKU fields.
Next.js
In the App Router, render <script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd).replace(/</g, '\\u003c') }} /> inside the page component, and build the object from the same data you fetch for the page. Make sure it is server-rendered, not injected after hydration, so crawlers see it in the HTML.
Check that it worked
✅ How to verify
- Google Rich Results Test shows 'Product snippets' or 'Merchant listings' for product URLs and 'Articles' for posts, with zero errors.
- View-source on a product page and a post shows an application/ld+json block whose @type is Product, ProductGroup, Article, BlogPosting or NewsArticle (directly or inside @graph).
- Google Search Console > Enhancements lists your pages as valid items, and the error count trends down after recrawl.
- Re-running the audit shows fewer than half of product and article pages missing the markup, ideally none.
⚠️ Common mistakes
- Adding markup through Google Tag Manager or client-side JavaScript after the page loads. Many crawlers and AI agents read only the server HTML, so they never see it.
- Using microdata or RDFa only. It is valid schema.org markup, but this audit looks for JSON-LD, and JSON-LD is easier to maintain.
- Hard-coding price or availability so the markup drifts from the visible page. Google can then disapprove merchant listings or ignore the snippet.
- Adding aggregateRating or review markup for reviews that are not shown on the page, or that you collected about your own business. This violates Google's review snippet guidelines.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Do I need both Product and Article schema on the same site?
Only if you have both page types. Put Product on individual product pages and Article or BlogPosting on posts. Each page should describe its main content with one primary type, not both.
Is BlogPosting better than Article for SEO?
Google treats Article, BlogPosting and NewsArticle the same for article rich results. Pick the one that most accurately describes the content. BlogPosting is the natural choice for a company blog.
Why doesn't my product show stars or a price in Google after adding schema?
Valid markup makes a page eligible but does not guarantee the snippet. Google also needs to recrawl the page, trust the site, and see data that matches the visible page. Check Search Console for warnings, and make sure the reviews and price appear on the page itself.
Can one page have multiple JSON-LD blocks?
Yes. Organization, BreadcrumbList and Product can sit in separate script tags or in one @graph. Just avoid two different Product blocks for the same item with conflicting data, which often happens when a theme and an app both add markup.
How to Fix Missing Security Headers (CSP, Referrer-Policy)
How to Fix Missing WebSite Schema (JSON-LD Guide)
How to Fix Server Uptime: Monitor and Reach 99.9%+
How to Fix Missing Organization Schema (JSON-LD Guide)
How to Fix Slow DNS Response Time for Your Website
How to Fix Structured Data Errors on Your Website