Schema markup is structured data added to a webpage so search engines and AI systems can understand what the page is about. In 2026, schema is no longer optional. Google uses it for rich results, AI search engines (Perplexity, ChatGPT, Gemini) cite schema-marked pages preferentially, and properly marked content earns 20 to 35 percent higher click-through rates from search results. The technical work to add schema is small. The competitive advantage is significant.
What Schema Markup Actually Is
Schema is a vocabulary defined at schema.org, a joint project of Google, Microsoft, Yahoo, and Yandex. It standardizes how to describe people, places, products, articles, events, businesses, and dozens of other entity types. Adding schema to a page means embedding a small block of JSON-LD (JavaScript Object Notation for Linked Data) that maps the visible content to schema.org types.
JSON-LD is the recommended format. Microdata and RDFa exist but are deprecated for new builds. JSON-LD lives in a script tag in the page head or body, separate from the visible HTML. This is cleaner than the older inline approaches.
A minimal example for a blog post:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Schema Markup for Websites",
"datePublished": "2026-05-02",
"author": {
"@type": "Person",
"name": "Jane Designer"
},
"publisher": {
"@type": "Organization",
"name": "Framer Websites",
"logo": {
"@type": "ImageObject",
"url": "https://blog.framerwebsites.com/logo.png"
}
}
}
</script>That eight-line block tells Google and AI engines: this is an article, here is the title, here is the publish date, here is the author, here is the publisher. The visible page does not change. The crawlers see structured meaning.
Why Schema Matters More in 2026
Three forces have made schema higher-stakes than it was three years ago.
First, Google rich results increasingly require schema. FAQ rich results, How-To carousels, Product rich snippets, Recipe cards, Event listings, Local Business pack results all rely on schema. Pages without schema simply do not appear in these enhanced result types.
Second, AI search engines (ChatGPT search, Perplexity, Gemini, Claude search) prefer structured data when generating answers. A page with proper Article schema, FAQ schema, and clear authorship signals is far more likely to be cited than a page with raw HTML and no metadata. Citations drive referral traffic.
Third, voice assistants and zero-click results pull from schema. When a user asks Siri or Alexa “what time does the dentist office open,” the answer comes from LocalBusiness schema, not from scraped HTML.
The Schema Types That Matter Most
Twenty-plus schema types exist. Six cover 90 percent of what most websites need.
Article (or NewsArticle, BlogPosting): for any editorial content. Required for Top Stories, Discover, and citation in AI search.
FAQPage: for any page with question-and-answer content. Triggers FAQ rich results in some searches and is heavily used by AI systems.
Product: for ecommerce. Includes price, availability, reviews, ratings. Drives shopping rich results.
LocalBusiness: for any business with a physical location. Required for proper local pack visibility. Includes hours, address, phone, geo coordinates.
Organization: for the homepage. Establishes the entity behind the brand for knowledge graph entries.
BreadcrumbList: for navigation hierarchy. Drives breadcrumb rich results that improve CTR.
Less common but high-leverage:
- HowTo for instructional content
- Recipe for cooking content
- Event for events with dates
- VideoObject for embedded videos
- Course for online courses
- JobPosting for job pages
- Review and AggregateRating for testimonials
- Person for author and team pages
Implementing Schema on Common Platforms
The implementation path depends on the platform.
WordPress: Yoast SEO and Rank Math handle the core schema (Article, Organization, BreadcrumbList) automatically. Custom types (FAQ, How-To, Product) need either custom code, a schema plugin (Schema Pro, Schema by Brainstorm Force), or manual JSON-LD blocks in posts.
Framer: Add JSON-LD via the embed component or in the page settings. For dynamic CMS-driven pages, use template variables to populate schema fields. The Framer SEO guide covers schema implementation in detail.
Webflow: Add JSON-LD in page settings under custom code, or via embed components. CMS-driven schema uses dynamic field bindings.
Squarespace: Add JSON-LD via code injection in the site header or per-page header. Limited dynamic capabilities; mostly works for site-wide schema like Organization.
Custom Next.js or React sites: Use the Head or Metadata API to inject JSON-LD per page. Many teams use a small wrapper component that takes the entity type and properties as props.
FAQ Schema: The Highest-Leverage Win
FAQ schema is the most-implemented and highest-impact schema type for content sites. It produces FAQ rich results in some searches (less common since 2023) and is heavily used by AI search engines as a citation source.
Implementation:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long does schema take to implement?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Most sites can add core schema in one to two weeks. Article and Organization schema are usually 80 percent of the value."
}
},
{
"@type": "Question",
"name": "Do I need a plugin or can I write schema manually?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Both work. Plugins handle common cases automatically. Manual JSON-LD gives precise control."
}
}
]
}
</script>The FAQ block must match the visible content on the page. Adding FAQ schema for content not visible to users is a violation of Google’s spam policies and can trigger manual actions.
Article Schema for Editorial Content
Every blog post and editorial page should have Article schema. The fields that matter:
- headline: the article title (max 110 characters)
- datePublished: ISO 8601 date when first published
- dateModified: ISO 8601 date of most recent significant edit
- author: a Person entity with at minimum a name and ideally a sameAs link to LinkedIn or another profile
- publisher: an Organization entity with name and logo
- image: a featured image URL with at least 1200×675 dimensions
- description: a 1-2 sentence summary
Author schema with a sameAs link to a LinkedIn profile or institutional bio establishes authorship for Google’s E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness). This matters more in 2026 than it did before generative search.
LocalBusiness Schema for Brick-and-Mortar
For any business with a physical location, LocalBusiness schema is the highest-leverage schema type. Required fields:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Riverside Family Dental",
"address": {
"@type": "PostalAddress",
"streetAddress": "1247 Pine Street",
"addressLocality": "Boulder",
"addressRegion": "CO",
"postalCode": "80302",
"addressCountry": "US"
},
"telephone": "+1-303-555-0119",
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday"],
"opens": "08:00",
"closes": "17:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Friday",
"opens": "08:00",
"closes": "13:00"
}
],
"geo": {
"@type": "GeoCoordinates",
"latitude": 40.0150,
"longitude": -105.2705
},
"priceRange": "$$"
}
</script>Use a more specific subtype when applicable: Dentist, AttorneyLaw, MedicalBusiness, Restaurant, AutoRepair, etc. The more specific subtype gives search engines a clearer signal.
Validating Schema
Three tools to validate schema, in order of usefulness:
- Schema.org Validator: validator.schema.org. The official validator. Strict and authoritative.
- Google Rich Results Test: search.google.com/test/rich-results. Tests whether the schema qualifies for Google rich results.
- Google Search Console: the Enhancements section reports schema errors and warnings on indexed pages over time.
Run the validators on staging before pushing schema to production. After launch, monitor Search Console weekly for new schema errors, especially after CMS updates that can break dynamic schema generation.
Common Schema Mistakes
Six mistakes show up in nearly every audit. Schema that does not match the visible content (Google treats this as spam). Missing required fields like author or datePublished on Article schema. Using schema types that do not exist (typos like “Aritcle” or made-up types). Multiple schema blocks contradicting each other (two different prices on the same Product). Hardcoded dates that never update (datePublished from 2019 on a 2026 article). Forgetting to update schema after migrations or template changes.
Run an annual schema audit alongside the SEO audit to catch drift.
Schema for AI Search
Generative AI search engines treat schema as a signal of trustworthiness. Pages with proper schema get cited more often than pages without. The schema patterns that matter most for AI citation:
- Article with full author and publisher metadata
- FAQPage for question-and-answer content
- HowTo for instructional content
- Organization on the homepage with sameAs links to social profiles
Beyond schema, AI search engines also pull from open standards: clean HTML semantics, accessible heading hierarchies, llms.txt files, and clear factual content. Schema is one signal among several but is the easiest to implement.
For broader Core Web Vitals and SEO context, the Core Web Vitals guide covers the performance signals that complement schema.
Maintenance and Updates
Schema is not set-and-forget. Three maintenance habits keep it healthy:
- Validate schema on every new page or template change
- Monitor Google Search Console weekly for new errors and warnings
- Run a full schema audit annually with Screaming Frog or Sitebulb to catch drift
Schema in 2026 is table stakes. Sites that skip it lose visibility to sites that implement it well. For a Framer build that ships with full schema markup baked into every template, see our pricing.
Frequently Asked Questions
Do I need schema markup if I have a small website?
Yes. Even a 5-page site benefits from Organization schema on the homepage and Article schema on blog posts. Local businesses with a physical location should always have LocalBusiness schema. The implementation effort is small; the visibility gain is meaningful.
Will schema markup directly improve my rankings?
Schema is not a direct ranking factor in the traditional sense. It does enable rich results, which boost CTR by 20 to 35 percent on triggered queries, and it improves how AI search engines interpret and cite your content. The indirect ranking impact through better CTR and engagement is real.
What is the difference between JSON-LD and Microdata?
JSON-LD is a separate script block that does not affect visible HTML. Microdata is inline attributes added to HTML elements. Google recommends JSON-LD for new implementations because it is cleaner, easier to maintain, and easier to template.
How do I add schema markup to WordPress?
Use Yoast SEO or Rank Math for the core types (Article, Organization, BreadcrumbList) which they generate automatically. For custom types (FAQ, Product, How-To), use a dedicated schema plugin or add JSON-LD via the post editor’s HTML block.
Can schema markup hurt my rankings?
Yes, in two cases. Schema that does not match visible content is a spam violation and can trigger manual actions. Schema with errors that prevents pages from being indexed properly. Validate every schema block before publishing and monitor Search Console for warnings.
If you want a Framer build that ships with full schema markup baked into every template (Article, FAQ, Organization, LocalBusiness), talk to our team.