Schema.org JSON-LD Generator - Free Structured Data Tool

Schema.org Structured Data Generator

Generate valid JSON-LD structured data markup for your website in seconds. This free tool supports five common schema types — Article, FAQ, HowTo, LocalBusiness, and Organization — and outputs clean, spec-compliant code ready to paste into your pages. Structured data helps search engines understand your content and can unlock rich results that boost visibility in Google, Bing, and other search engines.

How to Use This Schema Generator

The generator works in four steps:

Choose a schema type. Select from five supported types: Article, FAQ, HowTo, LocalBusiness, or Organization. Pick the type that best matches the content of the page where you plan to add the markup.
Fill in the fields. Each schema type has its own set of required and optional properties. Required fields are marked — fill in as many optional fields as possible for maximum coverage. The form validates input in real time.
Preview the JSON-LD output. As you type, the tool generates a live preview of the JSON-LD code block. Review the output to make sure all values are correct and properly formatted.
Copy and paste into your site. Click the copy button to place the JSON-LD snippet on your clipboard. Paste it inside a <script type="application/ld+json"> tag in the <head> section of your HTML page (or use one of the methods described below).

After adding the markup, test it with Google’s Rich Results Test or the Schema Markup Validator to confirm there are no errors.

What Is Schema.org Structured Data?

Schema.org is a collaborative vocabulary created in 2011 by Google, Microsoft, Yahoo, and Yandex. It defines a standardized set of types and properties that describe entities — articles, businesses, products, events, people, and hundreds of other things — in a way that machines can parse reliably.

Structured data is the practice of embedding this machine-readable metadata into your web pages. When a search engine crawls a page that contains structured data, it can extract specific facts (an article’s author and publication date, a business’s address and opening hours, an FAQ’s questions and answers) without relying on natural language processing alone.

Why JSON-LD?

There are three formats for embedding structured data in HTML:

Format	Syntax	Google Recommendation
JSON-LD	JavaScript object in a `<script>` tag	Recommended
Microdata	HTML attributes (`itemscope`, `itemprop`)	Supported
RDFa	HTML attributes (`vocab`, `typeof`, `property`)	Supported

Google explicitly recommends JSON-LD. The key advantages are separation of concerns (the markup lives in a standalone script block, not woven into your HTML), easier maintenance (you can update structured data without touching page templates), and compatibility with tag managers and server-side injection. JSON-LD is also the only format Google supports for certain features like Speakable and some event types.

Why Structured Data Matters for SEO

Structured data does not directly influence rankings — Google has stated this repeatedly. What it does is qualify your pages for rich results (also called rich snippets or enhanced results), which change how your listing appears on the search engine results page (SERP).

Rich Results and CTR

Rich results can include star ratings, FAQ accordions, how-to steps, product prices, event dates, breadcrumbs, and more. Pages with rich results occupy more vertical space on the SERP and display additional information that standard blue links lack. According to a 2019 study by Milestone Research analyzing 4.5 million search queries, pages with structured data achieved a 40–50% higher click-through rate compared to those without. A separate analysis by Search Engine Land found that FAQ rich results increased organic CTR by up to 87% for some queries.

Types of Rich Results by Schema

Schema Type	Possible Rich Result	Where It Appears
Article	Top stories carousel, article snippet with image	Google Search, Google News
FAQPage	Expandable Q&A accordion below listing	Google Search
HowTo	Step-by-step carousel or list	Google Search, Google Assistant
LocalBusiness	Knowledge panel, Google Maps listing	Google Search, Google Maps
Organization	Knowledge panel with logo, social links	Google Search

Note that Google does not guarantee rich results even when valid structured data is present. Eligibility depends on content quality, policy compliance, and algorithmic decisions. However, without the markup, rich results are impossible for most of these features.

Competitive Advantage

Despite the clear benefits, structured data adoption remains relatively low. A 2023 analysis by Ahrefs found that less than 35% of websites use any form of schema markup. For smaller businesses and niche publishers, implementing structured data correctly is a low-effort, high-impact optimization that most competitors are still ignoring.

Supported Schema Types Explained

Article Schema

The Article schema type (and its subtypes NewsArticle and BlogPosting) is designed for news stories, blog posts, opinion pieces, and editorial content. It tells search engines who wrote the article, when it was published and last modified, and what it is about.

Required properties: headline, image, datePublished, author.

Recommended properties: dateModified, publisher, description, mainEntityOfPage.

Article markup is valuable for any site publishing editorial content. It enables eligibility for Google’s Top Stories carousel (especially for news content) and can surface author and date information directly in the SERP snippet. Example:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Google Rolls Out March 2026 Core Update",
  "image": "https://example.com/images/core-update.jpg",
  "author": {
    "@type": "Person",
    "name": "Marcus Chen"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Inimino",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "datePublished": "2026-03-15",
  "dateModified": "2026-03-16"
}

FAQ Schema

The FAQPage schema is for pages that contain a list of questions and answers authored by the site owner (not user-generated Q&A — that uses QAPage). When Google processes valid FAQ markup, it can display expandable question-and-answer accordions directly in the search results.

Required properties: mainEntity (an array of Question items, each with an acceptedAnswer containing a Text value).

FAQ schema is particularly effective for service pages, product pages, and support content. It also maps well to Google’s “People Also Ask” feature. Limit FAQ items to 5–10 per page for best results — Google may truncate listings with excessive questions. Example:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is structured data?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Structured data is machine-readable metadata added to web pages using a standardized vocabulary like Schema.org."
      }
    },
    {
      "@type": "Question",
      "name": "Does structured data improve rankings?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Structured data does not directly boost rankings, but it enables rich results that can significantly increase click-through rates."
      }
    }
  ]
}

HowTo Schema

The HowTo schema describes a set of steps to accomplish a task. Google can display these steps as a visual carousel or numbered list directly in search results. It is suitable for tutorials, DIY guides, recipes (though Recipe is preferred for cooking), and process documentation.

Required properties: name, step (array of HowToStep with text).

Recommended properties: image, estimatedCost, totalTime, tool, supply.

Each step should describe one discrete action. Avoid combining multiple actions into a single step. Adding images per step increases the likelihood of a visual rich result. Example:

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Add JSON-LD to WordPress",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Generate the markup",
      "text": "Use a JSON-LD generator to create the structured data code for your page."
    },
    {
      "@type": "HowToStep",
      "name": "Copy the code",
      "text": "Copy the generated JSON-LD script block to your clipboard."
    },
    {
      "@type": "HowToStep",
      "name": "Add to your theme header",
      "text": "Paste the script into your theme's header.php or use a plugin like Insert Headers and Footers."
    }
  ]
}

LocalBusiness Schema

The LocalBusiness schema (and its many subtypes like Restaurant, Dentist, LegalService) is essential for businesses with a physical location. It powers local search features including Google Maps integration, the local knowledge panel, and business information cards.

Required properties: name, address (with streetAddress, addressLocality, addressRegion, postalCode, addressCountry).

Recommended properties: telephone, openingHoursSpecification, geo (latitude/longitude), image, priceRange, url.

For multi-location businesses, create separate LocalBusiness markup for each location on its respective page. Do not place all locations on a single page. Include accurate geographic coordinates — they improve accuracy in Google Maps results.

Organization Schema

The Organization schema describes a company, nonprofit, school, or other entity. It is typically placed on the homepage or About page and feeds into Google’s Knowledge Graph, helping populate the brand knowledge panel with a logo, social profiles, contact information, and founding details.

Required properties: name, url.

Recommended properties: logo, sameAs (array of social media profile URLs), contactPoint, foundingDate, description.

The sameAs property is particularly important — it establishes connections between your website and your official social media profiles on platforms like LinkedIn, X (Twitter), Facebook, and others. This helps Google verify brand identity and can populate the knowledge panel’s social links.

How to Add JSON-LD to Your Website

Once you have generated your JSON-LD code, there are several ways to add it to your pages.

Direct HTML Insertion

The most straightforward method: paste the <script type="application/ld+json"> block into the <head> section of your HTML page. This works for any website regardless of platform.

<head>
  <title>Your Page Title</title>
  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "Your Company",
    "url": "https://example.com"
  }
  </script>
</head>

JSON-LD can technically appear anywhere in the HTML document (including the <body>), but placing it in the <head> is the convention and ensures crawlers process it before rendering page content.

WordPress Methods

For WordPress sites, you have several options:

SEO plugin: Plugins like AIOSEO, Yoast SEO, and Rank Math can generate and inject structured data automatically for articles, pages, and certain other types. However, they may not support all schema types or give you full control over properties.
Insert Headers and Footers plugin: Use a lightweight plugin like WPCode or Insert Headers and Footers to add custom code to the <head> section site-wide or per page.
Theme header: Add the script directly to your theme’s header.php file (or child theme). This works but is harder to manage for page-specific markup.
Custom field or block: Use a custom HTML block in the WordPress editor to add the JSON-LD script to individual posts or pages.

Google Tag Manager

Google Tag Manager (GTM) can inject JSON-LD dynamically. Create a Custom HTML tag, paste your JSON-LD script, and set it to fire on the appropriate pages. This is useful for marketing teams that manage structured data across many pages without developer access to the codebase. Be aware that Google has confirmed it renders JavaScript-injected structured data, but some SEO practitioners prefer static insertion for reliability.

Validation and Testing

After adding structured data, always validate it:

Google Rich Results Test — Tests whether your page is eligible for rich results. Shows detected structured data types and any errors or warnings.
Schema Markup Validator — Validates markup against the full Schema.org specification (not just Google’s subset). Useful for catching spec violations that Google’s tool might not flag.
Google Search Console — The Enhancements section shows structured data detected across your site over time, including error trends and affected pages.

Common Structured Data Mistakes

Even well-intentioned implementations can fail. These are the most frequent errors:

Missing Required Properties

Each schema type has mandatory fields. An Article without headline, an FAQPage without mainEntity, or a LocalBusiness without address will generate errors in Google’s testing tools and will not be eligible for rich results. Always check the Google Search Central documentation for the current list of required and recommended properties for each type.

Schema That Does Not Match Page Content

The structured data must accurately represent the visible content on the page. Adding FAQPage markup to a page that does not contain questions and answers, or using Article schema on a product page, violates Google’s structured data guidelines. This can result in a manual action (penalty) that removes rich results for your entire site.

Duplicating Schema Across Pages

Placing identical Organization or LocalBusiness markup on every page of your site is unnecessary and can confuse crawlers. Use Organization on the homepage or About page. Use Article on individual articles. Use FAQPage only on actual FAQ content. Each page should contain schema that is specific and relevant to that page’s content.

Not Testing After Implementation

Structured data can break silently — a theme update might alter the HTML structure, a CMS migration could strip script tags, or a developer might accidentally introduce a syntax error. Run periodic checks in Google Search Console’s Enhancements reports and revalidate with the Rich Results Test whenever you make significant site changes.

Outdated or Deprecated Types

Schema.org evolves, and Google periodically changes which types and properties it supports. For example, Google deprecated data-vocabulary.org markup in 2020 and has adjusted FAQ rich result display policies multiple times. Stay current with Google Search Central Blog announcements to avoid using deprecated markup.