Everything here is generated and validated in your browser. We don't upload, log, or store your schema content.
Can support Google's Knowledge Panel and logo display for some sites, subject to Google's current eligibility criteria.
Generated JSON-LD
65 bytes{
"@context": "https://schema.org",
"@type": "Organization"
}Syntax valid — basic schema checks passed
- name is missing.
This checks JSON syntax and basic schema.org structure only — it does not evaluate or guarantee Google Search rich-result eligibility, which depends on Google's own current, separate requirements.
What Is JSON-LD?
JSON-LD (JSON for Linking Data) is a way of embedding structured data in a webpage as a self-contained <script type="application/ld+json"> block, separate from the page's visible HTML. It's the format Google's own documentation recommends for structured data.
What Is Schema.org?
Schema.org is a shared vocabulary of types and properties — Article, Product, Event, Organization, and many more — maintained jointly by Google, Microsoft, Yahoo and Yandex, so that structured data means the same thing regardless of which search engine or service reads it.
What Is Structured Data?
Structured data is content described in a standardized, machine-readable format rather than left for a program to infer from plain text — for example, explicitly labeling a date as a datePublished value instead of leaving it as ambiguous text on the page.
Why Use JSON-LD?
It lets a page describe its own content precisely, independent of how that content is visually laid out. Some Schema.org types are also documented as eligible for specific Google Search rich-result treatments — though eligibility for any given type is decided by Google, changes over time, and is never guaranteed by adding markup alone.
JSON-LD vs Microdata
Both express the same Schema.org vocabulary. JSON-LD is one self-contained script block, independent of the surrounding HTML; microdata is embedded directly as attributes on the visible HTML elements it describes, so changes to the page layout can more easily break it. Google supports both formats.
Schema.org vs Google Rich Results
These are two related but separate things. Valid Schema.org structured data simply follows the Schema.org vocabulary correctly. A Google rich result is a specific, enhanced way Google Search may choose to display a result for certain types — FAQPage, for instance, is valid Schema.org markup, but Google discontinued the FAQ rich result entirely in May 2026, so that markup no longer produces a distinct rich result there even though it remains valid data. Always check Google's own current documentation for which types are currently eligible for which features.
Common Schema Markup Mistakes
- Fabricating ratings, review counts, or reviews that don't genuinely exist.
- Marking up content that isn't actually visible to users on the page.
- Using NewsArticle for content that isn't genuinely a news article.
- Inventing exact geographic coordinates instead of leaving them blank.
- Assuming a schema type still triggers a rich result Google has since discontinued.
- Leaving @context or @type out of hand-written JSON-LD.
How to Add JSON-LD to a Website
Copy the full script tag this tool generates and paste it into your page's HTML, most commonly in the <head>, though Google also accepts it in the <body>. On a CMS, look for a custom code, header scripts, or structured data field rather than editing template files directly.
How to Validate Structured Data
This tool checks JSON syntax and basic Schema.org structure as you build or paste markup. For a live, already-published page, Google's own Rich Results Test and Search Console are the authoritative way to confirm actual rich-result eligibility, which depends on requirements beyond structural validity.
When Not to Use a Schema Type
Only mark up a type that genuinely matches your content — don't use NewsArticle for non-news content, don't use Product markup for something you don't sell, and don't add LocalBusiness markup with an address or coordinates that aren't your business's real location. Structured data is meant to describe what's already true of the page, not to manufacture an impression of it.
Frequently Asked Questions
Explore more
Check a live page's existing tags with our Meta Tag Checker, preview how it could look on social platforms with Open Graph & Social Share Preview, or in a Google result with the SERP Snippet Preview. Generate a sitemap and robots.txt with our XML Sitemap Generator and Robots.txt Generator & Tester, check your links and status codes with the Broken Link Checker and HTTP Status Checker, or analyze your content with the Keyword Density Checker and Word Counter. Run a full Buzzing Bee website & SEO audit, explore the rest of our free marketing tools, or see our SEO & organic growth services.
Related tools & resources
Related tools
- On-Page SEO CheckerAnalyze key on-page SEO elements of a webpage and identify optimization opportunities.
- SEO Title & Meta Description GeneratorGenerate editable SEO title and meta description ideas based on your page topic and search intent.
- Open Graph & Social Share PreviewPreview Open Graph and social sharing metadata before publishing a page.
Learn more
- SEO GuidesTechnical SEO, on-page fundamentals, and the checklist we run against every client site before it goes live.
- SEO & Organic GrowthMost SEO work stalls after the first few technical fixes because there's no system connecting content, author…
Related articles
- How to Do Keyword Research for a Service BusinessKeyword research for a service business is not about finding the biggest search volumes. The keyword that pay…
- The 2026 Technical SEO Checklist for Growing BrandsCore Web Vitals, structured data, and crawl budget: the technical fundamentals still separate the sites that…
