Customer Impact

SEO & GEO

How to Add JSON-LD to Your Website (and Get Found by ChatGPT, Claude & Google)

Copy for AI

You add JSON-LD as a small script in your page’s <head>.

That script tells Google, ChatGPT, Claude and Perplexity in plain facts who you are: your name, your logo, your profiles and how they connect.

The verdict: JSON-LD won’t make anyone cite you, but it removes the guesswork about who you are. For most B2B sites, an accurate Organization block plus Person is enough to start.

Curious how AI sees you? Ask us for a free GEO check of your page via our contact page, or run our GEO checker yourself.

What is JSON-LD, actually?

JSON-LD (JavaScript Object Notation for Linked Data) is a small script you place in your webpage, usually inside the <head> section.

It describes your content in a structured, machine-readable way. Search engines and AI systems can then contextually understand who you are, what a page is about, and how it relates to other entities on the web.

Our JSON-LD glossary entry gives the short definition.

Why “linked” is the key word

Without JSON-LD, a machine has to guess from your prose.

It has to work out that “Customer Impact” is a company. And that a LinkedIn URL belongs to that same organization.

JSON-LD states those relationships explicitly. It sits invisibly in your code, so it changes nothing about how your page looks.

Machines get a clean map of the facts. Our guide to the knowledge graph explains where those facts end up.

Why Google prefers JSON-LD

Google supports 3 formats for structured data:

  • JSON-LD: a script, kept separate from the visible text
  • Microdata: attributes inside your HTML tags
  • RDFa: an HTML5 extension that also uses tag attributes

Google says “all 3 formats are equally fine for Google, as long as the markup is valid.” But it still recommends JSON-LD “if your site’s setup allows it” (Google’s intro to structured data).

The reason: it keeps structured data separate from visible markup.

That makes it easier to maintain.

Why does JSON-LD help AI understand your site?

Because it hands the model an unambiguous summary of your entity.

Large language models like ChatGPT, Claude, Gemini and Perplexity build an internal picture of your brand from whatever they can read.

When your entity data is spread across unstructured sentences, that picture is fuzzy and easy to get wrong.

Structured data fixes that. It lists name, role, links, offerings and the connections between them.

Three concrete benefits

In practice we see three concrete benefits.

Fewer factual errors: when an AI answers “who is Customer Impact?”, explicit Organization markup reduces the chance it invents a wrong location, founder or service line.

Stronger entity association: the sameAs property ties your site to your LinkedIn, Instagram and other authoritative profiles. Engines then treat those as one entity rather than several loosely related pages.

This is the same entity consistency that underpins AI visibility. Our guide to sameAs schema goes deeper.

Better eligibility: valid schema is what makes a page eligible for Google rich results. And clean, well-structured facts are easier for an answer engine to lift into a response.

What Google’s own case studies show

Google’s documentation lists results from sites that added structured data:

GOOGLE’S STRUCTURED DATA CASE STUDIES What sites reported after adding markup Nestlé CTR of rich results +82% Food Network visits +35% Rotten Tomatoes CTR, about 100,000 pages +25% Source: Google Search Central, intro to structured data. Results of other sites, not a promise for yours.

Rotten Tomatoes, for instance, added markup to about 100,000 pages. Those pages saw a 25% higher click-through rate.

Those are Google search results, not AI citations.

But the mechanism is the same: clear facts are easier to show and to quote.

Be honest about the limits

JSON-LD is a trust signal, not a ranking guarantee.

It makes your facts legible, but it doesn’t force any model to cite you. Google is blunt about it: it “does not guarantee that your structured data will show up in search results.”

It works best alongside genuinely useful content and the other signals that make you worth quoting.

Want the full picture of getting quoted by AI? See becoming source material for AI answers.

Our experience: structured data for your organisation, people and products is the baseline. If you can’t state your positioning clearly, the model fills the gap and starts to hallucinate.

Which schema types matter (and what is each for)?

Visit schema.org and pick the type that matches your content.

Most B2B sites need only a handful. The table maps the common ones to their job, so you pick deliberately rather than copying whatever a generator defaults to.

Schema typeWhat it’s forGood fit when
OrganizationDescribes your company as an entity: name, logo, social profiles, founderYou want AI to know who your brand is (most B2B homepages)
PersonDescribes an individual: role, employer, profilesPersonal branding, author or team bio pages
ArticleMarks up a blog post or news pieceKnowledge base, blog and press content
LocalBusinessAdds address, opening hours and geo dataYou have a physical office or storefront
ProductDescribes a sellable product with price and availabilityEcommerce catalogues (rarely the right pick for services)
FAQPageMarks up question-and-answer pairsYou have a genuine FAQ block on the page
EventDescribes a webinar, workshop or conferenceYou host or promote events

The Product trap for service businesses

A common trap for service businesses is reaching for Product schema because it feels commercial.

For a B2B company the honest, accurate choice is almost always Organization, plus Person for the people behind it.

Pick the type that’s true, not the one that looks the most feature-rich. Our guide to product and service schema for B2B covers the edge cases.

Add the next layer once the basics work

For deeper cases, two types each solve a specific problem:

Author schema is the third one to add when you publish expert content.

How do you add JSON-LD to your website, step by step?

In five steps: choose the type, generate the code, add it, test it and keep it current.

JSON-LD Adding JSON-LD in five steps 01 Choose type match your page 02 Generate minimal, accurate 03 Add to site inside <head> 04 Test Rich Results 05 Maintain keep it current

Step 1: Choose the schema type

Match your page to one row in the table above:

  • Homepage: Organization
  • Team member page: Person
  • Knowledge article: Article

Google advises placing Organization on “your home page, or a single page that describes your organization” (Google’s Organization structured data docs). You don’t need it on every page.

Step 2: Generate the JSON-LD

You can write it by hand or use a helper, such as Google’s Structured Data Markup Helper or a schema generator.

Keep it minimal and accurate.

Here’s a compact Organization example:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Customer Impact",
  "url": "https://www.customerimpact.be",
  "logo": "https://www.customerimpact.be/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/customerimpact/",
    "https://www.instagram.com/customerimpact.be/"
  ],
  "founder": {
    "@type": "Person",
    "name": "Tanguy De Keyzer",
    "url": "https://www.tanguydekeyzer.com"
  }
}
</script>

Every value here should be a real, verifiable fact.

The sameAs array does quiet heavy lifting: it links your site to profiles engines already trust.

Required properties: Google lists none for Organization. It recommends “adding as many properties that are relevant to your organization.”

Logo: Google’s guidelines ask for an image of at least 112x112 pixels at a crawlable URL.

Step 3: Add it to your website

Insert the <script type="application/ld+json"> block, ideally inside the <head> of your HTML.

On WordPress you can add it through:

  • your SEO plugin (for example RankMath or Yoast, under the “Schema” section)
  • a custom HTML block in the header
  • your theme’s header.php file

On modern frameworks and headless setups, render it in your page head component.

Watch out: make sure a plugin and a manual block don’t both declare the same entity. That’s a frequent source of conflicts.

Our guide on how to implement schema markup walks through more CMS setups.

Step 4: Test it

Never ship structured data unvalidated. Paste your URL or code into:

Here’s the Schema.org Validator on our own English homepage:

Schema Markup Validator result for the customerimpact.be English homepage after adding JSON-LD: 2 items detected, WebSite and FAQPage, with 0 errors and 0 warnings The Schema Markup Validator on our own English homepage, October 2026. It detects WebSite and FAQPage, with 0 errors and 0 warnings.

Our page shows 2 items, 0 errors and 0 warnings. Aim for the same: zero errors, then review the warnings.

Warnings won’t block eligibility. But they often point at missing recommended properties worth filling in.

The Rich Results Test then shows which Google features the page qualifies for:

Our list of schema markup validator tools covers the eight most common mistakes these tests catch.

Step 5: Keep it updated

Structured data is maintenance, not a one-off.

Update the markup whenever something changes:

  • you change your logo or social handles
  • you add a new content type
  • you rebrand or restructure your team

Stale schema that contradicts your live pages is worse than no schema. It feeds engines a confident wrong answer.

What are the most common JSON-LD mistakes to avoid?

Five mistakes cause most of the problems we see.

Mistake 1: marking up content that isn’t on the page

Only describe what a visitor can actually see.

Google’s structured data guidelines are explicit: “Don’t mark up content that is not visible to readers of the page.”

Invented FAQ answers or fake review counts violate those guidelines and risk a manual action. That action removes the page’s eligibility for rich results.

Mistake 2: choosing the wrong type

For example, Product on a services page sends the wrong signal.

So does LocalBusiness for a company with no physical premises.

Mistake 3: duplicate or conflicting entities

A plugin and a hand-coded block both declaring Organization with different details leaves engines to guess.

Pick one source for each entity, and remove the other.

Mistake 4: skipping validation

A single misplaced comma breaks the whole block silently.

Always run the Rich Results Test before and after publishing.

Mistake 5: treating it as a magic ranking lever

Schema supports visibility. It doesn’t replace useful content, E-E-A-T signals or a crawlable site.

If crawlers can’t reach the page, start with allowing and optimizing for AI crawlers. Our own robots.txt keeps it simple:

The robots.txt file of customerimpact.be: one rule that allows every crawler plus the sitemap line, so AI bots can read the JSON-LD on every page Our own robots.txt, October 2026: one rule for all crawlers, so every AI bot may read the site.

If a bot can’t fetch the page, it never sees your JSON-LD.

Frequently Asked Questions

Does JSON-LD improve my Google rankings directly?

Not directly. JSON-LD makes your page eligible for rich results and helps engines understand your entity, but Google treats structured data as a way to interpret content, not as a standalone ranking factor. Think of it as removing ambiguity rather than buying position.

Which schema type should a B2B service company use?

Start with Organization for the company and Person for the people behind it. Add Article on knowledge content and FAQPage only where a real FAQ exists. Avoid Product unless you actually sell a catalogue item with a price.

Will ChatGPT or Claude read my JSON-LD?

They read the page, and clean structured data makes the facts on it far easier to extract correctly. It’s one input among many, so pair it with content genuinely worth quoting and consistent entity data across your profiles.

Where do I put JSON-LD: in the head or the body?

Google accepts JSON-LD in the <head> or the <body>. The <head> is the usual choice: one predictable place in every template.

How does JSON-LD fit into your AI visibility?

JSON-LD gives AI models like ChatGPT, Perplexity and Claude structured trust signals about your brand and content.

It’s not just SEO anymore. It’s how you teach AI who you are.

At Customer Impact, we help companies go beyond SEO, and we optimize for leads, not vanity rankings.

We build GEO frameworks: visibility strategies that make your brand show up inside ChatGPT, Claude, Gemini and Perplexity. See our GEO agency approach.

Want a self-check first? Run the AI-ready website checklist.

Here’s how we help

Our work runs in four steps:

  1. Audit & Setup: we scan your site for missing entity data
  2. JSON-LD Implementation: we link your brand, team, products and trust signals in markup
  3. AI Visibility Reporting: we measure how often your brand appears inside AI answers
  4. Continuous Reinforcement: we optimize language, structure and credibility signals every 90 days

Want your brand to be seen, not just searched?

Contact Customer Impact to get your GEO audit and structured data setup.

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.