Schema markup generator

Generate valid JSON-LD structured data for a business or organisation, so search engines can understand what your page represents.

Structured JSON-LD Schema Creator

Generate schema.org markup for local services or businesses. Structured schema helps Google display rich search results (reviews, price metrics, maps).

Business Type

Business Name

Business Website URL

Logo Image URL

Business Email

Phone Number

Street Address

City / Locality

Postal Code

Country Code

Price Range (e.g. ££)

JSON-LD Code Output

Copy-Paste Schema Script

How to use this tool

Search engines read your page as text and make educated guesses about what it means. Structured data removes the guessing: it states explicitly that this string is a business name, that one is a postcode, and this number is an opening hour — in a vocabulary (schema.org) that Google, Bing, Yahoo and Yandex jointly maintain.

The payoff is rich results. Correct structured data is what lets a recipe show a star rating in search, an event show its date, or a local business appear with its address and hours in a knowledge panel. Those enhanced listings occupy more space and attract more clicks than a plain blue link.

Why JSON-LD rather than Microdata

There are three ways to add structured data, and Google explicitly recommends JSON-LD. Unlike Microdata and RDFa, which scatter attributes throughout your HTML, JSON-LD sits in a single <script> block — usually in the <head> — completely separate from your markup.

That separation is the whole advantage. You can restructure your HTML without breaking your structured data, generate it server-side independently of your templates, and read it as one coherent object rather than reverse-engineering it from attributes spread across a page.

The rule that gets sites penalised

Structured data must describe content that is actually visible on the page. Marking up a review rating that appears nowhere, or listing opening hours you don't display, violates Google's structured data guidelines and can trigger a manual action that removes your rich results entirely — sometimes site-wide.

This is the most common way well-intentioned SEO work backfires. The safe rule: if a user can't see it on the page, don't put it in the schema.

Testing and building up

Always validate before shipping. Google's Rich Results Test shows which rich result types your markup qualifies for, and the Schema Markup Validator at validator.schema.org catches syntax errors and unrecognised properties. Search Console then reports errors it finds across your live site.

Start small. A correct LocalBusiness or Organization block with name, URL, logo and address delivers most of the value. Once that's validating cleanly, layer on the types that fit your content — FAQPage for question sections (this site uses it on every page), BreadcrumbList for navigation trails, Article for posts. Each type has required and recommended properties; missing a required one disqualifies the whole block, which is exactly what the validators are for.

Developer Implementation Guide: Injecting JSON-LD in Modern Apps

Search engines require schema markup to be present in the initial DOM. If you are building a Single Page Application (SPA) with React or Vue, injecting JSON-LD dynamically requires care to ensure crawlers actually see it.

React Implementation (Next.js / Gatsby)

The safest way to inject JSON-LD in a React component is by dangerously setting the inner HTML of a script tag. This prevents React from escaping the JSON string.


// components/LocalBusinessSchema.jsx
export default function LocalBusinessSchema({ businessData }) {
  const schema = {
    "@context": "https://schema.org",
    "@type": "LocalBusiness",
    "name": businessData.name,
    "image": businessData.logo,
    "telephone": businessData.phone,
    "address": {
      "@type": "PostalAddress",
      "streetAddress": businessData.street,
      "addressLocality": businessData.city,
      "postalCode": businessData.zip,
      "addressCountry": businessData.country
    }
  };

  return (
    <script
      type="application/ld+json"
      dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }}
    />
  );
}

Ensure this component is rendered inside the <head> of your document if possible, though Googlebot will parse JSON-LD even if it's placed in the <body>.

Frequently asked questions

What is JSON-LD and why does Google prefer it?

JSON-LD is structured data expressed as a JSON object inside a single script tag, separate from your HTML. Google recommends it because it does not depend on your markup structure — you can redesign a page without breaking the data.

Does structured data improve my ranking?

Not directly. It makes your page eligible for rich results — star ratings, FAQs, business details — which occupy more space in search and attract more clicks. The benefit is visibility and click-through rather than a ranking boost.

Can structured data get my site penalised?

Yes, if it describes content not visible on the page. Marking up ratings or details users cannot see violates Google’s guidelines and can trigger a manual action removing your rich results. Only mark up what is genuinely on the page.

How do I test my schema markup?

Use Google’s Rich Results Test to see which rich result types you qualify for, and the Schema Markup Validator at validator.schema.org for syntax errors. Search Console then reports issues found across your live site.