Schema Markup Generator: Free JSON-LD Builder
Build JSON-LD structured data for Article, Product, LocalBusiness, Organization, Person, Event, Recipe, Breadcrumb, Review, FAQ and HowTo. Each type shows whether Google still supports it for rich results. Live preview, validation hints, copy and download. Free and private.
By Troopus · Updated: October 24, 2026
- 11 schema types
- Live JSON-LD preview
- Google eligibility notes
- Validation hints
- 100% private
Generate your JSON-LD structured data
Your JSON-LD
Test the result with Google's Rich Results Test and the Schema Markup Validator after you publish it. Checks here are based on Google's documentation but are not a substitute for those tools. 100% private: nothing you type leaves this page.
What is schema markup?
Schema markup is structured data, using the schema.org vocabulary, that describes what a page is about in a format search engines can read, most often as JSON-LD. It can make a page eligible for rich results, but Google does not guarantee them and does not describe markup as a ranking factor.
A page says "Trail Running Shoe, $89.99, in stock, rated 4.6" in words. Schema markup says the same thing in labeled fields: a Product with a name, an Offer with a price and a currency, and an AggregateRating. Search engines use that to understand the page and, when the page qualifies, to show extras such as prices, ratings or breadcrumbs.
Google recommends JSON-LD where your setup allows it, and also accepts Microdata and RDFa. The markup must describe content that visitors can actually see on the page. Hidden or misleading markup, such as fake reviews, breaks Google's guidelines and can lead to a manual action that removes rich result eligibility.
How do I use this schema markup generator as a JSON-LD generator?
To generate JSON-LD, choose a schema type, fill in the fields, check the validation notes and copy the code, then paste the script tag into the head or body of the page it describes. Publish the page, then test it with Google's Rich Results Test.
- Pick the type that matches the page, such as Article for a blog post or Product for a product page.
- Fill in the fields. Required fields are marked, and recommended fields are marked too. Use values that match what is visible on the page.
- Read the checks under the output. They flag missing required properties and format problems such as a price with a currency symbol.
- Copy the code. Leave "Wrap in a script tag" on if you paste into HTML. Turn it off if your plugin or CMS field wants raw JSON.
- Paste it into the page. Google reads JSON-LD in the head or the body. In WordPress, an SEO plugin field or a custom HTML block on that page works; a site-wide header snippet would put the same markup on every page, which is wrong for page-specific types.
- Test after publishing.
Use the title and meta description checker alongside this tool, since the title and description control how the result reads while structured data adds the extras.
Which schema types does the schema generator support?
Use the schema types that match your page content and that Google still supports for rich results: Article, Product, LocalBusiness, Organization, Event, Recipe, Breadcrumb and Review. FAQPage and HowTo are valid schema.org types, but Google no longer shows rich results for them.
| Type | Google rich result? | What Google requires |
|---|---|---|
| Article | Yes | No required properties. Recommended: author, datePublished, dateModified, headline, image. |
| Product | Yes | Name plus one of offers, review or aggregateRating. An offer needs a price. |
| LocalBusiness | Yes | Name and address. |
| Organization | Limited | No required properties. Helps Google understand the organization and can influence the logo and knowledge panel. |
| Person | Only in ProfilePage | ProfilePage needs a mainEntity (Person or Organization) with a name. |
| Event | Yes, physical events | Name, startDate and a location with an address. |
| Recipe | Yes | Name and image, plus many recommended properties. |
| BreadcrumbList | Yes | At least two items, each with a name and an item URL (the last may omit it). |
| Review | Yes, for eligible types | Author, itemReviewed and reviewRating. Self-serving reviews on LocalBusiness or Organization pages are not eligible. |
| FAQPage | No | Google discontinued FAQ rich results; its documentation says they no longer show in Search (2026). |
| HowTo | No | Removed from desktop and mobile in September 2023. |
Valid markup for a type with no rich result is not wrong, and other systems may read it. Just do not add it hoping for expandable FAQ or step results in Google. Pick types by what the page really is, and do not mark up content that is not on the page.
- An FAQ schema generator for question and answer pages.
- An article schema generator for blog posts and news.
- A product schema generator for shop pages.
- A local business schema generator for a business with an address and opening hours.
Because the vocabulary comes from Schema.org, the tool also works as a schema.org generator for the other types listed above.
How do I test output from a structured data generator?
Test structured data with Google's Rich Results Test, which checks eligibility for Google features, and the Schema Markup Validator, which checks general schema.org syntax. After publishing, use the URL Inspection tool and the rich result reports in Search Console to confirm Google found it.
The checks in this generator catch the common problems before you publish: missing required fields, a price like "$19.99" instead of 19.99, a rating outside its scale, an end date before the start date. They are based on Google's documentation but they are not a replacement for the official tools.
- Rich Results Test: paste the code or a URL to see which Google features the markup qualifies for and which properties are missing.
- Schema Markup Validator: checks the syntax against schema.org, regardless of Google features.
- Search Console: the rich result status reports show errors after deployment, which matters because template changes can quietly break markup.
Even valid markup is not a promise. Google says required properties and its guidelines must be met, and a rich result is never guaranteed. Do not block the page from crawling: check that it is allowed with the robots.txt generator and validator.
Schema markup generator mistakes to avoid
The most common schema markup mistakes are marking up content that is not visible on the page, leaving out required properties, using the wrong type, and copying one block of markup across every page. Google can apply a manual action to spammy structured data and remove rich result eligibility.
- Markup that does not match the page. Prices, ratings and reviews in the code must be visible to visitors.
- Fake or self-serving reviews. Reviews of your own LocalBusiness or Organization written by you or collected by your widget are not eligible for stars.
- Missing required properties. A Product with only a name, or an Event with no address, will not qualify.
- Wrong formats. Use plain numbers for prices, ISO 8601 dates and full URLs. Give latitude and longitude at least five decimals.
- Expecting retired features. FAQ and HowTo markup no longer produce Google rich results.
- One snippet everywhere. Product or Article markup is page-specific. Put Organization markup on the home or about page.
- Skipping the test. Run the Rich Results Test and monitor Search Console after changes.
Frequently asked questions
What is schema markup?
Schema markup is structured data written with the schema.org vocabulary that tells search engines what a page contains, such as a product, article or event. JSON-LD is the format Google recommends. It can make pages eligible for rich results but does not guarantee them.
How do I create schema markup with a structured data generator?
Choose the schema type for your page, fill in the fields in the generator above, review the validation notes and copy the JSON-LD. Paste it into the page it describes, publish, and then test it with Google's Rich Results Test.
Is JSON-LD better than microdata?
Google says it generally recommends JSON-LD when your site setup allows it, and also supports Microdata and RDFa. JSON-LD keeps the data in one script block instead of mixing it into the page HTML, which usually makes it easier to maintain.
Where do I put JSON-LD code?
Put the script tag on the page the data describes, in the head or in the body. Google reads both. In WordPress, use an SEO plugin field or a custom HTML block on that page rather than a site-wide header snippet for page-specific types.
How do I test schema markup?
Use Google's Rich Results Test to check eligibility for Google features, and the Schema Markup Validator for general schema.org syntax. After publishing, the URL Inspection tool and the rich result reports in Search Console show what Google found.
Does schema markup improve rankings?
Google does not describe structured data as a ranking factor. Its documented benefit is eligibility for rich results and a clearer understanding of the page. Rich results can improve how a listing looks, but Google never guarantees them.
Which schema types does Google support for rich results?
Google's gallery includes Article, Breadcrumb, Event, Job posting, Local business, Organization, Product, Recipe, Review snippet, Software app, Video and more. FAQ rich results were discontinued and HowTo was removed in 2023, so those no longer appear.
Does Google still show FAQ and HowTo rich results?
No. Google removed HowTo rich results from desktop and mobile in September 2023, and its documentation says the FAQ rich result is no longer shown in Search in 2026. You can still publish the markup, but it will not create those results.
Sources
- Google Search Central: Introduction to structured data
- Google Search Central: Structured data search gallery
- Google Search Central: General structured data guidelines
- Google Search Central: FAQ structured data (rich result discontinued)
- Google Search Central: Product snippet structured data
- Google Search Central: Review snippet structured data
- Rich Results Test
- Schema Markup Validator