BlogPosting Schema vs FAQPage Schema: The Core Distinction
BlogPosting Schema is structured data that identifies a page as a written article — it signals authorship, publication date, headline, and editorial context to search engines. FAQPage Schema marks up a page that contains a list of questions with their corresponding answers. One describes what a piece of content *is*; the other describes a specific structural pattern *within* content.
The practical difference shows up immediately in how Google renders each type. BlogPosting Schema contributes to rich results like article carousels and byline display in Google News or Discover. FAQPage Schema drives the expandable question-and-answer accordion that can appear directly beneath a search listing. These are distinct SERP features, triggered by different signals, serving different search intents.
What Each Schema Type Actually Marks Up
BlogPosting Schema wraps document-level properties: `headline`, `author`, `datePublished`, `dateModified`, `image`, `publisher`, and `description`. These properties describe the article as a whole object. Search engines use this data to establish content freshness, attribute authorship for E-E-A-T signals, and determine eligibility for article-type rich results. There is no inherent requirement for a specific content structure — a long-form guide, a news post, and a product review can all carry BlogPosting markup.
FAQPage Schema wraps a `mainEntity` array of `Question` and `Answer` pairs. Every question must have exactly one accepted answer, and that answer must already appear on the visible page — Google does not accept FAQ markup that hides answers behind a paywall or requires user interaction to reveal. The schema is entirely about repeating structured Q&A units, not about the document as a whole entity.
A single URL can carry both schema types simultaneously. An ecommerce brand publishing a blog post that ends with a FAQ section can implement BlogPosting at the document level and FAQPage for the Q&A block. Search engines process both independently and may display both types of rich results for the same page.
SERP Eligibility and Rich Result Differences
BlogPosting Schema makes a page eligible for the Top Stories carousel, Google Discover cards, and the byline/image treatment in standard blue-link results. These placements reward freshness and authorship — the schema properties `datePublished` and `author` directly influence whether a post qualifies. Pages without a recognized publication entity or consistent update cadence see limited benefit from BlogPosting markup alone.
FAQPage Schema makes a page eligible for the FAQ accordion in desktop and mobile search results, which expands the physical space a single listing occupies. Each accordion item shows one question-answer pair from the markup. Google has narrowed eligibility for this feature over time, prioritizing authoritative government and health sites in some query categories, but ecommerce product and category pages with genuine FAQ content still qualify.
The two schema types therefore compete for different SERP real estate. BlogPosting Schema targets top-of-page placement through content discovery features. FAQPage Schema targets enhanced organic listings that expand visibility within standard search results. Neither schema type guarantees its associated rich result — Google treats all structured data as eligible signals, not automatic triggers.
When to Apply Each Type to Ecommerce Content
Apply BlogPosting Schema to any URL whose primary content is an authored article: buying guides, trend posts, how-to articles, brand stories, and editorial comparisons. The schema is most valuable on pages where demonstrating recency and authorship serves the content's purpose — for example, a seasonal gift guide that gets updated annually benefits from clear `dateModified` markup so search engines surface the current version rather than a cached earlier iteration.
Apply FAQPage Schema to any page — blog post, product page, category page, or landing page — that contains a discrete list of questions with visible answers. A product detail page with a 'Common Questions' section at the bottom is a legitimate FAQPage Schema candidate even if the rest of the page carries Product Schema. The key criterion is that the Q&A content exists on the page, not that the page is primarily a FAQ document.
For ecommerce blog content that includes a FAQ section, implement both. Use BlogPosting at the top level with standard article properties, then nest FAQPage markup within the same JSON-LD block or as a separate script tag. Google's Structured Data Testing Tool and Rich Results Test both handle multiple schema types on a single page without conflict.
Common Implementation Mistakes That Hurt Both Schema Types
The most frequent BlogPosting Schema error is omitting `datePublished` or using an inconsistent date format — Google requires ISO 8601 format and ignores markup where dates contradict visible on-page text. For FAQPage Schema, the equivalent error is marking up questions whose answers do not appear in the visible HTML. If a user must click to expand an accordion to read the answer, the markup may still qualify, but if the answer text is completely absent from the page source, the markup is invalid.
Another mistake is applying FAQPage Schema to dynamically generated Q&A content that changes based on user input or session state, since search engine crawlers see only the server-rendered version. For BlogPosting Schema, a common error on ecommerce sites is applying it to category or product pages to try to capture article rich results — this misrepresents the page type and will not generate article-type features because the underlying content does not match the schema's semantic intent.
Choosing Between Them: A Practical Decision Framework
Start with the page's primary content type. If the page exists to deliver a written article authored by a person or brand editorial team, BlogPosting Schema is the baseline requirement. If the page contains a list of questions and visible answers — regardless of whether it is also an article — add FAQPage Schema on top. These are not competing choices in most ecommerce content scenarios; they address different dimensions of the same page.
Prioritize FAQPage Schema when the primary conversion goal is capturing more SERP real estate on high-intent queries. A product-adjacent blog post answering 'What size air purifier do I need?' benefits more from FAQ accordion visibility on that specific search query than from an article carousel placement. Prioritize BlogPosting Schema when the goal is content discovery, brand authority in Google News or Discover, and long-term freshness signaling for evergreen guides.