How to Fix Schema Required Fields

Valid JSON-LD doesn't guarantee rich results. Each schema type has Google-specific required fields, separate from schema.org's minimum spec. Article needs headline AND image AND datePublished AND author. Product needs name AND image AND offers AND aggregateRating. Miss one required field, lose the rich result placement even if everything else is correct. This guide lists the required-field minimums per common type and the data-layer fixes to populate them.

1. Audit missing fields

2. Article required fields (Google)

{
  "@type": "Article",
  "headline": "Article title (required)",
  "image": [
    {
      "@type": "ImageObject",
      "url": "https://yoursite.com/article.jpg",
      "width": 1200,
      "height": 675
    }
  ],
  "datePublished": "2024-01-15T14:00:00Z",
  "dateModified": "2024-02-03T10:30:00Z",
  "author": {
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://yoursite.com/authors/jane-doe"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Acme Co",
    "logo": {
      "@type": "ImageObject",
      "url": "https://yoursite.com/logo.png",
      "width": 600,
      "height": 60
    }
  }
}

Required for Article rich result

• headline (max 110 chars for AMP)
• image (min 1200px wide, ImageObject preferred)
• datePublished (ISO 8601)
• author (Person or Organization with name)

Required for Top Stories / News rich result

• All Article requirements above
• publisher (Organization with name and logo)
• dateModified for freshness signals
• Use NewsArticle @type for news content

3. Product required fields

{
  "@type": "Product",
  "name": "Product name",
  "image": ["https://yoursite.com/product.jpg"],
  "description": "Product description...",
  "sku": "SKU-12345",
  "brand": {
    "@type": "Brand",
    "name": "Brand name"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://yoursite.com/products/widget",
    "priceCurrency": "USD",
    "price": "29.99",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.5",
    "reviewCount": "234"
  }
}

Required for Product rich result

• name
• image (at least one, recommend multiple aspect ratios)
• offers (Offer or AggregateOffer)
• offers.price and offers.priceCurrency
• offers.availability (use schema.org URLs not just text)

Required for Product Review rich result

• review (Review with author and reviewRating)
• OR aggregateRating (with ratingValue and reviewCount)
• brand (Brand with name)
• name and image of Product

4. Recipe required fields

{
  "@type": "Recipe",
  "name": "Recipe name",
  "image": ["https://yoursite.com/recipe.jpg"],
  "author": { "@type": "Person", "name": "Chef Name" },
  "datePublished": "2024-01-15",
  "description": "Description...",
  "recipeYield": "4 servings",
  "recipeIngredient": [
    "2 cups flour",
    "1 tsp salt",
    "1 cup water"
  ],
  "recipeInstructions": [
    { "@type": "HowToStep", "text": "Mix ingredients" },
    { "@type": "HowToStep", "text": "Bake for 30 minutes" }
  ],
  "prepTime": "PT15M",
  "cookTime": "PT30M",
  "totalTime": "PT45M"
}

Required for Recipe rich result

• name, image, datePublished
• recipeIngredient (array of strings)
• recipeInstructions (HowToStep array preferred)

5. FAQ required fields

{
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Question text?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Answer text..."
      }
    },
    {
      "@type": "Question",
      "name": "Second question?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Second answer..."
      }
    }
  ]
}

Required for FAQ rich result

• mainEntity (array of Questions)
• Each Question needs name (the question text)
• Each Question needs acceptedAnswer with text

6. Event required fields

{
  "@type": "Event",
  "name": "Event name",
  "startDate": "2025-06-15T19:00:00-05:00",
  "endDate": "2025-06-15T22:00:00-05:00",
  "eventStatus": "https://schema.org/EventScheduled",
  "eventAttendanceMode": "https://schema.org/MixedEventAttendanceMode",
  "location": {
    "@type": "Place",
    "name": "Venue name",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "123 Main St",
      "addressLocality": "City",
      "postalCode": "12345",
      "addressCountry": "US"
    }
  },
  "image": ["https://yoursite.com/event.jpg"],
  "description": "Event description",
  "offers": {
    "@type": "Offer",
    "url": "https://yoursite.com/events/buy-ticket",
    "price": "25.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "validFrom": "2024-12-01T00:00:00-05:00"
  },
  "organizer": {
    "@type": "Organization",
    "name": "Organiser name",
    "url": "https://organiser.example"
  }
}

7. Add data fields to CMS where missing

Common missing-field root cause: CMS lacks the data field. Fix by adding:

• Author profiles: WordPress user profiles often lack URL, image, bio — add via custom fields
• Product brand: Shopify products have vendor field; map to schema brand
• SKU / GTIN: required for product rich results; ensure CMS captures
• Recipe yield and times: structured fields, not free-text
• Event location and ticket URL: separate fields, not paragraph descriptions

8. Verify per type