Is FAQ schema still worth adding?

What happened to FAQ rich results?

FAQ markup (FAQPage structured data) used to turn a search listing into a set of clickable questions and answers under the page title. In 2023 Google cut that back, and since then it shows FAQ rich results only for a limited set of sites, mainly well-known government and health websites. For almost every other site the markup is still valid, but the visible reward is gone.

Many older guides still promise expandable results and extra clicks. Check the date of any advice you read, and do not judge the markup by screenshots from before the change.

So is FAQ schema still worth adding?

Yes, in a limited way. If a page already has a genuine FAQ section, adding the markup takes minutes, carries almost no risk while it matches the page, and gives search engines a clean list of the questions the page answers. What you should not do is write questions only to have something to mark up, or expect extra traffic from it.

What does FAQ markup still do for search and AI?

It states, in a form machines read without guessing, which questions a page answers. That is the whole benefit, and it is small.

Do not count on it for AI answers. Google's May 2026 guide to AI features says no special markup is required, and an Ahrefs study from May 2026 of JSON-LD in general found no meaningful lift in AI citations. The research that does exist points to clear, specific, well-sourced text. A question heading followed by a short, direct answer is that text, with or without markup. For the wider picture, see how AI assistants decide which websites to cite.

What is the rule about matching visible content?

Google's guidelines are strict on one point: the questions and answers in the markup must be visible to people on the page. Markup that does not match the page can be ignored, and in serious cases can lead to a manual action.

• Put the full text of each question and each answer in the markup, not a teaser.
• Every question in the markup must appear on the page with the same meaning. Nothing hidden, nothing missing, no advertising dressed as an answer.
• Use FAQPage only where you write both the questions and the answers. Pages where visitors can submit their own answers use a different type, QAPage.
• When you edit the page, edit the markup in the same change, or the two drift apart.

How do you add and check FAQ schema?

1. 1
   Write the visible section first

   Make each question a heading and put the answer directly below it, in two to four sentences that make sense alone.

2. 2
   Generate the code

   Use the FAQ block in your SEO plugin (Yoast SEO and Rank Math both offer one), an FAQ schema generator, or write the JSON-LD by hand: a FAQPage with a mainEntity list of Question items, each with an acceptedAnswer of type Answer and its text.

3. 3
   Validate it

   Run the page through Google's Rich Results Test and the Schema Markup Validator. A pass means the code is valid, not that Google will show a rich result.

4. 4
   Let Arcline watch it

   Arcline checks that your markup matches what the page shows, and can draft a FAQ page from your own site text, with matching markup, for you to read before it goes live. That needs a Next.js website connected through GitHub and the Premium autopilot.

What makes a FAQ section worth having?

The markup is the small part. A useful FAQ answers what customers really ask you by phone, e-mail and chat, in their words. Lead each answer with the direct answer, then add detail, and link to the page that covers the topic in depth. That shape is also what wins featured snippets and People also ask spots, because every answer makes sense on its own. For more on this, see how to write content so AI assistants quote it and the full list of checks.