Skip to content
Chalk Labs / AI SEO
How-to guide

How to Add FAQ Schema Markup to Your Website

By Rahil Jain, founder of Chalk LabsUpdated How we research

The short answer

Add FAQ schema by writing real questions and answers on the page, then describing them in JSON-LD using the FAQPage type, and testing the code in the Schema Markup Validator. Google stopped showing FAQ rich results on 7 May 2026, so do it for clarity and consistency, not for a visible Google reward.

  • Google's FAQ rich result stopped appearing in Search from 7 May 2026, and Google removed its FAQ documentation on 15 June 2026.
  • Google says no special schema.org markup is needed for AI Overviews or AI Mode.
  • Schema.org still defines FAQPage, and the markup remains valid. Its value now is tidy, machine-readable structure.
  • Markup must match visible text. Never mark up questions or answers readers cannot see on the page.

What is FAQ schema?

FAQ schema is a block of code that labels the questions and answers on a page so software can read them without guessing. Schema.org, the shared vocabulary behind it, defines FAQPage as a web page presenting one or more frequently asked questions 1.

The code usually sits in a script tag in JSON-LD format. JSON-LD is a way to write structured data as a block of text separate from your visible page. Google recommends it where your site setup allows 2. Each question is a Question item, and its reply is an Answer. Schema.org defines Question as a specific question, such as one collected in an FAQ document 3.

Do it step by step

0 of 7 done0%

  1. Add five to eight real questions as visible headings or list items, each followed by its answer. Put the direct answer in the first sentence.

    Tip: If you cannot see an answer on the page, it must not appear in the code.

  2. Take the FAQPage template below and replace each question and answer with your own text. Keep the structure: one Question item per question, each holding an acceptedAnswer.

  3. Inside any answer, replace a double quote with a backslash then a double quote, or use single quotes. Keep each answer as one line of text.

    Tip: Use straight quotes only. Curly quotes pasted from a word processor can break the code.

  4. Paste the block inside a script tag with the type application/ld+json, in the head or the body of the page that shows the FAQ. Check that a plugin is not already adding a second FAQPage block.

  5. Test the finished page at validator.schema.org and fix any errors it reports, then test again.

  6. Read each question and answer in the code against the visible page. Make sure the wording, numbers and prices agree.

  7. Note in your content process that any edit to an FAQ answer needs an edit to the code in the same change. Better, generate the code from the same data as the page.

Your ticks are saved in this browser only.

Copy-ready templates

FAQPage JSON-LD (two questions)

json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does a repair take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most repairs take two working days. We confirm the date in writing before we start."
      }
    },
    {
      "@type": "Question",
      "name": "Do you offer a warranty?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Every repair carries a 90-day warranty on parts and labour."
      }
    }
  ]
}

Wrap this in a script tag with type application/ld+json. The sample facts are placeholders; use your own.

Matching visible HTML

html
<section>
  <h2>Frequently asked questions</h2>
  <h3>How long does a repair take?</h3>
  <p>Most repairs take two working days. We confirm the date in writing before we start.</p>
  <h3>Do you offer a warranty?</h3>
  <p>Yes. Every repair carries a 90-day warranty on parts and labour.</p>
</section>

The text must match the JSON-LD above word for word.

Quick check that a page contains FAQPage markup

bash
curl -s https://example.com/your-page | grep -Eo '"@type": *"FAQPage"' | wc -l

Replace the URL. A result of 1 or more means the pattern was found in the raw HTML. It misses markup written without that spacing, so also validate.

Does Google still show FAQ results?

No. Google's documentation changelog says the FAQ rich result would no longer appear in Google Search starting 7 May 2026, and on 15 June 2026 Google removed the FAQ documentation because the feature is no longer shown 4. Before that, a change dated 14 September 2023 had limited the feature to well-known, authoritative government and health sites 4.

Google's current structured data gallery, last updated 16 October 2026, lists 25 features. It does not list FAQ or How-to, though it does list Q&A for pages where people submit answers 5. Do not confuse the two. A page of your own questions and answers is an FAQ, not a Q&A page.

Is it still worth adding for AI search?

It is low-cost and harmless when done correctly, but we found no source showing it raises AI citations. Google's AI optimization guide, updated 10 July 2026, says structured data is not required for generative AI search and that no special schema.org markup is needed 6. Google's AI features page says the same about extra markup for AI Overviews and AI Mode 7.

So what remains? Three reasons, and the last two are our judgement rather than published findings. The markup forces you to write clean question-and-answer pairs. It gives other software that reads schema.org a clear signal. And it costs little if your site generates it from the same content as the page.

Skip it if it means hand-editing code on hundreds of pages. Spend that time on the answers themselves; see how to write content AI engines quote. The broader question is covered in what is schema markup.

What do you need, and how long does it take?

You need edit access to the page, five to eight real questions that already appear on it, and a way to add a script tag. A small site takes about 20 minutes per page; that is our estimate. Many content-management plugins can generate the code from your FAQ blocks; check yours.

The free Schema Generator builds FAQ JSON-LD from your questions, so you can paste the output instead of hand-writing it.

Why must the markup match the visible page?

Because Google's structured data policies require markup to be a true representation of the page content and say not to mark up content that is not visible to readers 8. A manual action for a structured data problem removes rich result eligibility without changing web ranking 8, but a mismatch is still poor practice and invites a clean-up later.

Keep the questions word for word the same in the page and the code. If an answer in the code is shorter than on the page, make sure the code still states the same fact. Do not put promotional claims in the code that the page does not make.

What makes a good FAQ in the first place?

Use questions customers actually ask, not questions you wish they asked. Pull them from sales calls and support emails; our guide to finding the questions people ask shows how.

Put the answer in the first sentence and keep each reply to about 20 to 90 words. A reply that stands alone is easier for a person to scan and for an AI to quote. Avoid vague answers like 'it depends' without saying on what.

Weak versus strong FAQ answer
  • Weak: 'Pricing varies, so get in touch for details.'
  • Strong: 'Our standard repair costs $120 for parts up to $40, and we quote larger jobs in writing before starting. Call-out is free within 10 miles.'
  • Why it is better: it gives the number, the condition and the next step in two sentences. (Illustrative example; use your own prices.)

What goes wrong with FAQ markup?

The usual errors are marking up questions hidden in collapsed sections that do not load into the page source, repeating the same FAQ block on every page, putting links or ads inside answers, and leaving a plugin's default FAQ block active next to your own code so the page carries two FAQPage items.

Another is broken JSON: a missing comma, curly quotes or an unescaped double quote inside an answer. Validate every time you change the text. Last, do not add FAQ schema as a substitute for a real answer on the page.

How do you check it worked?

Run the page through the Schema Markup Validator at validator.schema.org. A clean result means the JSON parses and the types are real schema.org ones; it says nothing about whether your answers are good. Then open the page in a browser and confirm every question in the code is on screen, including any inside accordions.

Do not expect a change in search results. With the FAQ rich result gone, there is nothing to look for in Google. Pair the validation with a monthly look at how the page performs in your AI visibility tracker.

When should you skip FAQ schema?

Leave it out when the page has no genuine FAQ, when every page would need hand-written code, or when basics such as crawl access and clear answers are still missing. Check whether AI bots can crawl your site first.

If you do the work, a related page type is worth the same care: see how to add HowTo schema and how to add Organization and Person schema, which describe who you are.

Frequently asked questions

Does FAQ schema still help SEO?

Not with a visible Google reward. The FAQ rich result stopped appearing from 7 May 2026 4, and Google says no special markup is needed for AI features 6. It remains valid structured data, and we found no study proving a ranking or citation benefit.

Should I remove existing FAQ schema?

You do not have to. Valid markup that matches the page does no harm. Remove it if it no longer matches the content, or if maintaining it takes time better spent elsewhere. Check that every question in the code still appears on the page.

Is FAQ schema the same as Q&A schema?

No. Google's gallery lists Q&A for pages where users submit answers to a question 5. A page of your own fixed questions and answers is an FAQ. Use the type that matches the page you actually have.

Can I use JSON-LD generated by a plugin?

Yes, if it matches your visible text. Google recommends JSON-LD where possible 2. Always validate a plugin's output, because defaults can include questions you removed from the page.

How many questions should an FAQ have?

Five to eight real ones is plenty. More questions rarely help and make errors likelier. Choose questions customers ask often, answer each in the first sentence, and keep the page focused on one topic.

About the author

Rahil Jain

Rahil Jain is an AI SEO (answer engine and generative engine optimisation) consultant and co-founder of Chalk Labs.

LinkedIn · Method and credentials

Sources

  1. FAQPage · Schema.orgOpened October 20, 2026. Supports: FAQPage is defined as a WebPage presenting one or more frequently asked questions; the page lists no FAQ-specific required properties.
  2. Introduction to structured data markup in Google Search · Google Search CentralOpened October 20, 2026. Supports: Google generally recommends JSON-LD where site setup allows; structured data must describe visible content; Rich Results Test and status reports exist for rich result features.
  3. Question · Schema.orgOpened October 20, 2026. Supports: Question is a specific question, such as one collected in an FAQ document; acceptedAnswer takes an Answer.
  4. Search Central documentation updates · Google Search CentralOpened October 20, 2026. Supports: FAQ rich result deprecation notice (8 May 2026) with effect from 7 May 2026; documentation removed 15 June 2026; 14 September 2023 change limiting FAQ results to well-known government and health sites and removing How-to documentation.
  5. Structured data markup that Google Search supports · Google Search CentralOpened October 20, 2026. Supports: Gallery last updated 2026-10-16 lists 25 features; FAQ and How-to are not listed; Q&A is listed.
  6. Optimizing your website for generative AI features on Google Search · Google Search CentralOpened October 20, 2026. Supports: Structured data is not required for generative AI search and no special schema.org markup is needed; page updated 2026-07-10.
  7. AI features and your website · Google Search CentralOpened October 20, 2026. Supports: No additional requirements to appear in AI Overviews or AI Mode; structured data should match the visible text; last updated 2025-12-10.
  8. General structured data guidelines · Google Search CentralOpened October 20, 2026. Supports: Markup must be a true representation of the page; do not mark up content not visible to readers; manual action removes rich result eligibility without affecting web ranking.
How this page was made. Built on Rahil Jain's AI SEO method and drafted with AI research assistance. Every statistic links to the page we read it on (opened October 20, 2026 or nearby). Published October 20, 2026; last updated October 20, 2026. Chalk Labs sells AI SEO services, so we have a commercial interest in this topic. Spotted an error? Tell us and we will fix it.