Troubleshooting

Reference

Common structured data problems and how to fix them.

The item is not detected at all

• The @type, itemtype, or typeof value is misspelled or is not a real schema.org type. Confirm the exact type name.
• For JSON-LD, the block has a JSON syntax error such as a trailing comma or an unquoted key. The whole block is discarded when it fails to parse.
• The @context is missing or wrong. It should be https://schema.org.

A property is ignored

• The property name is misspelled. Property names are case sensitive.
• The property is not defined on the chosen type or any of its ancestors.
• The value type does not match what the property expects, for example a string where a nested entity is expected.

Dates are rejected

• Dates must use ISO 8601, for example 2026-06-10 for a date or 2026-06-10T19:30:00-05:00 for a date and time.

Prices look wrong

• price should be a string, not a number, so formatting and precision are preserved.
• priceCurrency must be a valid currency code such as USD.

Enumeration values are not recognized

• Enumeration members must be written as full vocabulary identifiers, for example https://schema.org/InStock, not the bare word InStock.

Markup does not match the page

• Structured data must describe content that is visible to users. Marking up content that is hidden or absent can be treated as spam.

The production page differs from what you validated

• A template or content management system changed the output after validation. Re validate the live page, not just the source you authored.

Quick checklist

1. Does the JSON parse.
2. Is the type real and correctly spelled.
3. Are all property names valid for the type.
4. Do value types match expectations.
5. Are dates ISO 8601 and prices strings.
6. Do enumeration values use full identifiers.
7. Does the markup match the visible page.