SEO Tools

Schema Markup Generator

Generate JSON-LD markup for local businesses, FAQs, products, and articles.

Worked example and publication checks

Browser-basedNo accountReady to use

Business name *Website *PhoneCategoryStreetCityPostal codeCountry

Output

JSON-LD is ready.

From input to publication

Worked example: a local shop contact page

This fictional shop has one public address. The goal is to describe that location on its contact page, without adding invented ratings or promises about search appearance. All example.com addresses below are illustrative.

Example inputs

Schema type: LocalBusiness
Business name: Northside Cycle Workshop
Website: https://example.com/contact/
Category: Store
Street: 12 Example Street
City: Vienna
Postal code: 1010
Country: AT
Phone: Leave blank for this example
Output: JSON only

Expected JSON output

{
  "@context": "https://schema.org",
  "@type": "Store",
  "name": "Northside Cycle Workshop",
  "url": "https://example.com/contact/",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 Example Street",
    "addressLocality": "Vienna",
    "postalCode": "1010",
    "addressCountry": "AT"
  }
}

Choose the entity before filling the form

Use this example for a physical shop. An online-only organization needs a different description; do not invent a street address to satisfy a validator. For two branches, create a separate location entry for each rather than combining their addresses.

The Category field becomes @type in the output. Enter a Schema.org type such as Store, not a marketing phrase such as Best bike repair. The visible contact page should show the same business name and address.

Put the result on the right page

In JSON-only mode, the output is data, not a complete HTML element. Switch to Script tag mode before adding it to an HTML page. Place the resulting application/ld+json script in the contact page head or body, outside any existing script element.

For WordPress, first check what your SEO plugin already outputs. If it owns the same business entity, update that configuration rather than adding a second contradictory copy through a custom HTML block. Preview the published source after clearing any page cache.

Separate syntax, meaning, and search eligibility

A JSON parser checks commas and quotes. The Schema.org validator checks the vocabulary. Google's Rich Results Test checks supported search features. A successful result at one level does not prove success at the others.

Start by testing the generated code, then test the real published URL. Compare the detected name and address with the page. Missing recommended fields deserve review, but should never be filled with fictional data just to remove a warning.

FAQ markup no longer produces Google FAQ rich results

Google discontinued FAQ rich results in May 2026. FAQPage remains a Schema.org type, and the generator can still describe visible questions and answers, but it should not be used with the expectation of FAQ expansions in Google Search.

Verification checklist

Enter the values above and compare the JSON with the example. There should be one Store with one PostalAddress and no telephone field.
Replace the fictional details with the real location. Inspect any existing structured data before adding another script.
Test both the code and the published URL. Confirm that crawlers can access the page and that the detected facts match the visible content.

Example and source review: September 9, 2026.

What this tool is for

Schema markup is structured data added to a page so search engines can understand entities, details, and relationships more reliably. For local businesses, products, articles, and FAQs, JSON-LD can clarify what the page is about, who operates the business, what is being offered, and which answers belong to the visible content.

This generator creates practical JSON-LD drafts for common website cases. It is especially useful for small business websites and client projects where structured data is often missing or copied from old templates. The output should be treated as implementation-ready markup only after the visible page content and business details have been checked.

How to use it

Choose the schema type that matches the visible page content.
Enter only facts that are actually present on the page or clearly true for the entity.
Generate the JSON-LD script and add it to the page head or body.
Validate the deployed page with a structured data testing tool before relying on it.

Other use cases

Local business page

Add name, address, phone number, URL, opening hours, and business category. Make sure the same details are visible on the page.

FAQ section

Generate FAQ structured data only for questions and answers that users can also read on the page. Hidden or unrelated FAQ markup is risky.

Article or guide

Use article markup for editorial content with a headline, author, publish date, and canonical URL. Do not use it for thin category pages.

Important notes

Structured data should describe the page, not add claims that users cannot verify on the page.
Use JSON-LD because it is easy to add, move, and validate without changing visible HTML structure.
Keep business data consistent with the website footer, contact page, Google Business Profile, and legal notice.

Limitations

Schema markup does not guarantee rich results or higher rankings.
Wrong or misleading structured data can create search quality problems.
The generator cannot verify every industry-specific field or local legal requirement.

Sources and review context

This page is maintained by Martin Trixner and was last reviewed on September 9, 2026. The tool output is based on public documentation and should still be tested against the target platform before production use.

Which schema type do I need?

LocalBusiness

For local businesses, service providers, stores, practices, and locations with an address or phone number.

FAQPage

For visible questions and answers. Google discontinued FAQ rich results in May 2026; this type does not restore that search feature.

Product

For product pages with a name, price, availability, image, and description.

Article

For blog posts, news, guides, and editorial content with an author and date.

Common mistakes

The markup describes content that is not visible on the page.
Required fields such as name, URL, price, or date are missing.
Multiple conflicting schema types are added to the same page.
FAQ markup is used for promotional copy instead of real questions and answers.

Test before publishing

Copy the JSON-LD markup into your page and then check it with a rich results or schema validator. The generator creates a solid starting point, but it does not replace a final review for your specific website.

FAQ

What is schema markup?

Schema markup is structured data that helps search engines better understand content such as businesses, products, FAQs, or articles.

Which format does the generator create?

The generator creates JSON-LD, the recommended script format for structured data on modern websites.

Should the markup still be tested?

Yes. Before publishing, you should check the result with a rich results or schema validator.

Can schema markup include information not visible on the page?

It should not. Structured data should describe content that users can also verify on the visible page.

Does schema markup guarantee rich results?

No. Valid markup can make a page eligible for certain features, but search engines decide whether to show them.

Where should JSON-LD be added?

JSON-LD is commonly added as a script tag in the head or body of the page. It should be present in the rendered HTML.

Optional usage statistics