Skip to content
AEO Canon · the reference for answer-engine optimization

FAQPage vs HowTo Schema — When to Use Each

Use FAQPage schema for question-and-answer content and HowTo for ordered, step-by-step tasks. Google deprecated HowTo rich results and limited FAQ rich results to government and health sites in 2023 — but the markup still gives AI parsers clean, structured data.

BBurke Atkerson1 min read

Use FAQPage schema for question-and-answer content and HowTo schema for ordered, step-by-step tasks. Since 2023 most sites no longer earn rich results from either — but the markup still hands AI parsers clean, structured Q&A and step data.

Quick answer

FAQPage = discrete question/answer pairs. HowTo = one ordered procedure with steps. Google deprecated HowTo rich results and restricted FAQ rich results to government and health sites in 2023, so most pages won't get those snippets — yet the markup still gives AI a structured version of your content. Never invent fake FAQs for markup.

What changed in 2023?

Google narrowed both. It deprecated HowTo rich results entirely and restricted FAQ rich results to well-known, authoritative government and health websites. For most sites, that means the visible snippet is gone — but the underlying structured data still describes your content to any parser reading the page.

When do I use FAQPage?

When the content is genuine question-and-answer pairs. Support pages, "common questions" sections, and objection-handling blocks all fit FAQPage — each Question node holds one real question and its acceptedAnswer. The rule: mark up questions people actually ask, not padding.

When do I use HowTo?

When you're documenting a single ordered procedure. A HowTo describes a task with sequential steps — "how to reset a router," "how to change a tire." If the content isn't a step-by-step task, it isn't HowTo.

FAQPage
Discrete question/answer pairs
Support, common-questions, objections
No fixed order between items
FAQ rich results now limited to gov/health
Still gives AI clean Q&A structure
vs
HowTo
One ordered, sequential procedure
Tutorials and step-by-step tasks
Order is meaningful
Rich results deprecated in 2023
Still gives AI clean step structure
Pick by content shape — questions map to FAQPage, ordered tasks map to HowTo.

Where to go next

The honest question is whether any of this moves citations — read does schema help AI citations, then check the details of FAQPage schema before you implement.

Frequently asked questions

When should I use FAQPage vs HowTo schema?
Use FAQPage for discrete question-and-answer pairs and HowTo for a single ordered procedure with sequential steps. Match the markup to the content's actual shape — questions map to FAQPage, tasks map to HowTo.
Do FAQPage and HowTo still get rich results?
Mostly no. In 2023 Google deprecated HowTo rich results and limited FAQ rich results to authoritative government and health sites. Most sites no longer see those snippets, though the structured markup still helps AI parsers read your content.
Should I add fake FAQs just to use the schema?
No. Inventing questions users never ask produces thin, low-value content and can look manipulative. Only mark up genuine Q&A that reflects what people actually want to know.

Related reading

The schema types with the highest AEO payoff are Organization and Person (entity clarity and sameAs) and LocalBusiness (local context) — Article, FAQPage, and HowTo help parsing and rich-result eligibility, and Product helps shopping. Rank types by entity value instead of marking up everything.

2 min read

Use JSON-LD. It lives in a separate script block, is the easiest format to add and maintain, and is the one Google recommends. Microdata and RDFa embed markup as inline HTML attributes, which is verbose and harder to maintain — and both Google and AI parsers favor JSON-LD.

1 min read

A JSON-LD block has four load-bearing parts — @context sets the vocabulary (schema.org), @type declares what the thing is, @id gives it a stable identifier other nodes can reference, and the remaining properties describe it. Understanding each part lets you write and debug markup with confidence.

1 min read