Schema Markup Generator
Pick a schema type, fill in the fields, and get ready-to-use JSON-LD markup instantly.
About the Schema Markup Generator
Structured data spells out what a page actually contains, an article, a product, a recipe, in a format search engines can parse directly, and it's often what decides whether a listing shows up with star ratings, FAQ dropdowns, or recipe cards instead of a plain blue link. Pick a type, fill in the fields above, and this tool builds valid schema.org JSON-LD ready to paste straight into a page's <head>.
Valid schema doesn't guarantee a rich result
This is worth being upfront about: adding correct, valid structured data makes a page eligible for an enhanced search listing, it doesn't force Google to display one. Google still decides case by case whether a rich result actually appears, based on factors well beyond the markup itself, overall page quality and trustworthiness among them. Running generated markup through the Schema Validator on this site confirms the syntax is correct, which is a necessary condition for a rich result, just not a sufficient one on its own.
FAQPage eligibility has narrowed significantly
Worth knowing before leaning on FAQPage markup specifically: Google substantially restricted which sites are eligible for the FAQ rich result (the expandable question dropdowns in search results) to a small set of well-known, authoritative government and health websites. Most regular sites can still add valid FAQPage schema, and the FAQPage JSON-LD used on this site's own hub pages remains genuinely useful as structured data for other purposes, including how AI answer engines parse Q&A content, it just shouldn't be relied on as a guaranteed way to win the expandable dropdown in a Google search result the way it once was.
Product schema and what it takes to earn shopping-style results
The Product type here covers the core fields, name, price, currency, and availability, that a valid Offer requires. Full shopping-style results with star ratings additionally expect review or aggregateRating data, which isn't collected by this generator since it depends on real review data a site would need to supply from its own review system rather than something to fill in generically. The core fields generated here are still the right foundation, review data can be added on top once a real review source exists.
Recipe time fields use ISO 8601 duration format
Prep and cook time fields expect a specific format, not plain English, PT15M means 15 minutes, PT1H30M means one hour thirty minutes, the PT prefix marks a time duration and letters after each number specify the unit (H for hours, M for minutes). Typing "15 minutes" directly into that field produces invalid schema even though it reads correctly to a person, the ISO format is what a parser actually expects.
Article and LocalBusiness cover the more straightforward cases
Article schema is the more forgiving of the five types here, headline, author, publish date, image, and description map fairly directly onto fields most blog and CMS platforms already track, making it a reasonable default for a standard blog post or news piece even without much SEO-specific tuning. LocalBusiness is similarly direct, name, address, phone, and price range cover what search engines look for to associate a page with a physical business location, useful for a local service page even outside a dedicated Google Business Profile listing.
One schema block per page is the general rule
A page usually gets one primary type reflecting its main content, an article page uses Article, a product page uses Product, rather than combining several unrelated types on the same page hoping to qualify for multiple rich result types at once. FAQPage is a common exception, since it's often layered onto an article or product page that also happens to include a genuine FAQ section, as long as that FAQ content is actually visible on the page itself rather than existing only in the markup.
Frequently Asked Questions
Does adding structured data guarantee my page gets a rich result?
No. Valid structured data makes a page eligible for an enhanced search listing, but Google still decides case by case whether to actually display one, based on factors beyond the markup itself. Valid syntax is necessary but not sufficient on its own.
Is FAQPage schema still worth adding to my site?
Google significantly narrowed which sites are eligible for the FAQ rich result in search listings to mostly well-known government and health sites. FAQPage schema is still valid and useful for other purposes, including how AI answer engines parse question-and-answer content, just not a reliable way to win that specific Google search feature anymore.
Why doesn't the Product schema here include star ratings?
Star ratings require review or aggregateRating data, which has to come from a site's actual review system rather than being something to fill in generically. This generator builds the core Product fields, name, price, currency, and availability, review data can be layered on top separately once a real review source exists.
Why do I need to type PT15M instead of "15 minutes"?
Structured data requires ISO 8601 duration format, PT15M means 15 minutes, PT1H30M means one hour thirty minutes. Typing plain English like "15 minutes" into that field produces invalid schema even though it's readable to a person, since a parser expects the specific ISO format.
Can I add more than one schema type to the same page?
Generally a page uses one primary type matching its main content, rather than combining unrelated types. FAQPage is a common exception, often layered onto an article or product page that also includes a genuine, visible FAQ section, as long as that content actually appears on the page rather than existing only in the markup.