FAQ page schema vs review schema: which to use and when

FAQPage schema is for question-and-answer content. Review schema is for customer reviews and testimonials. The two are not interchangeable. Most content that gets FAQPage markup should not have it, and most content that could have Review markup does not.

The choice comes down to the intent of the content. Is the content answering a question the reader asked? FAQPage. Is the content evaluating a product or service from a customer’s perspective? Review. Same content can sometimes be both, but the choice depends on which intent you serve. Most pages should pick one and stick with it.

The 2024-2026 policy changes have also affected the calculus. Google has been de-emphasizing FAQPage rich results, while Review rich results are still visible for eligible content. The technical right answer (which schema fits the content) and the strategic right answer (which schema gets visible benefit) are not always the same page.

What FAQPage is for

FAQPage schema is for content that answers questions. The content has a question, the content has an answer, the content is structured as a Q&A pair. The reader comes to the page with a specific question and the page answers it.

The right use case: a help center article titled “How do I reset my password?” with a clear Q&A structure. The wrong use case: a marketing page with a list of “frequently asked questions” that are really marketing copy. The schema is the same, but the intent is different, and Google knows.

FAQPage schema is also for content that explicitly answers multiple questions in a list format. The schema structure expects a Question and an acceptedAnswer for each item. If the content is not actually a Q&A list, FAQPage is the wrong schema.

What Review schema is for

Review schema is for content that evaluates a product, service, or experience. The content is a customer review, a customer testimonial, or an editorial review. The reader comes to the page to see what someone else thinks.

The right use case: a testimonial wall where each entry is a customer review of the product. The schema structure expects a review body, a rating (optional), an author, and a reviewed item. If the content is a customer evaluation, Review is the schema.

The wrong use case: a marketing page with a list of “5-star reviews” that are actually just taglines with a star icon. The schema is the same, but the content needs to be a real review with substance, not a tagline with a star.

For the full Review schema implementation, the schema markup for testimonials page is the reference. The schema is strict about which content qualifies.

The decision tree

A simple decision tree for which schema to use.

• Is the content a customer review or testimonial? Use Review. With an AggregateRating for the wall as a whole.
• Is the content a Q&A list (multiple questions, each with an answer)? Use FAQPage. If you can also fit it as an Article or HowTo, FAQPage is the more specific choice.
• Is the content a single question with a single answer? Use QAPage (a related but distinct schema), not FAQPage. Or use Article if the question is the topic of the page.
• Is the content a how-to with steps? Use HowTo. Not FAQPage or Review.
• Is the content marketing copy that happens to have questions in it? Use Article or nothing. Not FAQPage.

The decision is not “FAQ or Review.” The decision is “which schema fits the content, and is the content actually structured that way?” Most content is not actually a Q&A or a review, even when it has questions or stars in it.

The 2024-2026 FAQPage policy changes

Google has been de-emphasizing FAQPage rich results over the past two years. The FAQ rich result (the expandable Q&A shown directly in search) is shown less often, for fewer sites, and for fewer queries than it was in 2022.

The change does not mean FAQPage schema is invalid. The schema is still in Schema.org. The data is still machine-readable. The change is that the visible benefit (the rich result) is less reliable than it was.

The strategic implication: do not choose FAQPage schema because you want the rich result. The rich result is less reliable. Choose FAQPage schema because the content is actually Q&A, and accept that the rich result may or may not appear. If your goal is the rich result specifically, FAQPage is a worse bet than it was two years ago.

Review schema has not had the same de-emphasis. The Review rich result (the star rating in search) is still shown for eligible content. The eligibility rules are stricter than FAQPage was, but the visible benefit is more reliable.

The common mistake

The most common mistake is using FAQPage schema for testimonials. The marketing team has a list of “5 things our customers love about us” and adds FAQPage markup. The content is not a Q&A list. The content is a marketing list with questions as section headers.

The fix is either: reformat the content as actual Q&A (with real questions and real answers), or use a different schema (Article, or nothing). FAQPage is the wrong schema for marketing lists.

The second most common mistake is using Review schema for editorial content that is not actually a review. An editorial team writes a “review” of the product category, and someone adds Review markup. The content is editorial, not a customer review. The schema is wrong.

The schema should match the content. If the content is a customer review, Review is right. If the content is editorial, Review is wrong. The intent of the content drives the schema choice, not the topic.

Where AggregateRating fits

AggregateRating is a related schema, not an alternative. It applies when the content is a collection of reviews (a wall of love, a product page with many reviews) and you want to surface the average rating and the count.

The use case is specific. A single testimonial on a page does not need AggregateRating. A wall of fifty testimonials does. A product page with fifty reviews does. The schema structure expects a rating value and a review count, and the underlying data must be real reviews of the same item, not a mix.

The mistake to avoid is using AggregateRating on a wall that has only testimonials, not ratings. The schema needs a numeric rating. If the wall has text-only testimonials with no stars, the right move is to either add ratings (so the schema is valid) or skip the AggregateRating markup (so the wall is not misleading).

AggregateRating is usually added alongside the individual Review items, not in place of them. The wall has fifty Review items, the wall as a whole has an AggregateRating, and both are emitted as separate schema blocks. The full implementation is in the schema markup for testimonials page.

The recommendation framework

A three-question framework for choosing the schema.

1. What is the content? Customer review, testimonial, Q&A list, how-to, marketing copy, or something else. The answer drives the schema choice.
2. Is the content structured that way? A list of “5 things” is not a Q&A list. A tagline with a star is not a customer review. The structure of the content matters, not just the topic.
3. Is the rich result worth it? FAQPage rich result is less reliable than it was. Review rich result is more reliable. Other schemas (Article, HowTo) have less rich result upside but more reliable schema validity.

When in doubt, use no schema. A page with no schema is still machine-readable. A page with the wrong schema is harder for machines to interpret than a page with no schema. The schema should add information, not noise.

For the full Review schema implementation, the schema markup for testimonials page is the reference. For the broader structured data context, the review schema pillar is the parent reference. For the AI-readable layer, the llms.txt for testimonials page covers the companion format.

The schema FAQPage vs Review distinction has a sibling. The customer referrals page is the dedicated reference.

FAQPage for testimonial pages: when to use it

FAQPage is a schema type for question-and-answer pages. The use case is a real FAQ page: a page where the visitor has questions and the page has answers. The schema tells Google which questions are on the page and what the answers are.

The FAQPage schema is NOT for testimonial pages. The visitor is not asking a question. The page is not answering one. The schema type for testimonial pages is Review. The team that uses FAQPage on a testimonial page is misapplying the schema. The team that uses Review is applying the right schema.

The one exception: a FAQ section on a testimonial page. The team that has both testimonials and a FAQ section can use both Review schema for the testimonials and FAQPage schema for the FAQ. The two schema types can coexist on the same page. The visitor sees both. The crawlers see both.

The 2026 schema landscape for testimonials

The 2026 schema landscape has 3 relevant types: Review (for individual testimonials), AggregateRating (for the wall), and FAQPage (for the FAQ section). The team that uses all 3 correctly on a testimonial page is the team that ranks for testimonial queries in 2026.

The schema reference is the Schema.org Review type. The full implementation guide is in the schema markup for testimonials page. The AI citability angle (the LLMs.txt side) is in the llms.txt for testimonials page. The AI search context is in the testimonials and AI search page.