# FAQPage: What FAQ Schema Is and What Google Says in 2026 > What FAQPage is, how to mark up a frequently asked questions section, why Google retired its rich result in May 2026 and what is still worth doing. URL: https://clione.ai/glossary/faqpage/ Lang: en If someone offers you FAQ schema with the promise that your product pages will take up more space on Google with expandable questions, **that promise expired on May 7, 2026**. The markup still exists and is still correct; what disappeared was the way Google displayed it. A store should still care, for another reason: questions that settle buying doubts are about the most useful thing a [product page](/glossary/product-page/) can carry, for the shopper and for the assistants that answer on their behalf, and FAQPage is the standard way to describe them with [structured data](/glossary/structured-data/). ## What it covers [Schema.org](/glossary/schema-org/) defines FAQPage as a type of web page (WebPage) that presents one or more frequently asked questions, and points to QAPage as a neighboring type.[^schemaorg-faqpage] Each question is a Question, which Schema.org describes as a specific question, for example one from someone looking for an answer on the internet or **one gathered in a frequently-asked-questions document**; its answer goes in the `acceptedAnswer` property, as an Answer.[^schemaorg-question] The list of questions hangs from `mainEntity`, one of the properties FAQPage inherits.[^schemaorg-faqpage] The usual format is [JSON-LD](/glossary/json-ld/), which Google generally recommends for structured data because it is the easiest to implement and maintain.[^google-structured-data] And there is a rule that does not depend on the type: Google asks you **not to mark up content the visitor cannot see**. If the JSON-LD describes something, the body of the page has to describe the same thing.[^google-sd-policies] ## What Google has done with the FAQ result Of Google's [rich results](/glossary/rich-results/), the frequently asked questions one (the expandable questions under a result) was trimmed back in two steps: | Date | What changed | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | August 8, 2023 | Google announces that the FAQ result, which comes from FAQPage markup, will only be shown to well-known, authoritative government and health sites. For everyone else it stops being shown on a regular basis.[^google-howto-faq-2023] | | September 14, 2023 | The FAQ documentation is updated to say the same.[^google-updates] | | May 8, 2026 | Google adds a deprecation notice: the FAQ result stops appearing in Search as of May 7, 2026.[^google-updates] | | June 15, 2026 | Google removes the FAQ result documentation, because it is no longer shown in results.[^google-updates] | In 2023, Google added two sentences that still hold: you can remove this markup from your site, but **you do not need to remove it proactively**, and structured data that is not used causes no problems in Search, though it has no visible effects there either.[^google-howto-faq-2023] Google still uses the structured data it finds to understand a page's content,[^google-structured-data] but there is no special markup for its generative AI features.[^google-ai-guide] Outside Google, the frequently asked questions section is still well regarded. Bing recommends clear headings, tables and **FAQ sections** so AI systems can find the key information and cite it accurately.[^bing-ai-performance] Microsoft explains that assistants may copy a question-and-answer pair word for word into their answers, and that [Schema.org markup](/glossary/schema-markup/) can label content as a product, review, FAQ or event so machines interpret it with confidence.[^microsoft-ai-search] ## In a store A **fictitious example**: an electric kettle's product page shows two questions, visible under the description. The markup repeats exactly the same text: ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Does it shut off by itself when it runs out of water?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. It has dry-boil protection and cuts the power if it does not detect water." } }, { "@type": "Question", "name": "Is the inside made of plastic?", "acceptedAnswer": { "@type": "Answer", "text": "No. The tank and the inner lid are stainless steel." } } ] } ``` What you look at in that block is the equivalence: each `name` is the question as it reads on the page and each `text` is the visible answer, with no sentences added just for the markup. On a real product page, the FAQPage block can go inside the same `@graph` as the page's [Product](/glossary/product-schema/). **What we have measured ourselves.** In June 2026, Clione enriched 39 product pages at BenroUSA, Benro's US store for photography gear, and nine of them also received frequently asked questions. In [Search Console](/glossary/google-search-console/), from June 13 to 22 and against their starting point, **those nine pages gained 25% in impressions while the whole site gained 8%**. That increase could not have come from the FAQ result, which Google had stopped showing on May 7.[^google-updates] It is a correlation measured in one store over ten days, with the rest of the enrichment applied at the same time, not a forecast for your catalog. That an answer hidden in an accordion counts as visible to everyone. For Google it was valid: in July 2021 it clarified in its FAQ guidelines that the user has to be able to access the answer on the page and that clicking an expandable section to see it is a correct use.[^google-updates] Microsoft warns of the opposite for AI: **do not hide important answers in tabs or dropdown menus**, because AI systems may not surface hidden content.[^microsoft-ai-search] An answer the visitor opens with a click is in view; one that only arrives with JavaScript may not be read by whoever does not run it. ## How to check it 1. **Find the markup.** Open the product page's code, or the rendered HTML from Search Console's URL inspection, and find `"@type": "FAQPage"`. 2. **Compare text with text.** Every question and every answer in the markup has to be on the page, in the same words.[^google-sd-policies] 3. **Run the page through a [schema validator](/glossary/schema-markup-validator/)** to catch syntax errors: one extra comma or quotation mark invalidates the whole block. 4. **Do not measure by the rich result.** Since May 7, 2026 Google does not show the FAQ result, so its absence does not indicate any fault.[^google-updates] 5. **If your site is in [Bing Webmaster Tools](/glossary/bing-webmaster-tools/), look at AI Performance**, which counts the citations of your pages in [Copilot](/glossary/copilot/) and in Bing's summaries, and compare the product pages with frequently asked questions against those without.[^bing-ai-performance] ## Related concept: QAPage QAPage is the type for a page centered on **a single question and the answers users submit**, such as a forum or a support page where anyone can reply. Google says it with examples: a frequently asked questions page written by the site itself, with no way for users to add answers, is not a valid use of QAPage, and neither is a product page with several questions and answers on the same page, and it asks you not to use QAPage on FAQ pages or on pages with multiple questions.[^google-qapage] If you write the questions yourself and there are several, the type is FAQPage. To keep going, the [structured data reading path](/learn/structured-data/) puts the rest of the types in order, and the guide to [auditing a product page's structured data](/guides/audit-product-page-structured-data/) applies these checks step by step.