Schema Markup Generator
Fill in the form and copy ready-to-paste JSON-LD structured data for your page.
All required fields are filled in.
Paste it into the <head> or <body> of the page it describes. Then test it with Google's Rich Results Test or the Schema Markup Validator.
How to use the generator
- Pick the type that matches your page. The form changes to show that type's fields, and required fields are marked.
- Fill in the fields, or press "Fill with example" to see a complete sample first.
- Watch the notes above the code box. They list any required field you have not filled in, plus warnings about dates, URLs, numbers and currency codes.
- Press "Copy code" and paste the result into the page it describes, then test it with a validator.
The output is a complete <script type="application/ld+json"> block. It is rebuilt every time you type, entirely in your browser.
What the generator does for you
- Drops empty fields. Anything you leave blank is left out, so you never publish empty strings or empty lists.
- Converts minutes to durations. Schema.org wants times written in ISO 8601 form. You type 90 for a cook time and get
PT1H30M. A recipe's total time is added only when you give both a prep time and a cook time. - Builds nested objects. An author name becomes a Person, a brand becomes a Brand, a price becomes an Offer with a currency and an availability value, and a venue becomes a Place.
- Splits multi-line fields. Ingredients, steps, supplies and tools are written one per line, and each line becomes its own list item or step.
- Escapes the less-than sign in the output, so text from your page can never close the script tag by accident.
Worked example: an FAQ page
Choose "FAQ page" and write each question on its own line, followed by the answer on the next line. Leave one blank line between questions. If an answer runs over several lines, the lines are joined with spaces. A question with no answer is ignored, and at least one complete pair is needed before the tool treats the form as complete. The result is a FAQPage with one Question and one Answer for each pair.
Worked example: a product
A product needs a name, an image URL, a price and a currency code. The currency is converted to upper case, so "usd" becomes "USD", and availability defaults to in stock if you do not change it. Fill in a rating and a review count only if you actually display genuine reviews on the page. If you enter one without the other, the tool leaves the rating out and tells you to add both or neither.
After you paste it
Test the page with Google's Rich Results Test and the Schema Markup Validator, both linked above the code box. Errors there usually mean a value in your page differs from the markup, or a required field is missing. Remember that valid markup is not a promise of a special search result. Google decides what to show, and it has retired several. Its documentation says FAQ rich results stopped appearing in Google Search on May 7, 2026, and How-to rich results were retired in September 2023, so FAQ and How-to markup no longer changes how Google displays a page. Check the current documentation before relying on any type. The markup still describes your page clearly to any program that reads it.
More questions
Should the markup match the visible page?
Yes. The facts in the code, such as the price or the steps, should be the same as what visitors can see.
What date format should I use?
Use 2026-01-15, or with a time, 2026-01-15T10:00. Other formats raise a warning. Google recommends ISO 8601 and, for events, adding the UTC offset when you know it, such as 2026-01-15T10:00-05:00.
Can I combine two types on one page?
This tool produces one type at a time. Generate each block separately and put them both on the page, but keep one main subject per page.
Related tools
- JSON formatter to validate and tidy the code before you publish it.
- Programmer calculator, including Unix timestamp conversion for dates.
- Cloud cost calculator for comparing hosting prices.
What is structured data?
Structured data is a block of code that tells search engines exactly what a page is about: a recipe with its ingredients and cooking time, a product with a price, an FAQ with its questions. The most common format is JSON-LD using the vocabulary from schema.org. It sits in a script tag and is not visible to visitors.
Correct structured data can make a page eligible for rich results in search, such as recipe details, product prices and ratings, or event listings. Google has retired some types, including FAQ and How-to, so the markup for those no longer produces a special Google result. It does not guarantee a rich result, and it does not directly raise your ranking, but it helps search engines understand the page.
Rules to follow so the markup is accepted
- Describe what is on the page. The marked-up content must be visible to visitors. Do not add ratings, prices or questions that the page does not show.
- Only use real reviews. Include a rating only if it comes from genuine reviews displayed on the page.
- One primary type per page. A recipe page should describe that recipe, not other things.
- Keep it current. Update prices, availability and dates when they change.
- Use full URLs for images and links, starting with https://.
- Check the guidelines. Google no longer shows FAQ rich results (from May 7, 2026) or How-to rich results (from September 2023), so that markup has no effect on how Google displays your page. Check Google's structured data documentation for the types that are still supported.
Which type should I use?
- FAQ page: a page of questions and answers written by you. Google no longer shows FAQ rich results, so this is valid markup but gives no special Google result.
- Recipe: cooking instructions with ingredients and times. Google requires a name and an image for recipe rich results.
- Product: one product with a price and availability.
- Article: a news story, blog post or guide with an author and dates. Google lists no required properties for articles, only recommended ones.
- Event: something happening at a set time and place. Google requires a name, a start date and a location with an address.
- How-to: step-by-step instructions to do something. Google retired How-to rich results in 2023, so this is valid markup but gives no special Google result.
Related: format and check the output with the JSON formatter.
Frequently asked questions
Is my data uploaded?
No. The code is generated in your browser and nothing is sent anywhere.
Where do I paste the code?
Anywhere in the page's HTML, most often inside the <head>. If your site uses a CMS, look for a custom code or header scripts area.
Why is a field marked required?
Those are the fields this tool needs before the markup describes the item usefully. They are not always the same as Google's own required list: for example, Google lists no required properties for articles, requires a name and an image for recipes, and requires a name, start date and location with an address for events. Recommended extras, such as images, make your page eligible for richer results where Google supports them.
Does it work for other types?
This tool covers six common types. Schema.org has many more, and the output here can be used as a starting point.