Free JSON-LD builder

Build a starting Organization JSON-LD block

Fill in your organization name and canonical URL and this page builds a starting Organization JSON-LD block with a stable #organization identifier, plus optional logo and sameAs identity references.

Google currently documents no required Organization properties; this builder produces a practical starting shape rather than claiming rich-result eligibility. The stable @id is an OpenForBots graph-consistency convention, and sameAs should contain only URLs that unambiguously identify the same entity.

Runs only in your browser Nothing sent to a server Review before publishing

Methodology reviewed 2026-10-04

Live preview

JSON-LD preview

This updates as you edit the fields above. Nothing is sent to a server.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Example Product",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "sameAs": [
    "https://www.wikidata.org/wiki/Q12345",
    "https://www.linkedin.com/company/example"
  ]
}
</script>

This is a generated starting point, not a verified fix and not a file already published on your site. Review every line, then publish it yourself.

More free tools

Try the other free AI discovery tools

Each tool looks at a different layer of AI discovery readiness. Use them together, or open the complete audit for all of it at once.

Check robots.txt rules for documented AI crawlers

Enter a public hostname to test whether its deployed robots.txt policy allows, blocks, or has no matching restriction for documented AI crawler tokens at the root path.

Check AI crawler rules

llms.txt checker and validator

Check the live /llms.txt file on a public website, or paste a draft to validate it before deployment. Both modes use the same rules for title, introduction, sections, links, malformed Markdown, duplicate destinations, and insecure URLs.

Inspect llms.txt

Check how clearly your website identifies the business and its entities

Compare visible homepage identity with structured entities, graph identifiers, sameAs identity references, and trust signals.

Check structure and identity

Check Recipe structured data on a food publisher page

Check the actual public recipe page for Recipe JSON-LD, Google-required fields, and selected recommended properties.

Check Recipe schema

Build a starting llms.txt file

Fill in a title, short context, and the resource links you want to list, and this page builds a valid llms.txt file for you to review, edit, and publish.

Build llms.txt

Build a starting robots.txt from a declared policy goal

Choose a declared policy goal and this page builds robots.txt groups for the documented AI crawler tokens that goal has an explicit preference for, which you can review, edit, and publish.

Build robots.txt

AI citation forensics

Paste a prompt and the source an AI answer cited. See which public evidence differs from your site, what is worth testing, and what no external audit can prove.

Compare the evidence

Business facts consistency checker

Compare the business name, phone, email, address, and official profiles stated on your homepage, About page, Contact page, and JSON-LD, and see where any value differs.

Check business facts

Website launch and migration check

Compare the new version of a site or page with the current live one under the same audit rules, and see regressions in crawler access, content, and identity before you launch.

Compare before and after

How this builder works

From a few fields to a file you can publish

Everything runs locally in your browser — there is no server round-trip and nothing is stored.

1
Enter your business or organization name and canonical URL.
2
The builder derives a stable <code>#organization</code> @id from the canonical URL so other JSON-LD nodes can reference the same entity consistently.
3
Add a logo URL when accurate and useful.
4
Add sameAs identity-reference URLs only when they unambiguously refer to the same organization, then review and copy or download the generated block.

Example generated output

An Organization block with a reusable identity

Your entered name, canonical URL, logo, and identity-reference URLs replace this example as you type.

Generated example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Example Product",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "sameAs": [
    "https://www.wikidata.org/wiki/Q12345",
    "https://www.linkedin.com/company/example"
  ]
}
</script>

Understand the output

What this builder creates—and what it cannot tell you

What it builds

A schema.org/Organization JSON-LD block with a practical name and url starting shape.
A stable @id based on the canonical URL plus #organization.
A logo property when a logo URL is entered.
A sameAs array with one entry per entered identity-reference URL.
A ready-to-publish <script type="application/ld+json"> tag.

What remains your responsibility

Google currently documents no required Organization properties; generated fields are a practical starting point, not a provider eligibility checklist.
Use the most specific Organization subtype that accurately represents the business when a more specific type is appropriate.
The generated block is a starting point; review every property before publishing it and keep it synchronized with visible public information.
This tool does not verify that entered URLs are reachable or that an external identity reference is authoritative.
Publishing valid JSON-LD does not prove that any AI or search system recognizes, indexes, ranks, cites, or displays the entity.

Learn and take action

Related guides and tools

Already have JSON-LD? Validate it

Check an existing deployed page for Organization, WebSite, and other supported structured-data entities.

Place structured data in the wider access, content, structure, identity, and verification workflow.

Questions about this builder

Does publishing this block guarantee AI or search visibility?

No. This tool only generates a starting block locally in your browser. Publishing structured data does not prove provider recognition, indexing, ranking, rich-result display, retrieval, or citation.

Why does the generator add @id?

OpenForBots adds a stable canonical fragment such as https://example.com/#organization so other JSON-LD nodes can refer to the same entity consistently. This is a graph-consistency convention, not a Schema.org or Google requirement.

What can I put in sameAs?

Use a URL to a page that unambiguously identifies the same organization. That can be an official website or profile and can also be an accurate authoritative reference such as Wikidata or Wikipedia. Do not add unrelated or ambiguous links.

Where do I put the generated block?

Place the generated <script type="application/ld+json"> tag on the page that describes the organization, commonly the homepage. Review the final markup in context before publishing; this tool does not deploy anything.