Free Schema Markup Generator: Create JSON-LD for Google

How to generate schema markup

1. Choose a schema type that matches the page. For articles, local businesses and apps, pick the exact @type too.
2. Fill in the fields. Red asterisks are required by Google; "recommended" fields improve how the result can appear.
3. Copy the code (with or without the <script> tag) or download the .json file.
4. Test it with our Schema Checker before publishing.

Which schema type should you use?

Required vs recommended fields

Google splits properties into two groups. If a required property is missing, the page isn't eligible for that rich result. Recommended properties are optional but help Google show more detail. A few things surprise people:

• Article and Organization have no required properties. Fill in the recommended ones anyway.
• Product needs name plus offers, a review or a rating. For merchant listings, Google also wants an image and a price above 0.
• Local business needs name and address.
• Event needs name, start date, location and address.
• Video needs name, thumbnail URL and upload date.
• Software app needs a price (0 if free) and a rating or review.

Why FAQ and HowTo aren't here

Most schema generators still offer FAQ and HowTo markup and promise rich results. Those results are gone:

FAQPage is still valid schema.org vocabulary, so it isn't harmful, but it won't produce FAQ dropdowns in Google. Spend the effort on types that still do something.

How to add JSON-LD to your site

• Any website: paste the <script type="application/ld+json"> block into the page HTML, in the head or body.
• WordPress: use your SEO plugin's custom schema feature (Rank Math and Yoast both have one) or a header/footer code plugin. Check the plugin isn't already outputting the same type.
• Next.js and other frameworks: render the JSON-LD in a script tag in the page component.
• Google Tag Manager: possible, but Google has to run JavaScript to see it. Adding it to the HTML is more reliable.

Example: Article JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Vet a Guest Post Site",
  "image": "https://example.com/images/vetting.jpg",
  "datePublished": "2026-10-24T09:00:00+06:00",
  "dateModified": "2026-10-24T09:00:00+06:00",
  "author": {
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://example.com/author/jane-doe"
  }
}
</script>

Example: Product JSON-LD

A product page with a price, stock status and real customer rating looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Guest Post Package: 5 Links",
  "image": "https://example.com/images/package-5.jpg",
  "description": "Five guest posts on relevant, vetted sites.",
  "brand": { "@type": "Brand", "name": "Example Co" },
  "offers": {
    "@type": "Offer",
    "price": "499.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/packages/5-links"
  }
}
</script>

Only add aggregateRating if the ratings are real and shown on the page.

Connecting items with @id and @graph

Bigger sites often output several items on one page: an Organization, a WebSite, a WebPage and an Article. Instead of repeating the organization's details in each, give it an @id (for example https://example.com/#organization) and point to it from the Article's publisher. Put the items in a single @graph array. Rank Math and Yoast both output schema this way, which is why their code looks long. It's valid; just make sure any custom schema you add doesn't duplicate an item the plugin already outputs.

After you publish: test and monitor

1. Check the live page with our Schema Checker to confirm the markup is in the HTML and has no errors.
2. Run Google's Rich Results Test on the URL to see which rich results it is eligible for.
3. Request indexing in Search Console if the page is new or important.
4. Watch the Enhancements reports in Search Console. Each supported type gets its own report listing valid items and errors across the site.
5. Be patient. Rich results can take days or weeks to appear, and Google may choose not to show them.

Mistakes to avoid

• Marking up content that isn't on the page. Google says structured data must represent the visible content.
• Relative URLs. Use full URLs such as https://example.com/logo.png.
• Wrong date formats. Use ISO 8601 (2026-10-24), not "24/10/2026".
• Self-serving review stars on your own business or organization.
• Duplicate schema from a theme, a plugin and manual code all at once.
• Forgetting to update prices, dates and availability when the page changes.

About this tool

• Privacy: the code is generated in your browser; nothing you type is sent to our server.
• Rules: required fields follow Google Search Central documentation, checked October 2026.
• Output: JSON-LD using the https://schema.org context, ready to paste.

Frequently asked questions