Use FAQPage schema only when the page contains real, visible questions and answers; use Article schema for the article itself, and do not expect FAQ markup to save thin content. Google reduced FAQ rich result visibility for most sites in 2023, especially outside authoritative health and government domains [source: Google]. That changed the SEO value of FAQ schema. It can still help search engines understand content, but it is no longer an easy shortcut to larger search snippets.
TLDR: FAQPage schema is best for pages built around clear question-and-answer blocks, while Article schema is best for blog posts, guides, news pieces, and educational content. For example, a SaaS help article that added 6 visible FAQs saw impressions rise by 18% over 60 days, but clicks rose only 4% because FAQ rich results were not always shown. Use both only when the page truly supports both formats. Mark up the article as an Article, then mark up a genuine FAQ section as FAQPage.
FAQPage Schema vs Article Schema: What Each One Does
Article schema tells search engines that a page is an article. It can include the headline, author, date published, date modified, image, publisher, and main content details. It fits blog posts, tutorials, opinion pieces, research pages, and news-style content.
FAQPage schema tells search engines that a page contains a list of questions with direct answers. The questions must appear on the page. The answers must also be visible to users. Hiding answers in code only is a bad idea and may break Google’s structured data rules.
The catch is that many site owners still treat FAQ schema like a magic SEO button. It is not. It helps classify content. It may support rich results in limited cases. It does not replace useful answers, clean structure, or search intent.
When to Use Article Schema
Use Article schema when the page has a main editorial body. If the content has a title, author, publish date, sections, and a clear topic, Article schema usually belongs there.
- Blog posts: “How to Choose CRM Software”
- Guides: “Beginner’s Guide to Technical SEO”
- News articles: Product updates, industry news, company announcements
- Educational resources: Tutorials, explainers, comparison pages
Article schema gives search engines basic but useful context. It can help with content freshness, authorship signals, and eligibility for article-based search features. It also works well with other schema types, such as BreadcrumbList, Organization, and ImageObject.
Honestly, it feels like some SEO plugins make this more annoying than needed. You switch on one setting, then 40 seconds later you find the plugin added Article schema to a product page, a category archive, and a privacy policy. Always check the output with Google’s Rich Results Test before assuming it is correct.
When to Use FAQPage Schema
Use FAQPage schema when the content includes a proper FAQ section. Each item should have one question and one answer. The answer should be short enough to be useful, but complete enough to stand on its own.
Good FAQ questions sound like real user searches:
- What is FAQ schema?
- Can I use FAQPage schema on a blog post?
- Does FAQ schema improve rankings?
- Should every article have FAQ schema?
Bad FAQ questions are vague or promotional:
- Why are we the best?
- Do customers love our service?
- How amazing is this product?
Search engines are not impressed by padded content. Users are even less forgiving. If an FAQ section adds nothing, skip it.
Can You Use FAQPage Schema and Article Schema Together?
Yes, you can use both on the same URL if the page contains both an article and a real FAQ section. This is often the best setup for long-form SEO content.
For example, a 2,000-word guide about “email marketing automation” can use Article schema for the main guide. If the bottom of the page includes five visible questions and answers, that section can also use FAQPage schema.
The key is accuracy. Do not mark the entire article as FAQPage. Do not mark random headings as questions. Do not add FAQ schema for content that users cannot see. Structured data should describe the page, not decorate it.
Schema.org defines FAQPage as a page that contains one or more questions and answers, usually around a specific topic [source: Schema.org]. That definition is simple, but many implementations still get messy.
Does FAQ Schema Still Help SEO?
Yes, but its role has changed. FAQ schema is less about grabbing huge rich snippets and more about clarity. It helps search engines understand common questions tied to a page. It may also support voice search, AI summaries, site search features, and content extraction.
Still, rankings are not awarded just because a page has FAQ markup. Google ranks pages based on relevance, usefulness, quality, links, page experience, and many other signals. Schema supports interpretation. It is not a ranking bribe.
Expect to waste time if you add FAQ schema across 500 pages without checking intent. A legal article may benefit from FAQs. A short landing page with three sales blurbs probably will not. A product comparison page might benefit if users ask specific buying questions. A glossary page may not need it.
Best Practice: Use Article Schema First, Then Add FAQ Schema Only When Useful
For most informational pages, the safest SEO setup looks like this:
- Add Article schema to the main content.
- Add BreadcrumbList schema for site structure.
- Add Organization or Person schema where relevant.
- Add FAQPage schema only for visible, helpful Q&A content.
- Validate everything before publishing.
This setup keeps the page clean. It also reduces the risk of conflicting structured data. Search engines should be able to answer three simple questions: What is this page? Who created it? What extra details does it contain?
Common Mistakes That Hurt FAQ Schema SEO
- Adding FAQ schema without visible FAQs: This can violate structured data rules.
- Using sales copy as answers: FAQs should answer, not pitch.
- Repeating the same FAQs everywhere: Site-wide duplicate Q&A blocks look lazy.
- Marking comments as FAQ content: User-generated discussions are not the same as a curated FAQ.
- Using FAQPage schema for how-to steps: Use HowTo schema only where it fits and follows current search rules.
One more headache: some CMS themes inject schema you did not ask for. Then your SEO plugin adds its own. Now the page has two Article objects, one WebPage object, and a weird FAQ block from an old template. Check the rendered code, not just the editor screen.
How to Decide Which Schema Wins
Ask what the page mainly is. If it is mainly an article with a small FAQ section, Article schema is the primary type. FAQPage schema is secondary. If it is a pure FAQ page, such as a support page with 20 billing questions, FAQPage schema can be the main structured data type.
Here is a simple rule:
- Mostly editorial content? Use Article schema.
- Mostly questions and answers? Use FAQPage schema.
- Both are clearly present? Use both, but keep each markup tied to the correct content.
Final Recommendation
Article schema should be the default for SEO articles, guides, and blog posts. Add FAQPage schema only when the page includes helpful questions that real users would ask. Keep the FAQs visible. Keep the answers honest. Keep the markup clean.
The best SEO result comes from matching schema to content, not from adding every schema type you can find. If the page is useful, structured data can make it easier for search engines to understand. If the page is weak, FAQ schema will not carry it. That may be frustrating, but it saves everyone from search results stuffed with fake questions and empty answers.
