Schema JSON-LD Generator
Generate Schema.org JSON-LD markup for services, software, FAQs, and organisations. Copy-paste into your page head. Runs in your browser.
Schema JSON-LD Generator
Runs entirely in your browser — no server calls, no tracking.
Fill in the fields and click Generate schema.
🔒 Your data never leaves this tab. This tool has no backend.
About the Schema JSON-LD Generator
Schema.org JSON-LD is a block of structured data you place in your page's <head> to tell search engines the type and properties of your content in a machine-readable format. Google uses it to generate rich results — FAQ accordions, review stars, sitelinks, and product details in search results — and AI assistants use it to reliably extract facts about your business.
Which schema type to use
Service — for service pages (consulting, development, audits). SoftwareApplication — for tool or app pages, enables App Store-style rich results. FAQPage — for pages with Q&A sections; Google can show individual answers directly in search results. Organization — for your homepage or about page; establishes brand identity with Google. Article — for blog posts; enables date and author display in results. BreadcrumbList — for any page with a hierarchy; adds breadcrumb trail to the search snippet.
JSON-LD vs microdata
Google supports both JSON-LD and microdata (inline HTML attributes). JSON-LD is strongly preferred: it lives in one block in <head>, is easier to maintain, does not require changes to your visible HTML, and can be added or removed without touching the layout. All new schema should use JSON-LD.
Multiple schema blocks on one page are fine. A blog post might have Article + BreadcrumbList + FAQPage all as separate <script type="application/ld+json"> blocks, and Google processes them all independently.
Which schema types earn rich results
Structured data tells search engines what a page means rather than just what it says. Some types unlock visible rich results; most simply add machine-readable context.
| Type | Rich result |
|---|---|
| FAQPage | Expandable questions (now limited to authoritative sites) |
| Product | Price, availability, review stars |
| Recipe | Time, calories, rating, image |
| LocalBusiness | Hours, address, phone in local results |
| Article | Publication metadata; Top Stories eligibility |
| BreadcrumbList | Path instead of a bare URL |
| Organization | Knowledge panel signals |
Why JSON-LD rather than microdata
Google explicitly prefers JSON-LD. It lives in a single <script> block in the head, entirely separate from your markup, so you can change your design without touching structured data — and change structured data without risking your layout. Microdata and RDFa still work but interleave attributes through your HTML, which makes both harder to maintain.
The rule that gets sites penalised
Structured data must describe content that is visible on the page. Marking up FAQs that no visitor can see, or review stars for reviews that do not exist, is a spam violation and can trigger a manual action removing all your rich results. Everything in the JSON-LD should be findable in the rendered page.
Testing
Use Google's Rich Results Test to check eligibility and the Schema Markup Validator for general validity. They answer different questions: the first tells you whether Google will show a rich result, the second whether your markup is well-formed. Both matter.
Frequently asked questions
JSON-LD is structured data written as JSON inside a single script tag, kept separate from your visible markup. Google explicitly prefers it because it is easier to add, change and validate than microdata or RDFa, which interleave attributes throughout your HTML.
Product (price, availability, stars), Recipe, LocalBusiness, Article, BreadcrumbList and Event are the most commonly rewarded. FAQPage rich results are now restricted to authoritative government and health sites, though the markup still helps machines understand the page.
Yes, if it describes content that is not visible on the page. Marking up FAQs no visitor can see, or review stars for reviews that do not exist, is a spam violation and can trigger a manual action that removes all your rich results. Everything in the markup must be findable in the rendered page.
Use Google's Rich Results Test to see whether a page qualifies for a rich result, and the Schema Markup Validator to check the markup is well-formed. They answer different questions, so run both — valid markup can still be ineligible for a rich result.
Not directly. It makes pages eligible for rich results, which increase click-through by taking up more space and answering more of the query in the results page. The ranking position is unchanged; the traffic at that position often is not.
<script type="application/ld+json"> blocks to your <head>. Google processes each independently. A common combination for a service page: Service + BreadcrumbList + FAQPage (if the page has a FAQ section) + Organization on the homepage.Service for pages describing a service offering. Use LocalBusiness (or a subtype like ProfessionalService) for a physical business location with an address, opening hours, and a phone number. Remote-first or online-only businesses typically use Organization or Service.Need software built with SEO from day one?
ruxox builds production web products with proper schema markup, meta tags, and Core Web Vitals in the base build.