Structured data for AI search: the schema that actually matters
By Anshad P.V, Founder, Axpecto · · 2 min read
Structured data is a machine-readable label in your page's HTML, usually JSON-LD, that states facts directly: who the business is, what the page is about, when it was updated. For AI search, the schema that matters most is Organization (with sameAs links to your official profiles), a type describing what you sell, FAQPage for real FAQs, and dates on articles. No assistant publishes how much weight it gives schema, but it removes guesswork about facts that prose leaves ambiguous.
Which schema types matter most?
| Type | What it tells AI | Key fields |
|---|---|---|
| Organization (or LocalBusiness) | Which business this is, and that it's the same one other sites mention | name, url, logo, description, sameAs, disambiguatingDescription |
| WebSite | Which site is the canonical home of that business | name, url, publisher |
| Product, SoftwareApplication or Service | What you offer and on what terms | name, description, offers |
| FAQPage | Questions and answers in a form that can be lifted directly | mainEntity: Question, acceptedAnswer |
| Article or BlogPosting | Who wrote a page and when it was last true | headline, datePublished, dateModified, author |
| BreadcrumbList | Where a page sits in the site | itemListElement |
Why does sameAs matter so much?
sameAs lists your official profiles (LinkedIn, X, a Wikipedia or Wikidata entry, a Crunchbase page). It connects your website to everything else written about you, which is how an assistant decides that the business on your site is the one a review or article mentions. If another company shares your name, add a disambiguatingDescription too, or an assistant may describe the other company when asked about you. Random Talker links four official profiles, and every assistant asked about it by name described the right product.
What does a complete Organization block look like?
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#organization",
"name": "Example",
"url": "https://www.example.com/",
"logo": "https://www.example.com/logo.png",
"description": "Example makes accounting software for small bakeries.",
"disambiguatingDescription": "Not the Example consulting firm in Boston.",
"sameAs": [
"https://www.linkedin.com/company/example",
"https://x.com/example"
]
}
</script>What are the rules for structured data that AI can trust?
- Match what the page visibly says. Structured data that claims what the page doesn't show is a reason to distrust both.
- Put it in the HTML the server sends. Many AI crawlers don't run JavaScript, so JSON-LD added by a script after load may never be seen.
- Use one @id per entity and refer to it, so your Organization is one node across every page rather than a slightly different copy on each.
- Keep dates honest. Change dateModified when the content changes, not on every deploy.
- Validate it with a structured data testing tool after every change.