Schema Markup Generator v2.1
Generate clean, valid JSON-LD structured data for 20+ schema types — Article, Product, Local Business, Event, Recipe, FAQ, HowTo, Breadcrumb, Job Posting and more. Fill a simple form and get ready-to-paste markup, with live required-field checks, Google rich-result warnings, and one-click validation.
About Schema Markup Generator
A schema markup generator is a tool that turns a simple form into valid JSON-LD structured data, the code format Google recommends for telling search engines what a page is actually about. Writing that code by hand means reading schema.org documentation, nesting objects correctly, and catching every stray comma before the block breaks. The ToolsPivot Schema Markup Generator v2.1 builds the markup live as you type across 20 schema types, checks your fields against Google's required and recommended properties, and tells you when a type no longer earns a rich result at all. Everything runs in your browser.
What the Schema Markup Generator Does
The tool converts form input into a ready-to-paste script type="application/ld+json" block. You pick a type, fill in the fields that matter for that type, and watch a nested JSON object assemble in real time. Empty fields get pruned rather than shipped as blank strings, which is a common failure in generated markup and something validators routinely flag as a warning.
Version 2.1 adds a layer most form-based generators skip. Instead of handing you syntactically valid code and wishing you luck, it parses what it just built, reads the @type, and checks that output against a built-in map of what Google actually requires for each rich-result type. You get a verdict before you paste, not after Search Console tells you three weeks later.
The tool is aimed at people who ship structured data without a schema platform behind them: freelance developers handling client sites, in-house SEOs on WordPress or Shopify, agency staff prototyping markup before a developer templates it, and content teams who need Article or Recipe blocks that survive a validator. ToolsPivot built v2.1 around the assumption that the hard part is not generating JSON, it is knowing whether the JSON you generated will do anything.
How ToolsPivot Schema Markup Generator Works
- Pick a type. Select from the dropdown of 20 schema types. The form for that type loads on demand with only the fields that type needs.
- Fill the form. Each field maps to a path in the JSON object. The output panel rebuilds on every keystroke, so you see the block take shape as you go.
- Add list items where needed. FAQ, HowTo, and Breadcrumb use add and remove repeater rows that build the correct arrays: question sets, ordered steps, and positioned list items.
- Read the verdict. Green means complete. Amber means eligible but missing recommended fields. Red means a required property is absent, and the tool names which one.
- Combine or export. Hit Add to @graph to collect several blocks into one connected graph, or use Copy, Copy raw JSON, or Download .json.
- Test before publishing. The Test (Rich Results) and Validate (Schema.org) buttons open Google's current validators in one click.
All 20 Supported Schema Types
The type list covers four practical groupings rather than trying to mirror all of schema.org's vocabulary, which runs to hundreds of types most sites will never use.
| Category | Types |
|---|---|
| Business and places | Local Business, Restaurant, Hotel, Organization, Service |
| People and content | Person, Article / Blog / News, Book, Video, Review |
| Commerce | Product, Event, Job Posting, Course, Software Application |
| Site and lists | Website, Breadcrumb, FAQ Page, HowTo, Recipe |
Restaurant and Hotel matter more than their obscurity suggests. Both are subtypes of Local Business with extra properties Google reads, and using the parent type when a child type fits costs you specificity. Service and Course tend to be missing from lighter generators, which pushes people toward hand-editing a Local Business block into something it was never meant to be.
Live Validation Against Required and Recommended Properties
Google splits structured data properties into two tiers, and confusing them is where most rich-result eligibility quietly dies. Required properties are the ones without which your content will not be considered for the rich result at all. Recommended properties are optional for eligibility but improve how your result can be displayed and how confidently Google can interpret it.
A Product block missing offers is not a slightly weaker Product block. It is ineligible. The generator's amber and red states map directly onto that distinction, so an amber verdict means you can publish and still qualify, while red means paste this and nothing will happen.
What the check does:
- Reads the real output: validation runs on the generated JSON, not on form state, so it reflects what you would actually paste.
- Never counts empty as filled: a whitespace-only field does not satisfy a required property.
- Names the gap: the verdict lists exactly which properties are missing rather than showing a generic warning.
- Works per type: the required and recommended map differs for each rich-result type.
Once markup is live, the follow-through matters as much as the block itself. Confirm the marked-up pages are actually indexed with the index checker, and make sure your robots.txt is not blocking the very URLs you just marked up.
FAQ and HowTo Rich Results: What Actually Changed
Selecting FAQ or HowTo shows a deprecation banner, because both features are gone from Google Search and a lot of tooling has not caught up. This is the single most common piece of outdated advice in the structured data space right now.
FAQ rich results stopped appearing in Google Search on May 7, 2026, announced through a quiet note added to Google's own documentation rather than a blog post. The Search Console FAQ search-appearance filter, the rich result report, and FAQ support in the Rich Results Test were removed in June 2026, and Search Console API support for FAQ rich result data is scheduled to end in August 2026. This was the end of a three-year retreat: back in August 2023 Google had already restricted FAQ rich results to well-known authoritative government and health sites, so most commercial publishers lost that visibility years earlier without noticing. HowTo rich results were deprecated over the same 2023 period.
Here is the part worth being precise about. FAQPage and HowTo remain valid schema.org types. The markup does not throw errors, does not trigger a manual action, and does not damage rankings if you leave it in place. Google removed the SERP feature, not the vocabulary. Other crawlers, including Bing and various AI retrieval systems, still parse it. What ended is the reason most people added it: extra pixels in the results page.
So the generator still builds both types, because building valid FAQPage markup is a legitimate thing to want. It just refuses to let you believe you are buying a dropdown that no longer exists. If your goal was visibility in AI answers rather than a rich result, structured data is only part of that picture, and running a GEO audit or publishing an llms.txt file addresses it more directly than FAQ schema ever did.
Combining Multiple Blocks Into One @graph
A real page usually needs more than one schema type. A product page might legitimately carry Product, Organization, and BreadcrumbList. You can ship those as three separate script blocks and Google will read them, but they float as three unconnected islands with no stated relationship to each other.
The Add to @graph button collects blocks into a single connected @graph array under one @context. The counter shows how many blocks you have staged, and Copy @graph gives you the combined output. This matters most for the entity relationships search engines and language models use to work out that the Organization publishing the Article is the same Organization that runs the site.
Two things to avoid regardless of format: never put duplicate Organization or WebSite blocks on the same page, and do not hardcode prices or dates that will go stale the moment your catalog changes.
Choosing the Right Schema Type
Picking a type that does not match the page is the most common structured data mistake, and accuracy beats volume every time. Google can ignore or reject markup that describes something the page does not contain.
- Company homepage: Organization for who you are, social profiles, and contact routes.
- Physical storefront: Local Business instead, since it carries address, hours, and geo data that feed local results.
- Restaurant or hotel: use those specific types rather than generic Local Business.
- Individual product pages: Product with its own price and availability, never on category pages.
- Author and team profiles: Person, which helps connect published content to a real identity.
- Blog posts and news: Article, with author and publisher properly nested.
- Homepage sitelinks search: Website with a search action.
If you want to see how a competitor structured their markup before deciding, the spider simulator shows you a page the way a crawler reads it. Schema also sits alongside the rest of your head-section signals, so pair it with clean meta tags and proper Open Graph tags for social previews, then confirm nothing conflicts using the meta tags analyzer.
Where the Tool Stands Apart
Plenty of free generators do the core job well, and it would be dishonest to pretend otherwise. Form-based input, live JSON-LD preview, no signup, and browser-only processing are table stakes across the category. Merkle's TechnicalSEO generator remains the most widely used free tool for good reason, and jsonld.com's April 2026 rebuild added live required-field validation of its own.
What is genuinely uncommon:
- Deprecation honesty: most generators still market FAQ schema as a route to rich results. One popular competitor's page currently promises that each question and answer will appear directly in search, which stopped being true in May 2026.
- @graph combining: free generators typically hand you one block at a time with no way to connect them.
- Current validator links: the retired Structured Data Testing Tool link was removed here. At least one competing generator still routes users to it.
- Translated field labels: the interface and all 162 form-field labels are available in 18 languages, not just the surrounding page copy.
Honest Limitations
The built-in validation is a pre-check, not a replacement for Google's Rich Results Test. It checks presence and shape against a per-type map. It cannot know whether the price you entered is the price on your page, whether your image URL resolves, or whether Google will choose to show a rich result for your particular query. Always confirm in the Rich Results Test before publishing.
Second, a green verdict means eligible, not guaranteed. Rich result display is Google's decision, made per query, and eligibility is only the entry ticket.
Third, and most important: everything you mark up must be visible to users on the page. Marking up content that is not there violates Google's guidelines and can trigger a manual action. Building self-serving reviews on your own business is the classic version of this, which is why ToolsPivot surfaces a warning when you try. Structured data describes a page. It does not substitute for one.
Real Scenarios Where This Changes the Work
A freelancer inherits a client site with stale FAQ markup. Templated FAQ blocks sit on 400 pages, added in 2021 to chase dropdowns. The developer opens the generator, sees the deprecation banner, and stops the planned rollout to another 200 pages. Google says unused markup is harmless, so the cleanup gets deprioritized rather than rushed, and the sprint goes to Article and Breadcrumb markup that still earns display instead.
An agency SEO builds a homepage graph. The client needs Organization, Website, and Breadcrumb on one page. Rather than pasting three disconnected blocks, they stage each one, combine into a single @graph, download the .json, and hand it to the developer as one file. The entity relationships are explicit rather than inferred.
An e-commerce manager ships Product schema. Fifty best-sellers need markup. The red verdict on the first block flags a missing required property immediately, before it gets templated across the catalog. After deployment they track whether improved display correlates with movement using the keyword rank checker, and confirm the pages are crawlable through a current XML sitemap.
A publisher standardizes Article markup. Editors in four languages need the same block structure. Because the field labels are translated, each editor fills the form in their own language and produces identical English-key JSON-LD. Alongside a broader website SEO audit and a page speed check, the markup becomes one consistent part of the template rather than a per-editor guess.
Frequently Asked Questions
What is a schema markup generator?
A schema markup generator is a browser-based tool that builds structured data code in JSON-LD format from simple form inputs. You select a type, enter your details, and copy ready-to-paste code instead of writing it by hand against schema.org documentation.
Is the ToolsPivot Schema Markup Generator free?
Yes, it is free with no signup, no API keys, and no usage limits. Nothing you enter is uploaded, because all processing happens in your browser.
How many schema types does the tool support?
It supports 20 types, spanning business and places, people and content, commerce, and site structure. That includes less commonly offered types like Book, Service, Hotel, Course, and Software Application.
Does the tool send my data to a server?
No. Generation and validation both run client-side in JavaScript. The form fields themselves are served from a translation helper, but the values you type are never transmitted.
Does schema markup improve Google rankings?
Schema markup is not a direct ranking factor. It makes pages eligible for rich results and helps machines interpret your content unambiguously, which are different benefits from a ranking boost.
Do FAQ rich results still work in 2026?
No. FAQ rich results stopped appearing in Google Search on May 7, 2026, and Search Console reporting for them was removed in June 2026. HowTo rich results were deprecated back in 2023.
Should I remove FAQ schema from my pages?
Not urgently. FAQPage is still a valid schema.org type, Google has said unused structured data is harmless, and other crawlers still read it. Remove it only if it describes content that is no longer on the page.
What is @graph and when should I use it?
The @graph property collects multiple schema blocks into one connected array under a single context. Use it when one page legitimately carries several types, such as Product plus Organization plus Breadcrumb.
Where do I paste the generated JSON-LD?
Place the script block in your page's head or body section. On WordPress, a header-and-footer plugin or your SEO plugin's custom code field handles this without touching theme files.
Does the built-in validation replace Google's Rich Results Test?
No, it is a pre-check. It confirms required and recommended properties are present, but only Google's Rich Results Test can confirm eligibility on your live URL.
What is the difference between required and recommended properties?
Required properties are mandatory for rich-result eligibility, and missing one disqualifies the block entirely. Recommended properties are optional but improve how your result can be displayed and interpreted.
Can I use the tool in languages other than English?
Yes. The interface and all 162 form-field labels are translated into 18 languages. The generated JSON-LD keys stay in English, as the schema.org vocabulary requires.
