Schema Generator and Validator
Build JSON-LD for 12 Schema.org types with every field labeled required or recommended from Google's own documentation, then validate it before it goes on the page.
Pick the type that matches what the page is about. One main entity per page.
Everything runs in your browser. Nothing you type is sent to our servers, and there is no login.
Fields
JSON-LD output
You edited the output by hand. The next change in the form will overwrite it. Use Reset to generated to discard your edits.
Validation
What each check means
| JSON syntax | The output is generated, so it always parses until you edit it. After a hand edit or a paste we parse it again and point at the failure. Google silently drops any JSON-LD block that does not parse. |
|---|---|
| Required fields | Properties Google's documentation for that type marks as required. Missing ones make the page ineligible for the feature and show as errors in the Rich Results Test. Required fields inside an optional block, such as price inside an offer, only apply when the block is present. |
| Recommended fields | Optional properties Google says improve the result. We list the empty ones as a note, never as an error. |
| Date format | Every date property must be ISO 8601: 2026-10-05 or 2026-10-05T19:00:00-07:00. We also check the calendar date exists and warn when an event or publish time has no timezone offset. |
| Absolute URLs | url, image, logo, sameAs, thumbnailUrl, contentUrl, embedUrl, item, and menu must start with http:// or https:// and include the host. Relative paths are not followed by Google. |
| Prices and numbers | price, lowPrice, highPrice, salary values, coordinates, counts, and rating values must be plain numbers with a dot decimal. Currency goes in priceCurrency as a three-letter ISO 4217 code. |
| Rating range | ratingValue must sit between worstRating and bestRating, which default to 1 and 5. Rating and review counts must be above zero and must be real counts of ratings collected on your site. |
| Eligibility and retired features | Some types are valid Schema.org but earn no Google rich result: Organization alone, WebSite alone, FAQPage since May 2026, HowTo since September 2023, and reviews an organization publishes about itself. The panel says so with dates and links instead of letting you assume a result is coming. |
| Content match | Always shown as a warning because we cannot see your page. Every value in the markup has to be visible to the visitor on the same page. |
Rich results Google has retired
These types are still valid Schema.org markup and this tool will generate or validate them, but it will not tell you a rich result is on the way.
| HowTo | No longer shown in Google Search since September 2023 on desktop and mobile; documentation removed September 14, 2023. Announcement |
|---|---|
| FAQPage | Limited to well-known authoritative government and health sites from August 2023, then no longer shown for any site from May 2026 (changelog entry May 8, 2026; documentation removed June 15, 2026). Changelog |
| WebSite SearchAction | The sitelinks search box was retired in November 2024 (announced October 2024, documentation removed November 29, 2024). WebSite name and url are still used for your site name. Announcement |
| Course info | Deprecation banner June 12, 2025, documentation removed September 9, 2025. The course list carousel (Course items inside an ItemList) is still documented. Changelog |
| Others | Estimated salary, learning video, special announcement, and vehicle listing were removed September 9, 2025; practice problems January 6, 2026. Changelog |
Limitations and data sources
- Required and recommended labels follow Google Search Central's structured data documentation for each type, checked September 2026, and each form links to the exact page plus the Schema.org type definition. Google changes these; the documentation link wins if they disagree.
- This tool checks the markup itself. It cannot see your page, so it cannot confirm that the content matches, that images are crawlable, or that the page is indexable. Use the Rich Results Test on the live URL for that.
- Validation covers the 12 form types. Pasted markup of other types still gets syntax, date, URL, price, rating, and retired-feature checks, but no required-field list.
- We never fill in placeholder values. Empty fields are left out of the output entirely so you cannot ship "TODO" or example data by accident.
- Reviews, ratings, prices, authors, and dates must be real. The tool will format fabricated data as happily as real data; the manual action is yours.
Frequently asked questions
- Does structured data guarantee a rich result?
- No. Valid markup makes a page eligible for a feature; Google decides per query whether to show it, based on the page's quality, the searcher's location and device, and whether the feature exists at all. Several features have been retired since 2023, so the markup can be perfect and still show nothing.
- Should I use JSON-LD or microdata?
- Google recommends JSON-LD. It sits in one script block in the head or body, does not touch your visible HTML, and is easier to generate from a template or a tag manager. Microdata and RDFa are still supported but harder to maintain. This tool only produces JSON-LD.
- How do I test the markup after publishing?
- Run the live URL through Google's Rich Results Test to see which Google features the page is eligible for and any errors Google reports, then through the Schema Markup Validator at validator.schema.org for general Schema.org correctness. Search Console's enhancement reports then show how Google reads the markup over time.
- Why must the visible page content match the markup?
- Google's structured data policies require markup to describe content the visitor can see on that page. Markup for hidden, missing, or different content, and fabricated reviews, prices, or dates, can trigger a manual action that removes rich results across the whole site until it is fixed and a reconsideration request is approved.
- Which rich results has Google retired?
- HowTo rich results stopped showing in September 2023. FAQ rich results were restricted to authoritative government and health sites in August 2023 and retired for everyone in May 2026. The sitelinks search box was retired in November 2024. The course info rich result was deprecated in June 2025, though the course list carousel remains. This tool warns when you pick or paste one of those types.
Related tools
WHOIS Lookup
Registrar, expiry, status codes, and live DNS for any domain.
SERP Preview
See how your title and description will look in results.
Indexability Checker
robots.txt, meta robots, canonical, and status code in one pass.
Redirect Checker
Follow every hop and status code in a redirect chain.
SEO Audit
On-page checks with the evidence and the fix for each finding.