Schema Markup Generator

How to use this JSON-LD schema markup generator

Pick a schema type and fill in the fields — the JSON-LD code builds on the right as you type, with no page reload. Empty fields are left out of the output, so fill in everything that's actually on the page: the more complete the data, the better the chance of a rich result. The code comes wrapped in <script type="application/ld+json">, ready to paste as is. Everything runs in your browser; nothing you type is sent anywhere.

The generator covers six types: Article, Product, FAQPage, Organization, LocalBusiness and BreadcrumbList. Below is what each one produces and which properties to add by hand so the markup passes Google's checks without warnings.

Which schema type to use — and what to add

A note on FAQ: since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health websites. For everyone else the markup is valid and still describes the page, but there's no accordion in the results. HowTo rich results were removed the same year. More on how the types work in structured data explained.

Common Product schema errors

• No price. The generator adds the offers block only when the price field is filled. With no price, rating or review, Search Console reports that one of offers, review or aggregateRating must be specified.
• Rating without a count. Google requires reviewCount or ratingCount in aggregateRating — fill in both rating fields.
• Currency. Use a three-letter ISO 4217 code: USD, GBP, EUR, CAD — not "$" or "dollars".
• Price format. A plain number with a dot as the decimal separator (1299.00), no thousands separators or currency symbols.

Article schema: what Google actually uses

• headline — the same title readers see; don't stuff it with keywords that aren't in the H1.
• image — a large image from the article. Google requires at least 50,000 pixels in area (width × height) and recommends 16:9, 4:3 and 1:1 versions, which you can pass as an array.
• datePublished and dateModified — ISO 8601. The generator outputs a date such as 2026-10-13; adding time and time zone is better: 2026-10-13T09:00:00-05:00. Update dateModified only when the content really changes, not on every template deploy.
• author — a Person or Organization. The generator creates a Person with a name; add a "url" pointing to the author's bio page. List multiple authors as an array.

Organization and LocalBusiness: keep the details consistent

Name, address and phone in the markup should match what's on the site and in your Google Business Profile, down to the phone format. The Organization logo should be at least 112×112 pixels at a URL that robots.txt doesn't block. Use sameAs for official profiles — social accounts, Wikipedia, industry directories — to help Google connect the site to the entity. For multi-location businesses, give each location its own page with its own LocalBusiness block rather than one block with several addresses.

Where to add JSON-LD on your site

Google reads JSON-LD in both <head> and <body>. It also processes markup injected with JavaScript, but server-rendered markup is more reliable.

• WordPress. Yoast SEO and Rank Math already output Organization, WebPage, BreadcrumbList and Article as a single graph. Check the page before adding your own code to avoid two conflicting Organization blocks. For page-specific markup use a Custom HTML block; for sitewide markup, a header code plugin such as WPCode.
• Shopify. Most themes already print Product markup from the product template. Inspect a product page first; if it's there, extend it in the theme code rather than adding a second Product block.
• Wix and Squarespace. Both let you add custom code to the page head; Wix also has a structured data field in each page's advanced SEO settings.
• Custom builds and frameworks. Render the script tag server-side from the same data that renders the page, so price and availability can never drift from what visitors see.

Several types on one page are fine: add multiple script blocks, or combine them with @graph:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {"@type": "Organization", "name": "Acme Furniture", "url": "https://example.com/"},
    {"@type": "BreadcrumbList", "itemListElement": [
      {"@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/"},
      {"@type": "ListItem", "position": 2, "name": "Desks"}
    ]}
  ]
}
</script>

How to test your schema markup

1. Rich Results Test (linked under the code) shows which Google rich results the page is eligible for and any errors in supported types. Test the live URL once published, not just the snippet.
2. Schema Markup Validator checks syntax against the full Schema.org vocabulary, including types Google doesn't use for rich results.
3. Search Console enhancement reports list errors across every page on the site and let you validate a fix.

To see how a result might look, mock it up in the SERP preview tool. Social sharing cards are a separate standard: check them with the Open Graph debugger — Schema.org doesn't replace Open Graph tags.

Rules that get structured data ignored

• Markup must match visible content. Prices, ratings, questions and answers in JSON-LD must appear on the page. Google ignores hidden data, and repeated mismatches can lead to a manual action for spammy structured data.
• Self-serving reviews. Since 2019 Google doesn't show review stars for LocalBusiness and Organization when the business hosts the reviews about itself. Fill the rating fields for those types only with genuine reviews visible on the page — and don't expect stars.
• Ratings must be real. An invented 4.9 out of 5 is a direct violation of Google's guidelines.

Finally, schema markup isn't a ranking factor in itself. It makes a page eligible for a rich result, and that richer snippet can lift click-through rate at the same position.