01 The status in 2026
For three or four years, FAQ and HowTo schemas were everywhere. They earned rich results that took up triple the SERP real estate of a regular listing — accordion FAQ snippets, step-by-step HowTo cards. SEOs added them aggressively to almost any page they could justify.
Then in 2023, Google quietly dropped them from most search results. As of 2026, FAQ rich results trigger only for "well-known authoritative websites" (government, health authorities, major institutions). HowTo rich results were removed from desktop entirely and de-emphasised on mobile.
This guide covers what's still useful, what's not, and whether it's worth implementing either schema in 2026.
02 FAQ schema — what changed
The original FAQPage schema told Google "this page contains a list of questions and their answers." When Google trusted the markup, it could display the questions as an expandable accordion in the SERP, dramatically increasing visibility.
The problem: the schema got abused. Sites added FAQ markup to product pages, blog posts, even category pages — anywhere they could find or invent question-answer pairs. The accordion took over SERPs and pushed organic results below the fold.
Google's response (August 2023): restrict FAQ rich results to a narrow set of authoritative domains. Most sites now get no rich-result benefit from FAQ schema, regardless of how much they implement.
03 Where FAQ schema still triggers
FAQ rich results in 2026 still appear for:
- Government domains (gov.* TLDs).
- Major health authorities (WHO, NHS, CDC, etc.).
- Specific recognized authoritative sites in regulated industries.
For everyone else, FAQ schema no longer earns the accordion. But it still has value:
- Voice search and assistant answers. Voice queries that map to a question often pull from FAQ-tagged content.
- "People Also Ask" boxes. Google may use FAQ-tagged content in PAA panels even when no FAQ rich result triggers.
- Entity understanding. Question-answer pairs help Google understand the page's topical coverage.
So FAQ schema isn't dead — it's just no longer a guaranteed-rich-result lever. Add it where the questions and answers are genuinely useful to users, and skip it where they're not.
04 HowTo schema — also restricted
HowTo schema followed a similar trajectory. Initially it could earn step-by-step cards in the SERP, with images, time estimates and tools. Google removed HowTo rich results from desktop search in late 2023 and significantly reduced their appearance on mobile.
As of 2026, HowTo schema offers minimal SERP benefit. The technical implementation is unchanged, but the rich-result payoff has gone.
Where it might still be worth implementing:
- Sites where mobile-only is a meaningful traffic source.
- Recipe-adjacent content where the step-by-step structure overlaps with Recipe schema benefits.
- Documentation pages where structured how-to data feeds into AI answer engines (Gemini, ChatGPT browsing, Perplexity).
05 Implementation reference
If you're implementing FAQ schema for the cases where it still pays back:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long does an SEO audit take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A single-URL audit usually completes in under 10 seconds…"
}
},
{
"@type": "Question",
"name": "Is the data I submit private?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. All audit data is hosted in Switzerland…"
}
}
]
}Two implementation rules that were always required and still apply:
- The questions and answers must be visible on the page. Marking up content that isn't visible is a policy violation.
- Don't mark up promotional or call-to-action content as FAQ — only genuine question/answer content.
HowTo schema follows the same pattern with "@type": "HowTo" and a step array.
06 Is it still worth implementing?
Honest answer:
- FAQ schema: only if you genuinely have an FAQ-style page. The schema costs almost nothing to add, and the indirect benefits (voice search, PAA, entity understanding) are real even without rich results. Skip it on pages where the "FAQ" is forced.
- HowTo schema: low priority in 2026. Implement it if you're already producing how-to content and have a templated way to add the markup. Don't go out of your way to refactor existing pages for it.
The bigger lesson from FAQ and HowTo is structural: schema-driven traffic strategies are fragile. Google adjusts which schemas earn rich results regularly, and SEO strategies built on a single rich-result type can collapse overnight. Build your traffic strategy on content quality and topical authority — schema is a multiplier, not a foundation.
→ Related guides
Keep going — these companion guides go deeper on related topics.