FAQPage or Article Schema: Which Should You Use?

You've added structured data to your pages, but you're wondering: should you use FAQPage or Article schema? It's a common question, and the answer isn't always obvious. Both help search engines understand your content, but they serve different purposes and have different eligibility requirements. Let's break it down.

What Each Schema Type Does

Article schema marks up a single piece of content—a blog post, news article, or guide—so search engines can identify its headline, author, publish date, and main body. It's the standard for any page that's primarily text-based content.

FAQPage schema marks up a list of questions and answers on a page. It's designed for content that genuinely answers common queries, like a product FAQ section or a troubleshooting guide.

The Big Change: FAQ Rich Results Are Now Limited

Before 2023, adding FAQPage schema could earn you a rich result—a dropdown in search results showing your Q&As. That changed. Google now shows FAQ rich results only for authoritative government and health websites. For everyone else, FAQPage schema won't generate a visual rich result. It can still help search engines understand your content, but don't expect the fancy dropdown.

Similarly, HowTo schema's rich results were removed entirely. So if you were considering that, skip it.

When to Use Article Schema

Use Article schema when your page is a standalone piece of content—like a blog post, a news article, or a detailed guide. It's the safest, most universally understood schema for content pages. It tells Google: "This is a piece of editorial content, here's who wrote it and when." That's useful for establishing E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), especially if you include author and publisher markup.

Article schema is also a good choice if you have a Q&A section within a larger article. You can use mainEntity to mark up a Q&A within the article, but you don't need separate FAQPage markup for that.

When to Use FAQPage Schema

Even though FAQ rich results are limited, FAQPage schema still has value. Use it when your page is primarily a list of questions and answers—like a dedicated FAQ page, a product page with a Q&A section, or a support knowledge base. It helps search engines understand the relationship between questions and answers, which can improve how your content appears in search features like voice search or featured snippets.

But here's the catch: if you're not a government or health site, you won't get the visual rich result. So weigh the effort. If your FAQ section is genuinely useful, adding FAQPage schema is still worth it for clarity. If you're only adding it to chase a rich result, you might be disappointed.

Can You Use Both on the Same Page?

Yes, you can. A page can have both Article and FAQPage schema if it's an article that includes a clear FAQ section. Use Article schema for the overall content, and then use mainEntity to mark up the FAQ section as a QAPage or FAQPage within that article. Google's documentation allows this, as long as the markup accurately reflects the content.

How to Choose: A Simple Decision Flow

1. Is your page primarily a piece of editorial content? → Use Article schema.
2. Is your page mostly a list of questions and answers? → Use FAQPage schema.
3. Is it an article with a Q&A section? → Use Article schema, and optionally mark up the Q&A with mainEntity.
4. Are you a government or health site? → FAQPage schema might earn you rich results, so prioritize it.
5. Are you adding FAQPage schema just for the rich result? → Reconsider. Without eligibility, the value is limited.

Implementation Tips

• Use JSON-LD format—it's the easiest and recommended by Google.
• Validate your markup with Google's Rich Results Test and the Schema Markup Validator.
• Ensure the content matches the markup. Don't mark up content that isn't visible on the page.
• For Article schema, include headline, author, datePublished, and image.
• For FAQPage schema, each question must have a name and acceptedAnswer with text.

The Bottom Line

Article schema is the safe default for content pages. FAQPage schema is situational—use it for dedicated FAQ content, but don't expect rich results unless you're a gov/health site. The real benefit of structured data is helping search engines understand your content, which can lead to better visibility in other ways.

If you're unsure whether your current schema is set up correctly, run a free audit to see how your site's structured data and other technical elements stack up. You might also want to browse our guides library for more on technical SEO.

Remember: schema is a signal, not a guarantee. Focus on creating genuinely helpful content, and use schema to make that content easier for search engines to parse.

More guides · Compare audit tools · Run a free website audit