Back to blog

FAQ Schema and Structured Answer Markup: What Still Works

AEO Course

FAQ Schema and Structured Answer Markup: What Still Works

By Edward | Answer Engine Optimization Specialist

How FAQPage, QAPage, HowTo and DefinedTerm markup work, what Google still shows as rich results, how to write valid JSON-LD and when markup is worth adding.

Updated 11 November 2026 · Part of the AEO guide series

Short answer: FAQ schema is structured data, usually written as JSON-LD, that labels question-and-answer pairs on a page so that machines can read them clearly. It does not improve rankings by itself, and Google no longer shows FAQ rich results for most sites, so do not add it for the dropdowns. It can still be worth adding when the questions and answers are genuinely visible on the page, because it describes your content accurately to any system that reads structured data. Always match the markup to the visible text, validate it and keep your expectations modest.

What FAQ Schema Is

Schema.org is a shared vocabulary for describing the content of a web page. FAQPage is one of its types: a page that lists questions with 1 answer each. When you add FAQPage markup, you label each question and its answer so that a search engine does not need to guess which text is which.

JSON-LD is the format Google recommends for structured data. It sits in a script tag in the page's HTML and does not change what visitors see. The markup must describe content that is visible on the page.

What Changed: FAQ and HowTo Rich Results

Older guides promise expandable FAQ dropdowns under your search listing. That advice is out of date:

  • In 2023, Google announced that FAQ rich results would be shown only for well-known, authoritative government and health websites, and that it would stop showing HowTo rich results. For most sites, valid FAQ markup no longer produces the dropdowns in search.
  • Google has also been simplifying how structured data is used in search results, and the list of supported rich results changes over time. Check Google Search Central's current documentation before you plan around any rich result.

That does not make the markup worthless, but it changes the reason to use it. Think of it as a tidy description of your content, not as a way to earn extra space on the results page.

Does FAQ Schema Help AEO?

Honestly, nobody outside the search and AI companies can prove it. What can be said with confidence:

  • Visible, well-written questions and answers help readers, featured snippets and AI answers. That is the part with the biggest effect.
  • Markup describes that content in a machine-readable way. It may help some systems understand the page. Google says structured data helps it understand a page, but it does not state that FAQ markup improves rankings.
  • It does not replace good content. Valid markup on thin or unhelpful answers will not make them useful.

Be wary of claims that FAQ schema makes AI assistants cite you. Assistants do not publish how they choose sources, and no one can promise a result. Use it when it describes your page accurately and costs you little to maintain.

How to Write FAQ Schema Correctly

Follow these rules:

  1. Mark up only visible content. Every question and answer in the markup must appear on the page for visitors.
  2. Match the visible text. The text in the markup should be the same as the text on the page, with no extra promotional wording.
  3. Use FAQPage for questions you answer yourself. If users post answers, use QAPage instead.
  4. Do not use it for advertising. Google's guidelines do not allow FAQ markup for content that is mainly promotional.
  5. Put 1 FAQ block on a page, and do not repeat the same questions across many pages.

A minimal example with 1 question:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How long does a roof repair take?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Most minor roof repairs take from a few hours to 1 day, depending on the damage and the weather."
    }
  }]
}
</script>

Add 1 more object to the mainEntity array for each extra question. The example text is illustrative; use your own accurate answers.

HowTo Markup

HowTo markup labels the steps in a task. Because Google stopped showing HowTo rich results, it no longer brings a visible benefit in Google Search. Write the steps as a clear numbered list on the page and use markup only if your own tools or other systems use it. If you already have HowTo markup, keep it accurate, or remove it if you cannot maintain it.

QAPage Markup

QAPage is for pages where a question is posted and the community or staff provide answers, such as forums and help centers. It labels 1 question and 1 or more answers, and can mark an accepted answer. It is a different case from an FAQ, where the page owner writes both the question and the answer. Use it only for real user-generated or support threads, not for a page that you write yourself.

DefinedTerm Markup

DefinedTerm is part of schema.org and describes a term and its definition, which suits a glossary. Google does not list it as a source of rich results, so treat it as a descriptive label. A glossary with clear headings and plain-language definitions helps readers and snippets far more than the markup does.

Which Type Fits Which Page

Your pageBest choiceNotes
Questions you write and answerFAQPage (optional)Rich result display is limited for most sites
Forum or help thread with several answersQAPageUser-generated content only
Step-by-step tutorialClear numbered list; HowTo optionalNo HowTo rich results in Google Search now
Glossary or definitionsClear headings; DefinedTerm optionalDescriptive only
Article or blog postArticle or BlogPosting, plus Organization and author detailsDescribes who wrote it and when

Our guide to structured data and rich results explains the wider picture, including which types Google supports.

How to Validate Your Markup

  1. Use Google's Rich Results Test to check whether a page is eligible for a supported rich result.
  2. Use the Schema Markup Validator at validator.schema.org to check the markup against the schema.org vocabulary, including types that Google does not test.
  3. Compare the markup with the visible page. The questions and answers must match.
  4. Check the page's rendered HTML, because markup added by JavaScript can be missed if it is not rendered properly. Static or prerendered markup is the safest.
  5. Check Search Console for structured data reports and warnings after Google recrawls the page.

A free SEO audit also reports whether structured data is detected on a page, which makes a fast first check before using the other tools. If you also want to know whether AI crawlers can read the page, use the AI crawler access check.

Misuse to Avoid

  • Marking up questions that are not visible on the page.
  • Using FAQ markup for ads or sales copy.
  • Putting the same FAQ block on every page of the site.
  • Answers in the markup that differ from the answers on the page.
  • Marking up user reviews as if they were your own FAQ.
  • Leaving outdated answers in markup after the page changes.

Google can take manual action against structured data that is misleading, which can remove rich result eligibility for the affected pages or the site. Keep the markup honest and short.

Example: Deciding Whether to Add FAQ Schema

A home insurance site has a page for renters insurance. At the bottom it has 6 questions and answers that its own team wrote, all visible, covering cost, what is covered and how to claim. It adds FAQPage markup for those 6, checks that the text matches, validates the page and moves on. It does not expect dropdowns in search or a ranking boost. It does expect that the questions are easy to read for people and machines.

By contrast, a store that has no real questions to answer is better off writing 3 useful answers on the product page than inventing 20 questions just to mark them up.

Check Your Visibility

After you improve a page, see how it appears to AI tools. The AI visibility checker shows how assistants such as ChatGPT, Gemini, Perplexity and Claude rate your site, and the AI citation analyzer shows which pages Google's AI Overview cites for a question you care about and how those pages are written.

Action Checklist

  1. List 5 real questions your customers ask about one product or service.
  2. Write a short, accurate answer for each and show them on the page.
  3. Add FAQPage JSON-LD that matches the visible text, if you want the markup.
  4. Validate with the Rich Results Test and the Schema Markup Validator.
  5. Re-check the page after any content change, so the markup stays accurate.
  6. Judge success by how useful the answers are, not by whether dropdowns appear.

Related Guides

Official references: Google's Rich Results Test and the schema.org FAQPage definition.

FAQs

Does FAQ Schema Still Show Dropdowns in Google Search?

For most sites, no. Google announced in 2023 that FAQ rich results would be limited to well-known government and health sites. Valid markup can still describe your content, but you should not expect the dropdowns.

Does FAQ Schema Improve My Rankings?

Google does not say that it does. Structured data helps Google understand a page, but the quality and relevance of the content are what matter for ranking.

How Many Questions Should I Mark Up?

Only the real questions that appear on the page. A handful of useful questions is better than a long list of weak ones, and it is easier to keep accurate.

Can I Add FAQ Schema to Every Page?

Only to pages that genuinely contain a visible list of questions and answers. Do not add FAQ sections or markup to every page just to include schema, and do not repeat the same block across the site.

Is HowTo Schema Still Useful?

Google stopped showing HowTo rich results, so it no longer brings a visible benefit in Google Search. Write clear numbered steps on the page, which help readers, and keep any existing markup accurate if you decide to keep it.

How Do I Test My Schema?

Use Google's Rich Results Test for supported rich results, the Schema Markup Validator for general schema.org checks and Search Console for reports after Google crawls the page. Compare the markup with the visible text each time.