FAQ Schema: When to Use It and How to Add It

Google used to reward FAQ schema with expandable rich results right on the search page. You could mark up five or six questions, and each one would appear as a dropdown under your listing, pushing competitors further down the page. It was one of the easiest structured data wins in SEO.

Then, on August 8, 2023, Google announced it was “reducing the visibility of FAQ rich results.” The change rolled out globally within a week. FAQ rich results would only be shown for “well-known, authoritative government and health websites.” For everyone else, the visual benefit disappeared.

That announcement triggered a mass removal of FAQ schema across the web. Site owners stripped out their markup, developers stopped implementing it, and the SEO community largely moved on. But removing FAQ schema based on the loss of rich results misses what structured data actually does, and what it’s becoming more useful for as AI search grows.

What changed in August 2023

Google’s blog post was direct. Going forward, FAQ rich results from FAQPage structured data “will only be shown for well-known, authoritative government and health websites.” For all other sites, “this rich result will no longer be shown regularly.”

Google also noted that “while you can drop this structured data from your site, there’s no need to proactively remove it. Structured data that’s not being used does not cause problems for Search, but also has no visible effects in Google Search.”

That last sentence is important. Google explicitly said unused structured data doesn’t cause problems. It simply stops generating a visible rich result for most sites.

The change also affected Search Console reporting. FAQ search appearances in the performance report dropped, and impressions in enhancement reports fell. But Google confirmed this “should not be considered a ranking change.”

Who still gets FAQ rich results

Google’s current FAQ structured data documentation is clear: “FAQ rich results are only available for well-known, authoritative websites that are government-focused or health-focused.” The feature works on desktop and mobile devices in all countries and languages where Google Search is available.

Google also notes that “sites may automatically be considered for this treatment depending on their eligibility.” There’s no application process. If your site qualifies as a well-known government or health authority, Google may display your FAQ rich results automatically.

If you run a government agency website or a recognized health organization, FAQ schema still delivers the same visual benefit it always did. For everyone else, the rich result is gone, but the markup itself still has a role to play.

Why FAQ schema still matters for AI search

Google’s AI optimization guide explains that generative AI features in Google Search, including AI Overviews, are “rooted in our core Search ranking and quality systems.” These features use retrieval-augmented generation (RAG) to “retrieve relevant, up-to-date web pages” from Google’s Search index, then “review the specific information from those retrieved pages to generate a more reliable and helpful response.”

Google also describes a “query fan-out” technique where the model breaks down a question “into subtopics and issuing a multitude of queries simultaneously on your behalf.”

Think about what this means for FAQ content. When someone asks a question in AI Mode or triggers an AI Overview, Google’s systems fan out across multiple queries, retrieve pages from the index, and synthesize an answer. A page with clearly structured question-and-answer pairs, marked up with FAQPage schema, gives those systems an explicit signal: here are the questions this page answers, and here are the answers.

Structured data has always been about helping search engines understand content. Google’s introduction to structured data says it plainly: “Google uses structured data that it finds on the web to understand the content of the page, as well as to gather information about the web and the world in general.”

That understanding doesn’t stop at rich results. It feeds knowledge graphs, AI-generated answers, and the retrieval systems that decide which pages get cited in AI search responses. FAQ schema makes the question-answer relationship on your page machine-readable, not just human-readable.

The same logic applies to AI engines beyond Google. ChatGPT and Perplexity both scrape and process web content to generate answers. Clean, structured FAQ content with schema markup gives these systems a straightforward signal about what your page covers and how it answers specific questions. That’s the kind of content answer engines are designed to surface.

When FAQ schema is worth adding

Not every page needs FAQ schema. The markup is appropriate when your page genuinely contains a list of frequently asked questions, each with a single definitive answer provided by your site.

Google’s content guidelines for FAQ schema state: “Only use FAQPage if your page contains FAQs where there’s a single answer to each question. If your page has a single question and users can submit alternative answers, use QAPage instead.”

Google provides specific valid use cases: “An FAQ page written by the health site itself, with no way for users to submit alternative answers” and “a government agency’s support page that lists FAQs, with no way for users to submit alternative answers.”

Invalid use cases include forum pages where users submit answers, product support pages with user-submitted answers, and product pages where users can submit multiple questions and answers.

Here’s when adding FAQ schema makes sense for most sites:

Service pages with common questions. If your pricing page, product page, or service page has a genuine FAQ section at the bottom answering real customer questions, mark it up. These questions often match exactly what people ask AI engines.

Help center and support pages. If you maintain a knowledge base or help center, FAQ schema tells search engines exactly which questions each page answers. This is especially useful when AI systems are looking for definitive answers to specific support queries.

Location and contact pages. Local businesses that answer questions about hours, parking, services, or policies on their contact pages can use FAQ schema to make those answers more discoverable.

Blog posts structured around questions. If your article genuinely answers a set of related questions (not artificially stuffed with FAQs for SEO purposes), the markup helps search engines map your content to the queries people are asking.

When it’s wasted effort

Skip FAQ schema when:

• Your page doesn’t actually contain FAQ content in question-and-answer format
• The “questions” are marketing copy disguised as FAQs (“Why is our product the best?”)
• Users can submit their own answers, which makes it a QAPage, not an FAQPage
• The same FAQ content appears on multiple pages across your site (Google says to mark up only one instance per site)
• You’re adding it purely for the rich result, which no longer exists for most sites

The goal isn’t to game a system. It’s to accurately describe your content’s structure so machines can use it.

How to add FAQ schema

FAQ schema uses three types: FAQPage, Question, and Answer. The FAQPage wraps the entire set of questions, each Question contains the question text and its accepted answer, and each Answer holds the response.

Here’s the JSON-LD format, which Google recommends placing in the <head> of your page:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is your return policy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We offer a 30-day return policy on all unused items. Contact our support team to initiate a return."
      }
    },
    {
      "@type": "Question",
      "name": "How long does shipping take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Standard shipping takes 5-7 business days. Express shipping is available for 2-3 business day delivery."
      }
    }
  ]
}

The key required properties according to Google’s documentation:

• FAQPage requires a mainEntity property containing an array of Question elements. You must specify at least one valid Question item.
• Question requires a name property (the full text of the question) and an acceptedAnswer property. There must be one answer per question.
• Answer requires a text property containing the full answer text. The answer text can include HTML formatting.

Google’s content guidelines also require that “all FAQ content must be visible to the user on the source page.” You can hide answers behind expandable sections (accordions), but the user must be able to access them on the page. You can’t mark up FAQ content that doesn’t appear on the page at all.

Validating your markup

After adding FAQ schema, validate it using Google’s Rich Results Test. Google’s structured data documentation recommends this workflow:

1. Add the required properties to your page
2. Validate your code using the Rich Results Test and fix any critical errors
3. Deploy a few pages with your structured data
4. Use the URL Inspection tool in Search Console to test how Google sees the page
5. Submit a sitemap to keep Google informed of future changes

Even though most sites won’t see FAQ rich results, the Rich Results Test still validates whether your markup is correctly structured. Errors in your schema mean search engines can’t parse your FAQ content reliably, which defeats the purpose.

The structured data advantage in AI search

The sites that stripped out their FAQ schema after August 2023 made a reasonable decision based on the information available at the time. The visible benefit was gone, so the markup seemed pointless.

But AI search has changed the calculus. Google’s AI features use structured data to understand page content and retrieve relevant information for generated answers. Other AI engines process structured content more effectively than unstructured text. FAQ schema is one of the clearest ways to tell any machine, whether it’s a search crawler or a language model, exactly what questions your page answers.

If you already have FAQ schema on your site, leave it. If you’re building new pages that genuinely answer common questions, add it. The five minutes it takes to implement could be the difference between your answer getting cited in an AI response and being passed over for a competitor’s page that made its content structure explicit.

The rich result might be gone for most sites. The value of making your content machine-readable is not.