Schema markup generator

What is a schema markup generator?

A schema markup generator is a tool that writes structured data from a form, so you never type JSON-LD by hand. Schema markup uses the schema.org vocabulary to state facts about a page, such as a product's price or a business's address, in a form search engines read. Google recommends the JSON-LD format, which this generator writes.

Writing it by hand goes wrong in small ways: a missing comma breaks the whole block, a price typed as "$89" is not the number Google asks for, and a value that contains a closing script tag ends the block early. A generator handles the syntax so that you can spend your attention on the part no tool can check: whether the values match the page.

Most generators stop at the syntax. This one also compares the result with the required and recommended property lists in Google's structured data documentation, the same lists Convertica's schema markup validator uses, read on October 13, 2026.

Schema markup examples, worked by the generator

The schema markup examples below are built by the same code as the tool above, from the example each type loads. The shop, its address, its prices and its people are made up. They show how the markup is written, not what a business should say, and each one meets every property Google requires for its type.

1. Organization schema for a home page

The form's default values give 13 properties, with a nested PostalAddress and two profile links in sameAs. Google lists no required property for Organization, so the check shows only the recommended properties that are still empty. Organization markup belongs on the home page or on the one page that describes the organization.

2. Product schema with an offer

A product with one offer, ready for both of Google's product features. The price is a number with a dot and no currency sign, and the currency is a separate three-letter code:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Trail Helmet",
  "image": "https://www.example.com/images/trail-helmet.jpg",
  "description": "A made-up helmet used to show the markup.",
  "brand": {
    "@type": "Brand",
    "name": "Example Gear"
  },
  "sku": "EX-HELM-01",
  "offers": {
    "@type": "Offer",
    "price": "89.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition",
    "url": "https://www.example.com/trail-helmet/"
  }
}
</script>

The check still lists gtin and mpn as recommended for Merchant listing. Add them if the product has them; never make one up.

3. Local business schema with opening hours

A store open Monday to Friday and on Saturday. "Monday to Friday" in the form becomes one OpeningHoursSpecification with five days in dayOfWeek, and the coordinates become numbers inside a GeoCoordinates item:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Store",
  "name": "Example Bike Shop",
  "url": "https://www.example.com/",
  "image": "https://www.example.com/images/storefront.jpg",
  "telephone": "+1-555-010-0199",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Example Street",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62701",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 39.7817,
    "longitude": -89.6501
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": [
        "Monday",
        "Tuesday",
        "Wednesday",
        "Thursday",
        "Friday"
      ],
      "opens": "09:00",
      "closes": "18:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "Saturday",
      "opens": "10:00",
      "closes": "16:00"
    }
  ]
}
</script>

4. Breadcrumb schema for a three-step trail

The generator numbers the steps itself, so position always runs 1, 2, 3 in the order of the rows. The last step has no URL, which Google's breadcrumb documentation allows for the current page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://www.example.com/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Helmets",
      "item": "https://www.example.com/helmets/"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Example Trail Helmet"
    }
  ]
}
</script>

5. A value that contains a closing script tag

Suppose a name is typed as Example </script><script>alert(1)</script> Shop. Pasted by hand into a script element, it would end the block and start a new script. The generator writes every < as the JSON escape \u003c:

"name": "Example \u003c/script>\u003cscript>alert(1)\u003c/script> Shop",

A JSON parser reads the name back exactly as typed. An HTML parser sees no tag in it, so the only closing script tag in the block is the one that ends it.

6. A product with mistakes

The image is typed as /images/trail-helmet.jpg, the price as $89 and the price end date as 12/31/2026. The generator leaves those three values out and says why under each field:

With those values left out, the check reports what Google requires and the markup lacks: offers.price or priceSpecification.price (Product snippet), image (Merchant listing), offers.price or priceSpecification.price (Merchant listing). The lowercase "usd" is not an error: the generator writes it as USD.

How to add schema markup to your website

To add schema markup to your website, paste the script block into the HTML of the page it describes, in the head or in the body. Google's introduction to structured data describes JSON-LD as a script tag in either place. Then follow four rules from Google's guidelines.

1. Mark up only what the page shows. Google's general structured data guidelines say not to mark up content that is not visible to readers of the page.
2. Put the markup on the page it describes. Product markup on that product's page, LocalBusiness on the location's page, WebSite on the home page.
3. Do not print the same item twice. If your theme or SEO plugin already prints Product or Organization markup, fix that block instead of adding a second one that may contradict it.
4. Change both together. When a price or opening hours change on the page, change the markup in the same edit.

In WordPress, Shopify or another CMS, look for the field your theme or plugin gives for custom head code or JSON-LD. Google also reads JSON-LD that a script adds to the page, which is how a tag manager adds it, but markup in the page's own HTML has one less thing that can fail.

How to test schema markup

1. Before you publish, paste the block into the schema markup validator. It runs in your browser and checks syntax, names and Google's lists.
2. After you publish, run the page through Google's Rich Results Test. It shows which rich results Google can read from the live page.
3. Use the Schema Markup Validator at schema.org for types Google has no rich result for, such as Person.
4. Open the page and compare the values with the markup by eye. No validator does this for you.

Related tools and guides

Schema markup is one part of making a page readable by machines. These cover the rest.