Ttooleras
📋

Schema Markup Generator

SEO Tools

Generate schema.org JSON-LD structured data for articles, products, recipes, FAQs, events, local business, and more.. Free, private — all processing in your browser.

Advertisement

The Schema Markup Generator creates JSON-LD structured data for any schema.org type, ready to paste into your HTML. Structured data helps Google understand your content and enables rich results in search: recipe cards with cooking times and ratings, article cards with publication dates and images, product snippets with prices and availability, FAQ accordions directly in search results, event cards with dates and locations. Without structured data, your pages show as plain blue links; with it, they stand out.

Pick a schema type (Article, Product, Recipe, FAQ, Event, Organization, LocalBusiness, BreadcrumbList, and more), fill in the fields via the form, and the tool outputs valid JSON-LD you drop into a <script type=\"application/ld+json\"> tag. Validation ensures required fields are present and data types match schema.org specs. Preview shows how the rich result might appear in Google. All generation runs client-side so proprietary business data stays in your browser.

Schema Markup Generator — key features

Most common types

Article, Product, Recipe, FAQ, Event, Organization, LocalBusiness, BreadcrumbList, Review, How-to, and more.

Form-based input

Fill in fields via structured forms rather than writing JSON by hand.

Validation

Checks required fields, data types, and ISO 8601 format compliance before output.

JSON-LD output

Copy-ready script tag with <script type=application/ld+json> wrapper.

Nested types

Handles nested schema types (Person within Article, Offer within Product) correctly.

Rich result preview

Shows how the structured data might render in Google search results.

Multiple entities

Generate one schema or combine multiple (e.g., Article + FAQPage + BreadcrumbList) on one page.

Client-side only

Proprietary business data (product prices, recipes, events) stays in your browser.

How to use the Schema Markup Generator

  1. 1

    Pick schema type

    Choose from Article, Product, Recipe, FAQ, Event, and other common types.

  2. 2

    Fill in fields

    Enter required and optional fields via the structured form.

  3. 3

    Add nested types

    For fields like author or location, fill in nested Person or Place forms.

  4. 4

    Generate JSON-LD

    Click generate to get the full script tag ready to paste.

  5. 5

    Paste into HTML

    Add the <script type=application/ld+json> block to the <head> or at the end of <body> of your page.

Common use cases for the Schema Markup Generator

Content SEO

  • Blog article markup: Add Article schema to blog posts for potential inclusion in Google News-style rich results.
  • Recipe site rich cards: Generate Recipe schema with cook time, ingredients, and ratings for recipe rich snippets.
  • FAQ accordions: Add FAQPage schema to FAQ pages so Google can display questions directly in search results.

E-commerce

  • Product listing: Add Product schema with prices, ratings, and availability for rich product results.
  • Review aggregation: Display star ratings in search with AggregateRating schema.
  • Offer and pricing: Mark up sale prices, deals, and limited-time offers for search visibility.

Local business

  • Google Business integration: Add LocalBusiness schema with address, hours, and contact info for Google Business enrichment.
  • Event promotion: Event schema for concerts, conferences, webinars to appear in event search results.
  • Organization identity: Add Organization schema for brand knowledge panel eligibility.

Schema Markup Generator — examples

Simple article

Blog post schema.

Input
Article: "Best Productivity Tools", author Ana Kowalski, published 2024-05-05
Output
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Best Productivity Tools",
  "author": { "@type": "Person", "name": "Ana Kowalski" },
  "datePublished": "2024-05-05"
}

FAQ

Question and answer markup.

Input
FAQ with 3 questions
Output
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    { "@type": "Question", "name": "Q1", "acceptedAnswer": { "@type": "Answer", "text": "A1" } },
    ...
  ]
}

Recipe

With cook time and ingredients.

Input
Chocolate chip cookies recipe
Output
Recipe schema with name, image, recipeIngredient array, recipeInstructions array, cookTime: PT20M, totalTime: PT35M, nutrition

Product

E-commerce listing.

Input
Wireless Headphones $89.99
Output
{
  "@type": "Product",
  "name": "Wireless Headphones",
  "offers": {
    "@type": "Offer",
    "price": "89.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}

Breadcrumbs

Navigation markup.

Input
Home > Tools > JSON Formatter
Output
BreadcrumbList with 3 ListItem: position 1/2/3, names, and URLs

Technical details

Schema.org is a collaborative project (Google, Microsoft, Yahoo, Yandex) defining vocabulary for structured data on the web. Over 800 types covering articles, events, products, places, people, and more.

JSON-LD is the preferred format. Recommended by Google over microdata or RDFa. Looks like:

<script type=\"application/ld+json\">
{
\"@context\": \"https://schema.org\",
\"@type\": \"Article\",
\"headline\": \"Title\",
\"author\": { \"@type\": \"Person\", \"name\": \"Ana Kowalski\" },
\"datePublished\": \"2024-05-05T12:00:00Z\"
}
</script>

@context: always https://schema.org
@type: the schema type (Article, Product, Recipe, etc.)
Remaining properties: fields defined by that type

Common types and their key fields:

Article: headline, image, datePublished, dateModified, author, publisher.

Product: name, image, description, brand, offers (with price, priceCurrency, availability), aggregateRating.

Recipe: name, image, description, author, cookTime (ISO 8601 duration), recipeIngredient, recipeInstructions, nutrition.

FAQPage: mainEntity array of Question objects, each with name (question) and acceptedAnswer.

Event: name, startDate, endDate, location (Place), offers.

LocalBusiness: name, address (PostalAddress), telephone, openingHoursSpecification, geo (GeoCoordinates).

BreadcrumbList: itemListElement array of ListItem objects with position, name, item (URL).

Organization/Person: similar fields for brand/individual identification.

Rich results requirements vary by type. Recipes need specific fields for the recipe card; without them, you get no rich result even with valid JSON-LD. Google\u2019s Rich Results Test validates against these specific requirements.

ISO 8601 dates and durations: structured data uses ISO 8601. Duration format is PT1H30M (1 hour 30 minutes), PT20M (20 minutes), etc.

Nested types: many fields expect other schema types. A Product\u2019s offers field is an Offer type, which has price, priceCurrency, availability, etc.

Validation: JSON syntax + schema.org type compliance + Google rich result requirements. This tool handles the first two; Google\u2019s Rich Results Test covers the third.

Common problems and solutions

Missing required fields

Each schema type has required fields for rich results. Recipe requires name, image, cookTime, ingredients. Missing any field means no rich result despite valid JSON-LD. The tool validates required fields.

Wrong date format

Structured data requires ISO 8601 dates (2024-05-05T12:00:00Z). Locale-specific formats (5/5/2024) fail. The tool outputs correct ISO format.

Duration format

ISO 8601 duration (PT1H30M) looks strange but is required. Time: PT means time period, then Hours/Minutes/Seconds. 20 minutes = PT20M.

Schema type wrong

Using SoftwareApplication when you meant WebApplication, or Article when you meant BlogPosting, changes what rich result is eligible. Check schema.org hierarchy to pick the most specific type.

JSON syntax errors

Missing commas, unquoted keys, trailing commas all break JSON. Always validate before publishing. Google’s Rich Results Test catches this.

Conflicting markup

Don’t mix JSON-LD, microdata, and RDFa for the same entity. Pick one (JSON-LD recommended). Mixing causes Google to apply arbitrary priority rules.

Fake or misleading markup

Google penalizes structured data that doesn’t match visible page content. Don’t claim ratings, prices, or features the page doesn’t show.

Schema Markup Generator — comparisons and alternatives

Compared to writing JSON-LD by hand, this tool structures the input via forms and validates as you go. Hand-writing JSON-LD works but is error-prone for complex schemas.

Compared to Google\u2019s Structured Data Markup Helper (discontinued), this tool is a modern replacement with more schema types and JSON-LD output.

Compared to specialized schema plugins (Yoast, Rank Math), this tool is framework-agnostic. Plugins integrate with WordPress; this tool works for any stack.

Frequently asked questions about the Schema Markup Generator

What is schema markup?

Structured data in HTML that describes page content using schema.org vocabulary. Helps search engines understand content and can enable rich results (enhanced search snippets). Most commonly added as JSON-LD in a script tag.

Does schema markup help SEO?

Indirectly. It doesn’t directly affect ranking, but rich results (enabled by schema) improve CTR and search visibility. For recipes, products, and events, rich results are essentially required to compete.

What schema types are most useful?

Article for blog posts, Product for e-commerce, Recipe for food blogs, FAQPage for FAQ sections, LocalBusiness for physical stores, BreadcrumbList for navigation hierarchy. Start with the types most relevant to your content.

How do I test my schema markup?

Use Google’s Rich Results Test (search.google.com/test/rich-results). Paste your URL or HTML and it reports validity plus rich result eligibility. This tool generates valid JSON-LD; the Rich Results Test confirms Google-specific requirements.

Where should I put the JSON-LD?

In the <head> or at the end of <body>. Either works. <head> is common for clarity. Don’t split one entity across multiple script tags; each script tag should contain complete JSON.

Can I have multiple schemas on one page?

Yes. A product page can have Product, BreadcrumbList, and Review schemas. An article page can have Article, Organization (publisher), and FAQPage schemas. Use separate script tags or combine into a @graph array.

What is the difference between JSON-LD and microdata?

Both express the same schema.org data. Microdata uses HTML attributes (itemscope, itemtype, itemprop) inline with content. JSON-LD is a separate script block. Google recommends JSON-LD because it’s easier to maintain (no HTML restructuring).

Is my data private?

Yes. All generation runs in your browser. Product prices, recipe ingredients, business details — all stay local.

Additional resources

Advertisement

Related tools

All SEO Tools

Learn more

Explore more tools

200+ free tools that run in your browser.

Browse all tools →