Schema markup,
made simpler.
Build Schema.org markup without writing it from scratch. Choose a template, add the real details, and leave with clean JSON-LD for your page.
Loading editor… If this message remains, reload the page and check that JavaScript is enabled.
02 / Add the real details
Organization
* Required by this template. Optional fields are omitted when empty. Country and currency codes use uppercase letters.
03 / Review & export
A basic pass is not Google approval. Confirm the content is accurate and visible, then test it with the official validators.
These links open external sites. No entered data is sent automatically.
Nothing is saved automatically. Save a project before leaving. Project files restore builder fields; ordinary JSON-LD belongs in the checker below. File limit: 200 KiB.
Start a new empty project? Your current project can still be restored with Undo while this page stays open.
Give your JSON-LD a basic check.
Paste JSON or one JSON-LD script snippet with only its type attribute. Checks syntax, duplicate keys, selected missing-field advisories and unsafe URL schemes. It does not validate the full vocabulary, custom contexts or Google eligibility.
Build carefully. Check the actual page.
Describe what is there
Use real names, prices, locations and dates. The markup should match the content people can see. Skip blocks and fields that do not apply.
Review the generated code
Fix field errors, read the notes and check your CMS for existing schema. Consistent entity IDs help describe the same thing without conflicting copies.
Validate after publishing
Run the external validators, publish to the relevant page, and check its live URL in Search Console. Passing a test cannot guarantee a rich result.
Choose a template that fits your content
Businesses can start with Organization or LocalBusiness. Publishers can use Article and VideoObject. Shops can describe one Product with one Offer. BreadcrumbList describes navigation; WebSite describes a site; Service, Person and an in-person Event cover other common entities. Recipe supports ingredients and step-by-step instructions; ProfilePage describes a person or organization profile. FAQPage remains available as vocabulary, but Google no longer displays FAQ rich results.
The builder intentionally covers a defined set of fields. It does not generate fictional review stars, full merchant shipping and return policies, job postings or every Schema.org type. You can extend exported JSON-LD with specialist properties and validate the result externally.
Structured data and search visibility
JSON-LD helps describe a page. It does not submit the URL to Google or override crawling and indexing decisions. Use a correct canonical and page metadata, check crawler directives, maintain your XML sitemap, and provide useful, internally linked content.
Guidance checked on September 30, 2026: Google structured-data policies, product snippets, video requirements, and Google Search documentation updates. Requirements can change.
Frequently asked questions
What does this schema generator create?
It creates Schema.org JSON-LD from 13 template families: Organization, LocalBusiness, Article, Product with an offer, BreadcrumbList, FAQPage, Service, WebSite, Event, VideoObject, Person, Recipe and ProfilePage. Local businesses and articles include selected subtypes. Combine up to 20 blocks for one page in an @graph.
Is this a complete Google rich-results validator?
No. The builder checks its supported fields and the separate checker checks JSON syntax and basic structure. Neither checks every Schema.org property, expands custom contexts, fetches URLs, reads your live page or verifies Google eligibility. Use the official external validators, then inspect the published page.
Will schema markup make Google index my page?
No. Structured data describes content; it cannot force crawling, indexing, rankings or rich results. Publish useful, accessible pages, link to them, include canonical URLs in your sitemap and review Google Search Console.
Does FAQ markup still produce Google rich results?
No. Google retired FAQ rich results in May 2026. FAQPage remains available as Schema.org vocabulary for appropriate visible questions and answers, without a Google rich-result promise.
Are my entries uploaded or saved automatically?
This editor and checker process your entries locally. They do not upload them or save them automatically. Save a project file before leaving if you want to continue later. Normal site analytics and feedback services can still load; the editor does not send your form values to them.
Can I import an existing JSON-LD file?
Open a JSON file or paste a single JSON-LD script snippet in the checker to inspect and format it. Existing JSON-LD is not converted into editable template fields. To restore the builder, open a project file previously saved by this tool. Both inputs have a 200 KiB limit.
What do the field checks cover?
Checks include required template fields, HTTP(S) URL syntax, real calendar dates, time-zone offsets, paired coordinates, decimal prices, GTIN check digits, duplicate entity IDs and breadcrumb order. Country and currency codes are checked for format only, not against the full ISO registry. The tool cannot verify that your claims are true.
Can I create product review stars or every schema type?
No ratings are generated automatically. The product template uses a real price and currency in one Offer; it is not a full merchant listing or product-variant editor. This release covers the listed templates and fields, not every Schema.org type. Extend specialist markup separately and validate it.
Where should I put the generated code?
After reviewing and testing it, place the HTML script snippet in the head or body of the page that contains the described content. A CMS may have a dedicated schema field that expects JSON only. Avoid conflicting duplicates from themes or SEO plugins. This tool does not edit your website automatically.
What are the limits and supported exports?
Use up to 20 entity blocks, 30 rows per repeated section or URL list, and 4,000 characters per field. Project and checker inputs are limited to 200 KiB. Export formatted or compact JSON-LD, an HTML script snippet, a project file or a field-check report. Undo and redo retain up to 30 edits within the open page.