Fix Schema Missing Required Property: Add Headline, Image, Offers

What's happening

Each Schema.org type that Google supports for rich results has a documented set of required properties. Article requires headline, image, datePublished, and author. Product requires name, image, and offers (with price, priceCurrency, availability). FAQPage requires mainEntity (an array of Question objects with name and acceptedAnswer.text). Recipe requires name, image, recipeIngredient, recipeInstructions.

Missing a required property does not make the JSON invalid — the page still parses — but it disqualifies the page from the rich result. Search Console reports this under Enhancements > [Type] as 'Missing field: [property]'. The page may still rank, but the visual SERP enhancement is gone.

The trickier issue is recommended properties. Google distinguishes required (must have for rich result eligibility) from recommended (improves quality but not strictly required). The Rich Results Test labels missing recommended properties as 'Warnings' versus required ones as 'Errors'. Both should be addressed for production schema.

Why it matters

Rich result eligibility lost. The most common consequence: Article without datePublished gets no Top Stories carousel placement; Product without offers gets no price/availability in the SERP; FAQPage without proper Question/acceptedAnswer pairs gets no FAQ accordion.

CTR drop on the affected URLs. Once the rich result disappears, listings revert to plain title-and-snippet — typically a 20-40% CTR drop on competitive head terms.

Search Console error volume. Enhancements > [Type] reports tens or hundreds of error rows, making it hard to triage real schema issues from systemic missing-property problems.

Common causes

• Author forgot to populate the date field on a content page.
• Programmatic generator omitted the offers property on out-of-stock products.
• Article author field was left empty because the CMS did not enforce it.
• FAQPage schema lists Question objects without the required acceptedAnswer property.
• Recipe missing recipeIngredient because ingredient list is rendered from a separate API.
• Image property points to a relative URL or a non-publicly-accessible URL.

Detect this on your site

Run a quick scan with the Schema Validator. The tool surfaces this exact issue with the records and context needed to apply the fix below.

How to fix it

1. 1

   Identify the affected schema types

   Open Search Console > Enhancements. Each detected type (Articles, Products, FAQs, Breadcrumbs, etc.) has its own report with valid/warning/error counts. Click into each error to see the specific missing property and the affected URL examples.

2. 2

   Look up Google's required properties for the type

   developers.google.com/search/docs/appearance/structured-data lists every supported type with required vs. recommended properties. Bookmark the page for the types you ship and treat the required list as a build-time check.

3. 3

   Add the missing properties to your generator

   If headline is missing on Article, source it from the page. If author is missing, default to the brand or page-owner. If image is missing, fall back to og:image. The fallback hierarchy keeps the schema valid even when authors skip fields.

4. 4

   Add data-type validation in the build

   Numbers must be numbers, dates must be ISO 8601, URLs must be absolute. Add a runtime check in the schema generator that throws if a required property is missing or has the wrong type. Catch errors in CI, not in production.

5. 5

   Use the Rich Results Test on representative URLs

   After deploying, run the Rich Results Test on 5-10 URLs from each schema type. Confirm the page is eligible for the rich result (the tool says 'Page is eligible for rich results') with no errors and no warnings.

6. 6

   Watch Search Console for resolution

   After Google recrawls (1-2 weeks), the Enhancements > [Type] error count should drop to zero. Click 'Validate fix' in Search Console after deploying to ask Google to re-evaluate the affected URLs sooner.

Example

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does SPF take to propagate?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "DNS propagation usually completes within 1-4 hours but can take up to 48 hours depending on the recursive resolver's TTL."
      }
    },
    {
      "@type": "Question",
      "name": "Is DMARC mandatory in 2026?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes for bulk senders to Gmail and Yahoo since February 2024 — both require DMARC alignment for senders over 5,000 messages per day."
      }
    }
  ]
}

FAQPage schema with all required Question/acceptedAnswer fields

Related fixes