Schema Settings
Define your schema type and details
Generated JSON-LD Schema
The schema markup generator writes JSON-LD structured data with AI from a schema type, page title, description and any extra details you add. It covers Article, Product, FAQ, LocalBusiness, Recipe, Event, Person and Review. It is built for site owners, bloggers and SEOs who do not want to write markup by hand. Free, no sign-up. Validate the code before publishing.
Define your schema type and details
Choose Article, Product, FAQ, LocalBusiness, Recipe, Event, Person or Review from the Schema Type menu.
You get a script block in JSON-LD, the format Google recommends when your site setup allows it.
Prices, addresses, dates, ingredients or authors in Additional Details become properties instead of guesses.
Copy the finished code and paste it into your page, theme or SEO plugin.
Three steps from a blank form to a result you can use.
Select the type that matches the main content of the page, such as Recipe for a recipe post or Product for a product page.
Enter the page title, a short description and the facts the markup should contain in Additional Details.
Click Generate Schema, copy the JSON-LD, replace any placeholders and test it before you publish.
Schema markup is structured data that labels what a page is about, such as a product's price or a recipe's cooking time, in a format search engines read. This tool drafts that markup for you so you can check it and paste it in.
| Schema Type | Use It For | Add to Additional Details |
|---|---|---|
| Article | Blog posts, news stories, guides | Author name, publish and update dates, image URL |
| Product | A single product page | Brand, price, currency, availability, SKU, image URL |
| FAQ | A page that lists questions with answers | Each question and its exact answer as shown on the page |
| LocalBusiness | A business with a physical location | Street address, phone, opening hours, area served |
| Recipe | One recipe per page | Ingredients, steps, prep and cook time, servings |
| Event | A concert, class, webinar or meetup | Start date and time, venue or online link, ticket price |
| Person | An author bio or profile page | Job title, employer, social profile URLs |
| Review | A review of a product, book, recipe or similar item | Item reviewed, rating, reviewer name |
Example: This is an illustration, and your output will differ. A food blogger adds markup to a recipe post.
A good result would be a <script type="application/ld+json"> block with "@type": "Recipe", the name and description, the author, the times written in a duration format, the yield, an ingredient list and instruction steps.
Before publishing, we would check three things: the ingredients and times match the visible recipe card, the image URL is real, and the steps in the markup are the same steps readers see.
Structured data is a standard way to describe a page and classify its content. Google can use it to show rich results, such as recipe cards or product details. A few points from Google's own guidance matter for anyone using a generator:
Schema does not raise rankings by itself. Its value is making a page eligible for richer search results, which can make the listing more useful to searchers.
Because the markup is written by AI, review it the way you would review code from a new colleague.
Copy facts straight from the page into Additional Details so the markup and visible content match exactly.
Give full URLs for images and profiles. Relative paths often fail validation.
Write dates with the day, month and year, and add a time and time zone for events.
Check whether your SEO plugin already outputs schema before you add a second block.
Revisit product and event markup whenever prices, stock or dates change on the page.
Manually writing schema markup requires memorizing the correct property names, data types, and nesting structure for each schema type. A single typo or missing required property can invalidate the entire block. Our generator handles all of this correctly by default.
Google's native tool is useful for simple cases but requires you to visually tag elements on a live page, which is slow and inflexible for developers or content teams managing many pages. Our generator is faster and works without any live URL.
CMS plugins like Yoast and RankMath add schema automatically, but they cover generic cases. For custom schema with specific properties, a precise product price, a specific event organizer, or a detailed recipe, a generator gives you full control over every field.
It is a tool that turns details about a page into structured data code. This one uses AI to write JSON-LD from a schema type, page title, description and extra details you provide. You copy the script block into your page so search engines can read facts such as prices, dates and authors.
It is written to follow schema.org conventions, but AI output can contain mistakes or placeholders, so we cannot promise it passes. Replace placeholder values, add any missing required properties and run the code through the Rich Results Test before publishing. Fix every error the test reports, then retest.
Paste the full script block into the HTML of the page it describes, usually in the head section. If you use WordPress or another CMS, add it through a header code field, a custom HTML block or your SEO plugin's schema settings. Each page needs markup that matches its own content.
Not directly. Structured data helps Google understand a page and can make it eligible for rich results such as recipe or product details. Google does not guarantee those results even when the markup is valid. A richer listing can help searchers choose your page, but content quality still decides rankings.
Google now states that the FAQ rich result is no longer shown in Google Search results. The markup is still valid schema.org code and other systems may read it, but it will not create expandable questions under your Google listing. We suggest putting effort into types that still earn rich results.
Yes, a page can carry more than one block when each describes something real on the page, such as an Article with its author as a Person. Run the tool once per type and add each block. Avoid marking up things that are not visible, and avoid duplicating what your plugin already outputs.