The short answer
Schema markup helps AI search visibility by removing guesswork. JSON-LD tells a machine what the page is, who published it, who wrote it, when it changed and which questions it answers, so an engine does not have to infer those facts from prose. It does not make weak content citable on its own, and no AI engine has published schema as a citation factor. Treat it as the layer that makes good, well-structured content easy to identify and attribute.
Schema is one part of the wider work of getting your business into AI search answers. This guide covers which types to add, how to add them, and the mistakes that waste the effort.
What Schema Does for AI Search (and What It Doesn't)
HTML describes how a page looks: this line is a heading, this block is a paragraph. It says almost nothing about meaning. A heading that reads "How to Calculate Churn Rate" tells a browser to show it large and bold, but not whether the page is a tutorial or an opinion, who wrote it, or when it was last updated.
Structured data fills that gap. When your Article markup states the headline, author, publisher and dates, a parser can read those facts directly. Google says it uses structured data to understand page content, and the same unambiguous facts are there for any other system that parses the page.
What schema does well:
- Identifies the publisher and author as specific entities rather than strings of text.
- Declares freshness through datePublished and dateModified.
- Labels questions and answers, products, steps and locations so they can be read without guessing.
What it does not do: it does not rank a page that answers the question badly, and it cannot describe content that is not visible on the page. Markup that contradicts or invents page content breaks Google's structured data guidelines and can cost you rich results.
The Entity Connection: Organization, Person and sameAs
Organization and Person schema connect your site to the wider web of entities that search engines and AI models already know about. The sameAs property is the link: it says "this author is the same person as this LinkedIn profile" or "this company is the same organization as this Wikidata entry".
An author tied to a verifiable profile is a clearer signal than an anonymous byline, even when the article text is identical. Practical steps:
- Add sameAs links from your Organization to your official social profiles, and to Wikipedia or Wikidata where an entry exists.
- Give each author a Person entity with sameAs links to their professional profiles, and Google Scholar or ORCID for research content.
- Use one official name everywhere. Do not abbreviate your company name differently across pages or markup.
- Keep the facts in your markup, About page and profiles consistent with each other.
How Each Schema Type Helps a Machine Trust a Page
Before an engine quotes a source, it needs to know what the source is. Each core schema type answers one part of that question explicitly:
- Article or BlogPosting: this is an article, with this headline, published on this date, updated on this date, written by this person.
- Person: this author exists and is the same person as these external profiles.
- Organization: this publisher is a real organization tied to this domain, with this logo and these official profiles.
- FAQPage: the publisher states that this is its answer to this question. Explicit pairs are easier to parse than answers buried in prose.
None of these is a guarantee. They make true facts about your content unambiguous, which matters most when an engine is choosing between several pages that say similar things.
The Schema Types Worth Adding First
Start with the types that describe who you are and what each page is, then add the ones that match specific content:
- Organization (sitewide): name, logo, URL and sameAs links. The base entity everything else points to.
- Article or BlogPosting with a Person author: on every editorial page, with accurate datePublished and dateModified.
- BreadcrumbList: shows where a page sits in your site, which helps crawlers understand topic structure.
- FAQPage: only where the page visibly shows questions and answers. Google limited FAQ rich results to well-known government and health sites in 2023, so add it for clarity, not for a SERP feature.
- Product, LocalBusiness or Service: where they describe what the page is actually about, such as a product page or a location page.
- HowTo: optional for step-by-step guides. Google stopped showing HowTo rich results in 2023, though the markup still labels the steps. Google explained both changes in its announcement on HowTo and FAQ rich results.
JSON-LD vs Microdata: Use JSON-LD
Schema.org supports JSON-LD, Microdata and RDFa. Use JSON-LD: Google recommends it, and it is the easiest to maintain.
- It sits apart from your HTML. JSON-LD lives in a script tag, so parsers can read it without walking the page's element tree.
- It survives redesigns. Microdata is attached to individual HTML elements and breaks when templates change. JSON-LD can be edited on its own.
- It is easy to validate as a single block.
One catch: put the JSON-LD in the HTML your server sends. If a script adds it after the page loads, crawlers that do not run JavaScript never see it.
Implementation Walkthrough: A Minimal Article Block
Place the block in a script tag of type application/ld+json in the page head, or just before the closing body tag. The fields that matter most for an article:
- @type: "BlogPosting" for editorial posts, or "Article".
- headline: the same text as the visible H1.
- author: a Person with a name and sameAs links to professional profiles.
- publisher: your Organization, with name and logo.
- datePublished and dateModified: ISO 8601 dates. Update dateModified whenever you make a meaningful edit.
- description: a one or two sentence summary that matches the page.
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Calculate Churn Rate",
"datePublished": "2026-03-10",
"dateModified": "2026-11-09",
"author": {
"@type": "Person",
"name": "Jane Doe",
"sameAs": ["https://www.linkedin.com/in/janedoe"]
},
"publisher": {
"@type": "Organization",
"name": "Example Co",
"logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
},
"description": "The churn rate formula, a worked example, and the mistakes that skew it."
}
Page Structure Matters as Much as the Markup
Markup describes the page; the page itself still has to be easy to quote. If you are optimizing for AI citation, work on both at once:
- Answer first. Put a direct one or two sentence answer under each heading.
- Question headings. Phrase H2s and H3s the way people ask.
- Self-contained sections. Each section should make sense without the one before it.
- Visible FAQ sections that match your FAQPage markup word for word. Our guide to writing a blog post AI search engines cite shows where FAQ sections fit and how to write the answers.
- Markup that matches. Headline equals H1, dates match the visible dates, FAQ answers match the visible answers.
Implementation Priority Order
Starting from zero, add schema in this order:
- Week 1: Organization markup on the homepage and About page, with logo and sameAs links. Check the facts match your visible About content.
- Week 2: Article or BlogPosting with Person authors and accurate dates on every post. Create author pages if you do not have them.
- Week 3: FAQPage on the top pages that already show questions and answers, and BreadcrumbList sitewide.
- Week 4: Product, LocalBusiness or HowTo where they fit. Validate everything.
On a CMS, most of this does not need a developer. Plugins handle the basics on WordPress, and Raechal's CMS agents can write and add validated schema on WordPress, Webflow, Wix or GitHub, staging each change for your approval before it goes live.
Validate every block before publishing with Google's Rich Results Test or the Schema.org validator. Malformed JSON-LD is worse than none. To see which of your key pages are missing markup today, run a free audit of how AI engines read your site.
Common Mistakes That Waste Schema
- Headline does not match the H1. Keep them identical so the markup and the page agree.
- Stale dateModified. Many CMS setups never update it. Change it whenever you make a meaningful edit, and not when you have not.
- Anonymous authors. A team name with no linked Person or Organization entity tells a machine very little.
- FAQ answers that lean on the page. Answers that say "as mentioned above" cannot be reused on their own. Each answer must stand alone.
- Marking up content that is not on the page. Schema must describe visible content. Hidden or invented FAQ answers break Google's guidelines.
- Schema added only by client-side JavaScript. Crawlers that read the server HTML miss it entirely.
- Skipping validation. One stray comma can void a whole block.
Frequently asked questions
Does schema markup help AI search visibility?
It helps engines identify what a page is, who published it and when, which makes good content easier to attribute. No AI engine has published schema as a citation factor, and markup cannot make a weak page citable, so pair it with clear, answer-first content.
Does schema markup directly boost Google rankings?
Not directly. Google uses structured data to understand pages and to show rich results, which can lift click-through rates, but the markup itself does not move rankings.
Is FAQ schema still worth adding after Google's 2023 change?
Yes, where the page shows real questions and answers. Google now shows FAQ rich results only for well-known government and health sites, but the markup still labels the pairs clearly for any parser that reads it. Do not add it to pages without a visible FAQ.
Which schema types should I start with?
Organization sitewide, then Article or BlogPosting with a Person author on every post, then BreadcrumbList. Add FAQPage, Product, LocalBusiness or HowTo only where the page content matches.
Can I add schema without a developer?
Yes. On WordPress, SEO plugins such as Yoast SEO and Rank Math generate Article and Organization markup. Raechal's CMS agents can also write validated JSON-LD for WordPress, Webflow, Wix or GitHub sites and stage it for your approval.
How do I check that my schema is valid?
Run the page through Google's Rich Results Test or the Schema.org validator before and after publishing. Then confirm the markup appears in the HTML your server sends, not only after scripts run.
