Tech for Retail 2025 Workshop: From SEO to GEO – Gaining Visibility in the Era of Generative Engines

Back to blog

FAQ structured data: when and how to use FAQPage markup in JSON-LD

SEO

Discover Incremys

The 360° Next Gen SEO Platform

Request a demo
Last updated on

1/11/2026

Chapter 01

Example H2
Example H3
Example H4
Example H5
Example H6

Structured data for FAQs describes, in FAQPage format, the official questions and answers on a page. It complements the other types presented in our guide to structured data: definition, formats and method. One fact frames everything else: since August 2023, Google has restricted FAQ rich results to authoritative government and health websites. A B2B site therefore gets no display, but the markup keeps its structuring value. What remains is knowing when to mark up, and how.

 

What FAQPage markup is for, and who reads it

 

The schema.org FAQPage type describes a page containing a list of questions written by the site publisher, each with a single, official answer. schema.org is an open, community-maintained vocabulary: it does not belong to Google, and several families of systems read this markup:

 

  • Google, to understand the question–answer structure of the page, even without a rich result;
  • other search engines (Bing, Yandex, Apple), which read schema.org with their own display rules;
  • AI crawlers of generative engines (GPTBot and OAI-SearchBot, ClaudeBot, PerplexityBot, Googlebot for AI Overviews and AI Mode), which read the HTML and therefore the markup;
  • aggregators, assistants and accessibility tools, which use an explicit question–answer pair rather than text they have to interpret.

 

Question and Answer: the structure of the schema

 

Technically, you declare a FAQPage entity whose mainEntity property contains a list of Question objects. Each question carries an acceptedAnswer of type Answer. The properties to populate first are few:

 

  • @context: "https://schema.org";
  • @type: "FAQPage";
  • mainEntity: the array of Question objects;
  • Question.name: the full question, as displayed;
  • Answer.text: the answer, with simple HTML allowed if the visible answer contains it too.

 

Google and FAQ markup: what is displayed at the time of writing

 

Many guides still present marked-up FAQs as a way to take up more space in the results. That is no longer true for a company website. In August 2023, Google restricted FAQ rich results to authoritative government and health websites, and in September 2023 it removed HowTo rich results.

 

The following table shows, at the time of writing, what Google displays for FAQ-related types and what the markup brings outside Google:

 

schema.org typeGoogle display (at the time of writing)Value beyond Google display
FAQPageRestricted since August 2023 to authoritative government and health websites; no display for a B2B siteExplicit question–answer structure
HowToRich result removed in September 2023; the type remains valid in schema.orgExplicit structure of the steps
QAPageActive for pages where users submit answers (forums, communities)Distinguishes the question, suggested answers and the accepted answer
Article, Organization, BreadcrumbListActive; breadcrumbs no longer shown on mobile since early 2025Author, publisher, date and hierarchy of the page carrying the FAQ

 

In practice, a valid test will not produce an FAQ rich result on a B2B site. The markup is still read and understood, but it no longer changes how your result looks. Judging FAQPage by the extra SERP real estate it brings no longer makes sense; judge it by the quality of the structure it provides.

 

Why mark up your FAQs anyway

 

Removing the display does not remove the reading. FAQPage remains a simple way to tell a machine, unambiguously, where a question starts, where its answer ends and who wrote it. For a B2B page that handles objections (security, integrations, timelines, compliance), this explicit structure keeps real value.

 

What the markup brings to generative engines

 

AI crawlers read the HTML, and therefore the markup. Structured data helps a system understand a page: which entity, which type of content, which organisation, which date, which facts. On an FAQ, it supports accurate reproduction of the answer and correct attribution, provided the marked-up text is identical to the visible text. The topic is covered in our guide to structured data and generative engines.

 

What the markup does not do

 

No study shows that marking up an FAQ as FAQPage gets a page cited by an AI. Nothing proves that the markup is useless to them either: both statements must be made together. What matters most for generative engines lies elsewhere:

 

  • entities named explicitly in the questions and answers;
  • structured content: a single H1, H2s and H3s, lists, tables;
  • consistent information between the page, its markup and other sources;
  • reachable pages, with no AI crawlers blocked by mistake.

 

FAQPage, QAPage or HowTo: choosing the right type

 

The right type depends on who writes the answers and on the shape of the content. Forcing FAQPage onto a community page or a procedure produces markup that does not describe the page. The following table compares the three types:

 

TypeUse and author of the answersMain propertiesGoogle display (at the time of writing)Value beyond Google
FAQPageMultiple questions, one official answer per question, written by the publishermainEntity, Question.name, acceptedAnswer, Answer.textNone for a B2B site since August 2023Explicit question–answer pairs
QAPageOne main question, answers submitted by users (forum, community support)mainEntity, answerCount, acceptedAnswer, suggestedAnswerActive on eligible pagesDistinguishes the accepted answer from suggested answers
HowToA step-by-step procedure, written by the publisher (configuration, tutorial)name, step, HowToStep.textRemoved in September 2023Ordered, explicit steps

 

When to use QAPage schema for community-driven pages

 

If users can submit answers, or if the same question receives several competing answers, QAPage is the logical type. It matches forums, community support spaces and single-question pages with multiple responses. An editorial FAQ, where your team writes one answer per question, remains FAQPage.

 

Combining multiple schemas without conflicts

 

The same page can carry FAQPage alongside Article, BreadcrumbList or Organization, provided each type describes what is actually present. To keep the combination readable, three precautions are enough:

 

  • do not declare the same information twice with different values;
  • do not let two sources (a CMS plugin and a template) each generate an FAQPage block;
  • do not mark up a type that does not match the visible content.

 

Compliance rules: visible questions, faithful answers, neutral tone

 

Google Search Central documentation and schema.org agree on one principle: markup describes what the page shows, nothing more. For an FAQ, this principle translates into concrete rules:

 

  • Visibility: every question and its answer are accessible on the page, in full or within an expandable accordion; declaring them only in code is not compliant.
  • Fidelity: the text in Answer.text matches the displayed answer word for word, with no enriched version reserved for crawlers.
  • One official answer per question: as soon as several user answers coexist, the page falls under QAPage.
  • Non-promotional tone: no salesy, repetitive or keyword-stuffed answers.
  • No duplication: the same FAQ, with the same wording, is not copied across dozens of pages.

 

Markup that describes content absent from the page exposes you to a manual action for spammy structured data. Treat your FAQ as editorial content in its own right, not a technical shortcut.

 

Writing questions from real requests

 

No amount of markup will compensate for an irrelevant FAQ. Good questions come from objections heard in pre-sales conversations, support requests and the definitions users need to understand the offer. Phrase them the way your readers ask them: 70% of searches contain more than three words (SEO.com, 2026), and a complete question, with its named entities, is easier to understand than a string of keywords.

 

For the answers, put the direct answer in the first sentence, then the conditions and limitations. A definitional, neutral and verifiable answer serves both the reader and the systems that reproduce it.

 

Complete code example: an FAQPage JSON-LD template

 

The following template marks up two questions; the second answer contains an HTML link, also present in the visible answer. Replace the texts with those actually displayed on your page:

 

  • <script type="application/ld+json">
  • {
  •   "@context": "https://schema.org",
  •   "@type": "FAQPage",
  •   "mainEntity": [
  •     {
  •       "@type": "Question",
  •       "name": "How long does deployment take?",
  •       "acceptedAnswer": {
  •         "@type": "Answer",
  •         "text": "Deployment takes four weeks, from configuration to team training."
  •       }
  •     },
  •     {
  •       "@type": "Question",
  •       "name": "Where is the data hosted?",
  •       "acceptedAnswer": {
  •         "@type": "Answer",
  •         "text": "In the European Union. Details on our <a href='https://www.example.com/security'>security page</a>."
  •       }
  •     }
  •   ]
  • }
  • </script>

 

Each new question adds a Question object to the mainEntity array, separated from the previous one by a comma. The JSON must remain valid: one extra comma or one unclosed quote is enough for the whole block to be ignored.

 

Adding links in answers: when it helps

 

Answer.text accepts simple HTML, including links. A link belongs there when three conditions are met:

 

  • the same link appears in the visible answer, with the same anchor;
  • it genuinely helps: a definition, a process, a support or security page;
  • it does not turn the answer into a sales prompt.

 

Avoid adding links to every answer: it makes the FAQ harder to read and turns it into an excuse for internal linking, which undermines its core purpose.

 

To mark up or not: a framework by page type

 

The decision no longer depends on Google display, but on two questions: does the page contain a real, visible FAQ, and do the answers add something to the body text? The following framework applies these criteria to the most common pages of a B2B site:

 

Page typeDecisionWhy
Blog articleYes, if the FAQ answers questions the body does not coverAn FAQ that repeats the article adds nothing for the reader or the markup
Product pageYes, for real questions (compatibility, delivery, warranty)Product and Offer remain the priority; FAQPage complements them
B2B landing pageYes, if the FAQ addresses objections with factual answers; no if the page carries only a marketing messageSecurity, GDPR, integrations and timelines are facts worth reproducing exactly
Support page or help centreYes, the most natural case; QAPage if the answers come from usersFixed questions, official answers, stable content
Pricing pageYes, if the answers stay accurate and up to dateAn outdated price or condition in the markup is propagated as is

 

Whatever the page, there is no quota for the number of questions to mark up: mark up those that are visible and useful, no more and no less.

 

Placement and deployment: one block per page, a single source

 

Think of implementation as maintained code, not a one-off task. The main risk is not a missing comma, but a lasting mismatch between the displayed FAQ and the markup.

 

Where to place the JSON-LD script and how to avoid duplicate markup

 

Google recommends JSON-LD, which can be added without modifying the visible HTML. The script can go in the <head> or in the <body>; JavaScript injection is accepted, as long as the block appears in the final rendered page. Three rules prevent most inconsistencies:

 

  • a single FAQPage block per page, covering all the visible questions;
  • one source of truth: a CMS plugin or a template, never both;
  • an FAQ that is always visible, generated from the same fields as the markup.

 

Pre-release checklist

 

Before rolling the markup out across a template, run these checks in order:

 

  • Generate the visible FAQ and the JSON-LD from the same CMS fields.
  • Check that nothing blocks crawling (noindex, robots.txt, authentication).
  • Test a sample set of representative URLs before rolling out widely.
  • Retest after every change of theme, template or page builder, and after every migration.

 

Checking the markup: testing and monitoring in Search Console

 

Before publishing, you can test the markup with the Rich Results Test, on a URL or a code snippet, and check its conformity with the vocabulary using the Schema.org validator. An error makes the markup ineligible; a warning flags a missing recommended property. For FAQPage on a B2B site, a valid result confirms the markup is read, not that it will be displayed. After going live, Google Search Console lets you check the indexed version with URL Inspection.

 

Depending on your situation

 

Depending on your starting point, these resources complement this guide:

 

 

To publish content whose FAQ is delivered with its FAQPage markup, the Incremys Content Production module, a GEO & SEO platform, produces questions, answers and JSON-LD from the same texts.

 

FAQ about structured data for FAQs

 

Does Google still show FAQ rich results?

 

No, not for a B2B site. Since August 2023, Google has restricted FAQ rich results to authoritative government and health websites. A company website can have perfectly valid FAQPage markup without any rich display appearing. The markup is still read to understand the page, but it no longer changes how the result looks.

 

Should you still mark up your FAQs?

 

Yes, if the FAQ is real, visible and useful. FAQPage keeps its value as an explicit question–answer structure for Google, other search engines and AI crawlers. It is no longer a display lever. The cost stays low when the markup is generated by a template from the same fields as the visible FAQ.

 

FAQPage or QAPage?

 

FAQPage fits when your team writes one official answer per question, on a page that groups several questions. QAPage fits when one main question receives answers submitted by users, as on a forum or a community support space. The deciding criterion is who writes the answers, not the format of the page itself.

 

Can you add links in the answers?

 

Yes. The Answer.text property accepts simple HTML, including links. The same link must appear in the visible answer, with the same anchor, and genuinely help: a definition, a process, a support page. A link in every answer makes reading harder and turns the FAQ into an excuse for internal linking.

 

How many questions should you mark up?

 

All those visible on the page, and only those. There is no official quota. A short FAQ focused on real objections is better than a long list of generic questions, which is harder to keep up to date and more likely to be duplicated from one page to another.

 

How do you check that the markup is valid?

 

Test the URL or code snippet in the Rich Results Test, then check conformity with the vocabulary using the Schema.org validator. After going live, URL Inspection in Search Console shows the indexed version. Retest after every template change, as redesigns frequently break the link between the visible FAQ and the JSON-LD.

 

Do AI systems read marked-up FAQs?

 

Their crawlers read the page's HTML, and therefore the markup it contains. FAQPage presents them with explicit question–answer pairs, which supports accurate reproduction. No measured effect of the markup on being cited has been demonstrated at the time of writing: clear answers and content structure matter more.

Discover other items

See all

Next-Gen GEO/SEO starts here

Complete the form so we can contact you.

The new generation of SEO
is on!

Thank you for your request, we will get back to you as soon as possible.

Oops! Something went wrong while submitting the form.