---
title: "FAQ Schema: How to Add It and What It Does for AI Search"
description: Learn how to add FAQ schema in six steps, why Google dropped FAQ rich results, and what the markup still does for AI search on your HubSpot pages.
---

[The Propello Blog | Go-to-Market, AEO and RevOps](https://www.finemediabw.com/blog)

# [FAQ Schema: How to Add It and What It Does for AI Search](https://www.finemediabw.com/blog/faq-schema)

 Written by [Tumisang Bogwasi](https://www.finemediabw.com/blog/author/tumisang-bogwasi) | Oct 10, 2026, 11:36:23 AM

If you lead revenue or marketing at a growing B2B company, FAQ schema is a small block of schema markup that labels the questions and answers on a page so machines can read them cleanly. You add it to a page that already has a real FAQ section, and you keep the two in step. To tell engines who wrote the page, add [author schema](https://www.finemediabw.com/blog/author-schema) too.

This guide is for CEOs, founders, CROs and the marketing lead who ships the page. You get the straight answer on what Google changed, a six-step method for adding FAQPage schema in HubSpot, and an honest view of what it does for AI search. It is a supporting tactic, not a ranking lever.

 

| **FAQ Schema** FAQ schema is structured data, usually JSON-LD, that marks up the questions and answers visible on a page so search engines and AI systems can read each pair as a unit. |
| --- |

## By the end you will have a page that is easy for machines and people to read

Most FAQ sections on B2B sites are written for visitors and never tested against a machine reader. Valid FAQ schema markup closes that gap without changing what the visitor sees.

- One page with a visible FAQ section of five questions, each answered in a few plain sentences.
- A valid FAQPage block that matches that visible text word for word.
- The block live in the page head, with the checks that show it is read correctly.
- A short routine for keeping the markup and the page in step.

## What to have in place before you start

Check these four things first. Schema cannot rescue a page that has nothing worth marking up.

- **A real FAQ page or section.** The questions must be ones buyers ask, answered on the page for anyone to read.
- **Editing access to the page head.** In HubSpot that means the Head HTML field for a blog post or page.
- **A decision on who owns the answers.** Someone with product knowledge should approve each one.
- **Realistic expectations.** The next two sections explain what the markup does and does not do.

If you have not yet mapped the wider set of on-page signals, the [AEO checklist with an annotated page](https://www.finemediabw.com/blog/aeo-checklist-annotated-page) shows where schema sits among them.

### Know what Google changed about FAQ rich results in Google Search

For years, FAQ schema could make a page show expandable questions under its link on Google Search. That has ended. Google's own changelog says the [FAQ rich result stopped appearing in Google Search from May 7, 2026](https://developers.google.com/search/updates), and the feature documentation has since been removed.

Even before that, Google's documentation said in September 2023 that the feature was shown only for well-known, authoritative government and health websites. So the old promise, more space in search results from a few lines of code, is gone. Anyone still selling FAQ schema on that promise sells something that no longer exists.

Many marketers ask whether to delete FAQPage structured data markup that is already live. Google's notice says the rich result is gone from search results; it does not announce any penalty for keeping accurate markup.

### Know what FAQ schema markup can still do for AI Overviews

Google is direct about AI features. Its guidance says there is [no special schema.org structured data you need to add](https://developers.google.com/search/docs/appearance/ai-features) to appear in AI Overviews or AI Mode, and that structured data should match the visible text on the page.

Google's spam policies also apply to generative AI responses in Google Search, so honest markup matters there too.

That does not make the markup useless. FAQ schema still gives some indirect SEO benefit despite the lost rich result, because structured data helps search engines understand where a question ends and an answer begins. Traditional SEO still rewards a clear page, and schema markup is one small part of how search engines read it.

Other search engines and AI tools that read pages also benefit from a clear question and answer format, although none of them promise a result.

The same habit supports featured snippets and voice search, since voice assistants rely on structured question and answer formats to deliver answers.

Markup does not guarantee a place in People Also Ask boxes or any other feature. Both favor a direct, helpful answer near its question, as a good FAQ section already gives. Treat the markup as cheap, clean labeling, not a way to earn citations, and keep the valuable information in the visible text.

## How to add FAQ schema in six steps

Each step ends with what done looks like, so you know when to move on.

### 1. Choose the FAQ page and write five questions buyers ask

Pick one page where questions genuinely belong: a service page, a guide or a product page. Draw the questions from sales calls, support tickets, CRM data and the questions prospects ask in discovery, not from guesses.

Keep each question in natural language, phrased the way a buyer would say it. Three to five well-structured questions is a sensible range for one page. Group them around one subject so the FAQ section supports the page rather than wandering. Collecting these questions also shows which customer queries your content strategy has missed.

You are done when you have five real questions, each tied to a buyer you can name.

### 2. Write short answers that stand alone

Write each answer so it makes sense if read without the page around it. Lead with the direct answer in the first sentence, then add one or two sentences of context. Aim for 40 to 55 words. Concise answers are easier for AI systems to quote as citations, though nothing guarantees one.

Put these answers on the page as normal visible text. A collapsible menu, often called an accordion, is fine as long as the text is in the page and not loaded from somewhere else.

You are done when each answer can be read aloud and understood alone.

### 3. Write the FAQPage schema as JSON-LD

Google recommends JSON-LD as the easiest structured data format to maintain, as its [introduction to structured data](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) explains. The vocabulary comes from [schema.org's FAQPage type](https://schema.org/FAQPage), where a page lists its questions in mainEntity, each as a Question with a name and an acceptedAnswer.

The required properties are the question text and the answer text. Recommended properties add detail but are optional here. This example of FAQPage schema shows the shape with two questions:

```
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is a discovery call?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A discovery call is the first conversation where we learn about your goals and systems."
      }
    },
    {
      "@type": "Question",
      "name": "Who should join the call?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Bring the person who owns revenue and the person who runs your CRM."
      }
    }
  ]
}
```

You can also write it as Microdata or RDFa, and Google accepts all three formats, but JSON-LD keeps the code out of your layout.

Wrap the JSON-LD code in a script tag of type application/ld+json. Copy each question and answer from the page exactly, because Google's [quality guidelines for structured data](https://developers.google.com/search/docs/appearance/structured-data/sd-policies) say not to mark up content that readers cannot see on the page.

You are done when the block parses and every question and answer matches the visible text.

### 4. Add it to the page head in HubSpot

In HubSpot, open the content, choose Settings, then Advanced, and paste the script into the Head HTML field. HubSpot's page on [using code snippets with HubSpot content](https://knowledge.hubspot.com/website-and-landing-pages/use-code-snippets-with-hubspot-content) describes this path and notes that the footer field is not available for blog posts.

Check the blog's own structured data setting too. HubSpot's [blog settings guidance](https://knowledge.hubspot.com/blog/manage-your-blog-template-and-settings) says to avoid enabling its built-in structured data when custom schema already exists. Duplicate blocks can cause confusion, so keep one source per schema type.

You are done when the page is published and the script appears once in the source.

### 5. Test the schema markup

Run the page through the [Schema Markup Validator](https://validator.schema.org/). This schema markup validator checks your syntax against schema.org. It catches missing commas, broken quotes and misspelled properties. Audit and validate the markup again whenever the page changes, so it keeps meeting current standards.

Google's Rich Results Testing Tool checks eligibility for Google's own result features, and FAQ is no longer one of them, so do not expect a green FAQ result there. Instead, open the live page and confirm that the visible FAQ section and the JSON-LD say the same thing.

You are done when the validator shows no errors and a person has compared the code to the page.

### 6. Monitor it and keep it in step

Use Google Search Console to watch how the page shows up in search results over the following weeks. Expect no sudden jump. Monitoring search performance and user engagement shows whether clearer pages help, and the point is clean markup, not a traffic spike.

Add the page to your review calendar. When an answer changes on the page, change it in the code in the same sitting. The [organization schema maintenance guide](https://www.finemediabw.com/blog/organization-schema-markup-maintenance) covers a quarterly routine that works for every schema type you run.

You are done when the review date is on the calendar and one person owns it.

## Mistakes that make FAQ schema a liability

Check your page against this list before you publish.

- **Marking up answers that are not on the page.** Hidden or mismatched text breaks Google's guidelines on visible content.
- **Using FAQPage for a forum or community thread.** Pages where users submit answers belong to a different type, covered in the next section.
- **Adding it to every page.** Mark up only pages with a genuine FAQ section.
- **Writing promotional answers.** An answer that reads as an advert is not helpful to a visitor or a machine.
- **Letting the code drift.** Old answers in the markup after the page has changed are worse than none.
- **Promising results.** Tell your team it helps machines read the page, and stop there.

### Pick QAPage only when users can submit answers

Google's page on [QAPage markup](https://developers.google.com/search/docs/appearance/structured-data/qapage) is for pages where users can submit answers to a single question, such as a forum thread. It says not to use QAPage markup for an FAQ written by the site owner, where there is only one answer and no way to add alternative answers.

So a B2B FAQ written by your team uses FAQPage. A product support page where members submit alternative answers to a single question can apply QAPage markup. A single answer written by you, with no way to add alternative answers, does not qualify. The wrong type quietly makes good markup invalid.

Website owners often reach for QAPage by mistake. Use one FAQPage block per single page, with multiple questions in the same block. Do not roll the questions for your entire site into one block, because each page should describe only what its own visitors can see.

## What you gain when this is done properly

A well-labeled FAQ section makes one page easier to read for people and machines alike, and structured FAQ content improves the user experience by answering common questions directly. The gains show up differently for each team.

### Sales gets answers it can point to

Prospects arrive having read the same answers your reps give on calls, so early conversations skip the basics. Reps can send a link to a single question instead of retyping it.

### Marketing gets cleaner pages to build on

Marketing owns one tidy example for question-led content that works for featured snippets, voice search and AI answers alike. Reuse it across service pages, and tie it into your wider plan for [optimizing content for AI search](https://www.finemediabw.com/blog/how-to-optimize-content-for-ai-search).

### Customer success gets fewer repeat questions

Customer success sees the same questions asked less often once the answer sits on the page. The questions that still arrive show which answers need work, and those go straight back into the FAQ.

## Make your FAQ page easy for machines to trust

FAQ schema will not earn a rich result in Google Search any more, and it is no shortcut to AI citations. What it gives you is a habit that serves readers and machines: real questions, plain answers and markup that matches the page. Pair it with entity work such as [knowledge graph and entity authority](https://www.finemediabw.com/blog/knowledge-graph-seo-entity-authority).

Propello is a [HubSpot partner](https://www.finemediabw.com/about-us) and designs and builds connected go-to-market systems on HubSpot. If your pages, data and reporting do not yet agree with one another, an audit is the place to start.

[Book a Propello GTM Audit](https://www.finemediabw.com/contact)

## Frequently asked questions

[View full post](https://www.finemediabw.com/blog/faq-schema)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Tumisang Bogwasi"
  },
  "dateModified" : "2026-10-10T16:07:50.081Z",
  "datePublished" : "2026-10-10T11:36:23Z",
  "headline" : "FAQ Schema: How to Add It and What It Does for AI Search",
  "image" : {
    "@type" : "ImageObject",
    "height" : 630,
    "url" : "https://5034240.fs1.hubspotusercontent-na1.net/hubfs/5034240/Blog/AEO/Consideration/FAQ%20Schema%20-%20How%20to%20Add%20It%20and%20What%20It%20Does%20for%20AI%20Search/faq-schema-share-1200x630.png",
    "width" : 1200
  },
  "mainEntityOfPage" : "https://www.finemediabw.com/blog/faq-schema",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60.0,
      "url" : "https://f.hubspotusercontent40.net/hubfs/5034240/Fine_Media_logo_Set%20copy_HubSpot_Logo_Long_Stacked.svg",
      "width" : 60.000004
    },
    "name" : "An Inbound Marketing Blog for Marketers"
  }
}
```