FAQ Schema and How to Add It and What It Does Now

FAQ schema is structured data that labels the questions and answers on a page so search engines can read them as an FAQ. Google stopped showing FAQ rich results in Google Search on May 7, 2026, so adding it no longer earns the expandable answers under your listing.

This guide is for owners and marketers who have an FAQ page, or are told to add one, and want to know whether FAQ schema markup is still worth the work.

It shows exactly what Google documented, how to add the markup correctly in JSON-LD, how to test it, and what it can still do for your site.

The short answer: add FAQ schema only if the questions are already visible on the page and you can maintain it cheaply. Expect no visible change in Google Search. Do not rip out existing markup, because Google says unused structured data causes no problems.

FAQ schema labels questions and answers so search engines can read them

An FAQ page lists questions with one answer each. FAQ schema, which schema.org calls FAQPage, is the markup that tells search engines this page is exactly that.

Schema.org defines a FAQPage as a web page presenting one or more “Frequently asked questions” (Schema.org). Inside it sit Question items, and each Question holds an accepted Answer.

The words on the page do not change. The markup is a label, a second copy of the same content in a form a machine can parse without reading your design.

Google supports three formats for structured data: JSON-LD, Microdata and RDFa. Google recommends JSON-LD, and it is the format used for the example below (Google Search Central).

For background on how this fits into the wider picture, see our guide to schema markup for AI search.

Google stopped showing FAQ rich results on May 7, 2026

This is the part most guides on the results page still get wrong, so it is worth reading the dates from Google’s own changelog.

On May 8, 2026, Google added a deprecation notice to its FAQ rich result documentation. The notice says the feature will no longer appear in Google Search starting May 7, 2026.

On June 15, 2026, Google removed the documentation and stated that the FAQ rich result is no longer shown in Search results (Google Search Central updates).

The decline began earlier. In August 2023, Google announced it was reducing the visibility of FAQ rich results. From then on, they were shown only for well-known, authoritative government and health websites. For all other sites, the rich result was no longer shown regularly (Google Search Central Blog).

So there are two stages. For most sites, the expandable answers disappeared in 2023. For the government and health sites that kept them, they ended in May 2026.

The same changelog shows this is a pattern. Google has also removed documentation for other structured data types that are no longer shown in Search, including practice problems in January 2026 (Google Search Central updates).

What Google’s FAQ rich result rules required before it ended

Google’s old FAQ documentation is gone from its site, but an archived copy from April 2, 2026 records the rules. They still matter, because they describe what a correct FAQ page looks like and the same logic runs through Google’s general structured data guidelines (Archived Google FAQ documentation).

The documented limits were:

• Only for well-known, authoritative government or health sites. Rich results were limited to these sites, on desktop and mobile, in every country and language.
• One answer per question. FAQPage was for pages with a single answer to each question. If users can submit alternative answers, the documentation said to use QAPage instead.
• No advertising. Google said not to use FAQPage for advertising purposes.
• Full text. Each Question had to include the entire text of the question, and each Answer the entire text of the answer.
• Visible content. All FAQ content had to be visible to the user on the page. An answer hidden behind an expandable section counted as visible. Content users could not find at all did not.
• No repeats. If the same question and answer appeared on several pages, only one instance was to be marked up for the entire site.
• Content rules. Obscene, profane, sexually explicit, graphically violent, hateful or harassing content, or content promoting dangerous or illegal activities, might not be shown.

Three properties were required: mainEntity on the FAQPage, then name and acceptedAnswer on every Question, and text on every Answer.

Google’s general guidelines add that you should not mark up content that is not visible to readers of the page. They also say that using structured data enables a feature to be present but does not guarantee it will be (Google Search Central).

How to implement FAQ schema in five steps

If you still want to use FAQ schema, the process is short. It works the same way on a single page of a hand-built site, in a content management system or in WordPress with an SEO plugin.

1. Write questions people really ask

Start with the questions your customers send you by email, ask on calls or type into your site search. Keep each question as people phrase it, and answer it fully in a few sentences.

Aim for helpful answers, not keyword lists. Four to eight questions on a page is plenty, and each should have one answer only.

2. Put the FAQ content on the page

Add the questions and answers as visible text, in a plain list or a collapsible menu. A collapsible menu is fine as long as the reader can open it.

The markup in the next step must match this text exactly. A page with no visible FAQ content and FAQ markup is the clearest way to break Google’s guidelines.

3. Create FAQ schema in JSON-LD

Place a script tag with the FAQPage code in the page. This is a small, invented example for a lodge:

“` <script type=”application/ld+json”> { “@context”: “https://schema.org”, “@type”: “FAQPage”, “mainEntity”: [{ “@type”: “Question”, “name”: “What time is check-in?”, “acceptedAnswer”: { “@type”: “Answer”, “text”: “Check-in opens at 2 p.m.” } }] } </script> “`

Add one more Question object inside mainEntity for each extra question. Use one FAQPage per page. The answer text may contain simple HTML such as links and lists.

If you use a content management system, an SEO plugin can generate this from a block. Check that the plugin output matches the visible text before you publish.

4. Test the markup in Google’s Rich Results Test

Run the page through Google’s Rich Results Test and the Schema Markup Validator. Run both, since a second tool can catch syntax errors the first one does not flag. Double check that every question and answer in the structured data markup also appears on the page.

Do not expect the Rich Results Test to promise a FAQ result. Google no longer shows one, so a clean test confirms syntax only.

5. Check the live page and monitor it

After you publish, inspect the live URL in Search Console with the URL Inspection tool. Confirm that Google can fetch the page and that robots.txt or a noindex tag does not block it.

Google’s guidelines say not to block pages that carry structured data. Recheck the markup after any template change, because a redesign can silently drop it.

What FAQ schema can still do after rich results ended

Google’s own statements set the limits, and they are narrow.

It still describes the page. Google calls structured data a standardized format for providing information about a page and classifying its content (Google Search Central). An FAQ page marked up correctly is easier for a machine to read.

It causes no harm if you leave it. Google said in 2023 that you can drop this structured data but there is no need to proactively remove it. Structured data that is not used does not cause problems for Search, and it has no visible effect in Google Search (Google Search Central Blog).

It does not unlock AI answers. Google’s guide to AI features says you do not need to create new machine readable files, AI text files or markup to appear in them. It also says there is no special schema.org structured data to add (Google Search Central).

Google’s guide to generative AI search names overfocusing on structured data as a mistake. It still calls structured data a good idea within an overall SEO strategy (Google Search Central).

Other search engines are a separate question. We opened no documentation from other search engines that promises a result from FAQ markup, so we make no claim about them.

The honest value of an FAQ section is the content itself. Clear questions with direct answers help readers, and they are the kind of passage an answer engine can quote. Whether markup improves that is not documented, and we say so plainly.

If AI answers are your goal, our guide on how to run an AI citation audit shows how to see whether your pages are being cited at all.

Mistakes that make FAQ schema wrong

Most problems come from copying FAQ schema markup without the discipline behind it.

Marking up content that is not on the page. Hidden questions that readers cannot find break Google’s rule on visible content. Fix it by showing the text or removing the markup.

Using FAQPage for a forum or product support page. If users can submit alternative answers to a single question, or submit multiple questions on the same page, the correct type is QAPage, so apply QAPage markup instead. Google’s QAPage documentation covers that case (Google Search Central).

Writing questions as advertising. A question that is really a sales pitch is not an FAQ. Keep answers useful on their own.

Repeating the same FAQ across the entire site. Mark it up once, with only one answer per question, not on every page.

Treating it as a ranking tactic. Google describes no ranking boost from FAQ schema. Better returns come from fixing the basics in a technical SEO audit.

A good FAQ page still helps readers and search visibility

Take the markup away and the FAQ page remains. Answers that sit in one place give readers a better user experience, because they find what they need without a call or an email.

Answer common questions in plain words, and put the most useful information first. That serves search visibility more than the code does, since search engines still read the visible text.

You will see older guides call the expandable answers rich snippets and promise more traffic from them. Do not plan around that promise. Use FAQ schema as housekeeping, not as the strategy.

Where FAQ schema fits in a wider plan for being found

FAQ markup is a small piece of a larger job. The pages Google can crawl, the answers it can quote and the organization it can identify matter far more than any one type of markup.

Start with the pages that answer the questions your buyers ask. Then make sure search engines can fetch them. Our overview of how AI search changes SEO and what GEO is set out the bigger picture.

If you want the thinking behind being found when AI answers first, read When AI Answers First. Our distribution strategy service covers this work for businesses in Southern Africa. Ground Truth, our weekly newsletter on Wednesdays, covers changes like this one as they happen: subscribe here.

FAQ