FAQPage schema in 2026: check 10, honestly

Short answer: FAQPage markup used to put expandable questions under your Google result. That's over. Google stopped showing FAQ rich results on 7 May 2026 and removed the documentation in June. The markup is still valid schema.org and still describes the page accurately, but it no longer earns anything visible in Google. What still matters is the FAQ itself: real questions, answered in a sentence or two, in plain text on the page. Crawl Audit check 10 warns when a page looks like an FAQ but has no FAQPage markup.

What Crawl Audit checks

• Pass: the page has a FAQPage node.
• Warning: no FAQPage node, but the page looks like an FAQ. That means an element whose class contains "faq" or "accordion", or at least two H2 or H3 headings that end in a question mark.
• Pass: no FAQ content, so the markup isn't needed.

Given what Google has done, a warning on check 10 is low priority. Fix your crawler access, your Organization markup and your page content first.

What happened to FAQ rich results

• 8 August 2023: Google limited them. "FAQ (from FAQPage structured data) rich results will only be shown for well-known, authoritative government and health websites."
• 8 May 2026: Google announced they'd go entirely: "This feature will no longer appear in Google Search starting May 7, 2026."
• 15 June 2026: Google removed the FAQ documentation.

Some platform help pages haven't caught up. Wix's structured data page, for example, still says FAQ results appear for government and health sites. That was true from 2023 until May 2026, and isn't now.

So is FAQPage markup worth adding?

It's cheap and harmless if your platform adds it for you. schema.org still defines FAQPage as "a WebPage presenting one or more 'Frequently asked questions'", and any system that reads structured data gets an exact map of your questions and answers. We keep it on this site's FAQ page for that reason. Just don't expect anything to change in Google because of it.

The part that does matter is visible on the page:

• Use the questions customers really ask you on the phone or on WhatsApp, in their words.
• Put the answer in the first sentence after each question. A direct answer is easy for search engines and AI answers to read and quote.
• Keep the answers as text. An answer that only appears inside an image or a video can't be read.

How to build the FAQ itself on your platform

• WordPress: the core Details block (type /details) makes a question that opens to show its answer. WordPress notes it "can be useful on faq pages". Give several Details blocks the same Name attribute to make them behave like an accordion.
• Wix: add the Wix FAQ app from Add Apps.
• Squarespace: use an Accordion block, which Squarespace describes as "a great option for structured, text-heavy pages like FAQs".
• Shopify: in Online Store › Edit theme, use Add section to add a section that fits your theme, or put the questions and answers in the page's rich text.
• Next.js: plain <h2> or <h3> questions with <p> answers, or <details> and <summary> if you want them collapsible.

Common mistakes

• Answers that only appear after a click handled by JavaScript. AI crawlers download the HTML and generally don't run JavaScript. Make sure the answer text is in the HTML even when collapsed. <details> does this for you.
• Marking up questions that aren't on the page. Google's rule: "Don't mark up content that is not visible to readers of the page."
• Twenty questions nobody asked, written to fit keywords. Five real ones beat them.

Sources

• Google Search Central blog, Changes to HowTo and FAQ rich results, 8 August 2023.
• Google Search Central, documentation updates (8 May and 15 June 2026 entries), checked 3 October 2026.
• schema.org, FAQPage.
• WordPress, Details block; Wix, Wix FAQ app; Squarespace, Accordion blocks.