---
title: "Does FAQ schema get your business into Google AI answers?"
description: "Check what Google says about FAQ markup and AI Overviews, run a ten-minute Rich Results Test, and decide whether a vendor's FAQ add-on is worth paying for."
url: "https://webleveling.com/blog/does-faq-markup-help-with-ai-answers/"
lang: "en"
published: "2026-10-11"
modified: "2026-10-11"
author: "Cal Hewitt"
tags: ["generative-engine-optimization","ai-search","seo"]
image: "https://webleveling.com/og/blog-does-faq-markup-help-with-ai-answers.jpg"
alternates:
  es: "https://webleveling.com/es/blog/esquema-faq-y-respuestas-de-ia.md"
---

# Does FAQ schema get your business into Google AI answers?

Check what Google says about FAQ markup and AI Overviews, run a ten-minute Rich Results Test, and decide whether a vendor's FAQ add-on is worth paying for.

![A closed black binder with a blank index tab on a clean wooden desk beside a sharpened pencil and a small brass key.](https://webleveling.com/blog/does-faq-markup-help-with-ai-answers/faq-schema-ai-answers-featured.jpg)

No. FAQ schema, also called FAQPage markup, does not put a business into Google's AI answers. Google says AI Overviews and AI Mode need no special schema, so a proposal that lists FAQ schema as your way into them is promising something Google has not described.

If a vendor, a web designer or an SEO has told you otherwise, you can check it yourself in about ten minutes, and you do not need a developer to do it.

The markup is not useless in every case, and it is not dangerous to leave on your site. What matters is the dates, the exact wording Google uses, and the point at which paying for it makes sense.

**Key Takeaways**

**No special schema**

Google's December 10, 2025 AI features guidance says no additional technical requirements or special schema.org markup apply to AI Overviews or AI Mode.

**FAQ rich results are gone**

Google limited them to well-known government and health sites in August 2023, deprecated the feature on May 7, 2026, and removed the documentation on June 15, 2026.

**A valid test is not a citation**

The Rich Results Test reports detected items, errors, warnings and crawlability, and a clean result does not guarantee display, ranking, indexing or an AI citation.

**Markup earns its place only in one case**

The page visibly holds real questions and answers, the markup says the same thing they say, and someone can keep both current.

**A markup-only add-on is hard to justify**

A paid job is worth the fee when it covers an audit, technical repairs, better content, indexing checks or conversion tracking.

## Get your answer in one minute: what FAQ markup does for AI answers

FAQ markup is a block of code, usually JSON-LD, that labels questions and answers already visible on a page. It describes content. It does not add content, authority or a ticket into an AI panel.

Google's own AI features guidance, published December 10, 2025, says there are no additional technical requirements or special schema.org markup for AI Overviews or AI Mode. A page needs to be indexed and eligible to appear in Google Search with a snippet, and that is the entry requirement. You can read the wording in [Google's AI features documentation](https://developers.google.com/search/docs/appearance/ai-features).

Google's generative AI guide, dated July 10, 2026, goes one step further. It says structured data is not required for generative AI search, and that there is no special AI schema. The same [AI optimization guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) points to ordinary work: crawlable pages, useful text, internal links, good page experience and structured data that matches what is on the page.

So, when a proposal says "FAQ schema for AI visibility," ask which Google document the claim comes from. The two documents above are where Google describes how its AI features choose pages, and FAQ markup is not a requirement in either.

![A closed black three-ring binder with a single blank index tab, resting on a clean wooden desk next to a sharpened pencil.](https://webleveling.com/blog/does-faq-markup-help-with-ai-answers/faq-schema-closed-binder-pencil.jpg)

The markup labels what is already on the page; it does not add anything to it.

## See exactly what Google changed, so you can read any proposal against the dates

The reason FAQ schema became a sales item is that it once did something visible. For a few years, Google could show a business's questions as expandable answers right in the search results, and an SEO could point at that and charge for it.

That feature has been wound down in steps, and each step has a date.

Google's FAQ rich result timeline

| Date | What Google did | Where to read it |
| --- | --- | --- |
| August 2023 | Limited FAQ rich results to well-known, authoritative government and health websites | Google Search Central blog |
| December 10, 2025 | Published AI features guidance: no special schema.org markup for AI Overviews or AI Mode | AI features documentation |
| May 7, 2026 | Deprecated the FAQ rich-result feature | Search documentation updates log |
| June 15, 2026 | Removed the FAQ rich-result documentation | Search documentation updates log |
| July 10, 2026 | Published the generative AI guide: structured data not required for generative AI search | AI optimization guide |

Google's [August 2023 announcement](https://developers.google.com/search/blog/2023/08/howto-faq-changes) described the first restriction, and the [Search documentation updates log](https://developers.google.com/search/updates) records the 2026 changes. The old FAQPage documentation address now lands on that log, because the feature page was taken down.

For an ordinary business, that means the expandable FAQ result is not a deliverable anyone can sell you today.

## Know what ChatGPT and Bing say before you pay for either

Google is only one of the places a customer might ask a question. A vendor may also say that FAQ markup helps you show up in ChatGPT or Microsoft Copilot, so it is worth reading what those companies tell site owners.

OpenAI's [publishers and developers FAQ](https://help.openai.com/en/articles/12627856-publishers-and-developers-faq) says public websites can appear in ChatGPT Search, and it recommends allowing OAI-SearchBot to crawl the content you want found, summarized, cited and linked. The step it names is crawl access. FAQPage markup is not part of it, so no one can quote OpenAI for a promise that markup produces a ChatGPT citation.

Bing's side is more detailed. Bing Webmaster Tools supports Schema.org, JSON-LD, Microdata and RDFa, and its [structured data guidance](https://www.bing.com/webmasters/help/marking-up-your-site-with-structured-data-3a93e731) says markup may support clearer grounding but does not guarantee visibility. Microsoft's [AI Performance documentation](https://www.bing.com/webmasters/help/ai-performance-9f8e7d6c) describes citations as a record of which URLs were cited, not a measure of ranking or authority.

![A pair of small brass keys on a plain string lying beside a closed notebook on a gray stone surface.](https://webleveling.com/blog/does-faq-markup-help-with-ai-answers/faq-schema-brass-keys-notebook.jpg)

Crawl access is the key OpenAI names; markup is a label on the door.

## Decide in five minutes whether the markup is worth adding to your pages

FAQ markup earns a place on your site when three things are true at once. The page visibly contains genuine questions and answers. The markup accurately mirrors them. And the whole thing is easy to maintain, so the code and the words do not drift apart.

When those conditions hold, the value is modest and practical. The markup keeps your page's description consistent, other tools that read structured data can use it, and it fits cleanly into a broader structured-data setup. It is not a promised Google result, and [Schema.org](https://schema.org/FAQPage) itself only defines the vocabulary; it does not control whether Google, ChatGPT or Bing uses it.

When the conditions do not hold, skip it. Questions that appear only in code, answers that no longer match the page, or a plugin that adds a second copy on top of your theme's copy all create work and no benefit. Google's [structured data policies](https://developers.google.com/search/docs/appearance/structured-data/sd-policies) require markup to match visible content, and they say valid markup can enable features but does not guarantee display.

If your FAQ page itself is thin or missing, fix that first. Our guide to [building an FAQ page for a small business website](https://webleveling.com/blog/faq-page-for-a-small-business-website/) covers the page, and [schema markup for a local business](https://webleveling.com/blog/schema-markup-for-local-business/) covers the types that describe who you are and where you work.

## Check your own markup in ten minutes, with no developer

Google's Rich Results Test is free, and it reads your page the way a crawler would. Run it before you pay anyone to change anything, and again after they have.

Work through these steps in order:

1.  Open the [Rich Results Test](https://search.google.com/test/rich-results).
2.  Enter the public URL of the page and choose Test URL.
3.  Review the detected structured-data items.
4.  Expand every error and warning.
5.  Compare each question and answer in the markup with the words on the visible page.
6.  Confirm the page is publicly crawlable, with no login wall, robots.txt block or noindex tag.
7.  Save the result, or a screenshot, so a developer can fix what it flags.

Google's [Rich Results Test help page](https://support.google.com/webmasters/answer/7445569) explains what the report shows. A valid result confirms technical eligibility for the Google features that still exist. It does not confirm display, ranking, indexing or an AI citation, so treat a clean test as a clean page and nothing more.

Step six matters more than it looks. A page that cannot be crawled or is marked noindex is out of reach for every search feature, with or without markup. If you suspect that, our guide to [pages that Search Console says are not indexed](https://webleveling.com/blog/page-not-indexed-search-console/) walks through the fix.

![A magnifying glass resting on a blank sheet of graph paper, with a ruler lying along one edge of a wooden table.](https://webleveling.com/blog/does-faq-markup-help-with-ai-answers/faq-schema-magnifier-graph-paper.jpg)

The test reads your page closely; what it finds is a to-do list, not a ranking.

## Spend your budget where AI answers actually come from

Google's guidance for AI features keeps returning to the same basics: a page that is indexed and eligible for a snippet, text a crawler can read, internal links, useful and reliable content, a good page experience, and structured data that matches the page. Bing's guidance adds clear entities, focused URLs and content that can be checked independently.

For a small business, that turns into a short audit. These are the problems that cost the most visibility, listed as a working order for the audit rather than a ranking by frequency:

- **Hidden or mismatched content**: The questions in the markup are not on the page, or the answers differ. This is usually a small edit to the page or template.
- **Syntax errors**: Broken JSON-LD punctuation, nesting or properties. This is usually a small developer task.
- **Blocked or unindexed pages**: Robots.txt, noindex, canonical or server problems. The work ranges from small to substantial, depending on the cause.
- **Thin or generic questions**: Answers copied from elsewhere, or unrelated to what customers ask before they buy. This is editorial work, and it is worth doing.
- **Conflicting plugins**: Several plugins or themes writing overlapping structured data. Consolidating them is small to moderate technical work.
- **Stale answers**: Prices, policies or services changed and the FAQ did not. Someone has to own the updates.
- **Measuring the markup instead of the business**: Calls, bookings and qualified leads are the numbers to watch. Our post on [whether ChatGPT and Google AI can read your website](https://webleveling.com/blog/can-chatgpt-and-google-ai-read-your-website/) shows how to check the readable side of this.

You can also stop worrying about a few things. Google's 2023 announcement said unused structured data does not need to be proactively removed, so leaving existing FAQ code in place will not cost you rankings. Nor is there a secret AI-only schema to find, and Google says no special chunking format or ideal page length is needed.

## Tell a real structured-data job from a markup-only add-on

Now you have the facts to read a quote. A vendor should not sell FAQ markup as a guaranteed route into Google AI answers, because Google has said no special schema is needed and the FAQ rich result no longer shows. An add-on that is only markup is unlikely to justify its own fee.

That does not make every paid job suspect. Here is how the two kinds of line item tend to look:

Reading a proposal that mentions FAQ schema

| Line item | Worth paying for? | What to ask |
| --- | --- | --- |
| "FAQ schema for AI Overviews, guaranteed citations" | No | Which Google document says markup gets a page into AI Overviews? |
| FAQPage JSON-LD added to one page, no other work | Rarely as a separate fee | Does the page already have visible questions and answers worth marking up? |
| Structured-data audit with a written list of errors | Yes | Which pages were tested, and where is the saved result? |
| Technical repairs: crawl, noindex, canonical or plugin conflicts | Yes | What was blocked, and how will you confirm it is fixed? |
| Content improvement on pages customers actually read | Yes | Which customer questions does the new copy answer? |
| Indexing checks and conversion measurement | Yes | Which calls, bookings or leads will be tracked, and where will you see them? |

The common thread is a deliverable you can inspect: a tested page, a fixed error, an indexed URL, a number in your own reports. For the wider list of questions to put to any vendor, see our post on [what to ask a marketing agency](https://webleveling.com/blog/questions-to-ask-a-marketing-agency/).

![A stack of three blank paper invoices clipped together beside a closed pen on a plain tabletop.](https://webleveling.com/blog/does-faq-markup-help-with-ai-answers/faq-schema-clipped-invoices-pen.jpg)

Pay for work you can inspect afterward, not for a promise about a panel.

**Quiz: Check what you know about FAQ schema and AI answers**

1. What does Google say about special schema for AI Overviews and AI Mode?
   - Product schema is required
   - FAQPage markup is required
   - No additional special schema.org markup is required **(correct answer)**
   - Only government sites can use any schema
2. What does a valid Rich Results Test result tell you?
   - The page will appear in AI Overviews
   - The markup is technically readable, but display, ranking, indexing and AI citation are not guaranteed **(correct answer)**
   - The page will rank on the first page
   - ChatGPT will cite the page
3. When is FAQ markup worth adding?
   - When the page shows real questions and answers, the markup mirrors them, and it is easy to maintain **(correct answer)**
   - Whenever a vendor recommends it
   - When the questions appear only in the code
   - When you want a guaranteed AI citation

## Frequently Asked Questions About FAQ Schema and AI Answers

**Is FAQ schema still relevant?**

It is still part of the Schema.org vocabulary and can describe visible questions and answers accurately. Google restricted FAQ rich results in August 2023 and deprecated the feature on May 7, 2026, so it no longer produces a Google FAQ result for ordinary businesses.

**Does schema help with AI search?**

Google says no special schema is required for AI Overviews or AI Mode, and its July 10, 2026 guide says structured data is not required for generative AI search. Structured data that matches the visible page can still clarify what the page contains. Bing says markup may support clearer grounding but does not guarantee visibility.

**Can FAQ markup get my business cited by ChatGPT or Copilot?**

OpenAI's publisher guidance names crawl access for OAI-SearchBot as the step for ChatGPT Search, and it does not promise that FAQPage markup produces citations. Bing's guidance says structured data does not guarantee visibility.

**Should I remove FAQ schema from my site?**

You do not have to. Google's 2023 announcement said unused structured data did not need to be proactively removed. Keep it if the questions are visible, the code matches them, and someone maintains both. Drop it if it adds upkeep and nothing else.

**Can FAQ schema improve my rankings?**

Google makes no such promise. Its guidance says structured data can enable features but does not guarantee display, and a valid test result does not guarantee ranking.

**How do I test whether my FAQ markup is valid?**

Enter the public URL in Google's Rich Results Test, review detected items, errors and warnings, compare the markup with the visible page, and confirm the page can be crawled and is not set to noindex.

## Moving Forward

FAQ schema does not put a business into Google's AI answers, and Google has said so in dated, public documents. The FAQ rich result is gone for ordinary businesses, AI Overviews and AI Mode need no special schema, and a valid Rich Results Test is a clean page rather than a citation. The markup is worth adding only when the page shows real questions and answers that the code mirrors and someone keeps current.

Knowing that saves you a fee today and gives you a way to read the next proposal. The work that builds visibility in AI answers is the work on the page itself: a crawlable site, specific answers to what your customers ask, and measurement tied to calls and bookings. If you want the wider picture, our explainer on [generative engine optimization](https://webleveling.com/blog/what-is-generative-engine-optimization/) lays out what that work covers.

If you want someone to run the audit with you, [Web Leveling](https://webleveling.com/) can test your structured data, repair what is broken and rework the pages your customers read, as part of our [generative engine optimization](https://webleveling.com/services/generative-engine-optimization/) service. We work with small and medium businesses across the country and overseas. [Send us the proposal you were given](https://webleveling.com/contact/), and we will tell you which lines are worth paying for.

## Terms

Words used in this post

Tap a term to see what it means.

**FAQPage markup.** Code that labels a page's visible questions and answers so software can read them. Also called FAQ schema.

**Structured data.** Code on a page, often JSON-LD, that describes what the page contains in a format search tools can read.

**JSON-LD.** A common format for writing structured data in a block of code that sits in the page.

**Rich result.** A search result with extra display features, such as expandable answers, that Google can show when a page qualifies.

**AI Overviews.** Google's AI-written summaries at the top of some search results, with links to supporting pages.

**Rich Results Test.** Google's free tool that reads a page or code and reports detected structured data, errors and warnings.

**OAI-SearchBot.** The crawler OpenAI says to allow if you want your pages found and cited in ChatGPT Search.

- [Can searchers turn off Google AI Overviews? What to do now](https://webleveling.com/blog/people-turn-off-google-ai-overviews/): Customers can see an AI Overview or regular results. Check your page and Business Profile in both, then compare calls and forms to decide where to focus.
- [Query fan-out and the service page: what to add for AI search](https://webleveling.com/blog/why-ai-answers-pull-from-several-pages/): Check whether your service page answers scope, cost, timing, service area, process and next step, starting with what buyers ask before they hire.
- [Business Disappeared From an AI Overview? What to Check First](https://webleveling.com/blog/business-disappeared-from-google-ai-overview/): Your business disappeared from an AI Overview? Run a ten-minute check of the search, Search Console and your page before you pay anyone to fix it.
