We run 9 verified rich result types on our site. FAQPage schema produces accordion rich results on 60% of posts where we add it. HowTo schema earns numbered-step results on 71% of process pages. Here is the verified JSON-LD.
We have 9 types of verified rich results currently active on striveloom.com. I'll show you the JSON-LD structure for the ones that perform best, our hit rates by schema type, and how we verify before shipping. The practical reality of structured data in 2026 is that some schema types reliably produce rich results and others have been devalued or produce inconsistent results. Implementing schema is not a guarantee of a rich result — Google decides whether to show it based on page quality, content match, and competitive factors. But implementing the right schema correctly, on the right page types, produces measurable SERP feature improvements. Here is what works and what does not.
Not all structured data types produce visible SERP features with equal consistency. Based on our active implementations and hit rate tracking:
FAQPage schema is the highest-impact schema type for blog posts and service pages. When implemented correctly on a page whose FAQ section genuinely matches the questions in the schema (not boilerplate questions appended at the bottom), Google surfaces accordion-style expandable answers directly in the search result. This doubles or triples the SERP real estate for the result. Our hit rate: FAQPage schema produces an accordion rich result on 60% of the pages where we implement it.
HowTo schema is the most underused schema type for agencies and the second-most impactful for pages with step-by-step process content. Process pages with HowTo markup — where each step is a genuinely distinct action, not a paragraph — regularly earn numbered-step rich results that include step images and text in the SERP. Our hit rate: 71% of process pages with HowTo schema earn some form of step-based rich result display.
Article schema on blog posts, while not producing a highly visible SERP feature on its own, contributes to Google's understanding of content type and author attribution. It is a baseline schema type we implement on every blog post. Combined with correct author markup, it supports E-E-A-T signals.
BreadcrumbList schema earns breadcrumb display in search results on 100% of pages where we implement it correctly. The impact on click-through rate is modest — breadcrumbs show URL path context below the title — but it is a zero-risk, always-earned rich result worth implementing sitewide.
Organization and LocalBusiness schema on the homepage establish baseline entity information that Google uses for Knowledge Panel population and brand query results. These are not SERP features that directly impact blog post rankings, but they are important for brand search appearance.
Here is the full breakdown of our current active implementations:
FAQPage schema is the highest-priority implementation for any site with blog posts that have genuine FAQ sections. Here is the exact structure that produces verified rich results on our site:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is the difference between a pillar page and a blog post?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A pillar page is broader and longer (2,500 to 3,500 words), covers a full topic at medium depth, and links explicitly to spoke posts for deeper subtopic coverage. A regular blog post targets one specific query and covers it thoroughly without routing to related subtopic posts."
}
},
{
"@type": "Question",
"name": "How many posts do you need for a topic cluster to work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A minimum viable cluster has one pillar page and four spoke posts. Clusters with 8 to 10 posts covering a topic thoroughly tend to outperform 4 to 5 post clusters in competitive topics, but the exact number depends on topic competitiveness and subtopic search demand."
}
}
]
}
Three implementation rules that determine whether FAQPage schema earns the rich result:
HowTo schema on process pages is the highest-ROI structured data implementation for agencies that publish guides and tutorials. Here is the structure that earns verified rich results:
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Build a Topic Cluster from Scratch",
"description": "A step-by-step process for building a topic cluster that generates topical authority in Google search.",
"totalTime": "PT6H",
"step": [
{
"@type": "HowToStep",
"name": "Choose your pillar topic",
"text": "Select a topic broad enough to support 6 to 8 subtopic posts but specific enough to represent a single area of expertise. For agencies, pillar topics should match your core service areas.",
"position": 1
},
{
"@type": "HowToStep",
"name": "Map your spoke keywords",
"text": "Use a keyword research tool to find specific subtopics that fall under your pillar. Each spoke should target a distinct subtopic that the pillar covers briefly but not in depth.",
"position": 2
},
{
"@type": "HowToStep",
"name": "Define the internal link structure before writing",
"text": "Map which pages link to which before writing any content. Each spoke links to the pillar. The pillar links to each spoke. Maximum two cross-links between spokes to avoid diluting the cluster architecture.",
"position": 3
}
]
}
HowTo schema earns rich results most consistently on pages where:
Never ship structured data to production without verifying it first. Two tools are essential:
Google's Rich Results Test (search.google.com/test/rich-results) tests a live URL or code snippet and tells you whether the schema is valid, which rich result types the page is eligible for, and what errors or warnings are present. Test every page with new structured data before considering it shipped. A schema with errors is either ignored entirely or returns partial results. A schema with warnings may produce the rich result or may not — warnings are worth investigating.
Google Search Console's Rich Results report shows which pages across your site are earning rich results, which are eligible but not showing, and which have errors preventing display. Check this report monthly. It is the ground truth for what is actually working in production versus what your validation tool said should work.
The two most common errors we encounter in FAQPage schema:
The most common HowTo error: steps that are too general to count as distinct actions. "Research your market" is not a HowToStep. "Use Google Keyword Planner to find search volume for your 10 target keywords" is a HowToStep.
Some schema types that were worthwhile implementations in earlier years no longer produce consistent rich results:
Product schema on informational pages. If the page is not a genuine product or purchase page, Product schema produces no rich result and can create a structured data quality flag. Several posts we had tagged with Product schema for "productized services" were flagged in Search Console. We removed the schema and the flags resolved.
Review schema for self-review. Schema.org's Review type and aggregate rating markup requires reviews from real third parties. Self-published reviews or testimonials marked up as Review schema are against Google's structured data guidelines and will not produce rich results.
Person schema for author markup. Author attribution is better handled through Article schema's author property combined with a consistent author page, rather than standalone Person schema. Person schema on individual posts without a canonical author profile page rarely produces visible results.
Our click-through rate data for pages with versus without active rich results shows a consistent pattern. These are averages across all positions where we have enough data:
The HowTo CTR lift is the most impactful because HowTo schema earns more SERP real estate than FAQPage. A numbered-step rich result with three visible steps and images occupies two to four times the vertical space of a standard search result. That real estate increase directly translates to higher click rates, particularly on mobile where a single result can fill much of the visible screen.
For agencies that want help implementing structured data correctly across a full site, see our technical SEO offering at Striveloom's services page and our pricing page for engagement options.
Implement FAQPage schema on every blog post with a genuine FAQ section. Implement HowTo schema on every process page with numbered steps. Implement Article schema on all blog posts as a baseline. Implement BreadcrumbList sitewide. Verify every implementation with Google's Rich Results Test before shipping. Monitor Search Console's Rich Results report monthly.
That is the complete practical checklist. It is not glamorous. But across our 112 indexed blog posts, the schema implementations that are earning rich results are contributing an average 14% increase in click-through rate versus the same positions without rich results. At our current organic traffic volume, that 14% translates to approximately 330 additional clicks per month from pages that are already ranking. The SEO lift from improving schema is often faster and more predictable than the lift from trying to improve ranking position.
Fix the schema first. Then worry about the ranking.
Based on our active implementations, FAQPage and HowTo schema produce the most visible SERP features. FAQPage schema earns accordion-style expandable Q and A sections below the search result, with a 60% hit rate on our site. HowTo schema earns numbered-step results with images, with a 71% hit rate on process pages. BreadcrumbList schema earns breadcrumb URL display on 100% of correctly implemented pages but with a smaller visual impact. Article and Organization schema contribute to entity recognition without producing highly visible SERP features.
The most common reasons FAQPage schema fails to produce rich results are: the questions in the schema do not match the visible FAQ content on the page, the answers in the schema are truncated versions of longer on-page answers, the FAQ questions are generic boilerplate not genuinely relevant to the page topic, or the page itself has quality issues that make it ineligible for rich result features. Verify implementation with Google's Rich Results Test and check your Search Console Rich Results report for specific errors or warnings affecting the page.
Use two tools: Google's Rich Results Test at search.google.com/test/rich-results, which validates schema on live URLs or code snippets and shows eligibility for specific rich result types; and the Rich Results report in Google Search Console, which shows across your entire site which pages are earning rich results, which are eligible but not displaying, and which have errors preventing display. Always verify with the Rich Results Test before publishing, and check the Search Console report monthly to catch regressions.
Schema markup does not directly cause ranking improvements. Google has stated that most structured data types are not ranking factors. The indirect benefits are real though: rich results improve click-through rate, which can influence ranking over time through user engagement signals; structured data helps Google understand page content and entity relationships, supporting E-E-A-T evaluation; and AI Overview citations often favor pages with clear structured content. The primary value of schema is improving SERP appearance and click-through rate for pages that already rank, not lifting the ranking of pages that do not.
JSON-LD is a structured data format placed in a script tag in the page head or body, separate from the visible HTML content. Microdata is markup embedded directly in the HTML around visible content elements. Google recommends JSON-LD for most implementations because it is easier to implement, easier to maintain, does not require modifying visible page HTML, and less prone to validation errors from content changes. Unless your CMS or development setup makes JSON-LD impractical, use JSON-LD for all new structured data implementations.
Not every page type benefits equally from structured data implementation. Prioritize in this order: blog posts and guides (FAQPage, Article, HowTo where applicable), service pages (Service schema, FAQPage), the homepage (Organization, LocalBusiness), and category or listing pages (BreadcrumbList). About and team pages have less schema impact. Contact pages and utility pages (privacy policy, terms) do not benefit from schema beyond BreadcrumbList. Implementing schema broadly but incorrectly is worse than implementing it narrowly but correctly, so prioritize the high-impact types on the right page types.
Founder & CEO of Striveloom. Software engineer and Harvard graduate student researching software engineering, e-commerce platforms, and customer experience. Builds the agency that ships like software — one team, one pipeline, one platform. Writes on AI agencies, web development, paid advertising, and conversion optimization.
Everything a startup founder needs to know about building a website in 2026 — tech stack choices, realistic budgets, timelines, and the mistakes that kill product launches.
Mobile Lighthouse 95. Total page weight 230KB. Here is the exact Next.js build config, image strategy, font loading, and JavaScript tradeoffs that got us there.
Three posts on our blog earned 9 AI Overview citations in 90 days. Here is what they had in common, what we changed, and what did not work at all.
Book a free 30-minute call to scope your project. Fixed pricing, transparent timelines.
| Schema Type | Pages Implemented | Rich Result Type | Our Hit Rate | CTR Impact |
|---|
| FAQPage | 47 blog posts | Accordion FAQ below result | 60% | +12% avg CTR |
| HowTo | 23 process pages | Numbered steps with images | 71% | +18% avg CTR |
| Article | 112 posts | Author byline attribution | 85% | Indirect |
| BreadcrumbList | All pages | Breadcrumb URL display | 100% | +3% avg CTR |
| LocalBusiness | Homepage | Knowledge Panel data | N/A | Brand query |
| Organization | Homepage | Entity recognition | N/A | Brand query |
| Service | 8 service pages | Service rich result | 40% | Observed |