Skip to main content
SerpGem
Schema & structured data · 5 tools

Schema & structured data tools

Structured data is how Google moves your page from 'blue link' to rich result. These 5 tools generate and validate the schema.org types Google actually supports (per Google's 2024 structured-data docs): Article, Product, FAQ, Breadcrumb, plus a general JSON-LD validator. Output is Rich Results Test-ready.

About these tools

Schema & structured data questions

Which schema types should I prioritize?
Per Google's documented rich-result types: (1) Article for blogs/news; (2) Product for e-commerce (required for Shopping appearance); (3) FAQPage for question-heavy content; (4) Breadcrumb for site structure; (5) Organization for homepage; (6) VideoObject for video pages. Beyond these 6, returns diminish — recipe, event, course are niche. Don't add schema you can't factually support.
JSON-LD vs Microdata vs RDFa — which should I use?
Google publicly recommends JSON-LD (schema.org docs, 2024). Reasons: (1) kept separate from visible content, so edits don't risk breaking markup; (2) easier to generate programmatically; (3) all Google's examples use JSON-LD; (4) maintained as a single <script> block, so caching and CDNs handle it trivially. Microdata is legacy; only use if your CMS forces it.
Does FAQ schema still work after the 2023 update?
Partially. In August 2023 Google restricted FAQ rich results to 'authoritative government and health websites.' For commercial sites, FAQ schema still: (1) appears in some AI Overviews; (2) helps Google understand page intent; (3) can show in Bing's FAQ rich results. Worth keeping for these reasons, but don't expect the old snippet real estate in Google SERPs.
How do I validate my schema markup?
Three tools: (1) Google Rich Results Test (search.google.com/test/rich-results) — official, tests if Google can parse + display rich results; (2) Schema.org Validator (validator.schema.org) — tests strict compliance with the spec; (3) our JSON-LD Validator — in-browser syntax check for quick iteration. Use (3) while authoring, (1) before shipping, (2) when debugging edge cases.

More in Technical SEO

Related sub-groups