Schema Markup Generator — JSON-LD for Local Business, FAQ & More
Fill a form, get valid JSON-LD for Organization, LocalBusiness, Person, Article, Product, FAQ, Event or Breadcrumbs. Copy it into <head>.
A schema.org subtype; leave blank for LocalBusiness
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness"
}
</script>Paste inside <head> or at the end of <body>, then check it with Google's Rich Results Test or the Schema Markup Validator. Empty fields are omitted automatically.
Runs entirely in your browser. Nothing you enter is sent to us or stored. Structured data across a whole site, with stable entity IDs that connect pages, is part of our technical SEO work. See how we approach it.
Found a problem, or something that could be better? We read every message and we fix things quickly.
This free schema markup generator turns a short form into valid JSON-LD structured data for the eight schema.org types that matter most to a business website: Organization, LocalBusiness and its subtypes, Person, Article, Product, FAQPage, Event and BreadcrumbList. Copy the script tag into your page's head, test it with Google, and you are done; there is nothing to install and nothing is sent to a server.
Structured data tells search engines and AI answer engines what a page is about in a form they cannot misread: this is a dentist at this address with these hours, this article was written by this person on this date, this product costs this much and is in stock. Some types still earn rich results in Google (products, events, breadcrumbs, articles); others, such as FAQ markup, lost their visible rich result for most sites in 2026 but still feed entity understanding and AI-generated answers. The notes below say which is which, so you spend effort where it pays.
How to use
- Choose the schema type that matches the page: LocalBusiness for a location page, Article for a blog post, Product for a product page, FAQPage for a page whose main content is questions and answers.
- Fill in the fields. Use absolute URLs for images and links, ISO dates (2026-09-24) and, for events, full timestamps with time zone.
- Read the JSON-LD on the right; empty fields are omitted automatically, so leave anything you do not know blank rather than guessing.
- Copy the <script> tag into the page's <head> (or the end of <body>). One block per entity is fine; a page can carry several.
- Validate the live page with Google's Rich Results Test, and watch Search Console's Enhancements reports after a few days.
Frequently asked questions
Does schema markup improve rankings?
Not directly; Google says it is not a ranking factor. It can win rich results (stars, prices, event dates, breadcrumbs) that raise click-through rate, and it helps search engines and AI assistants understand and cite the page accurately. The honest expectation is better presentation and clearer entity understanding, not a jump in position.
Should I still add FAQ schema in 2026?
Google stopped showing FAQ rich results for most sites (only some government and health sites keep them), so do not expect expandable questions in the results. The markup is still valid and still helps answer engines extract Q&A pairs, and it costs nothing if the questions are already on the page. Do not create FAQ content just to carry the markup.
Where do I put the JSON-LD?
Anywhere in the HTML, typically inside <head>. Google also reads it from the body and from scripts injected by JavaScript after load, though server-rendered markup is the safest. Do not put it in an iframe or an external file.
JSON-LD or microdata?
JSON-LD. Google recommends it, it lives in one block instead of scattered attributes, and it is far easier to generate from a CMS or a template. Microdata and RDFa still work but are harder to maintain.
Can I mark up content that is not visible on the page?
No. Structured data must describe content the visitor can see. Marking up reviews that are not shown, prices that differ from the page, or FAQs that do not exist violates Google's guidelines and can earn a manual action that removes all rich results for the site.
What is the difference between LocalBusiness and Organization?
Organization describes a company as an entity (name, logo, contact, social profiles) and belongs on the site's home or about page. LocalBusiness describes a physical place customers visit, with address, hours and geo, and belongs on each location page. A business with one storefront often uses a LocalBusiness subtype (Dentist, Restaurant, Store) as its main entity.
Which types earn rich results today
• Product: price, availability and ratings in results (merchant listings and product snippets). Requires real offer data.
• Article: enhanced headline and image presentation, Top Stories eligibility for news.
• Event: date, venue and ticket details in results and Google's event surfaces.
• BreadcrumbList: the path shown instead of the raw URL under a result.
• LocalBusiness and Organization: knowledge panel details and entity understanding rather than a snippet.
• FAQPage: no longer a visible rich result for most sites; still useful for AI extraction.
Connecting entities across a site
The single most useful upgrade beyond this generator is giving each entity a stable @id (for example https://example.com/#organization) and referencing it from every page: articles point at the organization as publisher and at a person as author, location pages point at the parent organization. That turns isolated blocks into a graph search engines can follow, and it is the pattern this site uses. It is also the kind of site-wide work we do for clients.
Related free tools
- Meta Tag Generator — Fill in a page's title, description and social card details; get a complete, correctly escaped <head> block with live length counters.
- Robots.txt Generator — Build a robots.txt with presets for allow-all, blocking AI crawlers, staging and WordPress, with warnings for the mistakes that de-index sites.
- Open Graph Preview — Enter a URL and see the exact card Facebook, LinkedIn, X and Slack will show, every tag found, and what is missing.