FAQ, article, business, breadcrumbs and product.
Each type has its own form: add FAQ rows or breadcrumb steps with one click, then copy the JSON-LD.
- FAQPage with Q&A rows
- Product with offers block
Pick a schema.org type, fill in the fields, and copy valid JSON-LD for FAQ, Article, Organization, LocalBusiness, breadcrumbs or Product. The preview updates live in your browser; empty fields are left out, and review or rating markup is never added.
Free, no account needed. JSON-LD is built in your browser and never sent to MrKeyword.
Built on first-party data from Google and Bing
Schema markup (structured data) is a short JSON-LD block that tells search engines what a page is about: an article and its author, a business and its address, a product and its price, or the questions on an FAQ page. Google reads it to understand the page and, for some types, to show a rich result such as breadcrumbs, product prices or article dates.
JSON-LD lives in a <script type="application/ld+json"> tag in the page head or body. It uses the shared schema.org vocabulary, so the same field names work across CMS plugins, hand-written templates and this generator.
This tool builds one block at a time from the fields you type. It drops empty properties, flags common gaps for Google rich results, and never outputs review or aggregateRating markup, so you are not tempted to mark up ratings that are not shown on the page.
Valid schema is always worth adding so Google understands your pages, but not every type still produces a visible enhancement in search. This table reflects Google’s published status as of 2026; confirm important pages in the Rich Results Test.
| Type | Rich result in Google | Notes |
|---|---|---|
| Product | Supported | Needs real offers (price and currency) that match what shoppers see on the page. |
| Article / BlogPosting | Supported | Image, headline, dates and author are strongly recommended; Google may show byline and date. |
| BreadcrumbList | Supported | Breadcrumb trail in results when the listed URLs match the site structure. |
| LocalBusiness | Supported | Address, hours and phone must match the visible contact details on the page. |
| Organization | Supported (logo / knowledge) | Often used for logo and site-name treatment; not a substitute for LocalBusiness on location pages. |
| FAQPage | Limited | FAQ dropdown rich results now show only for well-known, authoritative government and health sites. Markup on other sites is still valid but usually will not show the dropdown. |
Each type has its own form: add FAQ rows or breadcrumb steps with one click, then copy the JSON-LD.
Live JSON-LD preview with script tags escaped for HTML, warnings for missing rich-result fields, and a link to the schema markup validator.
The fictional northwind-plumbing.example sells an annual boiler service for £89. Filling the Product form with its name, description, brand, SKU and an InStock offer produces JSON-LD like this:
No common rich-result gaps flagged for this type.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Annual boiler service",
"description": "Full inspection, safety checks and efficiency tune-up for domestic boilers in Leeds.",
"brand": {
"@type": "Brand",
"name": "Northwind Plumbing"
},
"sku": "SVC-BOILER-89",
"offers": {
"@type": "Offer",
"price": "89",
"priceCurrency": "GBP",
"availability": "https://schema.org/InStock"
}
}
<\/script>Example Product JSON-LD for a fictional plumbing business. It is built by the generator’s own code at build time; change the fields above to match your page.
The block includes @context, @type, the product name, description, brand, SKU and an Offer with price and currency, which is what Google needs for product rich results. There is no aggregateRating or review markup. After you paste the script into the page template, run the live URL through the schema markup validator or Google’s Rich Results Test. Our on-page SEO checklist lists structured data alongside the other page checks.
Every value must appear on the page for people to read. Do not mark up prices, FAQs or addresses that are not visible in the HTML.
FAQPage is still valid, but Google shows FAQ rich results only for select government and health sites. Use FAQ schema to clarify content, not to chase dropdowns.
Do not add aggregateRating on your own Organization or LocalBusiness. This generator omits review fields on purpose.
Prefer this tool or your CMS plugin to generate JSON-LD. If you edit by hand, one stray comma invalidates the whole block.
Use absolute https URLs for image, logo and breadcrumb item URLs so crawlers resolve them correctly.
Generate JSON-LD when you add a new template or page type, or when an SEO plugin outputs the wrong type for the content.
FAQPage (questions and answers), Article and BlogPosting, Organization, LocalBusiness, BreadcrumbList and Product. Each type uses the properties Google documents for that rich result.
No. Review and aggregateRating markup must reflect ratings shown on the page. This generator never outputs those fields, so you cannot accidentally create self-serving review markup.
Yes. Copy the JSON object (or the full script block from the preview) into your page template, CMS custom field or SEO plugin. Replace placeholder values with real business facts that match what visitors see.
Use the Test in validator link to open our schema markup validator, paste a public page URL after you publish the markup, or paste the JSON into Google’s Rich Results Test for a final eligibility check.
Usually not. Since August 2023, Google shows FAQ rich results only for select government and health sites. FAQPage markup on other sites remains valid and can help search engines understand the page, but most sites should not expect the old FAQ dropdown.