Schema Markup Tool
Generate and validate JSON-LD structured data for your web pages. Boost your SEO with rich snippets.
Article Fields
Generated JSON-LD
{
"@context": "https://schema.org",
"@type": "Article",
"author": {
"@type": "Person"
}
}Paste this inside a <script type="application/ld+json"> tag in your page's <head>.
💡 Schema Markup Tips
- Placement: Add the
<script>tag inside<head>or at the end of<body>. - Testing:Use Google's Rich Results Test to verify your schema after deployment.
- Multiple schemas: You can include multiple
<script>blocks on the same page.
How to create schema markup
Pick a type, fill in the form, and paste the JSON-LD into your page. Then check it.
- 01
Pick the type that matches the page
There are eight: Article, Product, FAQ, Breadcrumb, Organization, Local Business, WebSite and Person. Choose the one that describes what the page is about, not what you hope Google will show.
- 02
Fill in the fields, starting with the required ones
Empty optional fields are left out of the output rather than written as blank values. Use full URLs, including https://, for images, logos and links.
- 03
Copy the JSON-LD into the page
Wrap it in <script type="application/ld+json"> and place it in the page's head or body. Most CMSs have a custom code or header scripts field for this.
- 04
Paste existing markup into the validator
The validator checks that the JSON parses, that @context and @type are present, and which required and recommended fields are missing for the detected type.
The eight schema types and what they can earn
Structured data tells search engines what a page is, in a format they don't have to guess at. Some types can unlock a visual rich result; others only help Google understand the page. The required fields below are what this tool asks for. Google's own requirements are sometimes stricter.
| Type | Use it on | Required here | What it can do in Google |
|---|---|---|---|
| Article | Blog posts and news | Headline, author, publish date | Can show in Top stories and article results |
| Product | Single product pages | Name | Price and stock in results; star ratings need review fields this tool doesn't add |
| FAQ | A page of questions and answers | At least one Q&A pair | Rich result limited to authoritative government and health sites since 2023 |
| Breadcrumb | Any page in a hierarchy | At least one item | Breadcrumb trail instead of the raw URL |
| Organization | Home or About page | Name, website URL | Logo and details in the knowledge panel |
| Local Business | Shops, clinics, restaurants | Name | Supports address and price range for local results |
| WebSite | Home page only | Name, URL | Helps Google show your site name |
| Person | Author or profile pages | Name | Ties articles to an author's profile |
Mistakes that get markup ignored
The most common is markup that doesn't match the visible page. If your Product schema says ₹1,499 and the page says ₹1,799, or your FAQ schema has answers that aren't on the page, Google can ignore it or flag it as spammy structured data in Search Console. Write the markup from what a visitor can actually see.
Next is putting site-wide types on every page. Organization and WebSite belong on the home page. Article, Product and Breadcrumb belong on the individual pages they describe. And keep dates in ISO format (2026-10-31). The date pickers here already produce that, but hand-edited markup often doesn't.
What schema markup is used for
Getting a product's price into results
Fill in price, currency and availability on each product page so search engines can show them alongside your listing.
Replacing a long URL with a breadcrumb
A Home › Shoes › Running trail tells searchers where a page sits before they click.
Telling Google who's behind the site
Organization markup on the home page, with logo and social profiles, gives search engines a single, consistent description of your business.
Checking markup a plugin already adds
Paste the JSON-LD from your page source into the validator to see what an SEO plugin is outputting and what's missing.
What the validator here doesn't cover
- It checks one top-level object. Markup that uses @graph or an array of several types isn't broken down item by item.
- Required and recommended fields come from this tool's own list, not Google's live rules, which change. Run important pages through Google's Rich Results Test before relying on a rich result.
- It doesn't check values. A price written as "twenty" or an image URL that returns 404 still passes.
- Event and Recipe are recognised for required fields in the validator, but there's no form to generate them.