What does this Schema Markup Tester check?

JSON syntax validity, presence of @context (must be schema.org), presence of @type, and required properties for the most-used schema types: Organization, Article, BlogPosting, Product, FAQPage, BreadcrumbList, HowTo, SoftwareApplication, WebSite, Event, Recipe, LocalBusiness, Person, and Review.

Is this the same as Google's Rich Results Test?

Complementary, not the same. Google's test fetches a URL, runs Googlebot on it, and tells you which rich-result types are eligible. This tool runs entirely in your browser on raw JSON-LD — useful when you are drafting markup before deploying it.

Does it support JSON-LD with multiple objects?

Yes. Paste either a single object {} or an @graph array — the tester walks every node and reports per-node issues.

Why does my markup pass here but fail in Google's test?

Google has additional rules beyond schema.org — for example, Article rich results require an `image` of at least 1200×675px in specific aspect ratios, FAQPage rich results require unique questions, and Product rich results require either offers or aggregateRating to surface stars. This tester checks structural validity; Google adds editorial/eligibility checks on top.

Is the JSON-LD I paste sent to your server?

No. All validation runs client-side in JavaScript. Your markup never leaves your browser, which matters for unreleased pages or anything containing customer data.

Free Tool

Schema Markup Tester

Paste any JSON-LD block. We'll tell you what's broken — required fields, syntax errors, common rich-result blockers. Runs entirely in your browser; nothing is uploaded.

Your JSON-LD

Results

Click Validate Schema to see results.

What this tester checks

• JSON syntax validity
• @context resolves to schema.org at the top level
• @type is present on every node
• Required properties for: Organization, Article, Product, FAQPage, HowTo, BreadcrumbList, SoftwareApplication, Event, Recipe, LocalBusiness, Person, Review, WebSite, BlogPosting, NewsArticle
• High-value optional properties (Article without image, Product without offers, etc.)
• FAQPage duplicate-question detection (Google blocks these from rich results)
• Walks nested nodes recursively (e.g. mainEntity, itemListElement, author)

For final pre-launch validation, complement this with Google's Rich Results Test — it adds Google-specific eligibility rules on top of schema.org structural checks.