# Structured data warnings that aren’t worth fixing

URL: https://ekom.blog/structured-data-warnings-that-arent-worth-fixing/
Published: 2024-09-23 · Updated: 2026-11-07
Author: Ekom
Topics: Technical SEO

> A practical guide to structured data warnings that aren't worth fixing and the decisions that make the work clearer.

The test tool shows a yellow warning, and the site owner asks: "Will this hurt my rankings?"

It depends on what the warning says. Some properties are optional recommendations. Others flag a real mismatch or a missing detail. Chasing every yellow notice without understanding it wastes time, and it can push inaccurate information onto your pages.

Structured data helps search engines interpret a page and can make it eligible for certain features. It doesn't guarantee a rich result, and it won't repair a weak page. The better question is whether the markup is valid, accurate, supported for the feature you want, and worth maintaining.

## Read the message before changing code

Work out which tool you're using and what feature it checks. Search Console enhancement reports, the Rich Results Test and general schema validators report different things. A warning in one isn't necessarily an error in another. Read the exact property name, affected URL and documentation linked from the report.

Check whether the property is required or recommended for eligibility. If a field is optional and you have no truthful value for it, I'd leave it out rather than invent one. Don't stuff in a placeholder image, rating, shipping detail or author just to make the warning vanish.

Confirm the page type. A Product page, an editorial review and an organisation homepage do not share identical requirements. The correct schema type and properties depend on what the page actually contains. Applying a product markup template to a category page may make the underlying data misleading even if the JSON is syntactically valid.

## Separate syntax from policy and usefulness

A validator can say whether markup parses and whether certain properties exist. It can't always tell you whether the claim is true, visible to users, or within every feature policy. Someone still needs to compare the data with the page and business records.

For example, an aggregate rating should reflect genuine visible reviews. A price should match the offer and currency. Availability should be current. A review markup warning cannot justify adding fabricated feedback. Similarly, an FAQ schema field should describe questions and answers that appear on the page, not content hidden only for search engines.

Some structured data is valid but does not enable a search feature the site owner expected. Google may change supported features or choose not to show a result. Check the current search documentation for the page's date and market; do not rely on an old plugin screenshot or a blog post from several years ago.

## Check for duplicate output

A theme, an SEO plugin, an e-commerce plugin and custom code can all print structured data. Check the rendered page for repeated Product or Article entities, conflicting canonicals or contradictory values. Adding yet another schema plugin often creates more warnings, not fewer.

Choose a single owner for each data source where possible. If WooCommerce outputs price and availability, confirm the SEO plugin does not provide conflicting values. If a custom script is needed, document its source and update process. A future editor should know where to fix the value when stock or policy changes.

Test a representative set of pages rather than only the homepage. Product variants, review pages, recipes, events and service pages may produce different output. One sample can confirm a pattern, but not every template.

## Prioritise warnings that affect the real page

Fix a warning when it reveals inaccurate, missing or important information, when the property is required for a relevant feature or when it affects a page the business relies on. For example, a canonical mismatch or stale price deserves attention beyond schema. The underlying page may have a more serious issue than the structured data message.

If a recommended property is optional and you don't have it, note it and move on. That's my default. If it could be added from a reliable source, decide whether the feature is useful enough to justify the work. For a small business, maintaining policy data accurately may be more valuable than filling optional fields that do not change the visitor's experience.

Keep an issue log with URL, message, feature, business impact, owner and decision. This avoids revisiting the same warning without context. If the issue is not being fixed, explain why; if the site or Google changes, the team can reassess later.

## Re-test after the change

When you do make an update, validate syntax, compare markup with visible content and check the live URL after deployment. Search Console may take time to recrawl. Do not assume the report will clear instantly or that a successful test means a rich result will appear.

Avoid changing several schema systems at once. If a warning disappears but a product page now reports the wrong price, the update did not improve the site's accuracy. Keep a backup or versioned record of custom code and test checkout or other relevant features after changing an ecommerce template.

## Notice when the warning points to a wider defect

Sometimes a structured-data warning is the first clue that product information is inconsistent. If a validator sees an unavailable product as in stock, or a price that differs from the page, check the catalogue sync and template rather than dismissing the notice as optional. The same applies if a canonical URL points to another item or if review data is attached to the wrong product. Fix the underlying source of truth, then verify both the visible page and the generated markup. The goal is accuracy, not a green tick.

## Related reading

- Schema markup on WordPress: where to start

- WooCommerce product schema: what plugins add and what's missing

- The URL Inspection tool in Search Console: a walkthrough

Open one warning and check the official documentation: is the property required, optional, or wrong? Does the warning point to a real gap that users would notice?

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
