Invalid schema: fix missing required properties

Your rich-result schema is missing required properties, so it won't earn rich results. A free schema markup validator that flags exactly what's missing.

786

audited sites affected

What it means

The structured data on this page is missing one or more properties that the declared schema type requires. For example, a Product markup without name, image, or offers.price will trigger this warning.

Why it matters

Missing required properties prevent the page from earning a rich result, even though the markup itself is found. It also means search engines and AI agents have less structured context to work with, which can reduce citation rates in AI Overviews.

How to fix it

Run the page through the Rich Results Test to see exactly which properties are missing.
Match the schema type to the content — use Product instead of LocalBusiness, for instance.
Add the required properties in JSON-LD inside the page's <head> or inline in the HTML.
Verify the fix appears in the Rich Result Status report within a few days after re-crawl.

Example

Before — JSON-LD

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Trail Shoe"
}

After — JSON-LD

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Trail Shoe",
  "image": "https://example.com/shoe.jpg",
  "offers": {
    "@type": "Offer",
    "price": "129.00",
    "priceCurrency": "USD"
  }
}

Product needs an image and offers with price/currency to earn a rich result. The 'before' would validate as JSON but not as an eligible Product.

When it's not a problem

If the schema type is correct and the properties are present but optional, the warning is harmless. Leftover or deprecated markup (FAQ, HowTo) also causes no ranking harm and can be left alone.

How Crawlinx detects it

We parse each JSON-LD block and check the required properties for its @type against Google's rich-result requirements. Missing required fields are listed by type in the detail (e.g. "Product missing: image, offers").

How common is it?

786 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.

FAQ

Why is my valid JSON-LD flagged as invalid?: It's valid JSON but missing properties Google requires for that type's rich result. Syntactically correct schema still fails eligibility if a required field like Product.offers is absent.

Related guides

Schema Markup Guide 2026: Types, JSON-LD & Testing

Breakdowns

CMS

View breakdown →

Category

View breakdown →

Catalog Article schema missing recommended properties (Top Stories / image carousel) BreadcrumbList present but structurally incomplete Deep page has no BreadcrumbList structured data Comma decimal in schema ratingValue/price (invalid number) Deprecated data-vocabulary.org markup (no rich-result eligibility) Dataset schema incomplete (name/description; Dataset Search only) Deprecated schema type with no Google rich result Event schema missing required properties (name/startDate/location) FAQPage structured data (rich result removed May 2026) Schema describes content not visible on the page Category CMS JobPosting schema missing required properties LocalBusiness schema missing required properties (name/address) JSON-LD block missing @context or @type No structured data detected Product schema missing required or recommended properties QAPage schema incomplete (mainEntity Question with an answer) Recipe schema missing required properties (name/image) Review schema missing required properties (author/itemReviewed/reviewRating) SoftwareApplication schema incomplete (name/offers-or-rating/recommended) Structured-data date has already passed (stale event/job/offer) VideoObject schema missing required properties (name/thumbnailUrl/uploadDate)

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →