Schema markup is structured data you add to your website to help search engines and AI systems understand your content. It uses the schema.org vocabulary, an open standard maintained by Google, Microsoft, Yahoo, and Yandex, to describe things on the web in a format machines can parse: businesses, products, articles, events, people, recipes, and hundreds of other types.
Most schema markup guides stop at rich snippets. This guide covers more. In 2026, structured data does more than generate star ratings in Google results. It serves as a primary machine-readable signal that helps AI search engines like Google AI Overviews, Perplexity, and ChatGPT decide whether to cite your content.
What this guide covers: What schema markup is and why it matters, the AI search angle most guides miss entirely, every schema type mapped to specific business types, complete JSON-LD code examples you can copy, step-by-step implementation for any platform, and how to validate and monitor your structured data over time.
What is schema markup? (and what is structured data?)
Schema markup is code you place on your web pages that tells search engines and AI systems what your content means. When a search engine crawls a page that says "Drew Chapin founded The Discoverability Company in Philadelphia," it sees text. When that same information is wrapped in schema markup, the search engine understands that Drew Chapin is a Person, The Discoverability Company is an Organization, and Philadelphia is a location. That distinction matters for how your content gets indexed, displayed, and cited.
JSON-LD: the recommended schema markup format
The standard format in 2026 is JSON-LD (JavaScript Object Notation for Linked Data). Google explicitly recommends JSON-LD over older formats like Microdata and RDFa. JSON-LD sits in a <script> tag in your page's <head>, separate from your visible content, which makes it clean to implement and maintain without touching your HTML structure.
Here is a minimal example of Organization schema in JSON-LD:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Business Name",
"url": "https://yourdomain.com",
"description": "What your business does in one sentence.",
"foundingDate": "2020",
"address": {
"@type": "PostalAddress",
"addressLocality": "Philadelphia",
"addressRegion": "PA",
"addressCountry": "US"
},
"sameAs": [
"https://linkedin.com/company/your-company",
"https://twitter.com/yourcompany"
]
}
</script>That block of JSON tells every search engine and AI system exactly what your business is, where it is located, when it was founded, and where its social profiles live. Without it, they have to guess from your page text. They often guess wrong.
Does schema markup help SEO? (rich snippets, rich results, and entity understanding)
Schema markup produces two concrete SEO outcomes: rich results (also called rich snippets) and entity understanding.
Rich results and rich snippets are the enhanced search listings you see in Google: star ratings under product results, FAQ accordions, recipe cards, event dates, and how-to steps. Pages with rich results consistently see higher click-through rates than standard blue links. FAQ rich results increase your search results real estate, pushing competitors lower on the page.
Entity understanding is less visible but highly important. When Google's Knowledge Graph recognizes your business as a distinct entity with known attributes (founder, location, industry, products), you become eligible for knowledge panels and entity-based search features. Schema markup is how you feed the Knowledge Graph the facts it needs.
Google has stated that structured data is not a direct ranking factor. The downstream effects (higher click-through rates from rich results, better entity understanding, eligibility for special search features) support organic growth over time. Every SEO audit we run at The Discoverability Company includes schema analysis. Sites that implement it correctly tend to outperform those that do not.
Schema markup for AI search: the new frontier
This is the section most schema guides miss, and it is critical in 2026.
AI-powered search engines are changing how information gets surfaced. Google AI Overviews appear on a large portion of search queries. Perplexity processes millions of searches daily with full source citations. ChatGPT's search integration pulls from the live web. These systems need structured, machine-readable data to make citation decisions. Schema markup provides that data.
How AI Overviews use structured data: When Google generates an AI Overview, it selects source content based on authority, relevance, and parseability. Pages with clean JSON-LD schema are easier for the AI to extract facts from. This makes them more likely to be cited. Pages with complete schema markup appear more frequently in AI Overview citations than equivalent pages without it.
How Perplexity and ChatGPT parse schema: These platforms crawl the live web (PerplexityBot and ChatGPT-User are their crawlers). When they encounter JSON-LD on a page, they can extract structured facts (business type, location, services, product specs) with high confidence. Unstructured text requires inference. Inference introduces error. AI systems prefer certainty.
Speakable schema: This is a schema type specifically designed for AI and voice assistants. It identifies which sections of your content are most suitable for text-to-speech playback and AI citation. Google Assistant and other voice platforms use it to determine what to read aloud. As AI search becomes conversational, Speakable schema becomes a direct signal for "cite this content."
The schema and llms.txt connection: The emerging llms.txt standard tells AI systems what your site is about at a high level. Schema markup tells them what each individual page is about at a granular level. Together, they create a machine-readable map of your content. Sites that have both are more discoverable in AI search contexts.
Check your AI readiness now: Our free AI Search Readiness Audit checks your site for schema markup, llms.txt, AI bot access, and other elements AI systems look for.
Types of schema markup: matched to your business
There are over 800 schema types in the schema.org vocabulary. You do not need all of them. You need the ones that match your business type and content. Here is a decision matrix:
Organization and local business schema markup
Organization or LocalBusiness: The foundation. Every website needs these. Identifies your business as an entity with a name, address, URL, logo, and social profiles. Use LocalBusiness (or a subtype like Restaurant, MedicalBusiness, LegalService) if you serve a geographic area. Use Organization for companies without a physical storefront.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Your Business",
"url": "https://yourdomain.com",
"telephone": "+1-555-123-4567",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main St",
"addressLocality": "Philadelphia",
"addressRegion": "PA",
"postalCode": "19103",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 39.9526,
"longitude": -75.1652
},
"openingHoursSpecification": {
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
"opens": "09:00",
"closes": "17:00"
}
}
</script>WebSite: Tells search engines this is a website with a name and optional search functionality. Including SearchAction enables the Google sitelinks search box.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Your Business",
"url": "https://yourdomain.com",
"potentialAction": {
"@type": "SearchAction",
"target": "https://yourdomain.com/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}
</script>BreadcrumbList: Provides navigation context. Helps search engines understand your site hierarchy and display breadcrumb trails in search results.
Article and FAQ schema markup
Article (or NewsArticle, BlogPosting): For any written content. Includes author, date published, headline, and image. This helps you appear in Google News, Discover, and AI citations.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Your Article Title",
"author": {
"@type": "Person",
"name": "Author Name",
"url": "https://yourdomain.com/about"
},
"datePublished": "2026-04-01",
"dateModified": "2026-04-01",
"publisher": {
"@type": "Organization",
"name": "Your Business",
"url": "https://yourdomain.com"
},
"description": "Article description for search results.",
"mainEntityOfPage": "https://yourdomain.com/your-article"
}
</script>FAQPage: For any page with questions and answers. This schema type maps to how people query AI systems. When someone asks ChatGPT a question and your FAQ schema contains the exact answer, you become a high-confidence citation source.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is schema markup?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Schema markup is structured data code added to web pages that helps search engines and AI systems understand the content in a machine-readable format."
}
},
{
"@type": "Question",
"name": "Does schema markup help SEO?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Schema markup enables rich results in Google (stars, FAQs, events), which increase click-through rates. It also improves entity understanding and AI search visibility."
}
}
]
}
</script>HowTo: For step-by-step instructions. Generates how-to rich results with numbered steps in Google.
Product, service, and review schema markup
Product: For ecommerce. Includes price, availability, reviews, and specifications. Generates product rich results with pricing and ratings directly in search.
Service: For service businesses. Describes what you offer, the area you serve, and pricing if applicable.
Review and AggregateRating: Displays star ratings in search results. Can be nested inside Product, LocalBusiness, or Organization schema.
Person schema markup (for professionals and personal brands)
Person: For individuals who want to establish entity recognition. Includes name, job title, education, awards, and social profiles. This is important for anyone managing their personal online reputation. When AI systems encounter Person schema with rich attributes, they can identify and describe that individual.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Jane Smith",
"jobTitle": "Chief Technology Officer",
"worksFor": {
"@type": "Organization",
"name": "Tech Company Inc"
},
"alumniOf": {
"@type": "CollegeOrUniversity",
"name": "MIT"
},
"sameAs": [
"https://linkedin.com/in/janesmith",
"https://twitter.com/janesmith"
],
"knowsAbout": ["artificial intelligence", "machine learning", "data science"]
}
</script>Event schema, video schema, and speakable schema markup
Event: For conferences, webinars, performances. Shows date, location, and ticket info in Google search.
VideoObject: For video content. Enables video rich results with thumbnails, duration, and upload date.
Speakable: Identifies content suitable for text-to-speech by AI assistants. Add this to your most important factual statements and business descriptions.
How to add schema markup to your website
Method 1: manual JSON-LD (any website)
A reliable method. Add a <script type="application/ld+json"> block to the <head> of your HTML. This works on any website regardless of platform: custom sites, static sites, headless CMS deployments, or hand-coded HTML.
Best practice: Use the @graph pattern to combine multiple schema types in a single block. This is cleaner than multiple separate script tags and allows you to reference entities by ID:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://yourdomain.com/#organization",
"name": "Your Business",
"url": "https://yourdomain.com"
},
{
"@type": "WebSite",
"@id": "https://yourdomain.com/#website",
"url": "https://yourdomain.com",
"name": "Your Business",
"publisher": { "@id": "https://yourdomain.com/#organization" }
},
{
"@type": "WebPage",
"@id": "https://yourdomain.com/about/#webpage",
"url": "https://yourdomain.com/about",
"name": "About Us",
"isPartOf": { "@id": "https://yourdomain.com/#website" }
}
]
}
</script>Schema markup in WordPress (Yoast, Rank Math, Schema Pro)
Yoast SEO and Rank Math generate schema markup automatically based on your content. Yoast handles Organization, Article, and BreadcrumbList out of the box. Rank Math is more granular, letting you configure schema per-page and per-post-type. For most WordPress sites, a plugin handles the majority of the work. The rest (FAQPage, custom types, Person schema) often requires manual JSON-LD blocks or a dedicated schema plugin like Schema Pro.
Schema markup in Shopify, Squarespace, Wix, and Webflow
Shopify includes Product and BreadcrumbList schema automatically in most themes. You can add additional schema via the theme.liquid file or apps like JSON-LD for SEO.
Squarespace adds basic schema for business info and blog posts automatically. Custom schema requires code injection in Page Settings or site-wide Code Injection.
Webflow does not add schema automatically. Use the Custom Code section in page settings to add JSON-LD manually. Webflow gives you full control, which means you can implement everything but need to do it yourself.
Wix generates basic schema for business info. Advanced schema requires the Wix Velo (code) editor or third-party apps.
Method 4: Google Tag Manager
If you cannot edit your site's HTML directly, you can inject JSON-LD via Google Tag Manager using a Custom HTML tag. This is a workaround. Google has stated it processes GTM-injected schema, but server-side rendering is more reliable.
Schema markup validator: how to test and validate structured data
Implementing schema is the first step. You need to verify it works. Here are schema markup testing tools and how to use them.
Run a free check now: Use our Schema Markup Validator to see exactly what structured data exists on any page, what's missing, and how it impacts your AI readiness score.
Google rich results test
An important validator. Enter a URL or paste code, and Google shows you which rich results your page is eligible for and flags any errors. This tells you what Google can do with your schema. Available at search.google.com/test/rich-results.
Schema.org validator
Validates against the full schema.org specification. Use this to catch issues Google's tool misses. Available at validator.schema.org.
Google Search Console
After your schema is live, check the Enhancements section in Google Search Console. It shows which schema types Google has detected across your site, which pages have errors, and which pages are eligible for rich results. This is your ongoing monitoring dashboard.
Common errors and how to fix them
Missing required properties: Each schema type has required and recommended properties. Google's test will flag missing required fields. The most common: Article schema missing author, Product schema missing offers, LocalBusiness missing address.
Mismatched content: Your schema data must match your visible page content. If your schema says a product costs $49 but the page shows $59, Google will flag it and may impose a manual action. Schema describes what is on the page.
Invalid JSON syntax: A missing comma, unclosed bracket, or unescaped quote will break the entire block. Use a JSON validator if your structured data test shows parse errors.
Deprecated types: Schema.org evolves. Types like DataFeed and properties like tickerSymbol have moved or changed. Check against the current schema.org documentation if you are working from an older guide.
Schema markup best practices
Implement schema on every page. Each page should have the schema types relevant to its content. The homepage gets Organization + WebSite. Blog posts get Article. Product pages get Product. Service pages get Service. Every page should include BreadcrumbList.
Use the @graph pattern to combine multiple schema types in a single JSON-LD block. This is cleaner, reduces script tags, and allows entity cross-referencing.
Keep schema in sync with content. If you update a product price, update the schema. If you move your office, update the address schema. Stale schema introduces conflicting signals.
Do not markup invisible content. Google's guidelines are clear: schema must describe content that is visible to the user on the page. Marking up content that users cannot see is considered spam and can result in manual penalties.
Test after every major site change. CMS updates, theme changes, and redesigns frequently break schema markup. Build schema validation into your deployment process.
Measuring schema markup impact
Schema markup impact is measurable. Here is how to track it:
Google Search Console rich result reports: The Enhancements section shows rich result impressions and click-through rates over time. Compare CTR before and after schema implementation for a direct measurement of impact.
Rich result appearance rate: In GSC's Performance report, filter by "Search Appearance" to see how often your pages appear with rich results. Track this monthly.
AI citation tracking: Periodically query ChatGPT, Perplexity, and Google AI Overviews with questions related to your business. Note whether your content is cited. Sites with complete schema are more likely to appear. Our AI Search Readiness Audit automates the technical side of this check.
Knowledge Panel eligibility: If your Organization or Person schema is complete and matches authoritative third-party sources, you become eligible for a Google Knowledge Panel. Track whether your entity appears in the Knowledge Graph by searching your exact business name.
Schema markup FAQ: common questions answered
Does schema markup directly improve rankings?
Google has said schema is not a direct ranking factor. The indirect effects (higher click-through rates from rich results, better entity understanding, AI citation eligibility) support organic growth. High-performing websites tend to have complete schema implementation.
Is schema markup still important in 2026?
It is important. AI search engines answer a large volume of queries. Schema markup provides a clear signal for whether AI systems can understand and cite your content. Sites without schema are harder for AI-powered search to parse.
What is the difference between JSON-LD, Microdata, and RDFa?
All three are formats for adding structured data to web pages. JSON-LD sits in a separate script tag and is the simplest to implement and maintain. Microdata is woven into your HTML attributes. RDFa is similar to Microdata but uses different attribute names. Google recommends JSON-LD, and it is the standard for new implementations.
How many schema types should I implement?
Start with the essentials: Organization (or LocalBusiness), WebSite, and BreadcrumbList on every page. Then add page-specific types: Article for blog posts, Product for products, FAQ for Q&A pages. Most business websites benefit from a handful of schema types.
Can schema markup hurt my SEO?
Only if you misuse it. Marking up content that does not exist on the page, using fake review schema, or implementing schema that contradicts your visible content can result in Google manual actions. Implemented correctly, schema is safe.
What to do next
Step 1: Run a free schema validation on your website to see what structured data you currently have and what is missing.
Step 2: Run a free AI readiness audit to see how your overall site scores across the dimensions AI systems evaluate.
Step 3: Implement the schema types recommended for your business type, starting with Organization and WebSite.
Step 4: Validate with Google's Rich Results Test and monitor in Google Search Console.
If you want professional help implementing schema markup and building AI search visibility, our AI search optimization services handle this. Start the conversation below.
Related resources
- AI Search Optimization: The Complete Guide, How to build visibility across ChatGPT, Perplexity, Claude, and Google AI Overviews
- How to Appear in AI Search Results, Step-by-step guide to getting cited by AI platforms
- Google AI Overviews: What They Mean for Your SEO Strategy, How to get featured in AI-generated summaries
- The Complete Business Website SEO Checklist, Full technical and on-page SEO audit framework including AI readiness
- SEO Deep Research: Free Analysis Tools, Schema validator, AI readiness audit, and more
Research and platform guidance behind this guide
The shift toward AI-mediated search is clear. Google's Search Central documentation on AI features confirms that structured data is a primary signal used when surfacing content inside AI Overviews. Google's guidance recommends JSON-LD specifically. It maps eligible schema types directly to which enhanced features your content can qualify for. If you skip that documentation, you are guessing at a system that has been documented in detail.
Understanding why structured data matters for AI systems requires understanding how large language models process and cite web content. OpenAI's published research and Anthropic's research publications describe how these models parse structured signals to resolve factual claims about entities. Clean, consistent schema markup reduces ambiguity for these systems. This increases the likelihood of being cited. The information retrieval research community tracks this trajectory closely. A steady stream of preprints published through arXiv's Information Retrieval section documents how retrieval-augmented generation systems weigh structured and unstructured content signals.
There is a trust dimension worth taking seriously. A March 2025 Pew Research study on how the U.S. public and AI experts view artificial intelligence found that public confidence in AI-generated information remains fragile. Most respondents expressed concern about accuracy. That skepticism puts pressure on AI search products to cite authoritative, verifiable sources. Websites with complete, accurate schema markup look authoritative to these systems. Investing in structured data is a bet on a trust ecosystem that is still being built.
What this looks like in practice
When local service businesses come to us with poor visibility in AI-generated answers, we often find their sites lack schema markup entirely. We implement LocalBusiness schema with complete name, address, and phone data. We define service area coverage and add FAQPage blocks across core service pages. Following implementation, these pages often qualify for FAQ rich results in Google. The businesses begin appearing in Perplexity answers for local queries. Organic click-through rates on the affected pages tend to rise over the following quarter.
Software companies often face a different problem. Their sites may have technically valid schema, but the data is generic and inconsistent. An Organization block might list one founding year while the About page lists another. Product schema descriptions often fail to match the homepage copy. These contradictions make it harder for Google's entity resolution systems to build a Knowledge Graph entry for the company. We reconcile all the signals. We update the schema to reflect accurate data and consistent product descriptions. We add SoftwareApplication schema with pricing and platform compatibility details. Over time, branded search results are more likely to show a Knowledge Panel, and the company becomes eligible to appear in ChatGPT responses to questions about tools in its category.
Why schema markup matters
The case for structured data has strengthened as AI-driven search has scaled. According to Google Search Central's AI features guidance, structured data supports how Google's systems understand and present content in AI-generated experiences. That is a meaningful policy signal. Google made that language explicit in 2024. It mirrors what we see in practice. Sites with complete JSON-LD coverage appear in AI Overviews more frequently than sites relying on unstructured text.
The research community tracks this shift closely. Preprints indexed through arXiv's Information Retrieval section examine how large language models weight machine-readable metadata against raw page text when selecting citation candidates. Structured entity signals reduce factual ambiguity errors. When an AI system has to choose between two pages covering the same ground, the one that has declared its facts in JSON-LD gives the model less to infer and more to confirm. A Pew Research survey published in March 2025 found that 65% of U.S. adults have used AI-powered search or chat tools. That adoption curve means the audience finding your content through AI intermediaries is growing. If your pages are not machine-readable, you miss a share of your potential traffic.
The click-through data from traditional rich results matters. Google's structured data documentation reports that FAQ schema increases search results real estate for a given result. Recipe pages with rich results see higher engagement than plain listings. Implementing Product and Review schema increases organic click-through rates by making results more visually compelling and informative. For reputation-focused sites where first impressions in search results carry weight, that lift helps users choose your page over a competitor's. The Google Search Central documentation maintains an updated list of supported schema types eligible for rich results treatment. Each new type represents an opportunity for enhanced visibility that many sites have not claimed.
If you are assessing where your site stands, the gap between having some schema and having complete, validated, entity-connected schema is where the competitive opportunity lives. Partial implementation leaves impactful signals on the table. The pages that show up in AI citations and knowledge panels are the ones where every major entity on the site has been declared, cross-referenced with sameAs properties pointing to authoritative external sources, and validated against Google's Rich Results Test without errors. That is an achievable bar. The sites that clear it pull ahead in AI-driven discovery.
How schema impacts professional services
Professional services firms often have strong content and a clean site, but zero schema markup. They publish detailed guides and rank poorly for high-intent queries. Their primary concern is often that a newer competitor with thinner content outranks them. We run a schema audit and frequently find that the competitor has implemented Organization, Person, FAQPage, and BreadcrumbList schema across their entire site. We deploy JSON-LD for advisors using Person schema with credentials, awards, and sameAs links to professional board profiles. We add Organization schema with full address and founding date. We wrap top guides in FAQPage markup. Over time, these guides earn FAQ accordions in Google results. Advisor profiles earn knowledge panel triggers in branded searches. The firms begin appearing in Perplexity citations for local planning queries. Schema implementation bridges the gap between good content and machine readability.