Schema Markup Dat Echt Verkeer Oplevert
There are over 800 schema types on schema.org. Google supports rich results for about 30 of them. Most sites implement schema that Google completely ignores — WebPage schema, Organization schema without a Knowledge Panel, breadcrumb markup that duplicates what Google already infers. Effort wasted.
The question isn't "should I add schema markup?" It's "which schema types will Google actually render as rich results in the SERP, and how much will they increase my click-through rate?"
The answer is specific and measurable. Here's the data.
Schema Types That Actually Trigger Rich Results
Not all schema is created equal. Google renders rich results for a limited set of schema types, and even within those types, only if the implementation meets specific requirements.
Tier 1: High-Impact Rich Results
These schema types consistently trigger visible SERP features and measurably increase CTR:
| Schema Type | Rich Result | CTR Increase (Average) | Requirements |
|---|---|---|---|
| FAQ | Expandable Q&A below listing | +15-25% | Min 2 questions, visible on page |
| HowTo | Step-by-step with images | +10-20% | Steps must match page content |
| Product | Price, availability, rating | +20-35% | Must have offer/price data |
| Review/AggregateRating | Star ratings in SERP | +15-30% | Valid rating scale, min 1 review |
| Article | Enhanced listing, date, author | +5-10% | Proper author/date markup |
Tier 2: Moderate-Impact Rich Results
| Schema Type | Rich Result | Notes |
|---|---|---|
| LocalBusiness | Knowledge Panel, Maps listing | Critical for local SEO |
| Event | Event listing with date/location | High CTR for event-specific queries |
| Recipe | Recipe card with prep time, calories | Food/cooking sites only |
| VideoObject | Video thumbnail in SERP | Requires valid video on page |
| JobPosting | Job listing in Google Jobs | Requires structured job data |
Tier 3: Low or No Visible Impact
These schema types are technically valid but rarely trigger visible rich results:
- WebPage — Google already knows it's a web page
- Organization — Only triggers Knowledge Panel if Google already recognizes the entity
- WebSite — Sitelinks search box only, and Google often generates this without markup
- BreadcrumbList — Google usually infers breadcrumbs from URL structure
- SpeakableSpecification — Experimental, limited to Google Assistant
Focus your implementation effort on Tier 1 and Tier 2. Everything else is optional maintenance.
Implementation with JSON-LD
Google recommends JSON-LD (JavaScript Object Notation for Linked Data) as the preferred format for structured data. It's separate from the HTML content, easier to maintain, and less prone to errors than microdata or RDFa.
FAQ Schema (The Highest ROI)
FAQ schema is the single highest-ROI structured data investment for most B2B sites. It expands your SERP listing with accordion-style Q&A, increasing your visual footprint by 200-400%.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How much does a custom website cost?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Custom websites typically range from $15,000 to $40,000 for B2B sites with CMS integration, multi-language support, and performance optimization. The three-year total cost of ownership is often comparable to template-based sites when maintenance costs are factored in."
}
},
{
"@type": "Question",
"name": "How long does a custom website take to build?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A typical custom B2B website takes 8-12 weeks from design to launch. This includes discovery, design, development, content integration, and testing. Complex sites with e-commerce, multi-language, or custom integrations may take 16-20 weeks."
}
}
]
}
Critical rule: Every question and answer in your FAQ schema must be visibly present on the page. Google's guidelines explicitly state that FAQ markup for content not visible to users violates their structured data policies and can result in a manual action.
Article Schema
For blog posts and articles, Article schema helps Google display the author name, publication date, and sometimes a thumbnail:
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Schema Markup That Actually Drives Traffic",
"author": {
"@type": "Person",
"name": "Minh LE",
"url": "https://empirium.io/about"
},
"publisher": {
"@type": "Organization",
"name": "Empirium",
"logo": {
"@type": "ImageObject",
"url": "https://empirium.io/brand/empirium-logo-512.png"
}
},
"datePublished": "2026-05-08",
"dateModified": "2026-05-08",
"image": "https://empirium.io/blog/seo/05-og.jpg",
"description": "Most schema markup adds no SEO value. The specific schema types that trigger rich results."
}
Service Schema for B2B
For service pages, combine Service and Offer schema to display pricing and service details:
{
"@context": "https://schema.org",
"@type": "Service",
"name": "Custom Website Development",
"provider": {
"@type": "Organization",
"name": "Empirium",
"url": "https://empirium.io"
},
"description": "Custom-built websites with Next.js, headless CMS integration, and performance optimization.",
"areaServed": "Worldwide",
"serviceType": "Web Development"
}
Implementation in Next.js
In Next.js, inject JSON-LD in your page's metadata or as a script tag in the layout:
export default function BlogPost({ article }) {
const jsonLd = {
'@context': 'https://schema.org',
'@type': 'Article',
headline: article.title,
author: { '@type': 'Person', name: article.author },
datePublished: article.publishedAt,
dateModified: article.updatedAt,
};
return (
<>
<script
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
/>
<ArticleContent article={article} />
</>
);
}
At Empirium, we generate schema programmatically from our content models. Every blog post, service page, and FAQ section automatically includes the appropriate structured data. No manual JSON editing required.
Validation and Testing
Implementing schema without validating it is like deploying code without testing. Three tools cover the full validation workflow:
Google Rich Results Test
The definitive test. Paste a URL or code snippet, and Google tells you:
- Which rich result types are detected
- Whether the implementation is valid
- Specific errors and warnings
Test every page type before deployment. A single missing required field can invalidate the entire schema.
Schema Markup Validator (schema.org)
More detailed than Google's tool — it validates against the full schema.org specification, not just Google's subset. Useful for catching structural errors that Google's tool might not flag but could cause issues with other search engines (Bing, Yandex).
Google Search Console
After deployment, monitor rich results in Search Console under Enhancements. GSC reports:
- Which pages have valid structured data
- Error counts by schema type
- Rich result impressions and clicks
- Changes over time
Check this weekly. Schema can break silently when page templates change or content is updated.
Automated Testing
For sites with many pages, integrate schema validation into your CI pipeline:
# Validate schema for all page types
npx structured-data-testing-tool --url https://yoursite.com/
npx structured-data-testing-tool --url https://yoursite.com/blog/example
npx structured-data-testing-tool --url https://yoursite.com/services
Common Mistakes That Waste Effort
Marking Up Content That Doesn't Qualify
Google's guidelines are specific about what qualifies for each schema type. Common violations:
- FAQ schema on pages without visible FAQ content. The questions and answers must be on the page, not hidden in tabs or accordions that require interaction.
- Review schema without actual reviews. Self-reviews or editorial ratings don't qualify for review rich results on commercial pages.
- HowTo schema for content that isn't instructional. A "how we work" page isn't a HowTo.
Violating these guidelines can result in a manual action that removes ALL your rich results — not just the violating pages.
Inconsistent Schema Across Page Types
If your blog posts have Article schema but your service pages have no schema at all, you're leaving traffic on the table. Every page type should have appropriate structured data. Map your schema strategy by page template:
| Page Type | Primary Schema | Secondary Schema |
|---|---|---|
| Homepage | Organization, WebSite | |
| Service pages | Service | FAQ |
| Blog posts | Article | FAQ (if applicable) |
| About page | Organization, Person | |
| Contact page | LocalBusiness | |
| Case studies | Article | Review |
Duplicate or Conflicting Schema
Having multiple @type: "Organization" blocks with different information confuses search engines. Use one Organization schema on the homepage, and reference it from other pages using @id.
Not Updating Schema When Content Changes
Schema that references outdated information — old prices, discontinued services, past events — can trigger rich results with wrong data. This damages credibility and can violate Google's freshness requirements for certain schema types. Keep schema in sync with content updates.
FAQ
Does schema markup directly improve rankings?
Schema markup is not a direct ranking factor. However, it indirectly improves rankings by increasing click-through rates (through rich results), improving crawl efficiency (through better content understanding), and supporting E-E-A-T signals (through author and organization markup). The CTR improvement alone makes it worth implementing — a 20% CTR increase on a page receiving 1,000 impressions/month translates to 200 additional clicks.
How does schema affect voice search?
Speakable schema and FAQ schema are the primary structured data types that influence voice search responses. When Google Assistant or other voice interfaces answer questions, they preferentially cite content that's marked up with structured data. FAQ schema is particularly effective because the question-and-answer format maps directly to voice query patterns.
Should I use schema for a service business without products?
Absolutely. Service schema, FAQ schema, and LocalBusiness schema are all relevant for service businesses. The FAQ schema alone can increase your SERP visibility significantly. Include questions that potential clients actually ask — pricing ranges, timeline expectations, geographic availability, and process descriptions.
Is there a limit to how much schema I can add to a page?
No hard limit, but Google recommends keeping structured data relevant and accurate. Adding 50 FAQ items to a page with only 5 visible questions violates guidelines. Add schema that reflects actual page content. For most pages, 2-3 schema types (Article + FAQ, or Service + FAQ + Organization) is the practical maximum.
How long before rich results appear after adding schema?
Typically 2-7 days after Google re-crawls the page. You can accelerate this by requesting re-indexing through Google Search Console. However, Google doesn't guarantee rich results even with valid schema — they evaluate whether the rich result would actually help users for each specific query.