When FAQ and HowTo schema still earn SERP visibility on SaaS pages
Written by Olayinka Olayokun·Published ·Updated ·Verified
FAQ and HowTo schema for SaaS are the structured data types that mark up frequently asked questions and step-by-step tutorials. Since 2023, Google shows FAQ rich results primarily for authoritative government and health sites, and HowTo for desktop-only on recognised tutorial sources — but the schema still feeds AI Overviews and SERP comprehension for all sites.
Summary and key takeaways
Google cut FAQ rich results for most sites in mid-2023 — they now show mainly for government and health authorities. HowTo rich results show desktop-only for recognised tutorial sites. But both schemas still feed AI Overviews and improve SERP comprehension for everyone, so they're worth implementing on real FAQ and tutorial pages even when the SERP-card stars aren't showing up.
- •FAQ rich results in SERPs are now restricted to government and health-authority sites.
- •HowTo rich results show desktop-only for recognised tutorial sites; mobile and most SaaS sites don't get them.
- •Both schemas still feed AI Overviews — and AIO citation is increasingly the bigger SEO prize.
- •FAQ schema requires genuinely-asked questions, not marketing copy disguised as FAQs.
- •HowTo schema requires real step-by-step instructions; using it on listicles invites manual action.
In plain English ·FAQ and HowTo schema lost their universal SERP rich-result entitlement in 2023, but both still feed AI Overviews and improve query comprehension. Use FAQPage on real FAQ pages and HowTo on step-by-step tutorials, even without the rich-card incentive.
- Mid-2023
- When Google restricted FAQ rich results to government and health authority sites Google Search Central blog
- Desktop-only
- Surface where HowTo rich results still appear (mobile removed) Google Search Central blog
- AIO citation
- Primary SEO benefit of FAQ/HowTo schema for non-authority SaaS sites today SERPNAUT playbook
How this compares
| Schema | SERP rich result | AIO citation | Recommendation |
|---|---|---|---|
| FAQPage on authority site | Yes | Yes | Implement |
| FAQPage on SaaS site | No | Yes | Implement for AIO + comprehension |
| HowTo on recognised tutorial site | Desktop only | Yes | Implement |
| HowTo on listicle / promo | Never (risks manual action) | Negative | Do not use |
Part of the Schema Markup for SaaS: JSON-LD That Actually Validates guide
FAQ and HowTo schema for SaaS are the structured data types that mark up frequently asked questions and step-by-step tutorials. Since 2023, Google shows FAQ rich results primarily for authoritative government and health sites, and HowTo for desktop-only on recognised tutorial sources — but the schema still feeds AI Overviews and SERP comprehension for all sites.
The 2023 Google update changed FAQ/HowTo schema from 'free SERP rich results for everyone' to 'mostly invisible in SERP but still useful for AI Overviews and query comprehension'. Most teams either over-react by ripping out the schema entirely (losing AIO citation) or under-react by leaving it on inappropriate pages (risking manual action). The middle ground is selective use on real FAQ and tutorial content.
What this chapter covers: real-content-only, aio-focused, sparse use, validated.
What changed in 2023 and what didn't
August 2023: Google restricted FAQ rich results to government and health-authority sites. SaaS sites with FAQ schema stopped seeing the expandable FAQ cards in SERPs.
August 2023: Google restricted FAQ rich results to government and health-authority sites. SaaS sites with FAQ schema stopped seeing the expandable FAQ cards in SERPs.
HowTo rich results were restricted to desktop SERPs only and limited to recognised tutorial domains. Most SaaS sites lost mobile HowTo visibility too.
What didn't change: both schemas still feed AI Overviews, still help Google understand page topic, still enable query coverage signals. The schema is valuable; the SERP-card incentive is mostly gone for non-authorities.
When to use FAQPage
Dedicated FAQ pages on the site (e. g. /help/faq, /pricing#faq). Real questions, substantive answers, ideally questions that map to real searches in Search Console's queries report.
Dedicated FAQ pages on the site (e.g. /help/faq, /pricing#faq). Real questions, substantive answers, ideally questions that map to real searches in Search Console's queries report.
Bottom-of-page FAQ blocks on pillar guides — the 4–6 questions a reader would naturally ask after reading the article. These feed AI Overviews effectively and improve dwell-time signals.
Don't use on: product landing pages dressed up with marketing 'FAQs', generic 'About us' Q&A sections, or anywhere the 'question' is really a headline for sales copy.
When to use HowTo
Genuinely step-by-step tutorial content with discrete actions. Example: 'How to connect Stripe to Invoicemonk' broken into 8 steps, each with a screenshot and an outcome.
Genuinely step-by-step tutorial content with discrete actions. Example: 'How to connect Stripe to Invoicemonk' broken into 8 steps, each with a screenshot and an outcome.
Not appropriate for: listicles ('10 ways to grow your SaaS'), opinion pieces, generic guides without enumerated steps, or any content where 'step 3' could be re-ordered without breaking the tutorial.
Misuse risk: Google's manual reviewers periodically sweep for HowTo abuse. A flagged site loses HowTo rich result eligibility globally; the recovery process takes weeks.
Implementation pattern
FAQPage: one JSON-LD block per page with @type FAQPage, mainEntity array of Question objects, each with acceptedAnswer. text. Match the visible HTML exactly — schema diverging from visible content triggers spam signals.
FAQPage: one JSON-LD block per page with @type FAQPage, mainEntity array of Question objects, each with acceptedAnswer.text. Match the visible HTML exactly — schema diverging from visible content triggers spam signals.
HowTo: one JSON-LD block per tutorial with @type HowTo, step array of HowToStep objects, each with name, text, and optionally image. Total steps in schema must equal total steps shown to users.
The checklist for this chapter
- ✓Apply FAQPage only on pages with real, search-derived questions
- ✓Apply HowTo only on pages with discrete, ordered, actionable steps
- ✓Match schema content to visible page content exactly
- ✓Validate every implementation with Rich Results Test
- ✓Track AI Overview citation rate, not SERP rich card impressions
- ✓Audit annually for new manual-action risk patterns
Where this chapter sits in the guide
SoftwareApplication schema — FAQ/HowTo are content-type schemas; SoftwareApplication is a product-entity schema. Read the softwareapplication schema for saas chapter →
AI Overview citation — both schemas give LLMs structured access to question/answer and step/instruction content.
the page format — implementing FAQPage commits the page to maintaining a true FAQ block; HowTo commits the page to step-by-step structure.
Rich Results Test (for syntactic validity) and manual SERP / AIO inspection (for actual visibility).
Quick answers about faq and howto schema for saas
- Is FAQ schema still worth implementing in 2026?
- For most SaaS sites — yes, but the rationale shifted. SERP rich-card eligibility is mostly gone outside authority sites, but AI Overviews lean heavily on FAQ schema for citation. Marking up real FAQs on real FAQ pages still earns visibility, just in a different surface than two years ago.#
- Which pages should have FAQ schema?
- Dedicated FAQ pages, product FAQ sections on landing pages, and the bottom-of-page FAQ blocks on pillar guides — provided the questions are real and the answers are substantive. Don't bolt FAQ schema onto unrelated pages just to chase rich results.#
- When is HowTo schema appropriate?
- On genuinely step-by-step tutorial content with a sequence of discrete actions, each producing a visible outcome. 'How to set up Stripe' as 8 numbered steps is appropriate. 'How to grow a SaaS business' as a listicle of tips is not — that's HowTo abuse and risks manual action.#
- What triggers a HowTo manual action?
- Using HowTo on promotional content, listicles disguised as tutorials, or pages where the 'steps' aren't actionable instructions. Google's manual reviewers periodically sweep for these patterns; sites caught lose rich result eligibility globally for HowTo, sometimes for months.#
Questions about faq and howto schema for saas
- No — keep it on pages with real FAQ content. The schema still feeds AI Overviews and helps Google understand the page. Remove only from pages where the 'FAQ' was marketing copy that should never have had schema applied.
- Google restricted FAQ and HowTo rich result eligibility in August 2023. Google Search Central — HowTo and FAQ changes
- FAQPage is the schema.org type for genuine FAQ pages. schema.org — FAQPage
This chapter is one node in the founder-led playbook. To see which nodes your specific URLs are bleeding traffic from, get a founder-grade SEO audit of your URLs. Same six disciplines, applied to the pages you actually own.
Olayinka Olayokun
Founder, SERPNAUT and Invoicemonk
Written by Olayinka Olayokun. I run SERPNAUT, a founder-led SEO service for B2B SaaS, and Invoicemonk, the SaaS I grew from zero to 300+ organic visits and a paying customer in 28 days using the same playbook. Everything below is what worked on my own URLs and on the audits I've shipped since.
More chapters in this guide
FAQ and HowTo schema are quieter wins than they were in 2022, but they're still wins — just in different surfaces. AI Overviews lean heavily on both. Implemented on real content with discipline, they earn visibility that the SERP-card era's blanket implementations never did. Skipping them entirely concedes the AIO citation lane to competitors who didn't.
See the full guide at schema markup for saas: json-ld that actually validates. The commercial bridge above is the canonical path from this chapter to your URLs.