Schema Markup Generator

Pick a schema type, fill in the fields, and get valid JSON-LD ready to paste into your page. Nine of the types that actually earn rich results are covered — Article, FAQ, Product, Organization, Local Business, Breadcrumbs, Website, Event and Recipe — each with its required fields marked and checked before you copy. Nested entities are built properly rather than flattened: an author becomes a Person, a price becomes an Offer, an address becomes a PostalAddress. That distinction is what separates markup that validates from markup that actually produces a rich result, and it is where hand-written JSON-LD most often goes wrong. Empty fields are dropped entirely, because a present-but-blank property is treated as malformed rather than simply absent. One caveat worth stating plainly: only mark up content that is genuinely visible on the page — marking up things a visitor cannot see is a policy violation, not a shortcut.

Which type suits which page

TypeUse it onKey required fields
ArticleBlog posts, newsHeadline, author, date published
FAQPagePages with visible Q&AQuestion and answer pairs
ProductProduct pagesName, price, currency
OrganizationAbout or home pageName, URL
LocalBusinessA business with an addressName, street, city
BreadcrumbListAny page in a hierarchyOrdered name and URL steps
WebSiteHome pageName, URL
EventEvent listingsName, start date, venue
RecipeRecipe pagesName, ingredients, steps

When to use it

  1. Add FAQ markup to a page to become eligible for the FAQ rich result.
  2. Mark up a product with price and availability for shopping results.
  3. Add breadcrumb markup so search results show your site structure.
  4. Describe a local business with its address and opening details.
  5. Generate Article markup with author and publication dates.

How to Use

  1. Choose the schema type that matches your page.
  2. Fill in the fields — required ones are marked and checked.
  3. Copy the generated script tag into your page.
  4. Verify with Google's Rich Results Test before relying on it.

Features

  1. Nine schema types covering the common rich-result cases
  2. Required-field checking before you copy
  3. Nested entities built properly, not flattened to strings
  4. Empty properties dropped rather than emitted blank
  5. Repeatable rows for FAQ pairs and breadcrumb steps
  6. Output wrapped in a ready-to-paste script tag
  7. 100% client-side — business details stay private

FAQs

What is JSON-LD and why this format?

JSON-LD is structured data expressed as a JSON block in a script tag, separate from your visible HTML. Google explicitly recommends it over microdata and RDFa because it does not entangle your markup with your content, which makes it far easier to maintain and much harder to break when the page layout changes.

Where do I put the output?

Anywhere in the page — head or body both work. Head is conventional. You can have several JSON-LD blocks on one page, which is the normal way to combine, say, Organization and BreadcrumbList markup.

Will this guarantee a rich result?

No, and nothing can. Valid markup makes a page eligible; whether Google shows a rich result depends on page quality, the query, and its own judgement. Validating correctly is necessary but not sufficient — and FAQ rich results in particular have been heavily restricted in recent years.

Can I mark up content that is not on the page?

No. Structured data must describe content a visitor can actually see. Marking up FAQs that are not rendered, or reviews that do not exist, is a structured data policy violation and can result in a manual action against the site. Use it to describe what is there, not to claim more.

How should I check it?

Run the output through Google's Rich Results Test and the Schema Markup Validator. This tool builds structurally correct JSON-LD, but only Google can tell you whether a specific page qualifies for a specific rich result.

Is anything uploaded?

No. The JSON-LD is assembled in your browser. Business details, prices and unpublished content you enter are never sent to a server, logged, or stored.

Technical Details

Each schema type carries a bundled field definition describing its properties, which are required, and how they nest. The JSON-LD object is assembled from those fields and then compacted: any property whose value is empty is removed entirely rather than emitted as an empty string or null, because Google's structured data parser treats a present-but-empty property as malformed rather than absent. Nested types are constructed as real nested objects with their own @type — an author becomes a Person, a product's price becomes an Offer, an address becomes a PostalAddress — since a flat string where the vocabulary expects an entity is the most common reason markup validates as a warning rather than an error but still fails to produce a rich result. Availability values are prefixed with the schema.org URL, breadcrumb positions are numbered from one in the order given, recipe steps become HowToStep objects, and multi-line inputs are split and trimmed into arrays. Required fields are checked and reported before you copy, and the output is serialised with JSON.stringify so quotes and newlines inside text are escaped correctly. Everything runs locally.

SEO Tools

SEO Tools

  • Meta Tag Generator
  • Sitemap Generator
  • Canonical URL Builder
  • Heading Structure Checker
  • Image Alt Text Auditor
  • Robots Meta Tag Generator
  • Sitemap Inspector
  • Robots.txt Generator