Schema Markup Generator

Next

Structured data is how search engines understand the difference between a page about a shoe and a page about a shoemaker. This generator produces a clean Schema.org JSON-LD snippet for one of four common types (Article, Product, LocalBusiness or Organization) using the core properties they all share: name, description, URL and image. It gives you a valid, copy-paste starting block that you extend with type-specific properties.

How to generate schema markup

  1. 1

    Pick a schema type

    Choose Article, Product, LocalBusiness or Organization based on the page you are marking up.

  2. 2

    Fill in the fields

    Enter the name, a description, the page URL and an image URL. Any field you leave blank is dropped from the output.

  3. 3

    Generate the JSON-LD

    The tool outputs a properly-formatted `<script type="application/ld+json">` block.

  4. 4

    Paste into the page head

    Drop it inside `<head>` or just before `</body>`. Google parses both positions equally well.

What this generator produces

This generator writes the shared core of a Schema.org entity: the @type you pick plus any of name, description, url and image you fill in. It is a clean, valid starting point that you round out with the properties each type needs for a rich result.

Supported types

Type Use it for
Article Blog posts, news stories and other editorial pages
Product A single product or item for sale
LocalBusiness A physical business with a storefront or location
Organization A company or brand as an entity

The output shape

Fill in a name, description, URL and image for a Product and you get:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Trail Running Shoe",
  "description": "Lightweight shoe for technical trails.",
  "url": "https://example.com/trail-shoe",
  "image": "https://example.com/trail-shoe.jpg"
}

wrapped in a <script type="application/ld+json"> block, ready to paste. Empty fields are omitted, so the snippet stays clean.

Going further

The four properties above are shared by every type, but a full rich result usually needs more. Add the type-specific properties by hand once you paste the block in:

  • Article commonly adds headline, datePublished and an author object.
  • Product commonly adds an offers object (price and availability) and aggregateRating.
  • LocalBusiness commonly adds address, telephone and openingHours.
  • Organization commonly adds logo and sameAs links to social profiles.

Tips that matter

  • Match the markup to the visible content. Google flags (and sometimes penalises) schema that describes things not on the page.
  • Use absolute URLs for the page and image, since relative URLs are sometimes silently ignored.
  • Test before shipping. Paste the snippet into Google’s Rich Results Test or a Schema.org validator to see which required fields your chosen type still needs.

Frequently Asked Questions

Google recommends JSON-LD and it is the easiest to maintain because it lives in a single script block, not sprinkled through the HTML. Microdata and RDFa are supported but fiddly, so stick with JSON-LD unless a CMS forces otherwise. This tool always outputs JSON-LD.

Not directly. Structured data is not a ranking signal by itself. What it does is unlock rich results, which usually lift CTR by 10-30%. The ranking lift comes from the CTR, not the markup.

Only the four that these types share: name, description, url and image, plus the @type you choose. It is a valid base snippet, so add the type-specific properties a rich result needs (for example offers for a Product, or datePublished for an Article) after you paste it.

Paste the generated block into Google’s Rich Results Test or a Schema.org validator. Because this generator fills in only the shared core properties, the validator will also tell you which type-specific required properties you still need to add.

Related Tools

Tool available in other languages