FAQ schema: frequently asked questions Google displays

What is FAQ schema and why is it valuable?

FAQ schema, officially the FAQPage type in Schema.org, is a structured data markup that lets you mark up frequently asked questions and their answers on your page. When Google detects and approves this markup, it displays the questions as expandable accordions directly in search results. This gives your page significantly more visual real estate on the results page, leading to higher click-through rates and more visibility.

The principle is simple: you already have a page with frequently asked questions (or an article with a FAQ section), and by adding FAQPage schema markup you explicitly tell Google that it is a list of questions and answers. Google no longer has to guess, it knows for certain. And it rewards that certainty with rich results.

FAQ schema fits within the broader framework of Schema.org markup as a communication tool for search engines and AI models. Where Product schema communicates your commercial information, FAQ schema communicates your knowledge content in question-and-answer format.

FAQPage JSON-LD: the complete structure

Implementing FAQ schema is relatively simple compared to more complex schema types. You have a FAQPage as container and within it an array of Question items, each with an acceptedAnswer of type Answer.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is AEO and how does it differ from SEO?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "AEO (Answer Engine Optimization) focuses on optimizing content so that AI models cite it as a source. Where SEO revolves around rankings in search results, AEO revolves around visibility in AI-generated answers. The two are complementary: good AEO also improves your SEO."
      }
    },
    {
      "@type": "Question",
      "name": "How long does it take for AEO to deliver results?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Technical optimizations like Schema.org markup and robots.txt configuration can be implemented within a week. Building content authority and E-E-A-T signals takes longer, usually several weeks to months. The fastest results are seen with Perplexity, which indexes content in real-time."
      }
    },
    {
      "@type": "Question",
      "name": "Is FAQ schema still relevant after the 2023 Google update?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, FAQ schema remains relevant. Although Google has limited visible FAQ rich results, it still uses the markup internally for AI Overviews, knowledge graphs and other features. Additionally, AI models like ChatGPT and Perplexity use FAQ-structured content as a reliable source."
      }
    }
  ]
}
</script>

Each Question item must contain a name property with the full question text and an acceptedAnswer with a text property containing the answer. The answer may contain HTML, but keep it limited to simple formatting like links, bold text and bullet lists.

Google guidelines for FAQ schema

Google follows strict guidelines for FAQ schema. Failing to follow these guidelines can result in your markup being ignored or receiving a manual action.

• The questions and answers must be actually visible on the page. Hidden FAQ sections or content that only exists in the schema markup is not allowed.
• Use FAQPage only for pages written by the website itself. User-generated questions and answers (like a forum) require the QAPage schema type.
• Each page may contain only one FAQPage schema. Do not use multiple FAQPage blocks on the same page.
• The answers must be complete and accurate. Do not use the FAQ as a teaser to force people to click through.
• Advertising content in FAQ answers is not allowed. The answers must be informational, not promotional.

Difference between FAQPage and QAPage

A common mistake is confusing FAQPage with QAPage. FAQPage is intended for questions and answers written by the website itself, such as a help page or a FAQ section under an article. QAPage is intended for pages where users ask questions and other users provide answers, such as a forum or community page. Using the wrong type leads to rejection by Google.

FAQ schema and AI answer engines

The value of FAQ schema extends beyond Google rich results. AI models like ChatGPT, Perplexity and Gemini recognize FAQ-structured content as a particularly reliable source. The reason is logical: a question-and-answer format exactly matches how users ask questions to AI models. When an AI model receives a question that matches one of your FAQ items, your answer has a greater chance of being cited.

This makes FAQ schema a strategic instrument for Answer Engine Optimization. By formulating your FAQ items around the questions your target audience asks AI models, you increase the chance that your website is selected as a source. Combine this with strong E-E-A-T signals and you have a powerful combination.

Strategically formulating FAQ items

The art of effective FAQ schema implementation lies not in the technology, but in the formulation of the questions. Use tools like Google Autocomplete, People Also Ask and AnswerThePublic to discover which questions your target audience actually asks. Formulate your questions in natural language, exactly as a user would type them into an AI chatbot.

1. Research which questions your target audience asks via Google Autocomplete and People Also Ask.
2. Formulate questions in first person or with "how", "what", "why" constructions.
3. Provide complete, self-contained answers of 50 to 200 words per question.
4. Incorporate relevant keywords naturally in both the question and the answer.
5. Add internal links in the answers to related content on your website.

HTML in FAQ answers

A lesser-known aspect of FAQ schema is that the answer text property may contain HTML. This opens possibilities for richer answers with links, bold text and lists. Google renders this HTML in the rich results.

{
  "@type": "Question",
  "name": "Which Schema.org types are most important for AEO?",
  "acceptedAnswer": {
    "@type": "Answer",
    "text": "<p>The most important Schema.org types for AEO are:</p><ul><li><strong>Organization</strong>: identifies your business and links it to your online profiles.</li><li><strong>Article</strong>: marks your blog posts and articles as editorial content.</li><li><strong>FAQPage</strong>: structures your frequently asked questions for rich results.</li><li><strong>HowTo</strong>: marks step-by-step instructions.</li></ul><p>Read more in our <a href=\"/blog/schemaorg-markup-the-language-ai-understands\">complete Schema.org guide</a>.</p>"
  }
}

Be careful with HTML in FAQ answers. Only use simple tags (p, ul, ol, li, a, strong, em, br, h2, h3). Avoid complex HTML with images, tables or iframes. Google ignores unsupported tags and can reject the markup entirely if the HTML is too complex.

Implementing FAQ schema in practice

Implementation varies per CMS and platform. Here are the most common scenarios.

WordPress with an SEO plugin

Plugins like Yoast SEO, Rank Math and Schema Pro offer built-in FAQ blocks where you can enter questions and answers. The plugin automatically generates the correct JSON-LD. This is the simplest approach for non-technical users.

Manual implementation

For developers who want full control, manual implementation in the HTML head or just before the closing body tag is the recommended method. Generate the JSON-LD dynamically based on your content, so the FAQ items always stay synchronized with the visible content on the page.

// Laravel Blade example for dynamic FAQ schema
@if(isset($faqs) && count($faqs) > 0)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    @foreach($faqs as $index => $faq)
    {
      "@type": "Question",
      "name": "{{ $faq['question'] }}",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "{{ $faq['answer'] }}"
      }
    }@if($index < count($faqs) - 1),@endif
    @endforeach
  ]
}
</script>
@endif

Summary: key takeaways

• FAQ schema (FAQPage) marks frequently asked questions and answers for Google rich results and AI models.
• Since the August 2023 Google update, FAQ rich results are limited, but the markup remains valuable for AI Overviews and AI answer engines.
• Each question has a Question type with name and an acceptedAnswer of type Answer with text. HTML is allowed in the answer text.
• Formulate FAQ items strategically around the questions your target audience asks AI models for maximum AEO impact.
• Always validate that the questions and answers in your schema are actually visible on the page to prevent manual actions.

Frequently asked questions

The best FAQ page answers the questions your customers ask before they know they have those questions.