Structured data21 rules onhow your structured data is formed, what it says and where it points.
Syntax, values, selected rich-result fields, consistency with visible content and linked identities.
Syntax
- A JSON-LD block fails the syntax checkA complete JSON-LD block in the page's served HTML fails the syntax check.In the report: Invalid JSON-LD structured data
- JSON-LD has an invalid context or unmapped termsAn original JSON-LD context has an invalid type, or an absent/null/empty context leaves concrete plain terms unmapped.In the report: JSON-LD has an invalid context or unmapped terms
Values
- A breadcrumb trail has inconsistent structureA captured breadcrumb trail has invalid positions, missing non-final fields or conflicting declarations of the same trail.In the report: BreadcrumbList structure is invalid
- A GTIN or ISBN fails identifier validationA captured product identifier has an invalid length, character pattern, placeholder or check digit.In the report: GTIN/ISBN fails length or check-digit validation
- A merchant offer has a malformed active priceA purchase price in a captured merchant offer fails the numeric price check.In the report: Offer price value is malformed
- A rating value falls outside its scaleA captured rating lies outside its declared scale or uses a comma decimal.In the report: Rating value outside its declared scale
- A structured-data date or duration is malformedA captured temporal property contains a value that fails the supported ISO 8601 grammar.In the report: Date or duration value is not valid ISO 8601
- Duplicate declarations disagree about the same entityTwo captured declarations of one entity give different comparable values for name, price, rating or availability.In the report: Same entity marked up twice with conflicting values
- Product priceCurrency is not an ISO 4217 codeAn effective price on a qualified Product offer declares a malformed currency or a code absent from the reviewed ISO current and historical lists.In the report: Product priceCurrency does not meet Google's ISO 4217 requirement
- A structured-data datetime omits its timezoneA valid captured datetime has a time component and no timezone designator.In the report: Date value has no timezone designator
- LocalBusiness values need a format reviewOriginal values on an explicitly typed LocalBusiness use too few coordinate decimal places, an unsupported opening-time/day format or an overly long price range.In the report: LocalBusiness values fail format requirements
Rich results
- Expired time-bound structured data remains on an indexable pageCaptured Event, Offer or BroadcastEvent markup declares a lifetime that has ended at the page’s observed response time.In the report: Time-bound markup has expired but the page is still live
- A structured-data image is smallAn image declared by Article or Product markup has measured dimensions whose width multiplied by height is below 50,000 pixels.In the report: A structured-data image is below the review size threshold
- Product markup conflicts with a declared product listThe current URL is explicitly declared a collection with a main product ItemList and also claimed by Product/Offer markup, with at least three list members showing local same-site link and price evidence.In the report: Product markup conflicts with a declared product list
- Review stars describe the site’s own organizationCaptured Organization or LocalBusiness review markup belongs to the explicitly declared site publisher.In the report: Self-serving review stars on the site's own Organization/LocalBusiness
- Structured data absent on a captured duplicate variantA captured canonical pair has identical normalized extracted text, but the variant has no structured data while its canonical target does.In the report: Duplicate page variants missing the canonical's structured data
- Static video player without VideoObject markupCaptured HTML declares a supported video player, but no recognized VideoObject appears in the complete supported markup.In the report: Static video player without VideoObject markup
Visible content
- A marked-up price has no matching static page priceAn explicitly associated product price has no supported corresponding price in the original main content.In the report: Marked-up price has no qualified static content match
- The article headline differs from the static page headlineAn original Article headline shares no normalized tokens with the main H1 or available head title and is absent from the fully scanned main.In the report: Article headline differs from the static page headline
Links and identity
- A structured-data image or video address cannot be fetchedA recorded markup reference returned a confirmed 404/410, has original DNS evidence of NXDOMAIN, or is disallowed for Googlebot by the captured robots.txt for its origin.In the report: Markup references an asset that could not be fetched
- A primary entity refers to a different variant of this pageAn explicit current-page url or mainEntityOfPage differs from the captured HTML canonical after supported normalization.In the report: Entity url/mainEntityOfPage doesn't match the page's canonical URL