FAQ Schema: When to Use FAQPage Markup and What It Can Still Do

FAQ schema is structured data for pages that present a list of questions and answers about one topic. Schema.org defines FAQPage as a WebPage that presents one or more frequently asked questions, and Google documents FAQPage, Question, and Answer as the markup used for FAQ content.

In simple terms, FAQ schema helps label a true FAQ page more clearly.

There is one important limit to keep in view. Google changed FAQ rich results in August 2023, and says FAQ rich results are now shown only for well known, authoritative government and health websites. For most other sites, including most commercial sites, FAQ rich results are no longer shown on a regular basis.

That changes the goal.

FAQ schema is still useful as a clean markup layer for real FAQ content, but it should not be treated as a quick route to more search features on a SaaS site. Google also says structured data does not guarantee rich result display.

Back to the Schema hub

What FAQ schema is

FAQPage markup is for pages where the site itself provides the questions and the answers. Google’s FAQPage documentation is clear on that point, and its QAPage documentation says not to use QAPage for content with one answer and no user submitted alternatives. In that case, Google says to use FAQPage instead.

That gives you a simple split:

• use FAQPage when the site publishes the questions and answers
• use QAPage when users can submit alternative answers to a question

This page fits closely with Schema for SEO, JSON LD Basics, and FAQ Blocks.

What FAQ schema can still help with

Google says it uses structured data to understand page content, and FAQPage remains in Google’s structured data documentation and Search gallery. At the same time, Google’s 2023 update sharply narrowed where FAQ rich results are shown.

So for most sites, FAQ schema now helps in a more modest way:

• it clarifies that the page contains FAQ content
• it keeps the markup aligned with visible questions and answers
• it supports a cleaner structured data layer for pages that truly are FAQs

For Semantec, that means FAQ schema should be treated as support markup for real FAQ sections, not as a feature chasing tactic. That is an implementation recommendation based on Google’s current display limits for FAQ rich results.

When to use FAQPage markup

Use FAQPage markup when the page contains a set of questions and answers written and maintained by your site, and when those questions and answers are visible to users on the page. Google’s structured data policies say the markup must reflect the visible page content.

Strong fit examples include:

• a product FAQ page
• a service FAQ page
• a support page with fixed questions and fixed answers
• an educational page with a clearly defined FAQ section written by the publisher

For this site, strong candidates include pages like MIRENA, Pricing, and selected educational pages with a true FAQ section near the end.

When not to use FAQPage markup

Do not use FAQPage markup on pages where users submit answers, because Google says those pages should use QAPage instead. Do not use FAQPage markup for hidden content, and do not mark up questions and answers that are not visible on the page. Google’s documentation ties structured data eligibility to content that matches the page users can see.

For Semantec, that means:

• do not add FAQ schema just because a page has two short questions
• do not mark up sales copy as an FAQ if it is not presented as one
• do not force FAQPage onto comparison pages, cluster pages, or category pages unless the FAQ section is clear and useful

FAQ schema vs FAQ blocks

An FAQ block is the visible content on the page.

FAQ schema is the structured data that describes that FAQ content.

You can have an FAQ block without FAQ schema. You can also have FAQ schema only when the visible FAQ block is already on the page.

That is why FAQ Blocks and FAQ schema should be built together, not as separate tasks. Google’s guidelines require the markup to match the page content users can access.

FAQ schema vs QAPage

This distinction is worth making clear because sites mix them up a lot.

FAQPage is for publisher controlled questions and answers.

QAPage is for pages where users can submit answers to a question. Google’s QAPage documentation gives that rule directly.

So:

• a SaaS pricing FAQ belongs under FAQPage
• a community thread where users answer one question belongs under QAPage

FAQ rich results today

This is the part many older SEO articles miss.

Google announced in August 2023 that FAQ rich results from FAQPage markup would only be shown for well known, authoritative government and health sites going forward. Google’s current FAQPage documentation still explains the markup, but the broader display rule remains restricted.

So for a SaaS site like Semantec:

• you can still use FAQPage markup on real FAQ content
• you should not expect frequent FAQ rich result display in Google Search
• the value is in cleaner structured data and cleaner page structure, not in chasing a rich result that most commercial sites will not get under current policy

A simple FAQPage example

Here is a clean JSON LD example for a page with one FAQ entry. Google’s FAQPage docs use FAQPage, Question, and Answer, and Google recommends JSON LD for structured data.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is FAQ schema in SEO?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "FAQ schema is structured data used for pages that present publisher written questions and answers about one topic."
      }
    }
  ]
}
</script>

If you want to align the page with your author setup, you can keep Kevin Maguire in the page level Article markup and use FAQPage only for the FAQ section where it fits. That is a practical implementation choice; Google’s docs here focus on the FAQ entities themselves, while Schema.org also supports broader page and article typing.

How to use FAQ schema well

1. Start with a real FAQ section

The questions should be clear. The answers should be visible. The section should help the reader, not pad the page.

Google’s policies tie markup to visible, representative content.

2. Keep the questions close to the page topic

A pricing FAQ should answer pricing questions. A product FAQ should answer product questions. An educational FAQ should resolve the most relevant follow up questions from the page.

This keeps the page tighter and makes the FAQ section feel earned.

3. Do not use FAQPage where QAPage fits better

If users submit answers, use QAPage. Google states this directly in its QAPage documentation.

4. Use JSON LD for implementation

Google recommends JSON LD for structured data. That makes it the cleanest implementation path for most teams.

5. Test the markup

Google recommends testing structured data with the Rich Results Test and reviewing issues in Search Console.

Common mistakes

Mistake 1: Expecting a rich result on most commercial sites

Google’s current rule restricts FAQ rich results to well known, authoritative government and health sites. That means most SaaS and commercial sites should not build FAQ schema around rich result expectations.

Mistake 2: Marking up hidden or thin content

Google’s structured data guidance says markup should match what users can see on the page.

Mistake 3: Using FAQPage on a user generated Q&A page

Google says those pages belong under QAPage, not FAQPage.

Mistake 4: Treating FAQ schema as a substitute for page structure

FAQ schema supports a clear page. It does not rescue a weak one. Google’s docs describe structured data as a way to help it understand content, not as a replacement for content quality.

FAQ schema for Semantec

For Semantec, FAQ schema makes the most sense on pages where a real FAQ section improves the page for readers first.

Strong candidates include:

• MIRENA
• Pricing
• selected use case pages such as Drafting + Rewriting
• selected educational pages where follow up questions fit the topic cleanly

Less suitable candidates include cluster hubs, index style pages, and pages where the FAQ section is only there to support markup.

How MIRENA should handle FAQ schema

MIRENA should treat FAQ schema as a support layer after the page structure is clear.

That means the order is:

• build the page
• write the FAQ block if the page needs one
• keep the questions tightly tied to the page topic
• add FAQPage markup only when the section is real and visible
• test the markup and leave the expectations realistic for rich result display under Google’s current policy

That keeps the workflow aligned with JSON LD Basics, Schema for SEO, and Drafting + Rewriting.

Quick checklist

• Is the FAQ section visible on the page?
• Are the questions written by the site, not by users?
• Does FAQPage fit better than QAPage?
• Does the markup match the visible copy?
• Has the markup been tested?
• Are expectations realistic given Google’s current FAQ rich result limits?

FAQ

What is FAQ schema in SEO?

FAQ schema is structured data for pages that present publisher written questions and answers about one topic, using FAQPage, Question, and Answer.

Does FAQ schema still work?

It still works as structured data for real FAQ content. But Google says FAQ rich results are now limited to well known, authoritative government and health websites.

Should a SaaS site use FAQ schema?

Yes, on real FAQ sections where the markup matches visible content. But a SaaS site should not expect regular FAQ rich result display under Google’s current policy.

What is the difference between FAQPage and QAPage?

FAQPage is for publisher controlled questions and answers. QAPage is for pages where users can submit answers to a question.

What is the biggest mistake with FAQ schema?

The biggest mistake is adding FAQPage markup to content that is not a real visible FAQ, or expecting rich results on site types Google no longer shows them for.

Final take

FAQ schema still has a place, but the role is narrower now.

For most commercial sites, it should be used to support real FAQ content and clean page structure, not to chase a rich result that Google now limits to a small set of sites. Build the FAQ block first, mark it up honestly, and keep it tied to the page topic.

From here, the best next pages are JSON LD Basics, Entity Markup, and FAQ Blocks.