Free JSON-LD generatorChecked against Google 19 October 2026
Schema markup generator, with Scout as your guide
Build valid JSON-LD for 13 schema.org types, see a working sample of each, and get a schema plan for your kind of business. Every type shows what Google really does with it today, so you mark up what matters and skip what no longer pays.
Hi, I am Scout. Tell me what kind of site you run and I will show you which schema belongs on each page.
Step 1
Which schema does my kind of site need?
Pick the closest match. Scout lists the schema types that belong on each kind of page, with the ones that earn a Google rich result first. Press any type to open it in the builder.
Google rich resultLimited Google useDescribes the page only
Schema plan: SaaS and software
Buyers compare tools on features, price and reviews. Make the product, the company and the people behind it unambiguous.
Recommended schema types by page: SaaS and software
Page
Schema to add
Homepage
Product or pricing page
Blog posts
Founder or author pages
Scout's tip: SoftwareApplication needs a real rating to qualify for the Google result. If you have no public reviews yet, ship the markup without one and add it later.
Shopping results and AI shopping assistants compare price, stock and identifiers. Product data has to be complete and match the page.
Recommended schema types by page: Online store
Page
Schema to add
Homepage
Product pages
Category pages
Buying guides
Scout's tip: Add GTIN or SKU to every product and keep price and availability in sync with the page. A mismatch is the most common reason product markup is ignored.
Event results need a date, a place and a status. Keep one block per date and update it when plans change.
Recommended schema types by page: Events and venues
Page
Schema to add
Venue page
Each event page
Organiser page
Scout's tip: Google only shows Event results for in-person events with a full venue address. Mark cancellations with eventStatus instead of deleting the page.
Schema plan: Courses and training
Learners compare who teaches, what it costs and when it runs. Google retired its Course info feature in 2025, so lean on entity, Event and Article markup.
Recommended schema types by page: Courses and training
Page
Schema to add
Homepage
Live workshops and cohorts
Instructor pages
Lessons and guides
Scout's tip: In-person or dated sessions can use Event. Name instructors with Person markup and link them from the course pages.
Schema plan: Food blog or recipe site
Recipe is one of the richest results Google still shows. Complete times, yield and ingredients make the difference.
Recommended schema types by page: Food blog or recipe site
Page
Schema to add
Homepage
Recipe pages
Author page
Scout's tip: Recipe requires a name and an image. Add prepTime, cookTime and recipeIngredient so the card is complete.
Choose a type, press Load sample to see a complete working example, then replace the values with what your page shows. Fields marked Required are what Google needs for its rich result; Recommended fields make the markup complete.
Entity
Content
Commerce
Navigation
Pick a schema type above and I will tell you what it is for and what Google does with it.
Your JSON-LD
Install: paste the whole snippet, script tags included, into the <head> of the page it describes, or into your CMS's structured data field. Then test it in Google's Rich Results Test and the Schema Markup Validator.
Schema markup examples for every type
Each example below is generated by the same code as the builder, so what you see is exactly what the tool produces. The businesses, people and URLs are invented; replace them with your own facts.
An author, founder, doctor, lawyer or expert. Use it on author and profile pages, and reference it from every article that person writes.
View the Person sample
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Jane Tan",
"jobTitle": "Head of Research",
"url": "https://example.com/team/jane-tan",
"image": "https://example.com/img/jane-tan.jpg",
"description": "Jane leads research at Example Media and writes about technical SEO and structured data.",
"worksFor": {
"@type": "Organization",
"name": "Example Media"
},
"knowsAbout": [
"Technical SEO",
"Structured data",
"AI search"
],
"sameAs": [
"https://www.linkedin.com/in/example-jane"
]
}
Article
Google rich result
Blog posts, news, guides and research. Names the author, publisher and dates so any reader, human or machine, knows who wrote it and when.
View the Article sample
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Allow AI Search Bots and Block Training Bots",
"url": "https://example.com/blog/ai-bots",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/ai-bots"
},
"image": "https://example.com/img/ai-bots.png",
"author": {
"@type": "Person",
"name": "Jane Tan",
"url": "https://example.com/team/jane-tan"
},
"publisher": {
"@type": "Organization",
"name": "Example Media",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
}
},
"datePublished": "2026-09-01",
"dateModified": "2026-09-27",
"description": "A two-group robots.txt that keeps AI search citations and opts out of model training."
}
FAQPage
No Google rich result
A page whose main content is a list of questions with answers written by the site. Only mark up questions and answers that are visible on the page.
View the FAQPage sample
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Can I block AI training but allow AI search?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Disallow GPTBot and ClaudeBot, and allow OAI-SearchBot, Claude-SearchBot and PerplexityBot, in robots.txt."
}
},
{
"@type": "Question",
"name": "Does blocking GPTBot affect Google rankings?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. Googlebot follows its own robots.txt group, not the groups written for other operators."
}
}
]
}
HowTo
No Google rich result
Step-by-step instructions. The steps in the markup must match the numbered steps a visitor reads on the page.
View the HowTo sample
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to check if AI crawlers can access your site",
"description": "Test robots.txt, the CDN and the page itself for each AI bot.",
"totalTime": "PT10M",
"step": [
{
"@type": "HowToStep",
"position": 1,
"name": "Scan robots.txt",
"text": "Run an AI crawler check on your domain."
},
{
"@type": "HowToStep",
"position": 2,
"name": "Fetch as each bot",
"text": "Use the AI crawler diagnostic to catch CDN and firewall blocks."
},
{
"@type": "HowToStep",
"position": 3,
"name": "Fix and retest",
"text": "Change the layer that blocks, then scan again."
}
]
}
Which schema types still earn a Google rich result?
Google has narrowed its structured data features several times. HowTo rich results went in September 2023, the sitelinks search box in November 2024, a group of niche features (Course info among them) in 2025, and FAQ rich results on 7 May 2026. Breadcrumbs now show on desktop only. Markup for a retired feature is not an error and does no harm; it simply no longer changes how Google displays the page.
Google status of each schema type, checked 19 October 2026
Type
Google status
What Google uses and requires
Organization
Used by Google
Helps Google understand your organisation and can feed the logo and details shown about it. There are no required properties; add the ones that apply.
LocalBusiness
Google rich result
Business details in Search and Maps. Required: name and address. Recommended: telephone, url, openingHours, geo, priceRange, image.
Person
No standalone rich result
Google reads Person as the author inside Article, and inside ProfilePage on profile pages. On its own it shows nothing extra.
Article
Google rich result
Better title, image and date display. No required properties. Recommended: author (name and url), datePublished, dateModified, headline, image.
FAQPage
No Google rich result
Google stopped showing FAQ rich results on 7 May 2026 and removed the documentation in June 2026. The markup stays valid schema.org.
HowTo
No Google rich result
Google deprecated HowTo rich results in September 2023. The markup stays valid schema.org.
Recipe
Google rich result
Recipe cards and carousels. Required: name and image. Recommended: author, datePublished, description, prepTime, cookTime, totalTime, recipeYield, recipeIngredient, recipeInstructions.
Product
Google rich result
Product snippets (price, stock, ratings). Required: name, plus at least one of offers, review or aggregateRating. Merchant listings need offers with price.
SoftwareApplication
Google rich result
Software app rich results. Required: name, offers.price, and aggregateRating or review. Recommended: applicationCategory, operatingSystem.
Service
No Google rich result
Valid schema.org that describes an offering. Google has no Service feature, so it never shows as a rich result.
Event
Google rich result
Event listings in Search. Required: name, startDate, location with address. Recommended: endDate, eventStatus, image, description, offers, organizer, performer.
WebSite
Site name only
Used for the site name shown in results. The sitelinks search box (SearchAction) was removed on 21 November 2024.
BreadcrumbList
Google rich result (desktop)
Breadcrumb trail in results. Required: itemListElement with position, name and item (item may be left off the last crumb). Shown on desktop only since January 2025.
Status checked against Google Search Central on . Google changes these features without much notice; the sources are listed at the end of this page.
Does schema markup help with AI search?
Short answer: it helps machines understand a page, but it is not a switch for AI citations. Google's own guide to its generative AI features says so directly: "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add." The same guide still recommends structured data because it makes pages eligible for rich results, and it lists "overfocusing on structured data" among the things not to worry about.
Other AI answer engines (ChatGPT search, Perplexity, Claude, Microsoft Copilot) have not published how, or whether, they weigh JSON-LD. What they all need first is to reach and read the page. That is why we treat schema as a supporting signal: worth doing well, never a substitute for access and good content.
What good schema does
States facts without ambiguity: who publishes the page, who wrote it, when, what it sells and for how much.
Joins your brand into one entity through a single Organization and consistent sameAs profiles.
Makes pages eligible for the Google features that remain: product, recipe, event, local business, article and breadcrumb results.
Survive mismatches. Markup that disagrees with the visible page breaks Google's structured data policies and can lead to a manual action.
To see how schema fits with crawler access, rendering and content on one specific page, run the GEO audit: it parses the page's JSON-LD and scores it next to everything else answer engines need.
How we built and checked this tool
Written by Scout Agent, reviewed by the AI Crawler Check editorial team. Last reviewed .
Required and recommended flags come from Google. For every type with a Google feature, we read the current Search Central page and copied its required and recommended properties into the builder. Types without a Google feature are labelled that way instead of being promised a result.
Every sample is valid. The samples are built by the same code as the tool, and our release checks generate each one in a real browser and parse it before the site ships.
No invented signals. We do not claim that any schema type is a ranking or citation factor for AI search, because no AI engine documents one. Where we quote third-party research, we say it shows a correlation, not a cause.
Industry stacks are editorial advice. They come from the types each kind of business can honestly describe and from the Google features available for them. Use the type that matches your page, not the one with the richest result.
Your data stays in your browser. The builder runs entirely on this page; nothing you type is sent to our servers.
Primary sources
We link each website once per page, so some entries below show the address instead of a link.
Google Search Central: General structured data guidelinesMark up only content visible on the page; the spam policies for structured data.developers.google.com/search/docs/appearance/structured-data/sd-policies
Google Search Central: Search galleryThe structured data features Google supports today.developers.google.com/search/docs/appearance/structured-data/search-gallery
Google Search Central blog: Simplifying the search results pageThe features Google retired in 2025, including Course info.developers.google.com/search/blog/2025/06/simplifying-search-results
Google Rich Results TestTests a page or a snippet for Google features.search.google.com/test/rich-results
Schema Markup ValidatorValidates any schema.org markup, including types with no Google feature.validator.schema.org/
Spotted a change in Google's documentation or a mistake on this page? Tell us and we will correct it.
Before you publish: a schema checklist
Whether the JSON-LD comes from this AI schema generator, a plugin or your own hand, the same six checks decide whether it helps or hurts.
Mark up only what is visible. Every value in the JSON-LD should appear on the page. Hidden claims break Google's structured data policies.
One entity, one description. Define your Organization once, give it an @id, and reference that id from every page, so systems can join the dots.
Keep dates honest. Update dateModified only when the content really changes.
Check the raw HTML. View the page source after publishing: the snippet should be in the HTML, not injected later by JavaScript.
Validate every change with Google's Rich Results Test and fix errors before they ship.
Prefer fewer, accurate types. A correct Organization and Article beat ten half-filled types.
Structured data is worth 6 of the 15 Technical Readiness points in the AI Visibility Score, next to a sitemap (6) and HTTPS (3). It helps systems understand pages they can already reach; it cannot help a page crawlers are blocked from. Our guides to schema markup for AI and schema types that help AI search go deeper.
Schema markup questions, answered
What is JSON-LD schema markup?
JSON-LD is a block of structured data, written in the schema.org vocabulary, that states facts about a page in a form machines can read: who published it, who wrote it, what it sells, where a business is. It sits in a script tag and does not change how the page looks.
Where do I put the JSON-LD code?
Paste the whole snippet, including the script tags, into the head of the page it describes, or into your CMS structured data field. Organization goes on the homepage or about page, Article on each post, Product on each product page and BreadcrumbList on inner pages.
Does schema markup help with ChatGPT, Perplexity and AI Overviews?
It helps machines understand a page, but Google says structured data is not required for its generative AI features and there is no special markup for them. Other AI engines have not documented using it. Treat schema as a supporting signal after crawler access and good content.
Is FAQ schema still worth adding?
Google stopped showing FAQ rich results on 7 May 2026, so FAQPage no longer changes how Google displays a page. The markup is still valid schema.org and accurately describes a Q&A page, so keep it where the questions and answers are visible, but do not add it expecting a Google feature.
Start with Organization on the homepage, then the content type of each page: Article for posts, Product for products, LocalBusiness for locations, plus BreadcrumbList on inner pages. The industry picker on this page lists the stack for each kind of business.
How do I validate my schema markup?
Use Google's Rich Results Test to check eligibility for Google features, and the Schema Markup Validator at validator.schema.org to check any schema.org markup, including types Google does not use. Fix errors before publishing, then check the page again after it goes live.