Schema Markup Generator
Generate schema.org JSON-LD structured data that helps search engines and AI systems understand your page. Supports Article, FAQ, HowTo, Product, LocalBusiness, and Breadcrumb schemas.
Related Tools
How to Use
- Select Schema Type — Choose the type of structured data: Article (blog posts and news), FAQ Page (Q&A sections), HowTo (step-by-step guides), Product (e-commerce), LocalBusiness (local businesses), or BreadcrumbList (navigation path).
- Fill in the Fields — Enter your content details in the form. Required fields are marked with a red asterisk and recommended fields are labelled. For FAQ, HowTo, and Breadcrumb types, click "+ Add" to add questions, steps, or breadcrumbs, and remove any of them with the × button.
- Generate, Validate & Copy — Click Generate Schema to create the JSON-LD. Click Validate to list missing required fields as errors and missing recommended fields as warnings. Click Copy to copy the complete script tag, then paste it into your page's HTML (usually the <head> section).
About the Schema Markup Generator
The Schema Markup Generator builds schema.org structured data as a JSON-LD <script> block from a short form, checks it for missing or badly formatted values, and copies it ready to paste into a page. Structured data describes a page in a machine-readable way (this is a product with this price, this article was published on this date), and Google says it generally recommends JSON-LD for it where a site’s setup allows. Small-business owners, bloggers and developers use the tool to produce correct markup without writing JSON by hand.
The six types and how they are used today
| Type | Fields the tool requires | Note |
|---|---|---|
| Article | Headline, author, date published | Author is output as a Person, publisher as an Organization with an optional logo |
| FAQPage | At least one question with an answer | Google stopped showing FAQ rich results on May 7, 2026 |
| HowTo | Title and at least one step | Google retired HowTo rich results in 2023 |
| Product | Name, price, currency | Price goes in an Offer; availability is written as a full schema.org URL |
| LocalBusiness | Name, street, city, country | Google shows no review stars when a business controls reviews about itself |
| BreadcrumbList | A page name for each item; a URL for every item except the last | Positions are numbered automatically |
Rich result facts are from Google Search Central, checked on 2026-10-14. FAQPage and HowTo remain valid schema.org types that other search engines and programs can read. When you add a rating, the tool also writes bestRating 5 and worstRating 1, and it requires a rating count, since Google needs a ratingCount or reviewCount with every aggregate rating. Characters such as <, > and & are written as JSON escape codes, so a stray </script> typed into a field cannot break your page.
Worked example
We chose Product and entered a coffee dripper with a description, image URL, brand, SKU, availability “InStock,” currency usd, price $24 and a rating of 4.6 with no count. Validate reported two errors: the price must be a plain number, and a rating needs a rating count. After changing the price to 24.00 and adding a count of 38, it reported “Valid JSON-LD with all required and recommended fields.” The offer in the output reads "price": "24.00", "priceCurrency": "USD", "availability": "https://schema.org/InStock"; the lowercase currency code was converted to uppercase automatically.
Limitations
- The checklist is the tool’s own. Its required and recommended labels are a practical baseline; Google’s requirements differ by search feature and change over time.
- It checks format, not truth. Validation cannot know whether a price is current or a rating is real. Google’s guidelines expect markup to match what visitors see, and ratings must come from users.
- A core set of properties only. There are no fields for opening hours, individual reviews, offer expiry dates or nested types; add those by hand if you need them.
- Author is always a Person. If an article is credited to an organization, change that
@typeafter copying. - It is not Google’s test. Passing here does not mean a page is eligible for any rich result, and no markup guarantees one.
Practical tips
- One page can carry several blocks. For a blog post, generate an Article block and a BreadcrumbList block and paste both.
- Use full https:// URLs and YYYY-MM-DD dates; Validate warns about relative URLs and other date formats.
- Update the markup when the page changes, especially prices and availability.
- After publishing, test the live URL with Google’s Rich Results Test for Google features and the Schema Markup Validator for schema.org in general.
- To tidy or edit the JSON by hand, use the JSON Formatter & Validator; for the title, description and social tags, use the Meta Tag Generator.
Privacy: the JSON-LD is built and validated in your browser, and nothing you enter is sent to WritePadPro, Google or any other service.
Frequently Asked Questions
What is JSON-LD schema markup?
JSON-LD (JavaScript Object Notation for Linked Data) is the format Google recommends for adding schema.org structured data to web pages. It sits in a script tag of type application/ld+json and describes the page in a machine-readable way: what kind of content it is (article, product, business), who wrote it, when it was published, and so on. Search engines and AI systems use it to understand a page. Some types, such as Product, Article, and BreadcrumbList, can make a page eligible for rich results in Google, but eligibility is never guaranteed.
What schema types are supported?
Six types: Article (headline, author, dates, image, publisher), FAQPage (question and answer pairs), HowTo (numbered steps with names and descriptions, total time, image), Product (price, currency, availability, brand, SKU, rating), LocalBusiness (postal address, phone, website, rating), and BreadcrumbList (page names and URLs in order).
Will FAQ or HowTo markup give me rich results in Google?
No. Google retired HowTo rich results in 2023 and no longer shows FAQ rich results, so do not add this markup expecting expanded Google listings. FAQPage and HowTo are still valid schema.org types: they describe your content clearly to search engines and AI systems, and other search engines may still use them.
How does validation work?
The Validate button rebuilds the JSON-LD from the current form, confirms it parses as valid JSON, and checks every field for the selected type. Missing required fields (marked with an asterisk) are shown as errors and missing recommended fields as warnings. It also checks formats: full https URLs, YYYY-MM-DD dates, ISO 8601 durations such as PT30M, numeric prices, 3-letter currency codes, ratings from 1 to 5, incomplete FAQ pairs, and breadcrumbs without URLs. For Google-specific checks, test the published page with the Google Rich Results Test; for FAQPage and HowTo, use the Schema Markup Validator at validator.schema.org.
Is the generated code safe to paste into my page?
Yes. Characters that could break out of the script tag (the less-than and greater-than signs of a closing script tag typed into a field, and the ampersand) are written as JSON Unicode escape sequences (a backslash, the letter u, and the character code, such as u003c for the less-than sign). The JSON stays valid and reads back as exactly the text you typed, but it cannot end the script tag early or inject HTML into your page.
Where do I put the generated code?
Copy the generated code (including the script tags) and paste it into the HTML of the page it describes, usually in the head section before the closing head tag. Many CMS platforms have a field for adding custom code to the head. Browsers do not execute a script tag of type application/ld+json; it is read by search engine crawlers and other programs that parse structured data.
Can I add multiple FAQ questions or HowTo steps?
Yes. For FAQ, HowTo, and Breadcrumb types, click the "+ Add" button to add as many items as needed and remove any of them with the × button. The form starts with 2 items. FAQ questions without an answer (or answers without a question) are left out of the output, and Validate tells you which ones.
Is this tool connected to Google?
No. The tool generates the JSON-LD locally in your browser and does not submit anything to Google or any other service. After adding the code to your page, you can check it with the Google Rich Results Test (search.google.com/test/rich-results) or the Schema Markup Validator (validator.schema.org).