zivooo
FREE JSON-LD GENERATOR

Free JSON-LD generator: every schema type in one linked @graph.

Updated

This JSON-LD generator builds one script block that holds several schema types at once, joined by @id: your Organization, your Website naming it as publisher, and the page's own Article, Product or breadcrumbs.

Tick the types the page needs, fill the short form for each, and copy one block. It runs in your browser, checks the graph before you copy, and needs no signup.

  • Free
  • No signup
  • Runs in your browser
Types in this block
Organization
Website
JSON-LD @GRAPHEXAMPLE
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://northwind-crm.com/#organization",
      "@type": "Organization",
      "name": "Northwind",
      "url": "https://northwind-crm.com",
      "logo": "https://northwind-crm.com/logo.png",
      "sameAs": [
        "https://www.linkedin.com/company/northwind"
      ]
    },
    {
      "@id": "https://northwind-crm.com/#website",
      "@type": "WebSite",
      "name": "Northwind",
      "url": "https://northwind-crm.com/",
      "publisher": {
        "@id": "https://northwind-crm.com/#organization"
      }
    }
  ]
}
</script>
ValidValid JSON-LD, with every field each type in the graph needs.
A graph per template, checked every month.Zivooo audits your structured data site wide and writes it into every article it publishes.
Start free, no card
WHAT THIS TOOL DOES

What the JSON-LD generator puts in the graph

Several types, one @context, and the links engines follow between them.

  • Seven types to combine

    Organization, WebSite, Article, Product, BreadcrumbList, FAQPage and LocalBusiness, in any mix.

  • One @graph, one @context

    A single script tag with every node inside, instead of a tag per type.

  • Stable @id on each node

    Built from your site's address, like yoursite.com/#organization, so other pages can point to the same node.

  • Links between nodes

    The Website and the Article name the Organization as publisher by its @id, not by repeating it.

  • Only the fields that count

    Each type asks for what Google requires, or what our audit checks where Google requires nothing.

  • A check on the whole graph

    The block is parsed back and each node tested against the required property rules our Schema Validator uses.

  • Script tag or bare JSON

    Copy or download either, with any less than sign escaped.

HOW IT WORKS

Five steps to one connected JSON-LD block.

  1. 01

    Tick the types

    Organization and Website are on to start.

  2. 02

    Fill each form

    Use your real site address: the @id values come from it.

  3. 03

    Watch the links

    Publisher references appear as you add nodes.

  4. 04

    Read the check

    Any empty field is named by type.

  5. 05

    Paste one block

    In the head of the page, or of every page for the site wide nodes.

WHY IT MATTERS FOR AI SEARCH AND GOOGLE

Why a linked JSON-LD graph beats loose blocks

JSON-LD stands for JavaScript Object Notation for Linked Data. The linked part is the point: an @id gives a node a name other nodes can refer to. Without it, a page with an Organization block and an Article block says two separate things; with it, the page says this article was published by this organization.

Search engines and answer engines build a picture of your brand from those connections. For SEO, one consistent Organization node with the same @id on every page removes doubt about who publishes the site. For GEO and AEO, an assistant reading your page finds the publisher, the website and the content joined up, instead of guessing which name belongs to which.

It also keeps your markup tidy. One block per page is easier to check than five from five plugins, and duplicate Organization blocks with slightly different names leave engines unsure which one is you.

HOW TO READ THE OUTPUT

Reading a JSON-LD generator's @graph output

The block opens with one @context, then an @graph list with a node per type you ticked. Each node starts with its @id, built from the address you entered for your Organization or Website.

The parts below are the ones to recognize. When you add the same Organization node to every page, keep its @id exactly the same each time.

The check turns green when the block parses, carries its schema.org context, and every node has its required fields. Confirm the live page afterwards with our Schema Validator, which reads it as served and after JavaScript.

PARTWHAT IT DOESEXAMPLE
@contextSays every type comes from schema.orghttps://schema.org
@graphHolds every node in one block[ Organization, WebSite, Article ]
@idNames a node so others can point to ithttps://northwind-crm.com/#organization
publisherLinks a Website or Article to its Organization{ "@id": "...#organization" }
@typeSays what each node isOrganization, WebSite, Article
HOW TO USE IT WELL

Getting a JSON-LD graph right across a site

  • Keep one @id per thing.

    Your Organization is https://yoursite.com/#organization on every page. Change it and engines see two companies.

  • Put site wide nodes in the layout.

    Organization and WebSite belong in the shared template; the page's Article or Product goes in that page's template.

  • Remove the duplicates.

    If a plugin already prints an Organization block, either turn it off or reuse its @id in your graph.

  • Use full addresses.

    Every url, logo and @id starts with https:// and your real domain, never a relative path.

Organization and Website in one graph, linked by @id, as the generator writes them:

JSON-LD @GRAPH
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://northwind-crm.com/#organization",
      "@type": "Organization",
      "name": "Northwind",
      "url": "https://northwind-crm.com",
      "logo": "https://northwind-crm.com/logo.png",
      "sameAs": ["https://www.linkedin.com/company/northwind"]
    },
    {
      "@id": "https://northwind-crm.com/#website",
      "@type": "WebSite",
      "name": "Northwind",
      "url": "https://northwind-crm.com/",
      "publisher": { "@id": "https://northwind-crm.com/#organization" }
    }
  ]
}
</script>
USE CASES

When one linked block is the better choice.

  • A custom built site: write the layout's Organization and Website graph once and ship it on every page.
  • A blog template: add the Article node to the graph so each post names your Organization as publisher.
  • Consolidating plugin output: replace three loose blocks with one graph that says the same thing once.
  • A headless or static site: generate the block here, then template the values in your framework.
  • Developer handover: send the exact graph to whoever owns the codebase, ready to paste.
GO FURTHER WITH ZIVOOO

Write the graph here. Zivooo checks it site wide.

Zivooo audits the structured data on every page of your site each month, on your own keys, flags pages where it only appears after JavaScript, and publishes each article it writes with its schema in place. $10 a domain a month after 7 days free, no card.

  • Structured data audited on every page monthly
  • Schema that only loads with JavaScript flagged
  • Articles published with their Article schema
  • Your brand tracked in ChatGPT, Gemini and Google
GENERATOR VS WRITING IT BY HAND

This JSON-LD generator vs writing the code yourself

Writing JSON-LD by hand is fine for anyone comfortable with JSON, and schema.org's own pages document every property. The trouble is the small things: a trailing comma that voids the block, an @id spelled two ways, a relative logo address. Most free generators write one type at a time, so you end up with loose blocks. This one writes the linked graph, keeps the @id values consistent, and checks the result before you paste it.

FAQ

JSON-LD, answered.

What is JSON-LD?

A way of writing structured data as JSON inside a script tag on the page. Search engines read it to learn what the page is about without parsing the layout.

What is an @graph in JSON-LD?

A list that holds several nodes in one block, sharing one @context. It lets you describe the organization, the website and the page together and link them by @id.

What should I use as the @id?

A full address that won't change, usually your site's URL with a fragment: https://yoursite.com/#organization. It never has to be a page that loads; it is a name.

Is one block better than several script tags?

Both are valid and Google reads both. One graph is easier to keep consistent and lets nodes point to each other without repeating themselves.

Where should JSON-LD go on the page?

In the head is tidiest. Google also reads it in the body, and reads it when JavaScript adds it, but crawlers that run no scripts only see it in the served HTML.

Does JSON-LD work for AI search?

It states your facts in a form every parser reads the same way. Google says its AI features need no special markup, so think of it as making your facts unambiguous rather than as a ranking lever.

Is anything I type sent to your servers?

No. The generator runs in your browser and makes no request, so there is nothing to sign up for and nothing stored.

One graph per page, checked every month.

Your keys, your costs, $10 a domain. 7 days free, no card.

Start free, no card