Pick a page profile
Choose Article, FAQ, Local business, Product, Web app, or About — the form fields update from the data model.
Build one connected JSON-LD @graph — Organization, Person, Article, FAQ and more, linked with @id nodes. Free schema generator that runs in your browser.
Privacy first · Nothing uploaded · One @graph, never isolated scripts
Scored fragmented schema in the AEO Readiness Checker? Rebuild it here as a single connected graph.
Loading the @graph generator…
One @graph, every node with an @id, cross-linked — not a pile of isolated schema scripts. That is the difference this free generator enforces in code.
Simple process
Choose Article, FAQ, Local business, Product, Web app, or About — the form fields update from the data model.
Enter the site root URL (every @id derives from it), Organization / Person / both, page URL, and type-specific fields.
Fix required errors, review yellow recommendations, then copy JSON or a ready <script> tag into your page.
A JSON-LD @graph is one script block that holds every schema entity on the page — Website, Organization, WebPage, Article, and so on — each with a stable @id. Entities point at each other by @id instead of duplicating nested objects. Connected graphs help search and answer engines resolve who wrote what, on which site, more reliably than scattered isolated scripts.
JSON-LD is the format Google recommends for structured data: a script block that describes the page's entities, such as the organisation, the article or the product, in schema.org vocabulary. Search engines and AI systems read it to understand what the page is about. It does not change what visitors see.
They solve different problems. JSON Schema validates the shape of JSON data in software, for example an API payload. JSON-LD adds meaning to web pages with schema.org types so search engines can read them. For SEO structured data you need JSON-LD; this tool generates JSON-LD.
Isolated scripts often repeat the same Organization or Person and never link the page to its publisher. This tool always emits one @graph and wires WebSite → publisher, WebPage → isPartOf / mainEntity, and Article → author / publisher automatically — you cannot accidentally export disconnected stubs.
No. The generator runs entirely in your browser. Form values never leave your device; there is no account and no upload step for the free builder.
Article / blog, FAQ, local business, product, web application / free tool, and personal About (ProfilePage). Each profile selects the node set and mainEntity wiring for that page type.
The FAQ profile does not emit a separate FAQPage stub. It upgrades the WebPage @type to FAQPage and places Question nodes in mainEntity — the correct pattern when the FAQ is the page itself. Answers must match visible page text word-for-word.