← Back to Blog

Schema Test-Case Generator — 16 valid JSON-LD templates, required fields enforced

Schema Test-Case Generator — 16 valid JSON-LD templates, required fields enforced

Part of the AEO / GEO / AI-search audit tool stack. See the pillar post for the full catalog of sibling audits and where this one fits in the lineup.

Every schema type Google supports has a required-fields list. Miss a required field and you don't just fail rich results — you fail validation entirely, and Google ignores the schema.

The default copy-paste behavior when adding schema is:

  1. Search for "product schema example"
  2. Grab the first result
  3. Edit the values
  4. Ship

This fails constantly because most examples online are partial — a minimal name, description, image, and nothing else. They demonstrate the shape, not the completeness.

The Schema Test-Case Generator emits 16 complete templates where every required and most recommended fields are present, validated, and annotated.

The 16 types

  1. Article — NewsArticle / BlogPosting / Article variants with author, publisher, datePublished, dateModified
  2. Product — name, sku, gtin, brand, offers (price, currency, availability, priceValidUntil), aggregateRating, review, shippingDetails, hasMerchantReturnPolicy
  3. FAQPage — mainEntity array of Question objects with acceptedAnswer
  4. HowTo — step array with images, total time, supply, tool
  5. LocalBusiness — address, geo, openingHoursSpecification, telephone, priceRange
  6. Recipe — cookTime, prepTime, totalTime, recipeYield, recipeIngredient, recipeInstructions, nutrition
  7. Event — startDate, endDate, eventStatus, eventAttendanceMode, location, offers, organizer
  8. Organization — legalName, url, logo, sameAs, contactPoint, founder, foundingDate
  9. BreadcrumbList — itemListElement with position, name, item
  10. VideoObject — thumbnailUrl, uploadDate, duration, contentUrl, embedUrl, interactionStatistic
  11. Review — itemReviewed, author, reviewRating, datePublished, reviewBody
  12. JobPosting — datePosted, validThrough, title, hiringOrganization, jobLocation, employmentType, baseSalary
  13. Course — name, description, provider, hasCourseInstance, offers
  14. SoftwareApplication — applicationCategory, operatingSystem, offers, aggregateRating
  15. Book — author, bookEdition, bookFormat, isbn, numberOfPages
  16. Person — name, jobTitle, worksFor, sameAs, image, alumniOf

For each, the tool emits:

  • The full valid JSON-LD
  • A checklist of which fields are required vs. recommended vs. optional
  • A notes block flagging common mistakes (e.g., datePublished must be ISO-8601 with timezone)
  • A test URL that runs the generated schema through Google's Rich Results Test

Why "complete" matters

Google's Rich Results eligibility is often all-or-nothing per feature. A Product without shippingDetails + hasMerchantReturnPolicy became ineligible for the Product rich result in March 2024. A FAQPage without acceptedAnswer.text is silently invalid. A HowTo without at least 2 HowToStep objects won't render.

Most schema audits flag "missing field" — few hand you the corrected template. This tool starts from valid and asks what you want to fill in.

How to use it

  1. Go to /tools/schema-test-case-generator/
  2. Select the schema type
  3. Fill in the fields (tool shows required in red, recommended in yellow)
  4. Copy the generated JSON-LD
  5. Paste into your page's <head> inside <script type="application/ld+json">
  6. Click "Validate on Google" to open Rich Results Test with your URL

What the tool doesn't do

  • It doesn't write schema for your actual data. You still paste in your product names, prices, etc.
  • It doesn't audit existing schema on a live page. Use Schema Validator or Rich Results Eligibility Audit for that.
  • It doesn't verify eligibility. Rich result eligibility depends on page content + quality signals, not just schema presence.

Related reading

Fact-check notes and sources

This post is informational, not SEO-consulting advice. Mentions of Google, schema.org, and similar products are nominative fair use. No affiliation is implied.

← Back to Blog

Accessibility Options

Text Size
High Contrast
Reduce Motion
Reading Guide
Link Highlighting
Accessibility Statement

J.A. Watte is committed to ensuring digital accessibility for people with disabilities. This site conforms to WCAG 2.1 and 2.2 Level AA guidelines.

Measures Taken

  • Semantic HTML with proper heading hierarchy
  • ARIA labels and roles for interactive components
  • Color contrast ratios meeting WCAG AA (4.5:1)
  • Full keyboard navigation support
  • Skip navigation link
  • Visible focus indicators (3:1 contrast)
  • 44px minimum touch/click targets
  • Dark/light theme with system preference detection
  • Responsive design for all devices
  • Reduced motion support (CSS + toggle)
  • Text size customization (14px–20px)
  • Print stylesheet

Feedback

Contact: jwatte.com/contact

Full Accessibility StatementPrivacy Policy

Last updated: April 2026