FAQ schema markup is a structured data format that tells search engines your page contains a list of questions and answers. When implemented correctly, Google can display those questions and answers directly in search results as expandable rich results, giving your listing more visual real estate and a higher click-through rate. This guide covers how to write the JSON-LD code, which pages qualify, how to match questions to real searcher intent, and – critically – why your FAQ schema may be implemented perfectly yet still not appear in search.

Step 1: Determine Whether Your Page Qualifies for FAQ Rich Results

Before writing a single line of code, confirm the page meets Google's eligibility criteria. Implementing schema on a page that does not qualify wastes time and can introduce misleading markup.

Pages That Qualify

Google's FAQ rich results documentation specifies that FAQPage schema applies to pages where a single authoritative source provides answers – as opposed to pages that host community-generated content, user forums, or open voting on answers. The distinction matters: a product FAQ written by your team qualifies; a support forum where users vote on answers does not.

Qualifying page types include:

  • Dedicated FAQ pages presenting curated Q&A content
  • Product or service pages with an embedded FAQ section
  • Knowledge base articles with structured question-and-answer pairs
  • Blog posts or guides with a FAQ section at the end

Pages That Do Not Qualify

  • Community Q&A pages where multiple users submit different answers to the same question
  • Pages where the "questions" are really just section headers reworded as questions
  • Pages with fewer than two question-answer pairs

Google's documentation also makes clear that the content must be visible on the page. Markup that represents content not actually present in the HTML is considered misleading structured data – a violation that can result in manual action.

Step 2: Write Question-Answer Pairs That Match Searcher Intent

The quality of your question-answer pairs determines both whether Google surfaces the rich result and how much traffic the feature actually drives. Schema that passes validation but answers poorly matched questions earns little.

How to Identify the Right Questions

Effective FAQ questions are exact or near-exact matches to queries real users type into search engines or ask AI tools. The practical sources for finding these questions are:

  • Google's "People Also Ask" boxes for your target keyword
  • Google Search Console queries that already send traffic to the page
  • Your site's internal search logs, if available
  • Questions your sales or support team receives repeatedly

Each question should reflect natural language, not your internal terminology. "How does the pricing work?" is how a prospective customer phrases it. "What is the fee structure?" is how your finance team phrases it. Use the customer version.

How to Write Answers That Get Extracted

Each answer must meet two standards: it must be genuinely useful to a person reading it, and it must be self-contained enough for an AI system or search engine to extract and display without surrounding context.

Answer-writing rules:

  1. Open with a direct response to the question in the first sentence – not background, not hedging
  2. Keep answers between 40 and 160 words; shorter risks being dismissed as insufficient, longer reduces extractability
  3. Include at least one specific fact, figure, named tool, or concrete example per answer
  4. Never reference the page itself ("as explained above") or other sections

Well-structured FAQ content also serves AI citation ranking factors – the same directness and specificity that makes an answer good for Google's rich results makes it easier for ChatGPT, Perplexity, and Gemini to quote it verbatim.

Step 3: Write the JSON-LD FAQ Schema Markup

JSON-LD is Google's preferred format for structured data and the most reliable format for FAQ schema. It does not require modifying your HTML; it is added as a <script> block.

The Correct JSON-LD Structure

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "FAQPage",
 "mainEntity": [
 {
 "@type": "Question",
 "name": "What is FAQ schema markup?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "FAQ schema markup is a structured data format based on Schema.org vocabulary that signals to search engines which content on a page represents questions and their authoritative answers. When Google validates the markup and deems the page eligible, it can display the questions and answers as expandable rich results directly in search."
 }
 },
 {
 "@type": "Question",
 "name": "Does FAQ schema still work in 2024?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Yes, FAQ schema still works, but Google restricted rich result eligibility in August 2023. Only websites with high authority and strong E-E-A-T signals consistently see FAQ rich results in search. Government and health sites are explicitly listed as priority cases. For other sites, the markup still aids structured data understanding and AI citation even when rich results are not shown."
 }
 },
 {
 "@type": "Question",
 "name": "How many questions should I include in FAQ schema?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Include all questions present on the page. Google's guidelines do not specify a minimum or maximum number, but most well-performing FAQ pages contain between four and ten question-answer pairs. Each pair must be visible in the page's HTML – do not mark up content that does not appear on the page."
 }
 }
 ]
}
</script>

Rules for the Markup Itself

The name field in each Question object must exactly match the question text as it appears visibly on the page. The text field in each Answer object should contain the full answer, including any HTML if your answer uses formatting – though plain text is acceptable and often preferable for clean extraction.

Multiple Question objects sit inside the mainEntity array, separated by commas. Each object is structured identically: @type, name, and acceptedAnswer containing its own @type and text.

If your page also warrants other schema types – Article, BreadcrumbList, or Organization – those can coexist in separate <script> blocks or within a @graph array. Combining unrelated schema types in a single block without using @graph correctly can cause validation errors.

For teams managing structured data across dozens of pages, automating JSON-LD generation at scale reduces both implementation time and the risk of formatting errors introduced during manual editing.

Step 4: Add the Schema to Your Page

Where and how you add the JSON-LD block depends on your CMS and technical setup.

Adding via HTML

Paste the <script type="application/ld+json"> block anywhere in the <head> or <body> of the page. Google reads JSON-LD from either location. Placing it in the <head> is conventional; placing it just before the closing </body> tag works equally well.

Adding in WordPress

WordPress users have two practical routes. The first is a plugin – Yoast SEO, Rank Math, and Schema Pro all include FAQPage schema support, either through block-level controls or page-level settings. The second is adding the script block directly to the page template using a function in functions.php or a lightweight custom plugin. Implementing schema in WordPress without developer access is achievable through either method.

Adding Without a Developer

Most modern CMS platforms – including Squarespace, Webflow, and Shopify – allow custom code injection at the page level or site-wide through settings panels. Adding schema markup without a developer is a realistic task for a marketer comfortable pasting code into a text field.

For agencies managing structured data across multiple client sites, a consistent process for schema markup across client properties prevents the drift that happens when each site follows a different implementation pattern.

Step 5: Validate the Markup Before Publishing

Validation catches syntax errors, missing required fields, and formatting problems before they go live. Unvalidated schema that contains errors either fails silently or triggers warnings in Google Search Console.

Using Google's Rich Results Test

Google's Rich Results Test (available at search.google.com/test/rich-results) accepts either a live URL or pasted code. It returns a pass or fail status for each rich result type detected, along with a list of warnings and errors. A green "FAQ" result with no errors means the markup is syntactically correct and the page is eligible to be tested for the rich result.

Using Schema.org Validator

The Schema.org validator (validator.schema.org) checks conformance to the Schema.org specification rather than Google's specific rich result criteria. Run both if you want comprehensive coverage: the Rich Results Test tells you whether Google can use it; the Schema.org validator tells you whether the markup is structurally correct.

Common Errors to Fix

  • name field does not match the visible question text on the page
  • text field is empty or contains only whitespace
  • JSON formatting errors – unclosed brackets, missing commas between objects
  • Markup present for content not visible on the page

A systematic approach to validating schema and fixing structured data errors before deployment eliminates most of the issues that cause rich results to never appear.

The AuthorityStack.ai schema generator can scan any URL and produce ready-to-paste JSON-LD, which reduces manual errors in the generation step before you run validation.

Step 6: Submit the Page for Indexing and Monitor in Search Console

After adding and validating the markup, prompt Google to recrawl the page rather than waiting for its natural crawl cycle.

Requesting Indexing via Search Console

In Google Search Console, enter the page URL in the URL Inspection tool and click "Request Indexing." Google does not guarantee immediate crawling, but the request moves the page higher in the crawl queue. For newly published pages or recently updated schema, this step can accelerate when the rich result becomes eligible to appear.

Monitoring the FAQ Rich Results Report

Search Console includes an "Enhancements" section with a dedicated FAQ report. This report shows the number of pages with valid FAQPage schema, any pages with warnings or errors, and – if rich results are being served – impression and click data for the FAQ feature.

Allow two to four weeks after indexing before drawing conclusions about performance. Rich results do not appear immediately after a successful crawl; Google evaluates eligibility after it processes the page.

Why FAQ Schema Stops Showing in Search (and What to Do About It)

This is where most implementation guides stop short. The markup is correct, Search Console shows no errors, but the FAQ rich result either never appeared or stopped appearing. Here is why that happens.

Google's 2023 Policy Change

In August 2023, Google announced a significant restriction to FAQ rich results. The change reduced FAQ rich result eligibility to two categories: government websites and health and medical websites. For all other sites, Google stated that FAQ rich results would be shown "less prominently" – effectively meaning most commercial and informational sites no longer see the expandable Q&A feature in standard search results.

This policy change was not a penalty. Sites with correct FAQ schema were not penalized; the feature was simply restricted. The markup itself remains valid and useful – it still contributes to schema markup's broader influence on SEO and AI citation, even when the rich snippet is not shown.

What "High Authority" Means in Practice

Outside the government and health categories, some sites continue to see FAQ rich results. These tend to be sites with strong E-E-A-T signals: established domains with substantial linking profiles, demonstrated expertise in their subject area, and consistent publishing history. Google's documentation on E-E-A-T and its relationship to AI search citation decisions makes clear that authority signals affect both traditional rich results and AI-generated answers.

Other Reasons FAQ Rich Results Disappear

Even for sites that qualify, FAQ rich results can stop appearing for reasons unrelated to the 2023 policy:

  • Content quality decline: Google recrawls pages periodically. If answer quality drops or answers become thin, the rich result may stop appearing.
  • Duplicate markup: The same questions appearing on multiple pages in your site can cause Google to suppress the feature to avoid redundancy.
  • Schema errors introduced during CMS updates: Plugin updates, theme changes, and CMS migrations frequently break schema output. Re-validating after any significant site update is good practice.
  • Manual action: Structured data that misrepresents page content can attract a manual penalty. Google penalties for incorrect schema are a real risk when markup is added to pages where the content does not match what the schema describes.

Why You Should Keep the Markup Anyway

FAQ schema markup still carries value after the 2023 restrictions. Structured schema markup for AEO purposes remains one of the clearest signals you can send to both traditional search engines and AI systems about how your content is organized. AI platforms including ChatGPT, Perplexity, Gemini, and Google AI Mode extract and cite well-structured Q&A content more reliably than unstructured prose. The connection between schema markup and AI search performance is separate from Google's rich result eligibility rules and that connection continues to strengthen as AI-generated answers become a larger share of how users discover information.

FAQ

What Is FAQPage Schema and How Does It Differ From Regular Schema Markup?

FAQPage schema is a specific Schema.org type – "@type": "FAQPage" – that tells search engines a page contains question-and-answer pairs from a single authoritative source. Regular schema markup refers to the broader family of structured data types including Article, Product, Organization, and BreadcrumbList. FAQPage schema is a subset of that family, used specifically when a page's primary or secondary content is a list of questions with direct answers.

Why Is My FAQ Schema Not Showing as a Rich Result Even Though It Passes Validation?

The most common reason is Google's August 2023 policy change, which restricted FAQ rich result eligibility primarily to government and health websites. A page can have valid, error-free FAQPage schema and still not receive the expandable rich result feature in standard search. The markup is not wasted – it still signals content structure to AI systems and contributes to how the page is understood by search engines, even when the visual rich result is not displayed.

Does FAQ Schema Still Help With SEO in 2024?

Yes, though the mechanism has shifted. FAQ schema no longer reliably produces rich results for most commercial sites following Google's 2023 policy restriction. However, the markup still communicates content structure to search engines, supports AI citation by making question-answer pairs machine-readable, and aligns with E-E-A-T quality signals. The SEO value now comes more from content organization and AI visibility than from the visual snippet feature.

How Many Question-answer Pairs Should I Include in FAQ Schema?

Include every question-answer pair that is visible on the page. Google's guidelines do not impose a specific minimum or maximum, but most well-performing FAQ sections contain between four and ten pairs. Each pair in the markup must correspond to content that actually appears on the page – marking up hidden or absent content violates Google's structured data guidelines and can result in a manual action.

Can I Add FAQ Schema to Every Page on My Site?

No. FAQPage schema should only be applied to pages where visible question-answer content actually exists. Applying the markup to pages without FAQ content, or applying it to community-generated Q&A where multiple users answer the same question, violates Google's usage guidelines. Over-application also reduces the credibility of your structured data overall. Apply it selectively to pages where real FAQ content is present and the answers are authoritative.

What Is the Difference Between FAQ Schema and HowTo Schema?

FAQ schema (FAQPage) is for pages where the primary content is a list of questions with direct answers. HowTo schema (HowTo) is for instructional content that walks a user through a sequence of steps to complete a specific task. A support page answering common product questions uses FAQPage. A tutorial showing how to set up an integration uses HowTo. The two types can coexist on the same page in separate schema blocks if both content types are genuinely present.

How Do I Know If My FAQ Schema Is Working Correctly?

Check the FAQ report in the Enhancements section of Google Search Console after the page has been indexed. If the markup is valid and the page has been processed, the report will show the page as eligible and – if the site qualifies for the rich result – impression and click data for the FAQ feature. For sites outside the government and health categories, absence from the rich results report does not necessarily indicate an error; it may reflect the 2023 eligibility restriction rather than a markup problem.

Does FAQ Schema Help With AI Search Citations?

Yes. AI systems including Perplexity, ChatGPT, and Google AI Mode favor content that is clearly structured and directly answers questions. FAQPage schema makes question-answer relationships explicit in a machine-readable format, which reinforces the content structure these systems use when selecting sources to cite. The markup is one layer of a broader AI visibility strategy – alongside content formatting, entity consistency, and topical authority but it is a meaningful one. Research on content formats that AI systems quote most reliably consistently shows that direct Q&A structures outperform unstructured prose for AI extraction.

What to Do Now

  1. Audit your existing pages to identify which ones contain visible question-answer content that qualifies for FAQPage schema.
  2. Write or revise your question-answer pairs so each answer opens with a direct response and contains at least one specific fact or example.
  3. Generate the JSON-LD markup using the structure in Step 3, or use a schema generator to produce it from your page URL.
  4. Validate the markup in Google's Rich Results Test before publishing – fix any errors flagged before the page goes live.
  5. Add the <script> block to the page, request indexing via Google Search Console, and monitor the FAQ enhancement report over the following four weeks.
  6. Accept that the rich result may not appear if your site falls outside Google's current eligibility criteria and keep the markup in place anyway for its structured data and AI citation value.

If you want to measure whether your structured data is contributing to AI citations and whether those citations are sending real traffic – track your AI visibility performance with AuthorityStack.ai to see exactly which platforms are citing your content and what those visits are worth.