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

Q: 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.

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

What JSON-LD Actually Is

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 so that search engines and AI systems can contextually understand who you are, what a page is about, and how it relates to other entities on the web.

The key word is linked. Instead of leaving a machine to guess from your prose 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 while giving machines a clean map of the facts. Google recommends JSON-LD over the older Microdata and RDFa formats precisely because it keeps structured data separate from visible markup, which makes it far easier to add and maintain.

Why It Helps AI Understand Your Site

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 hands the model an unambiguous summary: name, role, links, offerings and the connections between them.

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, which helps engines treat those as one entity rather than several loosely related pages. This is the same entity consistency that underpins AI visibility.
Better eligibility for rich results and citations. 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.

To be honest about the limits: JSON-LD is a trust signal, not a ranking guarantee. It makes your facts legible, but it does not force any model to cite you. It works best alongside genuinely useful content and the other signals that make you worth quoting. If you want the full picture of getting quoted by AI, see becoming source material for AI answers.

The Key Schema Types (and What Each Is For)

Visit schema.org and pick the type that matches your content. Most B2B sites need only a handful. The table below maps the common ones to their job so you pick deliberately rather than copying whatever a generator defaults to.

Schema type	What it’s for	Good fit when
`Organization`	Describes your company as an entity: name, logo, social profiles, founder	You want AI to know who your brand is (most B2B homepages)
`Person`	Describes an individual: role, employer, profiles	Personal branding, author or team bio pages
`Article`	Marks up a blog post or news piece	Knowledge base, blog and press content
`LocalBusiness`	Adds address, opening hours and geo data	You have a physical office or storefront
`Product`	Describes a sellable product with price and availability	Ecommerce catalogues (rarely the right pick for services)
`FAQPage`	Marks up question-and-answer pairs	You have a genuine FAQ block on the page
`Event`	Describes a webinar, workshop or conference	You host or promote events

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 (and Person for the people behind it). Pick the type that is true, not the one that looks the most feature-rich. For deeper cases, FAQPage schema and breadcrumb schema each solve a specific problem worth adding once the basics are in place.

Step by Step: Adding JSON-LD

Step 1: Choose the schema type

Match your page to one row in the table above. A homepage usually gets Organization; a team member page gets Person; a knowledge article gets Article.

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 is 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 is doing quiet heavy lifting: it links your site to profiles engines already trust.

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. Make sure the same entity is not declared twice by both a plugin and a manual block, which is a frequent source of conflicts.

Step 4: Test it

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

Confirm there are zero errors and review the warnings. Warnings will not block eligibility, but they often point at missing recommended properties worth filling in.

Step 5: Keep it updated

Structured data is maintenance, not a one-off. Whenever you change your logo or social handles, add a new content type, rebrand or restructure your team, update the markup so it keeps matching reality. Stale schema that contradicts your live pages is worse than no schema, because it feeds engines a confident wrong answer.

Common Mistakes to Avoid

Marking up content that isn’t on the page. Only describe what a visitor can actually see. Invented FAQ answers or fake review counts violate Google’s guidelines and risk a manual action.
Choosing the wrong type. Product on a services page, or LocalBusiness for a company with no physical premises, sends the wrong signal.
Duplicate or conflicting entities. A plugin and a hand-coded block both declaring Organization with different details leaves engines to guess which is right.
Skipping validation. A single misplaced comma breaks the whole block silently. Always run the Rich Results Test before and after publishing.
Treating it as a magic ranking lever. Schema supports visibility; it does not replace useful content, E-E-A-T signals or a crawlable site. If crawlers cannot reach the page, make sure you are allowing and optimizing for AI crawlers first.

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 is one input among many, so pair it with content genuinely worth quoting and consistent entity data across your profiles.

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. If you want a self-check first, run the AI-ready website checklist.

Here’s how we help:

Audit & Setup. We scan your site for missing entity data.
JSON-LD Implementation. We create structured markup that links your brand, team, products and trust signals.
AI Visibility Reporting. We measure how often your brand appears inside AI answers.
Continuous Reinforcement. We optimize your 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.