All posts
SEO & AI search

What Is JSON-LD? A Plain-English Definition

What is JSON-LD? A plain definition of the schema format Google recommends, a copy-paste Organization example, and what JSON-LD can and can't do for AI search.

By Mehdi Hassan4 min read

The short answer

JSON-LD is a format for adding structured data to a web page: a small block of code, placed in a script tag, that describes the page's content in schema.org vocabulary, such as who the organization is or who wrote an article. Google recommends JSON-LD because it sits apart from the visible HTML and is easy to maintain.

Key takeaways

  • JSON-LD is the code format. Schema.org is the vocabulary it uses. Rich results are one possible outcome.
  • It lives in a script tag, separate from your layout, so you can add or change it without touching the design.
  • Every startup site should ship Organization, Article and BreadcrumbList markup as basic hygiene.
  • Ahrefs' 2026 controlled test found no lift in AI citations from schema. Treat it as hygiene, not a hack.

Part of Web Design, SEO and AEO Glossary: 50 Terms Explained Simply

What is JSON-LD?

JSON-LD stands for JavaScript Object Notation for Linked Data. It's a way of writing facts about a page as labelled data that machines can read without guessing. Instead of a crawler inferring that a name in your footer is your company, JSON-LD states it: this is an Organization, this is its name, its logo and its social profiles.

It's one of three formats for schema markup, alongside Microdata and RDFa. Google's structured data documentation recommends JSON-LD where possible, and it's the format we use on every build. You'll find the related terms in our SEO and AEO glossary.

How is JSON-LD different from schema markup and Microdata?

JSON-LD is a format, schema markup is the general practice, and Microdata is an older format that mixes the same data into your HTML tags. The table shows where each fits.

Term

What it is

Where it lives

Schema.org

The shared vocabulary of types and properties

schema.org

JSON-LD

A format for writing that vocabulary

A script block in the page

Microdata

An older format using HTML attributes

Inside your visible markup

Rich result

An enhanced search listing some markup can earn

Google's results

Because JSON-LD is separate from the layout, a redesign doesn't break it. With Microdata, moving a component can silently drop the markup, which is a common issue we check when we handle migrating metadata and schema between platforms.

What does a JSON-LD example look like?

A JSON-LD block is a short list of labelled facts inside a script tag of type application/ld+json. The Organization example below is the one most startups should add first, usually on the homepage.

Copy-paste Organization example (replace the placeholder values)

Place this inside a script tag with type="application/ld+json" in the page head:

{ "@context": "https://schema.org", "@type": "Organization", "name": "Example Analytics", "url": "https://www.example.com", "logo": "https://www.example.com/logo.png", "sameAs": ["https://www.linkedin.com/company/example-analytics", "https://x.com/exampleanalytics"] }

The sameAs list matters most for entity understanding: it ties your site to your official profiles, so search engines and AI systems can connect them as one company. Test the result with Google's Rich Results Test or the Schema Markup Validator before you ship.

On a typical B2B site, we pair this with Article markup and a named author on blog posts, BreadcrumbList on every page, and DefinedTerm on glossary entries like this one.

JSON-LD helps search engines understand your entities clearly, but there's no evidence it gets you cited more by AI engines. Ahrefs' controlled 2026 schema test found no lift: AI Overview appearances fell 4.6%, while AI Mode and ChatGPT stayed flat.

So ship it for hygiene and rich-result eligibility, and put the real effort into the visible copy. The evidence is summed up in does schema markup help AI citations, and the wider build checklist is in how to build an AI-search-ready website.

Frequently asked questions

Where do I put JSON-LD on a page?
Put it in a script tag with the type application/ld+json, usually in the page head, though Google also reads it in the body. In Webflow and Framer you can add it through custom code settings per page or per CMS template. In Next.js, it's typically rendered as part of the page component so each page outputs its own data.
Can JSON-LD be added with Google Tag Manager?
Google can read JSON-LD injected by JavaScript, including through Tag Manager, but it's less reliable than server-rendered markup because it depends on the script running. Many AI crawlers don't execute JavaScript at all. If you can, render JSON-LD in the page's HTML so every crawler sees it on the first request.
How do I test my JSON-LD?
Use Google's Rich Results Test to see which rich results a page is eligible for, and the Schema Markup Validator to check the syntax against schema.org. After launch, Search Console's enhancement reports flag errors across the whole site. Test after every template change, because a broken bracket can silently invalidate the whole block.
Is JSON-LD the same as llms.txt?
No. JSON-LD is an established structured data format that search engines document and support. llms.txt is a proposed text file listing pages for language models, and Ahrefs found 97% of llms.txt files got zero requests. Our view on whether to bother is in [llms.txt: should your website have one](/blog/llms-txt-worth-it), but JSON-LD is the one with real support.

· CEO & Design Director

Copywriter, designer and developer, and founder of Designify Studio. Over five years, 60+ projects across 14+ industries, for startups that have raised $300M+.

Want this done for you? Website, $8,000.

A multi-page marketing site, designed by us, developed in Next.js and animated. $8,000, one-time, up to 6 pages. Book a free 30-minute call to see if it fits.

Schedule Call