Schema.org Validator
Paste JSON-LD, or a full HTML page containing <script type="application/ld+json">, and check it against the properties Google requires for rich results. Everything runs locally in your browser.
Checks run automatically. 1 JSON-LD block found.
Result
Passed
Detected nodes
1
BlogPosting
Errors
0
Warnings
0
Rich-result eligibility
BlogPosting
Eligible
Eligibility reflects the documented required properties only. Google can still decline to show a rich result.
Issues
No errors or warnings found.
What is checked
- JSON syntax,
@contextand a usable@type. - Article: headline, image, datePublished, author, publisher and date order.
- Product: name, offers, numeric price, currency, availability, ratings and IDs.
- FAQPage: questions, accepted answers and duplicate questions.
- BreadcrumbList positions, VideoObject fields, HowTo steps and Event dates.
- Placeholder text such as
example.comor “Your Company”.
Using the result
- Fix errors first: a missing headline or price usually blocks rich results.
- Review warnings; most are recommended properties that improve display.
- Deploy, then test the live URL in Google’s Rich Results Test.
- Only mark up content that is visible to users on the page.
Building markup from scratch? Try the Schema Generator or validate your sitemap.
Frequently asked questions
Is my markup uploaded?
No. Validation runs in this browser tab; nothing leaves your device.
Which type should a blog post use?
Use BlogPosting (a subtype of Article) with headline, image, datePublished, author and publisher. Add FAQPage separately when the page shows real Q&A.
Why does a valid page still not show stars or FAQs?
Rich results are not guaranteed. Google also restricts some types (for example FAQ rich results) to authoritative sites, so treat eligibility as a prerequisite, not a promise.
Related tools
More from SEO & Marketing
Build custom software with us
From internal tools to full platforms — we deliver end to end.