JSON-LD Schema for AI Search

Introduction

Structured data is the clearest signal you can give an AI engine about what your page actually says. While traditional SEO treated JSON-LD as a nice-to-have for rich snippets, AI Search Optimization treats it as foundational — it's how ChatGPT, Perplexity, Gemini, and Google AI Overviews parse ambiguous HTML into concrete facts they can quote and cite.

This guide covers every schema type that matters for AI visibility, with working code you can paste directly into your site.

What is JSON-LD and why does it matter for AI search?

JSON-LD (JSON for Linking Data) is a structured data format that sits inside a <script type="application/ld+json"> tag and describes your page's content in a machine-readable way. Instead of an AI model inferring "this is a product page with a price" from scattered HTML, JSON-LD states it directly: entity type, name, price, author, organization, and relationships between them.

AI answer engines don't crawl pages the way a human reads them. They extract entities and facts, then decide whether those facts are trustworthy enough to cite. A page with clean JSON-LD gives the model fewer inference steps and fewer chances to get something wrong — which makes it more likely to be quoted accurately rather than skipped.

The schema types that matter most for AI visibility

Not all schema types carry equal weight for AI citation. Here's how the most common ones rank by impact, based on what answer engines tend to pull from when generating responses.

Organization schema

This is the single highest-leverage schema for AI entity recognition. It tells every model crawling your site exactly who you are, what you do, and how your brand connects to your content. Without it, AI engines have to guess your brand identity from page copy alone — and guesses don't get cited.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company Name",
  "url": "https://www.yoursite.com",
  "logo": "https://www.yoursite.com/logo.png",
  "description": "A one-sentence description of what your company does.",
  "sameAs": [
    "https://www.linkedin.com/company/yourcompany",
    "https://twitter.com/yourcompany"
  ]
}
</script>

Place this on your homepage and ideally repeat it (or reference it) across key pages so the entity stays consistent site-wide.

FAQPage schema

FAQ schema is the most directly "quotable" structured data type that exists. Each question-answer pair is a self-contained unit an AI engine can lift almost verbatim into a chat response, because the format already matches how people ask questions of ChatGPT or Perplexity.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is JSON-LD?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "JSON-LD is a structured data format that describes page content in a way machines can parse directly, without inferring meaning from raw HTML."
      }
    },
    {
      "@type": "Question",
      "name": "Does schema markup help with ChatGPT citations?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Clean structured data reduces the inference work an AI model has to do, making your facts more likely to be extracted accurately and cited."
      }
    }
  ]
}
</script>

Write the questions the way people actually phrase them in a chat box — not the way you'd phrase an SEO title. You can generate FAQPage schema automatically with AISO's FAQ Generator.

Article / BlogPosting schema

This schema gives AI engines the metadata they weigh most heavily when judging content trustworthiness: who wrote it, when, and whether it's been updated.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "JSON-LD Schema for AI Search: The Complete 2026 Guide",
  "author": {
    "@type": "Person",
    "name": "Author Name"
  },
  "datePublished": "2026-06-20",
  "dateModified": "2026-06-20",
  "publisher": {
    "@type": "Organization",
    "name": "Your Company Name",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.yoursite.com/logo.png"
    }
  }
}
</script>

Missing author attribution is one of the most common issues flagged in AI visibility audits — it's an easy fix with an outsized effect on perceived trustworthiness.

Product schema

For e-commerce, Product schema is what lets an AI engine answer "what does X cost and is it in stock" without opening your page at all — which means you want to be the page it pulls from.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Product Name",
  "description": "Short, factual product description.",
  "offers": {
    "@type": "Offer",
    "price": "49.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7",
    "reviewCount": "183"
  }
}
</script>

Keep price and availability accurate and current — stale Product schema is worse than none, because it sends AI engines a fact they'll repeat even after it's wrong.

HowTo schema

When a query is procedural ("how do I..."), AI engines favor sources that already present the answer as ordered steps. HowTo schema makes that structure explicit instead of leaving it buried in prose.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Add JSON-LD to Your Website",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Choose your schema type",
      "text": "Identify which schema type matches your page content, such as Article, Product, or FAQPage."
    },
    {
      "@type": "HowToStep",
      "name": "Add the script tag",
      "text": "Insert your JSON-LD inside a script tag with type application/ld+json in the page head."
    },
    {
      "@type": "HowToStep",
      "name": "Validate the markup",
      "text": "Test the schema with a structured data validator before publishing."
    }
  ]
}
</script>

How to validate your JSON-LD before publishing

Schema errors are common and often invisible until something downstream breaks. Before publishing:

1. Run the page through Google's Rich Results Test or the Schema.org Validator.
2. Check that every @type matches an actual schema.org type — typos fail silently.
3. Confirm nested objects (like author or offers) use the correct sub-types.
4. Re-validate after any CMS or theme update, since these frequently strip or duplicate script tags.

Common JSON-LD mistakes that hurt AI visibility

• Mismatched data: schema that states a price, date, or rating different from what's visible on the page. AI engines treat this as a trust signal failure.
• Duplicate or conflicting schema: multiple Organization or Article blocks on one page that contradict each other.
• Schema with no matching visible content: marking up FAQs that don't appear anywhere in the page's actual text. This can read as manipulative rather than helpful.
• Forgetting dateModified: AI engines weight freshness heavily; an article that's been updated but doesn't say so loses an easy trust signal.

Where to start if you have none of this

If your site currently has no structured data, prioritize in this order: Organization schema sitewide, FAQPage schema on your highest-traffic pages, then Article/BlogPosting schema across your blog. This sequence covers entity recognition first, direct-answer extraction second, and content trust signals third — the three things AI engines check before deciding whether to cite a source at all.

For a faster path, run any page through AISO's Structured Data feature — it scans for existing JSON-LD, flags what's missing, and generates markup tailored to that page's actual content.

Published by AISO — the AI visibility platform built for SEO agencies, SaaS founders, content teams, and growth marketers.