Schema Markup for SEO: Which Types Actually Matter

A practical guide to schema markup for SEO — which structured data types generate rich results, how to implement JSON-LD correctly, and how to measure the impact on rankings and CTR.

Climer TeamFebruary 20, 202611 min read

Schema markup is the most consistently underused technical SEO lever available to most sites.

Only about 40% of web pages implement JSON-LD structured data, according to the 2024 Web Almanac. Yet among pages that rank on the first page of Google, the figure is 72.6% — nearly three-quarters of top-ranking pages use schema markup. That gap represents a meaningful competitive signal most content teams are leaving on the table.

This guide covers what schema markup actually does for SEO, which types generate measurable impact in 2026, how to implement JSON-LD correctly, and what changed recently with Google's structured data policies.

What schema markup does (and doesn't do) for SEO#

Schema markup adds machine-readable context to pages. When you publish a recipe, a structured paragraph of HTML tells humans it's a recipe. Schema markup tells Google it's a recipe — with specific ingredients, cook time, calorie count, and author attribution — in a format that can be parsed and acted on directly.

What schema markup does:

  • Qualifies pages for rich results (visual enhancements in SERPs like star ratings, event listings, breadcrumbs, product information)
  • Strengthens entity signals — helps Google understand who you are, what you sell, and where you operate
  • Improves AI citability — AI Overviews and conversational AI models preferentially cite content with explicit structured data that makes facts unambiguous

What schema markup doesn't do:

  • Directly improve rankings. Google has explicitly confirmed structured data is not a ranking factor.
  • Fix content quality problems. Putting Product schema on a thin product page doesn't make Google rank it above a competitor's well-reviewed product page.

The mechanism is indirect: rich results improve click-through rates, which over time can influence rankings. Rotten Tomatoes documented a 25% CTR improvement on 100,000 pages after implementing structured data — that's the pathway. Pages with rich results receive clicks at a 58% rate versus 41% for standard blue links, according to Search Engine Journal research.

JSON-LD: the only format worth using#

Schema markup can be implemented in three formats: JSON-LD, Microdata, and RDFa. For any new implementation in 2026, use JSON-LD. This isn't a preference — it's Google's explicit recommendation, and all new Google structured data features are released in JSON-LD format first.

JSON-LD is embedded in a <script> tag in the page's <head> or <body>:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Schema Markup for SEO: Which Types Actually Matter",
  "author": {
    "@type": "Organization",
    "name": "Climer"
  },
  "datePublished": "2026-03-15",
  "dateModified": "2026-03-15"
}
</script>

Why JSON-LD wins over the alternatives:

  • Non-intrusive. The structured data lives in one <script> block, completely separate from the visible HTML. Microdata and RDFa require embedding attributes on individual HTML elements — every structural change to a template risks silently breaking the markup.
  • Easy to template. A CMS, build pipeline, or tag manager can inject the <script> block without touching the rendered page HTML.
  • Easier to validate. Paste the entire JSON-LD block into Google's Rich Results Test — no need to scrape HTML or inspect rendered DOM.
  • The standard for new features. When Google releases new structured data types, JSON-LD support comes first. Some newer schema types are JSON-LD only.

Which schema types actually matter in 2026#

Google supports approximately 30 active rich result types. Most sites only need 4–6. Here's where to focus attention by content type.

For every website: Organization + BreadcrumbList#

Organization schema belongs on your homepage. It establishes your entity: legal name, URL, logo, and sameAs links pointing to authoritative profiles (LinkedIn, Twitter/X, Crunchbase, Wikidata if applicable). This is foundational for Knowledge Graph eligibility and AI visibility — models querying facts about your brand rely on these entity connections.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Climer",
  "url": "https://climer.ai",
  "logo": "https://climer.ai/logo.png",
  "sameAs": [
    "https://twitter.com/climerseo",
    "https://linkedin.com/company/climer"
  ]
}
</script>

BreadcrumbList schema belongs on any page with breadcrumb navigation. It reinforces the page's position in the site hierarchy and often causes Google to display the breadcrumb path below the URL in search results, making the SERP result more informative.

For blog posts and editorial content: Article / BlogPosting#

Article schema on blog content provides Google with unambiguous freshness and authorship signals. The critical fields:

  • headline — the article title
  • datePublished — initial publish date (ISO 8601)
  • dateModified — last updated date (update this when you refresh content)
  • author — with @type: Person or @type: Organization and a credible url or sameAs pointing to a real profile
  • publisher — with @type: Organization, name, and logo

The dateModified field matters: Google uses it to assess content freshness. Pages that update their dateModified when genuinely refreshing content tend to maintain freshness signals in queries where recency matters.

For e-commerce: Product schema#

Product schema is the highest-ROI structured data implementation for e-commerce. It enables:

  • Merchant listings in Google Shopping
  • Product rich results with price, availability, and review stars in organic results
  • Price drop alerts in Google Search Console

The required fields for Google's product rich results are: name, image, offers (with price and availability). For review snippets: aggregateRating with ratingValue and reviewCount. Without review data, product rich results appear without stars — still useful, but less click-compelling.

For local businesses: LocalBusiness#

LocalBusiness schema on your homepage and contact page provides structured information about your physical location: name, address, telephone, openingHoursSpecification, and geographic coordinates. This reinforces your Google Business Profile data and supports local pack ranking.

Key detail: your schema address should exactly match your Google Business Profile address. Inconsistencies between schema and GBP data create conflicting entity signals.

For events: Event#

If you run webinars, conferences, in-person events, or any time-bounded activity, Event schema can place your listing in Google's dedicated event rich results. Required fields: name, startDate, location (with Place schema or VirtualLocation for online events). Optional but effective: eventStatus, offers (with ticket pricing).

For recipes: Recipe#

Recipe schema enables rich results with cook time, calorie count, review stars, and ingredient lists. It also qualifies recipes for Voice search results (Google reads aloud recipe content on smart speakers). The required fields include name, image, recipeIngredient, recipeInstructions, and cookTime.

Continue reading

SEO ROIBest SEO Automation Tools in 2026 (By Workflow)LLM SEO

Fix Technical SEO Issues Faster

Climer audits your site, identifies issues, and helps you prioritize fixes that actually move the needle.

Get started freeSee features

What to skip in 2026#

Google removed or deprecated several structured data types in 2023–2026. Don't invest time implementing these:

FAQ schema (most sites) — Google restricted FAQ rich results to government and health websites in August 2023. For all other sites, FAQ schema no longer generates visual SERP enhancements. The markup causes no harm and may still help AI models parse Q&A content, but it doesn't warrant prioritization. If you have it implemented, leave it. Don't build new workflows around it.

HowTo schema — Removed from search results entirely in September 2023. No longer generates rich results for any site type.

Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement — Google removed these rich result types in June 2025 as part of a structured data simplification initiative. These types no longer generate SERP enhancements.

Implementing schema at scale#

For sites with large content volumes, manual schema implementation doesn't scale. The practical approaches:

CMS templates. Most CMS platforms can generate schema automatically from content fields. In WordPress, plugins like Yoast SEO and Rank Math generate Article, BreadcrumbList, and Organization schema automatically. In Webflow, schema injection requires custom code in page settings. In Next.js, schema generation belongs in the layout component with data pulled from your content layer.

Conditional generation. Your template logic should generate the correct schema type based on page type — Article for blog posts, Product for product pages, LocalBusiness for location pages — rather than applying one schema type globally.

The dateModified update problem. Most CMS systems don't automatically update dateModified when content is edited. Build an explicit step into your content refresh workflow to update this field.

Testing and monitoring#

Validate before deploying. Use Google's Rich Results Test to confirm your schema parses correctly and qualifies for the rich result types you expect. Paste your JSON-LD code directly into the tester — you don't need a live URL, which makes this useful during development.

Google Search Console. After deploying schema and allowing 1–2 weeks for Googlebot to recrawl, check Search Appearance → Rich Results in Search Console. This report shows which pages Google has identified as eligible for each rich result type and surfaces any errors preventing display. "Detected but not shown" is a common status — it means the page qualifies but isn't currently displaying a rich result (usually because Google's rendering logic determines it doesn't fit the current query context, not because the schema is invalid).

Measure CTR changes. Compare CTR in Search Console before and after deploying schema on a cohort of pages. Use the date range comparison feature to isolate the schema deployment window from other changes. If rich results are showing, you should see CTR improvement on queries where your rich result is displayed.

Don't chase zero errors. Some schema validation warnings won't prevent rich result eligibility. Focus on actual errors (missing required fields, incorrect data types) rather than recommended field warnings.

Common schema markup mistakes#

Multiple schema blocks defining the same entity. Two Article schema blocks on the same page with conflicting author or datePublished values create ambiguous entity signals. Use a single, complete schema block per entity.

Schema that contradicts visible page content. Google cross-references schema against visible text. A product schema claiming 5-star ratings when there are no reviews on the page, or an Article schema with a datePublished that doesn't match any date shown in the content, creates a trust signal conflict. Schema must accurately reflect what users can see.

Using deprecated types. Implementing FAQ or HowTo schema expecting rich results in 2026 wastes implementation time that could go toward Product, Event, or Article schema that still generates results.

Missing the @context declaration. Every JSON-LD block needs "@context": "https://schema.org". Without it, the markup is invalid.

Static dateModified. A page that was published in 2023 and last significantly updated in 2025, but still shows dateModified: 2023-01-15, is sending an inaccurate freshness signal. Keep this field current with actual content changes.

Schema markup and AI citability#

Beyond traditional rich results, structured data plays a growing role in AI search. Google's AI Overviews — which appeared on approximately 13% of US desktop searches by early 2025 — preferentially cite pages where schema markup makes factual claims explicit and machine-readable.

Organization schema that explicitly declares what your company does, who runs it, and where to verify that information (via sameAs links) creates an entity record that AI models can reference without ambiguity. Article schema that clearly attributes authorship and declares publication dates helps AI systems evaluate source credibility. Product schema that states price, availability, and specifications gives AI shopping results the structured facts they need to cite your product.

The pattern is consistent with how structured data has always worked: it helps machines understand your content without relying on inference from unstructured text. In an environment where AI models are increasingly mediating search results, reducing the ambiguity AI systems face when processing your content is a direct AI visibility strategy.

How Climer supports schema implementation#

Climer's /generate-schema command builds JSON-LD blocks for any article — generating Article, FAQPage, BreadcrumbList, and Organization schemas with correct field mappings from your content metadata. When publishing new content, the agent flags pages that are missing schema or using deprecated types.

For monitoring, Climer surfaces schema validation errors from Google Search Console alongside crawl errors and Core Web Vitals data — so structured data issues appear in the same workflow as other technical health signals, not as a separate audit task.

Ready to grow your organic traffic?

Climer handles keyword research, content creation, and performance tracking — so you can focus on running your business. No credit card required.

Get started free

Related Articles

Technical SEO Audit: The Complete Guide (2026)

20 min read

Technical SEO Audit Checklist: 50 Checks for a Healthy Site

16 min read

Site Architecture for SEO: How to Structure a Website That Ranks

12 min read

SEO Site Structure: How to Build a Website Structure That Ranks

10 min read

Internal Linking Strategy: A Practical SEO Framework

9 min read