Free Tool · Generator

Schema Markup Generator

Generate validated JSON-LD schema markup for 9 types — paste-ready for your site.

Schema type

Blog posts and editorial articles. Required for the Article rich result on Google. schema.org spec

Headline*

Google truncates headlines past ~110 characters in rich results.

Description

0/250

Article URL*

Featured image URL*

Recommended: 1200×630 PNG/JPG. Required for Article rich results.

Date published*

Date modified

Optional but recommended — signals freshness to Google + AI engines.

Author

Author name*

Author profile URL

Publisher

Publisher name*

Publisher logo URL

Section / category

Keywords

Word count

Missing required fields

Fill these to produce a valid Article (BlogPosting) schema: Headline, Article URL, Featured image URL, Date published, Author name, Publisher name.

JSON-LD output

json-ld

{
  "@context": "https://schema.org",
  "@type": "BlogPosting"
}

Paste-ready HTML embed

htmlDrop this inside your <head> tag

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting"
}
</script>

Validate against Google + schema.org

We don't run validation here — instead, paste the snippet above into Google's official testers (links below). They run the same parser Google uses for indexing.

Google Rich Results Test schema.org Validator

Tip: the testers accept pasted code OR a public URL — paste the embed snippet directly using the “Code” tab. Output length: 64 characters.

Automate it with Rankrize

Want schema on every article — automatically?

Rankrize generates FAQ schema, BlogPosting schema, BreadcrumbList, and Organization markup on every article it ships. Run a free site analysis to see the schema we'd add for your site.

Run free site analysisOne free per account · No credit card

How to use

How to use the Schema Markup Generator

Pick the most specific schema type that fits your page
An About page is an Organization. A blog post is a BlogPosting (more specific than Article). A pizzeria is a Restaurant (more specific than LocalBusiness). Specificity helps Google route your page into the right rich result format and helps AI engines describe you accurately.
Fill every required field — don't skip the recommended ones
Required fields are marked with a red asterisk and produce errors in Google's Rich Results Test if they're missing. Recommended fields (like dateModified, author URL, GTIN for products) aren't strictly required but they significantly improve eligibility for rich snippets and AI citation.
Use absolute URLs everywhere — never relative paths
Schema URLs must start with https:// (or http://). A relative path like /author/jane-doe will fail validation. The same goes for image URLs, sameAs profile URLs, and canonical URLs. If you don't have a specific page yet, use the homepage URL as a fallback.
Validate before you ship — every time
Paste the generated snippet into Google's Rich Results Test (link in the Validate panel) before you publish. The tester catches missing required fields, malformed dates, and type mismatches that would otherwise silently disqualify your page from rich results. Re-run it any time you change the schema.
Place the script in your page <head> — not the body
Google ignores JSON-LD outside the <head> on most page types. The 'Paste-ready HTML embed' panel produces the exact <script type="application/ld+json"> wrapper — drop it inside your page's <head> tag and you're done. Most CMSs (WordPress with a header-script plugin, Webflow, Framer, Shopify) support this out of the box.
Match the schema to what's actually on the page
Don't claim FAQ markup if the page doesn't visibly contain those questions and answers. Don't add Product schema if you're not selling that product. Google explicitly penalises schema mismatches as a manual action — every claim in your structured data must be reflected in the rendered page content.

Frequently asked questions

About the Schema Markup Generator

JSON-LD (JSON for Linked Data) is a JSON-based format for structured data. It lives in a <script type="application/ld+json"> tag inside your page's <head>. Google explicitly recommends it over older formats (Microdata, RDFa) because it's separate from the visible content — you can change rendered HTML without breaking schema, and you can add multiple schema types to a single page without polluting the markup.

Schema doesn't directly boost rankings, but it makes you eligible for rich results (FAQ accordions, star ratings, sitelinks search box, product cards, recipe rich results, etc) which dramatically increase your click-through rate. It also feeds AI search engines (ChatGPT, Claude, Perplexity, Gemini) the structured data they need to cite you accurately. Both downstream effects translate into more traffic.

Yes — every schema type in this tool is 100% free with no sign-up, no rate limits, and no watermark. You can build unlimited schemas. We make money from the paid Rankrize platform (rankrize.io) which automates schema generation as one stage of an 8-stage SEO content pipeline. The free tools exist to demonstrate quality.

Absolutely — and you should. A blog post page might combine BlogPosting (the article itself), BreadcrumbList (the navigation trail), Person (the author), Organization (the publisher), and FAQPage (if there's a Q&A section). Generate each one separately in this tool, then concatenate the <script> tags inside your page's <head>. Multiple JSON-LD blocks per page are explicitly allowed.

Google penalises self-referential and unverifiable reviews. Only emit AggregateRating schema if the ratings are real, collected from real customers, and visible on the page. Don't put 4.9 stars in your schema if your page doesn't show 4.9 stars to actual users. Google can issue manual actions for schema-spam — this is one of the most common reasons for being demoted from rich results.

BlogPosting (a sub-type of Article) is the right choice for blog posts and editorial articles — what most websites publish. NewsArticle is reserved for actual news media with reporting, datelines, and journalistic standards (Google News-eligible publications). Plain Article is the generic parent type — use the more specific BlogPosting unless you're a recognised news publisher. This generator emits @type: BlogPosting for the Article option.

Yes. AI engines parse the same JSON-LD that Google does — they use it to identify entities, extract pricing, and cite Q&A. Adding FAQ schema makes your Q&A more likely to appear in AI Overviews and Perplexity answers. Adding Product schema with proper pricing makes ChatGPT more likely to recommend you with the correct price. Schema is one of the highest-leverage things you can do for AI search visibility.

More free tools

The full Rankrize free toolkit

You're here