Pick a type, fill the form, and copy clean JSON-LD. The output updates live and you can send it straight to the validator.
{}
Copy includes the <script type="application/ld+json"> wrapper. Paste it into your page <head>.
Free schema markup generator: build JSON-LD without writing code
Switch the tool to Generate mode and you get a no-code schema markup generator. Pick a type, fill a short form, and it builds valid JSON-LD live as you type, with the required and recommended properties already in the right shape (nested address, author, offers, ratings, FAQ questions, breadcrumb items, and so on). Copy it with the <script type="application/ld+json"> wrapper and paste it into your page, or send it straight to the validator to confirm a clean pass. The generator currently covers the types most pages need:
- LocalBusiness (plus trade subtypes: Plumber, Electrician, HVACBusiness, RoofingContractor, Dentist, Attorney, Restaurant and more)
- Organization, Person, and Service
- FAQPage with repeatable question/answer rows
- Article / BlogPosting / NewsArticle with author and publisher
- Product with offer price, availability, and aggregate rating
- BreadcrumbList with auto-numbered items, plus Event and Review
Everything is generated in your browser, so nothing you type is uploaded anywhere. Generate, validate, and copy, all on one page.
What this schema validator checks (and what Google's doesn't)
Most people reach for Google's Rich Results Test, and it's useful, but it only evaluates the narrow set of types Google supports for rich results, and it stops at "eligible / not eligible." It won't tell you which recommended properties you're missing, it won't score how complete your markup is, and it definitely won't hand you corrected code. This validator does all three.
Paste your JSON-LD (or point it at a URL) and it parses the markup, identifies each schema type, and checks it against the documented requirements:
- Syntax: valid JSON, a real
@context, and a@typeon every object. - Required properties: the fields Google needs for rich-result eligibility (e.g.
headline+imagefor Article,name+addressfor LocalBusiness). - Recommended properties: the fields that strengthen the markup but won't block eligibility if missing.
- Value formats: dates in ISO 8601, absolute URLs, numeric prices, and other common gotchas.
Then it gives you a completeness score and, when something is missing, the corrected JSON-LD with the gaps filled in as placeholders, so you can copy it straight back into your page and replace the placeholder values.
How this validator compares to Google's tools
There are three tools most people use to check structured data: Google's Rich Results Test, the official Schema.org Validator, and this one. Here is what each actually does.
| Capability | This validator | Google Rich Results Test | Schema.org Validator |
|---|---|---|---|
| Checks required properties | Yes | Yes | Syntax only |
| Flags missing recommended properties | Yes | Partial | No |
| Completeness score (0–100) | Yes | No | No |
| Outputs corrected, copy-ready markup | Yes | No | No |
| Rich-result eligibility view | Per type | Yes | No |
| Validates types beyond Google's rich-result set | Yes | No | Yes |
| Paste code and validate by URL | Both | Both | Both |
| Shareable result link | Yes | No | No |
| Embeddable on your own site | Yes | No | No |
| Pasted markup stays in your browser | Yes | Sent to Google | Sent to server |
| Free, no signup | Yes | Yes | Yes |
The short version: Google's test tells you whether you qualify for a rich result and the Schema.org validator checks syntax against the full vocabulary. Neither tells you what to add or hands you the fixed code. That gap, telling you the fix and giving you the corrected markup, is what this tool was built to close.
Why schema markup matters for SEO and rich results
Schema markup is structured data you add to a page so search engines understand not just the words on it, but what those words mean: this is a product, that is its price, this is a review and its star rating, these are the steps in a recipe. When Google can read that structure confidently, your listing becomes eligible for rich results, the enhanced search appearances that take up more space and pull more clicks:
- Review stars under a product, business, or recipe listing
- FAQ accordions that expand right in the search results
- Breadcrumb trails instead of a raw URL
- Product price and availability, recipe cards, event dates, and job postings
- Sitelinks search box and richer knowledge-panel details for brands
Rich results do not directly raise your ranking position, but they reliably raise click-through rate because your listing is bigger and more useful than a plain blue link next to it. For local businesses, accurate LocalBusiness markup also feeds Google's understanding of your name, address, phone, hours, and service area, which supports map-pack and knowledge-panel visibility.
There is a newer reason it matters too. AI search engines (Google's AI Overviews, ChatGPT, Perplexity) lean on structured data to identify and cite businesses confidently. Clean, complete schema is one of the clearest signals you can give them about what your business is and what it offers. Validating it is step one.
One honest caveat: valid schema makes you eligible for rich results, it does not guarantee them. Google decides when to show an enhancement. But you cannot win a rich result with broken or incomplete markup, so getting a clean pass here is the prerequisite, not the finish line.
How to validate schema markup, step by step
- Copy the contents of your
<script type="application/ld+json">tag, or grab your page URL. - Paste it above (or use the URL tab) and click Validate.
- Read the errors (required, must-fix for rich results) and warnings (recommended, nice-to-have).
- Copy the corrected markup, swap the placeholders for your real data, and redeploy.
- Re-validate to confirm a clean pass, then submit the page in Search Console.
The most common schema markup errors (and how to fix them)
- Missing
@typeor@context. The two fields every object needs. Without them search engines cannot classify the markup at all. Fix: add"@context": "https://schema.org"and a@type. - Missing required properties. For example, an Article without
image, or a Product Offer withoutpriceandpriceCurrency. Fix: add the required fields for your type (see the reference below). - Wrong date format. Dates must be ISO 8601 (
2026-05-28), not "May 28, 2026". Fix: use the YYYY-MM-DD format. - Relative URLs. Properties like
image,logo, andurlshould be absolute (https://...), not/img/photo.jpg. - FAQ questions without answers. Every
Questionneeds anameand anacceptedAnswercontaining text. - Trailing commas and smart quotes. The classic JSON syntax breakers that creep in when you copy markup out of a document or CMS editor.
Schema type requirements: required and recommended properties
These are the properties Google looks for on the most common rich-result types. Required properties are needed for eligibility; recommended properties strengthen the result. This validator checks your markup against this exact reference.
| Schema type | Required | Recommended |
|---|---|---|
| Article / BlogPosting | headline, image | datePublished, dateModified, author, publisher |
| Product | name | image, offers, review, aggregateRating, brand, sku |
| Offer | price, priceCurrency | availability, url, priceValidUntil |
| Review | author, reviewRating | itemReviewed, datePublished |
| FAQPage | mainEntity (each Question needs name + acceptedAnswer) | – |
| HowTo | name, step | image, totalTime, supply, tool |
| LocalBusiness (and trade subtypes) | name, address | telephone, openingHours, geo, priceRange, image, url, aggregateRating |
| Organization | name, url | logo, sameAs, contactPoint |
| Event | name, startDate, location | endDate, offers, performer, image |
| Recipe | name, image, recipeIngredient, recipeInstructions | author, nutrition, aggregateRating, prepTime, cookTime |
| VideoObject | name, thumbnailUrl, uploadDate | description, duration, contentUrl |
| JobPosting | title, description, datePosted, hiringOrganization, jobLocation | baseSalary, employmentType, validThrough |
| BreadcrumbList | itemListElement (each ListItem needs position + name) | item |
Related tools
- AI Overview Optimizer: score a page against the 14 factors that decide AI-search visibility.
- AI Visibility Scanner: 11-signal self-audit for AI search.
- Google Business Profile optimization guide: where LocalBusiness schema fits the bigger local-SEO picture.
Frequently asked questions
Does this tool generate schema markup too?
Yes. Switch to Generate mode, pick a type (LocalBusiness, Organization, FAQPage, Article, Product, Service, BreadcrumbList, Person, Event, or Review), and fill a short form. It builds clean JSON-LD live as you type, you can copy it with the script-tag wrapper, and send it straight to the validator to confirm it passes. It is a schema markup generator and validator in one.
What is a schema markup validator?
It checks your structured data against the schema.org vocabulary and Google's rich-result requirements, flagging syntax errors, missing required properties, and missing recommended properties so search engines can read your markup.
How is this different from Google's Rich Results Test?
Google's tool only checks the types it supports for rich results and does not give you corrected markup. This one checks required and recommended properties, scores completeness, and generates corrected copy-ready JSON-LD with the missing fields filled in.
What happened to Google's Structured Data Testing Tool?
Google retired the original Structured Data Testing Tool and replaced it with the Rich Results Test (for Google-supported types) and handed the general validator to schema.org. People still search for the old tool because they want full-vocabulary validation with property-level feedback, which is exactly what this validator provides.
What is JSON-LD?
JSON-LD is the format Google recommends for structured data. It is a block of JSON inside a <script type="application/ld+json"> tag in your page's HTML, kept separate from the visible content. It is easier to add and maintain than Microdata or RDFa, which mix markup into your HTML tags.
Does schema markup help SEO and rankings?
Schema markup is not a direct ranking factor, but it makes you eligible for rich results, which reliably lift click-through rate, and it helps search engines and AI assistants understand and cite your content. Better understanding plus higher CTR is why it is worth doing.
Will valid schema guarantee a rich result?
No. Valid markup makes you eligible. Google decides when to actually show a rich result based on quality and relevance. But broken or incomplete markup makes you ineligible, so a clean pass here is the prerequisite.
Does my data get uploaded anywhere?
No. Pasted JSON-LD is validated entirely in your browser. URL validation fetches the page through a public proxy so your browser can read it, but the analysis stays local.
Which schema types does it validate?
Built-in rich-result requirements for Article, Product, Offer, Review, AggregateRating, FAQPage, HowTo, LocalBusiness and its trade subtypes, Organization, Person, Event, Recipe, VideoObject, BreadcrumbList, JobPosting, Service, and more. Any other schema.org type still gets full JSON syntax and structure validation.