JSON-LD schema generator for every page on your site

This free schema generator produces JSON-LD structured data ready to paste into any web page. Pick the schema type, fill in the fields, and copy the output. The tool follows Schema.org guidelines and is compatible with everything Google, Bing, and other search engines parse from rich-result eligibility to knowledge panel entities.

If you are new to structured data, the sections below explain what each schema type does, how to install the markup, and how to validate it before going live.

Schema markup generator, structured data generator, JSON-LD generator: same thing

These names all refer to the same kind of tool. The vocabulary you mark up with is called Schema.org. The format Google recommends is called JSON-LD. The category of tool that builds that JSON-LD is variously called a:

  • Schema generator
  • Schema markup generator
  • Structured data generator
  • JSON-LD generator
  • Schema.org generator
  • Schema code generator

All of them do the same job: turn a form-based input into valid Schema.org JSON-LD. The tool above is all of those things.

What rich results does structured data unlock?

Schema markup powers most of the visual enhancements you see on a Google search results page. The most commonly used types map to the following rich results:

  • FAQ schema powers expandable question-and-answer dropdowns on the SERP for relevant queries.
  • Article and BlogPosting schema power article cards in news carousels, Top Stories, and Discover.
  • Breadcrumb schema replaces the URL in the search result with a clear navigation path.
  • Product schema powers price, rating, and availability annotations on shopping results.
  • Organization schema is the entity record Google uses to build knowledge panels.
  • Event, Recipe, How-to, and Video schemas each have their own specialized rich result formats.

A page can carry multiple schema types at once. A blog post, for example, typically combines Article, Breadcrumb, and Organization schemas in a single JSON-LD block.

Schema types covered by this generator

The tool above directly generates JSON-LD for these schema types:

FAQ schema (FAQPage)

Marks up a list of question-and-answer pairs on a page. Eligible for the FAQ rich result in Google Search. Use it for genuine FAQ content where each answer is complete on the page itself.

Article schema

Describes editorial content (blog posts, news articles, long-form guides). Includes title, author, publish date, and image. Required for Top Stories and most article-related rich results. Note that BlogPosting and NewsArticle are subtypes of Article and inherit its properties.

WebPage schema

Describes the page itself as an entity (title, description, primary image, language, publisher). Useful as the foundation schema on landing pages and resource pages.

Encodes the navigation path from the homepage to the current page. When valid, it replaces the URL in the SERP with the breadcrumb trail, which improves CTR on deep pages.

Other Schema.org types to know

These types are not currently generated by the tool above, but they are common in B2B SEO. Each links to the official Schema.org documentation so you can hand-build the markup or use the generator output as a starting template.

Organization schema

The entity record for your company. Combine it with sameAs URLs (LinkedIn, Twitter/X, GitHub, Crunchbase) to help Google build a knowledge panel for your brand. Place it on the homepage and on the About page. See Schema.org/Organization.

LocalBusiness schema

A subtype of Organization for businesses with a physical location. Adds address, geo coordinates, opening hours, and price range. Critical for local SEO and Google Business Profile alignment. See Schema.org/LocalBusiness.

Service schema

Describes a service your business offers (consulting, SEO, web development, etc.). Useful on service-page templates and in conjunction with Offer to expose pricing. See Schema.org/Service.

Product schema

Describes a sellable product, including price, currency, availability, and aggregateRating. Eligible for product rich results and Google Shopping listings. See Schema.org/Product.

Person schema

Describes an individual, typically an author or executive. Pair with Article (as the author property) to build author-entity signals and improve E-E-A-T. See Schema.org/Person.

Event schema

Describes upcoming or recurring events with start date, location, and ticket availability. Eligible for event rich results in Google Search and Maps. See Schema.org/Event.

JobPosting schema

Lists an open role with title, employment type, location, and salary. Required for inclusion in Google for Jobs. See Schema.org/JobPosting.

Course schema

Describes an educational course or training program. Eligible for course list rich results. See Schema.org/Course.

HowTo and Recipe schema

HowTo marks up step-by-step instructions; Recipe is the food-specific equivalent with ingredients and cooking time. Both are eligible for visual rich results. See Schema.org/HowTo and Schema.org/Recipe.

Video schema (VideoObject)

Describes a video, its thumbnail, duration, and embed location. Required for video appearing in Google Video search and the video rich result. See Schema.org/VideoObject.

Review and AggregateRating

Adds star ratings to compatible parent schemas (Product, LocalBusiness, Service, Recipe, etc.). Google has tightened the rules around review snippets, so confirm eligibility in current Google documentation before deploying. See Schema.org/Review.

ImageObject schema

Describes an image as a structured entity, including license, creator, and credit. Useful for licensable image rich results and image-search visibility. See Schema.org/ImageObject.

Marks up the primary navigation of a site to help Google understand site structure and surface relevant sitelinks. See Schema.org/SiteNavigationElement.

SoftwareApplication schema (for SaaS)

Describes a software product with operating system, application category, pricing, and rating. The right type for SaaS landing pages and app store equivalents. See Schema.org/SoftwareApplication.

SpeakableSpecification schema

Marks a section of a page as suitable for text-to-speech (voice assistants reading article excerpts). Currently limited to specific publishers and locales, but worth implementing for news and editorial sites. See Schema.org/SpeakableSpecification.

How to use the schema generator

Using the tool above is a four-step process:

  1. Select the schema type that matches the content on the page (FAQ for question-and-answer pages, Article for editorial content, etc.).
  2. Fill in the form fields with the values from your page (title, description, dates, author, URL).
  3. Copy the generated JSON-LD from the output panel.
  4. Paste the JSON-LD into the head of the relevant page, inside a script tag with type=“application/ld+json”.

Repeat for every page that needs structured data, or template the output once and inject it dynamically through your CMS or framework.

How to install schema markup on your site

There are three common installation paths.

Direct insertion into the page template. Paste the JSON-LD script tag into the head of the relevant template (page.html, single.php, layout.astro, etc.). This is the cleanest approach for static sites, custom builds, and frameworks like Astro and Next.js.

Through an SEO plugin. WordPress plugins (Yoast SEO, Rank Math, All in One SEO) include dedicated fields for custom JSON-LD on a per-page basis. This is the lowest-effort path for content sites already running an SEO plugin.

Through Google Tag Manager. Create a Custom HTML tag that contains the script tag with your JSON-LD, then fire it on the URL paths that need the markup. This is the best option when you cannot easily edit page templates or when you need to roll markup out across hundreds of pages at once.

Whichever path you choose, deploy to a single page first, then verify with the Rich Results Test before rolling out to the rest of the site.

How to test and validate schema markup

Two complementary validators cover every scenario.

Google Rich Results Test (search.google.com/test/rich-results) tells you whether the page is eligible for a Google rich result, which type Google detected, and any blocking errors. Use this whenever the goal is a rich result.

Schema.org Validator (validator.schema.org) parses the markup against the full Schema.org vocabulary. It catches type mismatches, malformed properties, and missing required fields even when Google does not surface a rich result for that type. Use this for any schema type beyond what Google supports.

Run both validators on a staging URL before deploying changes to production. Once live, recheck the page in Google Search Console under the relevant Enhancement report (FAQ, Breadcrumb, Article, etc.) for indexing-level errors.

Common schema markup mistakes

These mistakes account for most rich-result eligibility failures.

  • Marking up content that is not visible on the page. Google enforces parity between the visible content and the structured data. Hidden FAQs, future-dated articles, or invisible review snippets will be rejected and can trigger manual actions.
  • Using FAQPage on pages that are not actually FAQ pages. Google has tightened this rule: FAQ rich results are now reserved for genuine support and reference content, not marketing pages with question-shaped headings.
  • Mixing types incorrectly. An Article cannot have a Product as its mainEntity. Each schema type has a defined set of properties; combining incompatible types produces validation errors.
  • Missing required properties. Each type has required and recommended properties (Article needs headline, image, datePublished; Product needs name, image, offers). The Rich Results Test will tell you which are missing.
  • Hardcoded sample data. Generators sometimes ship with placeholder URLs and example.com references. Always replace placeholders with real values before deploying.
  • Multiple conflicting Organization records on one page. Use a single Organization schema per page, and reference it by @id from other markup blocks rather than duplicating it.

Schema types that drive the most clicks in B2B

For B2B websites, the highest-ROI schema work in 2026 is typically:

  1. Organization on the homepage and About page, with complete sameAs URLs, to anchor a knowledge panel.
  2. Article (or BlogPosting) on every editorial page, with a real author Person record and accurate datePublished. This is foundational for inclusion in news carousels and AI-overview citations.
  3. FAQPage on resource and support content, focusing on genuinely informational questions tied to commercial keywords.
  4. Breadcrumb on every page deeper than the top level, for cleaner SERP listings and improved CTR.
  5. Service schema on service pages, with linked Offer entities where pricing is publicly disclosed.

For software companies, add SoftwareApplication to product landing pages. For consulting and agency sites, add Service schema with provider linked to your Organization.

If you want a more complete walkthrough of structured data alongside meta info and on-page SEO, see the guide to optimizing web presence with meta info and schema markup. For implementation tips on Astro specifically, see how to optimize an Astro website for SEO and performance.

Frequently Asked Questions

What is a schema generator?

A schema generator is a tool that builds structured data markup in JSON-LD format from a simple form, so you can add Schema.org metadata to a page without writing JSON by hand. The output is ready to paste into the head of any HTML page or to insert through a tag manager.

What is Schema.org?

Schema.org is a collaborative vocabulary supported by Google, Bing, Yahoo, and Yandex that defines a shared set of types and properties for describing entities on the web (organizations, products, people, events, articles, and hundreds more). Schema.org markup is what powers most rich results in search.

What types of schema can I create with this tool?

This generator currently outputs JSON-LD for FAQ, Article, WebPage, and Breadcrumb schemas, which cover the most common rich-result opportunities for B2B content sites. Additional Schema.org types are explained in the body below with links to their official documentation.

What is JSON-LD?

JSON-LD (JavaScript Object Notation for Linked Data) is the format Google recommends for structured data. It lives in a single script tag in the page head, does not require modifying existing HTML, and is the easiest format to add, validate, and maintain at scale.

What is the difference between JSON-LD, Microdata, and RDFa?

All three are structured data formats Google supports, but they differ in where the markup lives. Microdata and RDFa are inline attributes added directly to existing HTML tags. JSON-LD is a separate script block. Google explicitly prefers JSON-LD because it decouples the markup from the page template, which makes it easier to maintain.

Do I need schema markup for SEO?

Schema markup is not a direct ranking factor, but it is a prerequisite for nearly every rich result in Google Search (FAQ snippets, breadcrumb trails, article cards, product results, knowledge panels, sitelinks). For competitive B2B keywords, structured data is often the deciding factor between a plain blue link and an enhanced listing.

How does structured data help SEO?

Structured data helps search engines understand exactly what an entity is, its relationships, and which properties matter. That precision is what unlocks rich results, surfaces your content in knowledge panels, helps voice assistants quote your pages, and increasingly informs how AI overviews cite sources.

Does using schema guarantee rich results in Google?

No. Schema markup makes a page eligible for rich results, but Google decides when and how to display them based on content quality, page authority, and intent match. Valid markup is necessary but not sufficient.

How do I validate schema markup?

Use two tools. Google Rich Results Test (search.google.com/test/rich-results) tells you whether a page is eligible for rich results and which type Google detected. Schema.org Validator (validator.schema.org) checks the markup against the full Schema.org vocabulary, including types Google does not surface as rich results.

How do I add schema markup to my site?

Paste the generated JSON-LD inside a script tag in the head of the relevant page (type="application/ld+json"). On WordPress, most SEO plugins (Yoast, Rank Math, All in One SEO) accept JSON-LD directly. For platform-wide injection, use Google Tag Manager to add a Custom HTML tag that fires on the relevant pages.

Can I use the generated schema on any website?

Yes. The output is plain JSON-LD that works on any platform that allows custom HTML in the head, including WordPress, Webflow, Shopify, Squarespace, HubSpot, Astro, Next.js, and static HTML.

What schema type should B2B companies use?

Most B2B sites benefit from an Organization schema on the homepage (with sameAs links to social profiles), Article or BlogPosting on every editorial page, FAQPage on pages with question-and-answer content, and Breadcrumb on every page deeper than two levels. Service pages should use Service schema, and software companies should use SoftwareApplication.

Do I need technical knowledge to use the schema generator?

No. Fill in the fields above for the schema type you need, and the tool will produce ready-to-paste JSON-LD. You only need to know what data you want to mark up (your organization name, article title, FAQ questions and answers, etc.).