Schema validation errors occur when the format, content, or expected fields of structured data fail validation checks. They may make it harder for search engines to understand the data or prevent rich results from displaying correctly. Fixing them does not guarantee better rankings: first identify whether the issue involves parsing, Schema.org specifications, or requirements for a specific search feature, then confirm that the markup matches the page’s purpose. Focus on issues that affect how data is understood and displayed. Do not blindly add inapplicable content just to clear a notice.
Validation errors can involve different kinds of checks
Schema describes information on a page, such as organizations, businesses, products, articles, or events. A 2021 article on Neil Patel’s website noted that validation errors can arise when data is incorrectly formatted or Google cannot find expected information. This does not mean every error represents the same kind of problem.
In its 2024 version 20.0 update, Screaming Frog separated Google rich result validation errors from Schema.org validation and listed filters for parsing errors, rich result errors, and warnings. The categories in this historical release offer a useful reference for interpreting these issues:
- Parsing issues: First check the data format to determine whether the tool can read the markup.
- Schema.org specification issues: Check the types and properties used rather than immediately assuming that search rankings have been harmed.
- Rich result issues: Identify which search feature the notice relates to. Do not confuse these checks with general structured data validation.
Confirm the page’s purpose before adding fields or adjusting markup
A missing-field notice does not necessarily mean you should add data. On Local Search Forum, fisicx cautioned that validation tools may misunderstand a page’s purpose and point to an unsuitable Schema type. This is a forum participant’s caution, not an official rule, but it offers an important starting point: first confirm that the markup describes the right subject.
For example, the 2021 article on Neil Patel’s website discussed WooCommerce adding product markup to product archive and category pages. The approach proposed at the time was to remove inapplicable markup rather than always filling in product fields. This is only a historical example and cannot be applied as a rule to all category pages today. Using a plugin does not eliminate the need for checks either; the same article noted that automatically generated markup can still contain validation errors.
Fix errors to help data be understood and displayed correctly—not to guarantee higher rankings
The 2021 article cited above suggested that Schema errors were unlikely to have a substantial direct effect on rankings but could prevent rich results from displaying. Correct markup, meanwhile, might help improve click-through rates. These are reasons to fix errors, but they do not guarantee that traffic will increase afterward. A possible improvement in click-through rates does not mean rankings will rise as a result.
When a site has many issues, start by grouping recurring problems, then list the affected URLs and representative pages for each group. A 2019 Screaming Frog article introduced this kind of summary report, which groups recurring errors rather than listing every occurrence individually. When planning fixes, consider the issue type, page purpose, and scope of impact so developers can address shared problems rather than simply aim for an error count of zero.
Schema validation errors: perspectives from across the web
How should you interpret a notice that an aggregate rating is missing a maximum or minimum value?
If the markup includes an aggregate rating, first confirm that the data accurately describes the rating scale actually used. A 2021 article on Neil Patel’s website listed missing maximum or minimum ratings as a common issue and used a one-to-five-star scale as an example. However, the scale should reflect actual usage, and this historical article should not be treated as a statement of current platform rules.
Do you still need to check Schema if you use a website builder or plugin?
Checks are still necessary. Neil Patel’s website noted that although website builders and plugins can help handle Schema, validation errors can still occur. Automatically generated markup therefore does not guarantee accurate data. When a notice appears, you still need to verify that the generated data matches the page’s actual content rather than assume the tool has handled everything correctly.
References
- Sitewide Schema Validator/Checkerlocalsearchforum.com — Source used in the article above.
- Screaming Frog SEO Spider Update – Version 20.0www.screamingfrog.co.uk · 2024-05-07T07:54:04+00:00 — Source used in the article above.
- How to Fix Schema Validation Errorsneilpatel.com · 2021-05-07T18:00:00+00:00 — Discusses: How should you interpret a notice that an aggregate rating is missing a maximum or minimum value?; Do you still need to check Schema if you use a website builder or plugin?
- Screaming Frog SEO Spider Update – Version 11.0www.screamingfrog.co.uk · 2019-03-05T09:52:50+00:00 — Source used in the article above.

