The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A recall article should be described to search engines as an article. When its JSON-LD declares a Product node, the page is being classified as a product listing even though readers see a news-style report. The fix is to change the type to Article, remove any Product properties the page cannot truthfully support, and keep the recall facts in the visible text. A developer write-up on DEV Community describes this exact case: the recall facts were visible on the page, but the structured data used Article and BreadcrumbList nodes, and a warning about missing Product fields prompted the question of whether the type was right at all (DEV Community: The JSON-LD node that made a recall article look like a product).
Why the Product node is the wrong label
Structured data tells machines what a page is. An editorial report about a recall, a safety notice, or a defect investigation is a piece of writing about a product, not a product page. Google’s Product snippet documentation is built around product information: a product name, and at least one of review, aggregateRating, or offers so that a product result can be eligible for display (Google Search Central: Product snippet structured data). A recall article usually has none of those things. It has no price to show, no review of its own, and no aggregate rating.
Google’s Article guidance covers news, blog, and sports article pages. It says that Article markup “can help Google understand better what your page is about and show better title text, images, and date information for your page in search results on Google Search and other properties (for example, Google News and the Google Assistant)” (Google Search Central: Article structured data). That describes the job a recall report is doing: it is dated, written, headlined, and explanatory. The page is an article about a product.
Free tools Windows power users keep installed
One-click scans. No signup required.
The subject being a product does not make the page a product. Choose the type from what the page is for. A reader who lands on a recall report wants to know what was recalled, why, which units are affected, and what to do. That is editorial content.
When Product markup is legitimate
Product markup is appropriate on a page whose purpose is to present a specific product: a product detail page, or a review that evaluates one item. Those pages can carry the properties Google’s Product guide asks for. The same product name can appear on both kinds of page, so the decision has to be made page by page.
| Page purpose | Appropriate type | What the page must actually contain | Main risk if mislabeled |
|---|---|---|---|
| Recall or safety news about a product | Article | Headline, byline or publisher, date, and the recall facts in visible text | Product node with no offers, review, or rating triggers missing-field warnings and misstates the page’s purpose |
| Product detail page with a real purchase option | Product | Product name plus at least one of review, aggregateRating, or offers, all reflecting real data on the page |
Missing eligibility properties, so the Product snippet cannot be considered |
| Independent review of a product | Review or Article, assessed on its own content | Review content written by the publisher, with the product described accurately | Inventing an aggregate rating or offer to satisfy a Product guideline |
Google’s eligibility documentation describes what a product result needs. It does not promise that meeting those requirements will produce a display, so markup choices should follow accuracy first.
Rank #2
How the wrong node gets onto a recall article
In most sites, the stray node is not written by hand for a single article. It arrives through the system that builds the page.
Template-level schema
A theme or article template may emit one JSON-LD block for every page in a category, and the category may be named for products. Every post in that category then inherits the Product type, including editorial coverage that happens to live there.
Plugin field mapping
Many SEO and commerce plugins generate Product markup whenever a post has a product-like field, such as a SKU, price, brand, or a “product” taxonomy. A recall post that was tagged with the affected product’s name or model number can trigger that mapping without anyone deciding it should.
Copied product blocks
Editors sometimes reuse a product summary block from a shop page. If that block includes its own structured data, the recall article receives a second, product-focused node alongside the Article node.
Find the node on the live page
- Open the recall article in a browser and choose View page source. In Chrome on Windows or Linux, press Ctrl+U; on macOS, press Command+Option+U.
- Search the source for
application/ld+json. Each match marks a JSON-LD block. Check every block, because a page can carry more than one. - Search within those blocks for
"@type". Note every type value, including types nested inside other objects. A value of"Product"at any depth is the one to trace. - Check whether the Product block is emitted by the page template, a plugin, or a manually pasted snippet. The page source does not say which; the content management system’s settings and plugin list will.
Fix the type without inventing data
- Change the top-level type for the recall article to
Article. Keep theheadline,datePublished,dateModified, and author or publisher fields that match the visible page. - Remove the Product node, or disable the plugin rule that generates it for this page or template. Do not replace it with an empty or approximate
offers,review, oraggregateRatingblock. - Keep a
BreadcrumbListonly if its items match the navigation the reader can see on the page. - Make sure the recall facts appear in the article body in plain text: what was recalled, the affected models or batches as stated by the issuer, the reason, and the action readers should take. Structured data does not replace this text, and the text does not need to change because the markup did.
- Test the page again and confirm that the JSON-LD now declares the article type and that no Product node remains. Repeat the check after any template or plugin update, since those updates can restore the old mapping.
Keep, change, or remove
| Element on the recall article | Action | Reason |
|---|---|---|
| Article node with headline and dates | Keep | Describes the editorial page accurately |
| Product node generated by template or plugin | Remove for this page | The page does not present a product for sale or review |
| Offers or price fields | Remove unless a real offer is shown | Recall coverage has no purchase option to describe |
| Aggregate rating or review fields | Remove unless the page contains that rating or review | Invented ratings misrepresent the page |
| Recall facts in visible text | Keep and check for accuracy | Readers and search engines both rely on the visible content |
What the markup can and cannot do
Correct markup helps a search engine interpret a page. It does not guarantee a particular display, and it does not change how the recall itself is reported. A recall article with accurate Article markup and clear, dated text is in a better position than one that describes itself as a product it is not. The correction should be made for accuracy, and any change in search presentation should be treated as a side effect rather than the goal.
If the same product also has its own product detail page, evaluate that page separately against the Product requirements above. A recall report and a product listing should not share one node, even when they share a product name.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
