JSON-LD structured data for AI crawlers

Structured data in JSON-LD is a compact, machine-readable set of facts placed inside your pages. Search engines have relied on it for ten years to generate rich results and knowledge panels. It supplies machines with a clear account of your name, category, pricing, and relationships, alongside those same details in the visible page copy.

Do not assume JSON-LD is a certain path to AI recommendations. The way an assistant weighs structured data is not defined here. Instead, use it to describe your business in a consistent way, keep it accurate, and verify it whenever the public-facing facts change.

The three blocks most brands should ship

1. Organization: who you are. Include one sitewide instance on every page, at the layout level:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#org",
  "name": "Example",
  "url": "https://example.com",
  "description": "One factual sentence: category + who it's for.",
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://github.com/example"
  ]
}

Employ sameAs URLs to link your site to profiles that point to the same organization.

2. Product / SoftwareApplication: what you sell. Put this on your homepage or product page, and include actual pricing:

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Example",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Web",
  "description": "What it does, stated plainly.",
  "offers": {
    "@type": "Offer",
    "price": "39",
    "priceCurrency": "USD"
  },
  "publisher": { "@id": "https://example.com/#org" }
}

For physical goods, use Product with offers, brand, and aggregateRating, but only if real review data supports it.

3. FAQPage: the questions you answer. On pricing and comparison pages, reflect the questions buyers ask assistants:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Who is Example for?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Example is built for small agencies managing multiple client projects."
    }
  }]
}

Rules that keep it working

• Align with the visible page. If structured data conflicts with what appears on the page, that is the one pattern that tends to be penalized instead of ignored.
• Stay honest. Do not invent ratings or fabricate review counts. The goal is to be the reliable source of facts about yourself.
• Prefer a single `@graph` when you combine multiple blocks on one page, and connect them with @id references instead of scattering separate scripts.
• Validate after each change with Google's Rich Results Test or schema.org's validator: a single trailing comma can silently invalidate the block.

Structured data tells machines what you are; it cannot force them to recommend you. For that, see how citations actually work, and use the free scan to check what assistants say about you today.