Swap in your own questions and answers. Use them word for word as they appear on the page. Where the code goes depends on your CMS. Our guide on how to add JSON-LD to your website covers the common setups."}},{"@type":"Question","name":"Step 3: Validate the markup","acceptedAnswer":{"@type":"Answer","text":"Validation no longer happens in Google's Rich Results Test, because it no longer supports FAQ. Use a general schema validator instead, such as the Schema Markup Validator from Schema.org. It checks that your JSON-LD is syntactically correct. Here's that check on our own English homepage, which carries FAQPage markup: !Schema Markup Validator result for the customerimpact.be English homepage detecting WebSite and FAQPage structured data with 0 errors and 0 warnings, a valid FAQ schema markup check The Schema Markup Validator on our own English homepage, October 2026: FAQPage detected, 0 errors, 0 warnings. Zero errors means the syntax is right. It doesn't prove the answers are any good. The most common validation mistakes are in our guide to schema markup testing. > [!TIP] > Re-run the validator after every CMS or theme update. A plugin change can silently duplicate or drop your FAQPage block. The questions your buyers literally type in or ask an AI assistant, not the ones that suit you. That difference determines whether you get cited or ignored. In B2B this means four kinds of question: - Fit: who it's for and at what team size - Comparison: the difference between X and Y - Objection and risk: what if it doesn't work - Price and process: an honest frame, not a rate"}},{"@type":"Question","name":"Fit questions","acceptedAnswer":{"@type":"Answer","text":"\"What type of company is this for?\" or \"Does this also work for a team of X people?\" AI engines use this kind of content to match buyer and solution."}},{"@type":"Question","name":"Comparative questions","acceptedAnswer":{"@type":"Answer","text":"\"What is the difference between X and Y?\" This is where much B2B purchase research begins. AI likes to lift a clear answer there."}},{"@type":"Question","name":"Objection and risk questions","acceptedAnswer":{"@type":"Answer","text":"\"What if it doesn't work?\" or \"How long does implementation take?\" Honest answers build trust here. With the reader and with the model."}},{"@type":"Question","name":"Price and process frames","acceptedAnswer":{"@type":"Answer","text":"You don't have to name an exact rate. But do give an honest frame, so the answer is usable."}},{"@type":"Question","name":"Do question queries still get clicked?","acceptedAnswer":{"@type":"Answer","text":"On our own site, yes. In our CTR study, question queries in the top 10 didn't click less than other queries: !Bar chart of question queries in the top 10 earning a 0.19% CTR versus 0.09% for other queries, the kind of buyer questions an FAQ with FAQPage schema should answer Non-branded queries ranking in the top 10, customerimpact.be, 1 June to 15 October 2026. Watch out: the question group had only 41 clicks. So \"didn't click less\" is safe; \"click more\" isn't proven. Finding those questions is covered in our guide to question keywords. Google's People Also Ask box is a good free source too."}},{"@type":"Question","name":"How do you phrase questions and answers?","acceptedAnswer":{"@type":"Answer","text":"Phrase each question the way a human asks it, in full sentences, not as a keyword. For example, say your buyers search \"crm small team price\". Your FAQ question becomes \"What does a CRM cost for a small team?\" Keep each answer short and complete: two to four sentences that stand on their own, without \"as above\". That self-containment is precisely what an AI engine needs to extract your passage. If you want to tune this to your target audience, our guide on GEO for B2B takes you further. Rule of thumb: an FAQ answer should still make sense when it's quoted alone in someone else's AI answer. FAQ schema is no guarantee of citations and no substitute for good content. It's an amplifier, not an engine. Anyone who thinks a small block of JSON-LD suddenly triples visibility in ChatGPT is in for a disappointment. The figures on the direct effect contradict each other. That says enough: there's no miracle cure."}},{"@type":"Question","name":"What decides whether you get cited?","acceptedAnswer":{"@type":"Answer","text":"What's always true: a page that genuinely contains the best answer to a question wins, if it's written in clear, self-contained blocks. The schema makes that answer a bit easier to find and unambiguous. So never start with the schema. Start with your buyer's question and with an answer worth citing. Our AI citation checklist lists what else that answer needs."}},{"@type":"Question","name":"When does FAQ schema pay off, and when not?","acceptedAnswer":{"@type":"Answer","text":"Use this table to decide: | Your page | FAQPage schema? | |---|---| | Visible FAQ with real buyer questions | Yes, low effort and no risk | | FAQ hidden in tabs or only in the code | Fix the visible FAQ first | | Questions nobody asks, written for SERP space | Rewrite the questions, then mark up | FAQ schema comes afterward, with low effort and no risk. It does logical work within a broader GEO foundation. What that foundation looks like, you can read in our complete GEO guide. And how to end up in Google's AI Overviews has its own guide."}},{"@type":"Question","name":"Does Google still show FAQ rich results?","acceptedAnswer":{"@type":"Answer","text":"No. Since 7 May 2026, FAQ rich results no longer appear in Google Search, not even for the government and health sites that kept them after 2023."}},{"@type":"Question","name":"Should I remove my FAQPage markup?","acceptedAnswer":{"@type":"Answer","text":"You don't have to. Google ignores it for display and it causes no errors. Keep it if it matches your visible FAQ."}},{"@type":"Question","name":"How do I test FAQPage schema now?","acceptedAnswer":{"@type":"Answer","text":"With the Schema Markup Validator from Schema.org. Google's Rich Results Test dropped FAQ support in June 2026."}},{"@type":"Question","name":"Does FAQPage schema get me cited by ChatGPT?","acceptedAnswer":{"@type":"Answer","text":"Not on its own. Google says no special markup is needed for its AI features. The citable Q&A content on the page is what counts."}}]}
Customer Impact

SEO & GEO

Implementing FAQPage schema for AI citations (after Google's deprecation)

Copy for AI

Yes, FAQPage schema still makes sense, but for a different reason than before.

Google has removed the FAQ rich results from its search results, so that expandable block under your link is gone. Even so, the Q&A structure behind FAQ schema markup still works. It’s one of the most extractable content forms for AI engines like ChatGPT, Perplexity and Google’s AI Overviews.

The verdict: keep or add FAQPage schema as cheap insurance, not as a citation button. The real gain is the tight question-and-answer discipline it forces on your page.

FAQPage is a schema.org type for a web page that presents frequently asked questions. It sits under WebPage in the hierarchy.

New to markup in general? Start with our explainer on schema markup.

What exactly changed at Google?

Since 7 May 2026, Google no longer shows FAQ rich results in the search results, for anyone.

That’s the final chapter. The process began in August 2023. Back then, Google said FAQ rich results would only appear for well-known, authoritative government and health websites.

The FAQ block had been widely used to grab more SERP space, often with questions nobody was asking.

The timeline in one picture

Here’s how the deprecation rolled out, step by step:

FAQ RICH RESULTS How Google phased them out August 2023 Google Search Central blog Gov and health only everyone else lost them 7 May 2026 rich results stop showing Gone for everyone markup ignored for display 8 May 2026 Search Central changelog Deprecation logged official notice June 2026 report, filter, test, docs Tooling removed docs gone on 15 June August 2026 Search Console API API support ends last trace removed The markup still validates. Only the display in Google Search is gone.

In May 2026, Google pulled the plug for everyone. Its Search Central changelog logged the deprecation notice on 8 May.

It removed the FAQ rich result documentation on 15 June 2026.

What happened to the tooling?

The tooling followed: the Search Console FAQ report, the search appearance filter and Rich Results Test support went in June 2026.

Search Console API support ended in August 2026, as Search Engine Roundtable summarised from Google’s notice.

Do you have to remove your FAQPage markup?

No. Google simply ignores it for display, it causes no errors and it doesn’t harm your SEO.

John Mueller’s advice in the same notice: “No need to change anything.”

If you added the markup only for search, you can remove it if you want.

So removing it is optional, not required. That distinction is crucial.

It means the schema is free to play a different role: fuel for AI.

Why does FAQ structure still work for AI engines?

Because it ties each question to one self-contained, bounded answer.

That’s exactly the kind of block a language model can easily pick up. An AI engine composing an answer looks for passages that stand on their own and fully answer a concrete question.

A Q&A pair is the purest form of that.

You can see the passages AI engines lift in their source lists. Perplexity, for example, shows the pages behind every answer:

Perplexity sources panel for our test prompt listing the web pages behind the answer, the passages FAQ schema markup helps AI engines extract Perplexity’s sources panel for our own test prompt, 17 October 2026: 10 web pages behind one answer.

Each source earned its place. It has a passage that answers the prompt on its own.

Is the schema a citation button?

No.

Be precise about how this works technically, because that’s where a lot of GEO advice goes astray.

There’s no public evidence that assistants treat your JSON-LD as a separate data layer they trust on its own.

Google itself says there’s no special schema.org markup you need to add to appear in AI Overviews or AI Mode. So the schema isn’t a magic citation button.

Where does the gain come from?

The gain lies elsewhere. By implementing FAQPage schema, you force yourself into a tight Q&A pattern.

A clear question comes first. Then a short, complete answer.

That visible pattern on the page is what AI engines extract. The schema is therefore not a cause, but a discipline that enforces the right content pattern.

Google still lists one structured data practice for its AI features: “making sure your structured data matches the visible text on the page.”

That holds even though the rich result is gone.

How to cut a page into such blocks is the subject of our guide to content chunking for AI.

To understand more deeply how AI reads and extracts your page, read our guide on content architecture for AI extraction.

FAQ schema is just one tactic within that broader whole.

How do you implement FAQPage schema?

With a small block of JSON-LD in the <head> or <body> of your page.

Each question goes in as a Question and each answer as an acceptedAnswer. All of them sit inside the mainEntity array of one FAQPage.

Step 1: Write the visible FAQ first

The golden rule: the schema must match exactly the questions and answers that are visible on the page.

Google’s structured data policies say it plainly: don’t mark up content that isn’t visible to readers.

Watch out: hidden FAQs, or answers that diverge from the visible text, are a bad idea. For people and for AI.

Step 2: Add the JSON-LD

Here’s a copy-paste example for a B2B context that you adapt to your situation:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [

    {
      "@type": "Question",
      "name": "Which companies is your solution suitable for?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Our solution is built for B2B companies with a complex sales cycle and several decision-makers. We typically work with organisations of 20 to 500 employees in services, software and industry."
      }
    },

    {
      "@type": "Question",
      "name": "How quickly will we see results?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "You often see first impressions on long, specific questions and in AI Overviews within days to weeks. Broad search terms and enquiries usually take a few months, depending on your sector and competition."
      }
    },

    {
      "@type": "Question",
      "name": "What does working together cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A project typically starts from a fixed monthly fee that we align with your goals and scope. During a free intake we decide together which approach fits your budget and ambition."
      }
    }
  ]
}
</script>

Swap in your own questions and answers. Use them word for word as they appear on the page.

Where the code goes depends on your CMS. Our guide on how to add JSON-LD to your website covers the common setups.

Step 3: Validate the markup

Validation no longer happens in Google’s Rich Results Test, because it no longer supports FAQ.

Use a general schema validator instead, such as the Schema Markup Validator from Schema.org. It checks that your JSON-LD is syntactically correct.

Here’s that check on our own English homepage, which carries FAQPage markup:

Schema Markup Validator result for the customerimpact.be English homepage detecting WebSite and FAQPage structured data with 0 errors and 0 warnings, a valid FAQ schema markup check The Schema Markup Validator on our own English homepage, October 2026: FAQPage detected, 0 errors, 0 warnings.

Zero errors means the syntax is right. It doesn’t prove the answers are any good.

The most common validation mistakes are in our guide to schema markup testing.

Which questions do you put in your FAQ for B2B?

The questions your buyers literally type in or ask an AI assistant, not the ones that suit you.

That difference determines whether you get cited or ignored. In B2B this means four kinds of question:

  • Fit: who it’s for and at what team size
  • Comparison: the difference between X and Y
  • Objection and risk: what if it doesn’t work
  • Price and process: an honest frame, not a rate

Fit questions

“What type of company is this for?” or “Does this also work for a team of X people?”

AI engines use this kind of content to match buyer and solution.

Comparative questions

“What is the difference between X and Y?” This is where much B2B purchase research begins.

AI likes to lift a clear answer there.

Objection and risk questions

“What if it doesn’t work?” or “How long does implementation take?”

Honest answers build trust here. With the reader and with the model.

Price and process frames

You don’t have to name an exact rate. But do give an honest frame, so the answer is usable.

Do question queries still get clicked?

On our own site, yes. In our CTR study, question queries in the top 10 didn’t click less than other queries:

Bar chart of question queries in the top 10 earning a 0.19% CTR versus 0.09% for other queries, the kind of buyer questions an FAQ with FAQPage schema should answer Non-branded queries ranking in the top 10, customerimpact.be, 1 June to 15 October 2026.

Watch out: the question group had only 41 clicks. So “didn’t click less” is safe; “click more” isn’t proven.

Finding those questions is covered in our guide to question keywords. Google’s People Also Ask box is a good free source too.

How do you phrase questions and answers?

Phrase each question the way a human asks it, in full sentences, not as a keyword.

For example, say your buyers search “crm small team price”. Your FAQ question becomes “What does a CRM cost for a small team?”

Keep each answer short and complete: two to four sentences that stand on their own, without “as above”.

That self-containment is precisely what an AI engine needs to extract your passage. If you want to tune this to your target audience, our guide on GEO for B2B takes you further.

Rule of thumb: an FAQ answer should still make sense when it’s quoted alone in someone else’s AI answer.

What are the limits of FAQ schema?

FAQ schema is no guarantee of citations and no substitute for good content.

It’s an amplifier, not an engine.

Anyone who thinks a small block of JSON-LD suddenly triples visibility in ChatGPT is in for a disappointment.

The figures on the direct effect contradict each other.

That says enough: there’s no miracle cure.

What decides whether you get cited?

What’s always true: a page that genuinely contains the best answer to a question wins, if it’s written in clear, self-contained blocks.

The schema makes that answer a bit easier to find and unambiguous. So never start with the schema.

Start with your buyer’s question and with an answer worth citing. Our AI citation checklist lists what else that answer needs.

When does FAQ schema pay off, and when not?

Use this table to decide:

Your pageFAQPage schema?
Visible FAQ with real buyer questionsYes, low effort and no risk
FAQ hidden in tabs or only in the codeFix the visible FAQ first
Questions nobody asks, written for SERP spaceRewrite the questions, then mark up

FAQ schema comes afterward, with low effort and no risk. It does logical work within a broader GEO foundation.

What that foundation looks like, you can read in our complete GEO guide.

And how to end up in Google’s AI Overviews has its own guide.

Frequently asked questions

Does Google still show FAQ rich results?

No. Since 7 May 2026, FAQ rich results no longer appear in Google Search, not even for the government and health sites that kept them after 2023.

Should I remove my FAQPage markup?

You don’t have to. Google ignores it for display and it causes no errors. Keep it if it matches your visible FAQ.

How do I test FAQPage schema now?

With the Schema Markup Validator from Schema.org. Google’s Rich Results Test dropped FAQ support in June 2026.

Does FAQPage schema get me cited by ChatGPT?

Not on its own. Google says no special markup is needed for its AI features. The citable Q&A content on the page is what counts.

The short summary

Google no longer shows FAQ rich results since May 2026, but that doesn’t make FAQPage schema pointless.

AI engines don’t read your JSON-LD as data.

But the tight Q&A structure the schema enforces is excellent to extract.

For B2B it’s cheap insurance: low effort, no risk, and it labels each question and answer unambiguously for machines.

The real gain lies in the discipline underneath. Start with the questions your buyers really ask, give self-contained answers, and let the schema confirm them.

Want a quick first read on your own site? Run the free GEO checker.

Want to know how your entire site is ready for AI search engines and which quick wins deliver the most for your leads? Check out our approach for visibility in AI search engines or contact us.

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.