Skip to main content
ToolsByUs

SEO Schema Generator

SEO Schema Generator builds valid Schema.org JSON-LD markup without hand-writing JSON: pick a type — Article, Product, Local Business, Event, Job Posting, Recipe, Breadcrumbs or Organization — fill in the fields, and paste the output into your page's <head>. Required fields are validated against Google's documented requirements, and several entities can be combined into one @graph block. It cannot promise rich results — those are Google's decision, and FAQ and HowTo rich results have been retired entirely. Everything runs in your browser; nothing is uploaded.

Local-only
Google retired FAQ rich results in May 2026 and HowTo rich results in 2023 — those types are intentionally not offered here. Valid markup helps search engines and AI understand your page; whether Google shows an enhancement is its decision, not something any tool can promise.

Article

Blog posts and news articles. The most widely used structured data on the web.

Recommended. Usually matches the page's meta description.

Recommended. A representative image for the article.

Fill in when the article is updated after publishing.

Recommended. The organisation behind the article.

Need several entities on one page — e.g. Product + Breadcrumbs? Fill in each type and add it below; they combine into a single @graph block.

application/ld+json

Fill in the required fields — marked * — and valid JSON-LD appears here.
Single entity
Test with GoogleSchema.org validator
Markup must describe content visitors can actually see on the page. Hidden or unrelated markup can be treated as spam. Paste the block inside a <script type="application/ld+json"> tag in your page's <head>.

How does SEO Schema Generator work?

JSON-LD is a <script type="application/ld+json"> block that describes the page's content as structured data. @context pins the vocabulary to schema.org; @type picks the entity — an Article, a Product, an Event. Search engines and AI assistants parse this instead of guessing what the prose means.

Required is a documentation term, not a promise

Google documents required and recommended properties per type. Required here means required by that documentation: the form marks those fields and refuses to emit markup without them. Filling them makes the markup eligible for enhancements. Whether Google shows a rich result is a separate decision it makes per query, per page, per day — no generator can promise it, and any that does is lying.

One block per page, or @graph for several

A page usually carries one entity, but a product page with breadcrumbs legitimately carries two. The collection below combines entities into a single @graph array so you paste one block. Each entity is validated on its own before it is added.

What validation here actually checks

Presence of required fields, numeric fields holding numbers, dates parsing as dates, and URLs without spaces (a missing scheme gets https:// prepended). That is JSON validity plus field hygiene — the real verification is Google's Rich Results Test, linked below, which runs Google's own parser against your URL or code.

Fields

Type: Article
Headline: How We Cut Our Build Times in Half
Author: Ada Lovelace
Published: 2026-10-01

JSON-LD

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How We Cut Our Build Times in Half",
  "author": { "@type": "Person", "name": "Ada Lovelace" },
  "datePublished": "2026-10-01"
}

What options and edge cases does SEO Schema Generator support?

Supported types
ParameterTypeDefaultBehaviour & edge cases
Article@typeBlog posts and news articles. The most widely used structured data on the web.
Product@typeProduct name, Image URL, Price, CurrencyProducts with price and availability. Google requires name, image and offer details.
LocalBusiness@typeBusiness name, Street address, CityShops, restaurants and services with address, hours and contact details.
Event@typeEvent name, Start date & time, Venue name, Venue streetConcerts, workshops and meetups with date, venue and ticket info.
JobPosting@typeJob title, Job description, Date posted, Company name, Work cityJob ads with title, employer, location and posting date.
Recipe@typeRecipe name, Image URL, Ingredients, InstructionsRecipes with ingredients, steps and times. Google requires name, image, ingredients and instructions.
BreadcrumbList@typeTrail itemsNavigation trail (Home › Category › Page) so search engines understand page hierarchy.
Organization@typeOrganization nameYour company or brand: name, logo, website and social profiles.

Frequently asked questions

Will this guarantee rich results in Google?

No, and neither can any other tool. Valid markup makes a page eligible for enhancements; Google decides per query whether to show them. Treat any generator that promises rich results as a warning sign. What this tool does guarantee is syntactically valid JSON-LD with the fields Google documents as required.

Why is there no FAQ or HowTo type?

Because Google retired HowTo rich results in September 2023 and FAQ rich results in May 2026. Offering those types would imply a visual enhancement that no longer exists. FAQPage remains valid Schema.org vocabulary and AI engines may still consume it, but if you want it you are writing it by hand knowing exactly what it does and doesn't buy you.

Where do I paste the generated code?

Inside a <script type="application/ld+json"> tag in your page's <head>. It also works in the <body>, but head is the convention and keeps it out of the rendered content. One block per page is typical; use the collection below to combine several entities into a single @graph block.

Does the markup have to match my page content?

Yes — strictly. Markup must describe content that is visible to visitors on that page. Marking up content users can't see, or copying markup onto unrelated pages, can be treated as spam and hurt the page it was meant to help. Write the markup from the page, not the other way round.

How do I check that my markup is correct?

Use Google's Rich Results Test (linked above) — it runs Google's own parser against your URL or pasted code and reports exactly what Google sees. The Schema.org validator is a second opinion for vocabulary correctness. This tool's own checks cover JSON validity and required-field presence, which is necessary but not sufficient.

Is my content uploaded anywhere?

No. The form, the JSON-LD builder and the validator all run in your browser. Product prices, addresses and salaries people put into schema markup are business data — there is no reason to hand it to a server just to format JSON.

ToolsByUs team · How we check our tools