Free schema markup generator (JSON-LD)
Fill in a short form and get valid JSON-LD for FAQPage, Article, Organization, HowTo or SoftwareApplication, checked as you type.
Sample values loaded. Replace them with your own.
JSON-LD
Checks
Paste the block into the page's <head> or body, then confirm it with Google's Rich Results Test or the Schema Markup Validator.
What the checks compare your markup against
The generator writes structured data as JSON-LD, the format Google recommends, inside a script tag you can paste as is. Errors mean broken JSON or a missing required field. Warnings are recommended properties you left out. The rules come from Google's documentation for Article, Organization and software apps, and from schema.org for FAQPage and HowTo, which Google no longer turns into rich results.
Which schema type goes on which page?
Most sites need two types: Organization once, on the homepage or about page, and Article on every post. The rest depend on what you sell.
| Page | Type | Fields that matter most | Google rich result? |
|---|---|---|---|
| Homepage or About | Organization | name, url, logo, sameAs | Logo and knowledge panel details; no required fields |
| Blog post, guide, news | Article, BlogPosting or NewsArticle | author.name + author.url, datePublished, dateModified, image | Yes; no required fields |
| Product or app page | SoftwareApplication | name, offers.price, plus aggregateRating or review | Yes, but only with real ratings |
| Page with a visible FAQ | FAQPage | Each question and answer, word for word | No, since May 7, 2026 |
| Step-by-step tutorial | HowTo | name, steps with text | No, since September 2023 |
The FAQ change is recent. Google's documentation updates record that FAQ rich results stopped appearing in Search on May 7, 2026, after being limited to well-known government and health sites in 2023. HowTo went in September 2023. Google has said there's no need to remove markup that no longer earns a rich result, and we'd leave it in place.
Worked example: the Organization block most sites get wrong
Organization markup is where an entity gets defined, so it's worth ten careful minutes. Here's a version that does its job:
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#org",
"name": "Example Co",
"url": "https://example.com/",
"logo": "https://example.com/logo.png",
"description": "Example Co makes scheduling software for field service teams.",
"sameAs": [
"https://www.linkedin.com/company/example",
"https://www.crunchbase.com/organization/example",
"https://github.com/example"
]
}Three details carry most of the value. The @id gives the organization a fixed identifier your Article markup can point to as "publisher": {"@id": "https://example.com/#org"}, instead of repeating the name and logo on every post. The sameAs list ties your site to profiles that describe the same company. And the description is one plain sentence that matches what your homepage and LinkedIn say.
The common failures are the opposite: a name of "Example" on the homepage and "Example Co Inc." on the blog, sameAs pointing at a dead Twitter account and a founder's personal profile, or a logo given as a relative path. Each one makes it harder for a machine to decide these pages describe one company.
Does schema help with AI search?
Not directly, according to Google. Its guide to generative AI features says structured data isn't required for generative AI search and there's no special schema.org markup to add, while recommending you keep using it as part of normal SEO. OpenAI, Anthropic and Perplexity haven't published anything saying their engines rank sources by markup.
The work that does move AI visibility is on the page and in what other sites say about you. Our breakdown of how AI engines choose sources covers the evidence, the citability grader scores the on-page part, and the free Arobis AI visibility checker shows whether ChatGPT names your brand today.
Four markup mistakes that cost rich results
Marking up what readers can't see. Google's structured data policies say not to mark up content that isn't visible on the page. A FAQPage block with eight questions over a page that shows four can earn a manual action, which removes rich result eligibility (Google says it doesn't affect ranking).
Ratings you can't back up. SoftwareApplication needs aggregateRating or review for a rich result, which tempts people to invent one. Google's policies name fake reviews as misleading markup. If you don't have ratings shown on the page, ship the markup without them and accept no rich result.
Bumping dateModified on every deploy. It should change when the content does. A post that claims to be updated every week while saying the same thing sends a signal you can't support.
Testing with the wrong tool. The Rich Results Test only checks types Google turns into rich results, so it says little about FAQPage or HowTo now. Use the Schema Markup Validator for those, and the Rich Results Test for Article, Organization logo and software apps. Test the live URL, not pasted code, so you see what Google actually fetches.
Frequently asked questions
What is JSON-LD schema markup?
A block of JSON, placed in a script tag of type application/ld+json, that describes a page using the schema.org vocabulary. It tells search engines and other parsers that the page is an article, a company, an FAQ or an app, and lists facts such as author, dates and price. Google recommends JSON-LD over Microdata and RDFa because it's easier to maintain.
Does FAQ schema still work in Google?
Not for rich results. Google's documentation records that FAQ rich results stopped appearing in Search on May 7, 2026, after being limited to well-known government and health sites in 2023. FAQPage markup is still valid schema.org and harmless to keep, as long as every question and answer in it is also visible on the page.
Which Article properties does Google require?
None are required. Google recommends author with author.name and author.url, datePublished, dateModified, headline and image, ideally in 16x9, 4x3 and 1x1 ratios. The author URL should lead to a real profile page. Accurate recommended properties help Google understand the article; invented ones can cost you rich result eligibility.
What does Google require for SoftwareApplication markup?
For a software app rich result Google requires name, offers.price, and either aggregateRating or review. It recommends applicationCategory, with a supported value such as BusinessApplication, and operatingSystem. Use a price of 0 for free apps and add priceCurrency when the price is above 0. Ratings must come from real users and appear on the page.
Will schema markup get my site cited by ChatGPT or AI Overviews?
There's no evidence it does on its own. Google's guide to generative AI features says no special markup is needed for AI search, and OpenAI, Anthropic and Perplexity don't document markup as a source-selection factor. Use schema for rich results and consistent entity facts, and spend AI visibility effort on content, crawler access and third-party mentions.
Where should I put the JSON-LD on my page?
In a script tag of type application/ld+json, in either the head or the body. Google reads both, including JSON-LD injected by JavaScript, though server-rendered markup is more reliable. Put Organization markup on the homepage or about page and Article markup on each article, then test the live URL.