You copy a JSON-LD snippet from a tutorial, paste it into your page, and wait for the rich result to show up. Sometimes it does. Sometimes it doesn't, and Search Console quietly logs a warning you never see. The usual reason isn't a typo in the code — it's that the wrong schema type was used for the content in the first place. A product review got tagged as HowTo. A blog post got tagged as FAQPage because it happened to end with a Q&A. A recipe page got tagged as generic Article and lost the one rich result it actually qualified for.
FAQPage, HowTo, and Article are three of the most commonly confused schema types, because all three can technically be applied to a page that has questions, steps, and paragraphs on it at the same time. The trick isn't learning the syntax — it's learning which type actually describes what's on the page.
FAQPage marks up a list of questions with visible answers, HowTo marks up an ordered sequence of steps toward a task, and Article marks up a standard piece of written content like a blog post or news story. They target different content shapes, not different topics, so the right choice depends on how the page is structured, not what it's about.
What is schema markup?
Schema markup is structured data, most commonly written as JSON-LD, that describes what a
piece of content is in a format search engines can read directly, rather than inferring it
from raw HTML. FAQPage, HowTo, and Article are three separate @type values
within that vocabulary, each built around a different shape of content.
- FAQPage describes a set of
QuestionandAnswerpairs that are fully visible on the page, not hidden behind a click-to-reveal that changes the wording. - HowTo describes an ordered list of
HowToStepentries, each representing one action in completing a task, optionally with tools, supplies, and time estimates. - Article (and its subtypes
NewsArticleandBlogPosting) describes a standard written piece with a headline, author, publish date, and body content. - None of them are exclusive. A single page can legitimately carry Article schema for its main body and FAQPage schema for a genuine FAQ section beneath it.
The type isn't a label you pick for SEO effect — it's a structural description. If the markup doesn't match what a visitor actually sees on the page, it's not just ineffective, it can violate Google's structured data guidelines.
Why choosing the right type matters
Using the wrong schema type — or the right type filled in badly — has consequences beyond a missing rich result:
- Mismatched markup can be ignored or penalized. If HowTo schema is applied to a page with no actual step-by-step instructions, Google can disregard the markup or flag it as spam.
- Eligibility rules differ sharply by type. FAQPage rich results are now restricted to a narrow set of authoritative sites, while HowTo and Article eligibility depends on different criteria entirely — treating them as interchangeable wastes effort.
- Rich results change how a listing looks in search. Step counts, question dropdowns, and author bylines all compete for the same limited space in a search result, so the type you choose shapes what a searcher sees before they click.
- Wrong types can misrepresent content to search engines. A listicle tagged as HowTo, or an opinion piece tagged as FAQPage, sends an inaccurate signal about what the page actually delivers.
Step-by-step: picking and adding the right type
- Look at the content's actual shape first. Is it a list of questions with answers, an ordered sequence of steps, or a standard written piece? The shape decides the type, not the topic.
- Rule out overlap. A troubleshooting article with a few Q&A-style headers isn't automatically FAQPage — check whether the content is genuinely question-and-answer or just formatted that way for readability.
-
Write the markup in JSON-LD. Place it in a single
<script type="application/ld+json">block in the page head, keeping it separate from the visible HTML. - Match every field to visible content. Every question, step, headline, and author name in the markup should exist, word for word in meaning, somewhere on the rendered page.
- Layer types where genuinely appropriate. A recipe post can carry Article schema for the post itself and HowTo schema for the cooking steps, since both accurately describe different parts of the same page.
- Preview how it will actually appear in search. Rich result eligibility and appearance vary by type, so check the projected listing before assuming a rich result will show.
- Validate and monitor. Run the markup through a structured data validator, then check Search Console's Enhancements reports periodically, since Google's eligibility rules for these types change without much notice.
Common mistakes that cost you rich results
1. Tagging a Q&A-styled article as FAQPage
Headers phrased as questions don't make a page an FAQ — FAQPage schema is for a genuine list of discrete questions and answers, not a stylistic device inside a longer article.
2. Writing HowTo steps that don't match the page
If the markup lists eight steps but the visible content only walks through five, or reorders them differently, the mismatch between markup and rendered content is exactly what Google's guidelines prohibit.
3. Applying Article schema to non-article pages
Product pages, category pages, and landing pages aren't articles — using Article schema on them describes the page inaccurately and can conflict with more appropriate types like Product schema.
4. Assuming a rich result is guaranteed
Valid markup makes a page eligible for a rich result; it doesn't guarantee one. Google decides whether and when to display rich results independent of whether the markup is technically correct.
5. Forgetting to update markup when content changes
Editing a HowTo's steps or an FAQ's answers on the page without updating the matching JSON-LD leaves the markup describing content that no longer exists.
Real-world examples
How each schema type plays out on real page types:
The pattern across all four: the schema type follows the content's structure, and forcing a type onto content that doesn't fit it rarely produces the result you were hoping for.
FAQPage vs HowTo vs Article compared
A side-by-side look at what each type is for, and where it currently stands with Google.
| Type | Best for | Rich result status | Watch out for |
|---|---|---|---|
| FAQPage | Genuine question-and-answer content, fully visible on page | Restricted to select sites | Most sites won't see the dropdown even with valid markup |
| HowTo | Ordered, task-based instructions with discrete steps | Limited, device-dependent | Steps in markup must exactly mirror the visible sequence |
| Article | Blog posts, news stories, standard written content | Widely supported | Doesn't fit product, category, or landing pages |
Preview your rich results before you publish — free
The Rebrixe SERP Simulator renders your title, description, and structured data the way it will actually appear in search — so you can catch a mismatched schema type or a truncated headline before it goes live, not after. No account, no watermark.