What Is Schema Markup and Does It Help AI Visibility?

Schema markup is a set of machine-readable labels, usually a small JSON-LD script inside your page, that states plain facts about your business: who you are, what you sell, what it costs, which questions you answer. Google uses it for search features such as prices and review stars in results. For AI assistants the measurements show no effect, because chat assistants read the visible text of a page, not its markup.

That split between "useful for Google" and "no measured effect on AI answers" is worth being honest about, the same way we were honest about llms.txt. So this guide does four things: explains what schema markup is in plain words, traces how AI systems actually touch it, shows the code to copy, and draws a clear line between what it will and will not do for you.

What is Schema.org markup in simple terms?

Schema.org is a shared vocabulary for describing things on the web, launched in 2011 by Google, Bing, and Yahoo so that every machine could read the same labels the same way. A page about a product can say, in that vocabulary: I am a Product, my name is X, my price is $19, I ship to Canada.

One picture makes it concrete. Your website is a moving day, and every page is a box. A human can open a box and figure out what is inside. A machine in a hurry cannot. It reads the label. Schema markup is the label: written on the outside, in handwriting every carrier recognizes, saying exactly what is in the box.

There are three ways to write these labels, but only one you need: JSON-LD, a small script tag with the facts in structured form. It is the format Google recommends, and it lives separately from your visible HTML, so adding it breaks nothing.

How do AI systems actually use structured data?

The honest answer is a chain, and each link has a different amount of proof behind it.

The confirmed link: search engines read structured data, and Google documents exactly which schema types power rich results, such as prices in the listing and review stars. Bing parses it too.

The indirect link: AI answers are built on top of those same indexes. Google's AI Overviews sit on Google's index; several AI search products lean on Bing's. When a search index understands your prices and products because you labeled them, everything built on that index inherits the understanding.

The link that fails: a chat assistant that fetches a page to answer a question works from the visible text. In a searchVIU test, ChatGPT, Claude, Gemini, Perplexity and Google AI Mode were asked for a price that appeared only in JSON-LD, and none of the five found it. Every fact in your markup therefore has to appear in the visible text as well.

The measured result: an Ahrefs test of 1,885 pages that added JSON-LD found no meaningful change in their citations in AI Overviews, AI Mode or ChatGPT, and no AI provider has said that markup earns citations. Anyone who promises "add JSON-LD, get recommended by ChatGPT" is selling something. What you are actually buying is narrower: facts that search engines cannot misread.

Which schema types are worth adding?

A handful of types cover most businesses, and each one describes facts that search engines use:

• Organization states your name, logo, and official profiles. It anchors who you are, so machines connect your site, your socials, and your mentions into one entity.
• Product with Offer states the price, currency, and availability. State the same numbers in the visible text, because that text is what assistants read.
• FAQPage marks question-and-answer pairs. Google no longer shows FAQ rich results, so the type only describes questions that already appear on the page.
• Article states the author, publish date, and update date: the freshness signals search engines read.
• LocalBusiness states your address, hours, and service area: the facts local search results are built on.

How do I add JSON-LD to my site?

Here is a complete, valid Organization block for the imaginary bakery from our llms.txt guide:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Sunrise Bakery",
  "url": "https://sunrise-bakery.com",
  "logo": "https://sunrise-bakery.com/logo.png",
  "description": "Family bakery in Austin, TX. Daily sourdough, local delivery, weekend baking classes.",
  "sameAs": [
    "https://www.instagram.com/sunrisebakery",
    "https://www.yelp.com/biz/sunrise-bakery-austin"
  ]
}
</script>

Three rules make it work. Put the script in the page's server-rendered HTML, because many crawlers do not run JavaScript, so markup injected by a script after load may never be seen; our guide on why AI crawlers miss JavaScript content covers this trap in detail. Match the markup to the page: Organization on the home page, Product on product pages, FAQPage only where the questions actually appear. And check your work with Google's Rich Results Test plus the Schema Markup Validator; both are free and take seconds.

Does schema markup guarantee AI citations?

No, and the size of that "no" matters. Nothing guarantees AI citations, because no provider has published rules for earning them. What schema markup gives you is narrower and still worth having: search engines get your facts in a form they cannot misread, and your company is named unambiguously.

Schema markup does not make AI recommend you. Assistants read the visible text of your page, so that is where your facts have to be.

The priorities follow from that. Schema is confirmed infrastructure for Google's search features and a one-afternoon task. It belongs after your content actually answers buyer questions, and alongside server-rendered pages: a perfect label on an empty box helps nobody.

Frequently asked questions

Should I use JSON-LD or microdata?

JSON-LD. Google recommends it, and it keeps all facts in one block that is separate from your visible HTML, so redesigns cannot silently break your labels, which happens to microdata all the time.

Do FAQ rich results still show in Google?

No. Google restricted FAQ rich results in August 2023 to well-known government and health websites, and stopped showing them in Search on May 7, 2026. FAQPage markup is still valid and does no harm, but it no longer changes how the page appears.

Can schema markup hurt my site?

Only if it lies. Markup that contradicts the visible page (invented reviews, prices that do not match) can earn a manual action from Google for spammy structured data. Keep every labeled fact identical to what the page shows and there is no downside.

Label the box, then check who reads it

Schema markup is the label; the bigger question is what AI says about you once it can read everything. When a buyer asks ChatGPT or Claude for the best option in your market, does your name come up? Run the free check: it puts real buyer questions to the AI assistants and shows exactly who they name. Checking the markup on your own pages and the ready-made JSON-LD come with the full audit. Three minutes, and you have a verifiable fact instead of a guess. And if you want to see the answers before you touch any markup, how to check if AI mentions your brand is where to start.