FAQ Schema Generator

Google has retired FAQ rich results. Since May 7, 2026, the expandable question rows no longer appear under results in Google Search, for any site. The notice on Google’s FAQPage documentation said the FAQ search appearance, the FAQ rich result report and FAQ support in the Rich Results Test would be dropped in June 2026, followed by Search Console API support in August 2026.

That ended a long wind-down. In August 2023 Google limited FAQ rich results to well-known, authoritative government and health websites, so most sites had already lost them. If your FAQ dropdowns vanished from your listings in 2023, that was the reason, and the 2026 change only finished the job.

The markup itself is not deprecated. FAQPage, Question and Answer are still valid schema.org types, and Google’s line on structured data it doesn’t use has been consistent: it causes no problems for Search, it just has no visible effect. Nothing on your site is penalized for carrying it, and you don’t need to rip it out.

The generator turns each question-and-answer row into one Question inside a single FAQPage. The question goes in the Question’s name. The answer goes in acceptedAnswer, as an Answer with a text property. Rows keep the order you entered them in, and the whole block comes wrapped in its script tag, ready to paste.

It trims spaces from the start and end of every question and answer. A row with an empty question or an empty answer is left out of the output, so a half-finished row never produces a Question with no answer. If every row is empty, you get an FAQPage with an empty mainEntity list. That parses, but it describes nothing, so don’t paste it.

Text is passed through exactly as you type it. If you put HTML in an answer, such as a link, the output shows each less-than sign as \u003c. That is the escaped form of the same character. It stops your text from closing the script tag early, and every JSON parser reads it back as an ordinary tag, so leave it as it is.

It adds nothing else: no url or @id for the page, no inLanguage, no authors or dates. FAQPage never needed them, and Google’s FAQ guidelines never asked for them.

Be honest about the payoff. In Google Search, FAQPage markup now produces nothing you can see or measure. Other search engines and AI assistants can read schema.org markup, but none of them publishes FAQPage rules you can test against, so treat any benefit there as unproven. Google’s own guidance for AI Overviews says no special markup is needed to appear in them.

That leaves a short list of good reasons. Your SEO plugin or page builder adds the markup for free when you use its FAQ block, so it costs nothing. A template or a client expects it, and removing it would be more work than leaving it. Or you want a structured copy of the answers that stays tied to the visible text.

The FAQ content itself still earns its place, with or without markup. A visible section that answers the questions people actually search for gives the page more to rank for and gives visitors what they came for. Spend your time on the answers, not the JSON.

The rules Google applied to FAQ rich results are still the right rules for the content. Each question and its full answer must be visible on the page, even if the answer sits in a collapsed accordion the visitor can open. The answer is written by the site, not submitted by users. It answers the question instead of advertising something. And an FAQ repeated across many pages is marked up once, on the page that owns it.

Copy the question exactly as it appears in the heading or accordion title, then paste the answer as one block. If the page shows a bulleted list inside an answer, you can keep it as plain sentences or as simple HTML; both are valid. What you must not do is give the markup a longer or more persuasive answer than the visitor sees.

Phrase questions the way a customer would type them. "Shipping" is a heading. "How long does shipping to Canada take?" is a question someone searches for, and it forces a specific answer.

The right type depends on who writes the answers and how many questions the page is about. Getting it wrong describes the page falsely, which is the one thing structured data must not do.

First find out whether the page already has FAQ markup. Open the live page, view the source, and search for FAQPage. If it’s there, something on the site already prints it, and the generator’s block would be a second copy.

If you use the block editor with Yoast SEO, the Yoast FAQ block is the simplest route. You type each question and answer into the block, Yoast shows them on the page and adds them to the schema graph it already prints, marking the page as an FAQPage too. Rank Math’s equivalent is the FAQ by Rank Math block. SEOPress has an FAQ block in its free plugin. With any of these, the visible text and the markup come from the same field, so they can’t drift apart.

Use the generator when the FAQ is built some other way: a theme accordion, a page builder without a schema switch, or a page still in the classic editor. Paste the output into a Custom HTML block on the same page. WordPress only keeps script tags for users with the unfiltered_html capability: Administrators and Editors on a single site, and only Super Admins on multisite. If an Author pastes the block, WordPress strips the script tag when the post is saved, without a warning.

For pages you don’t edit in the block editor, a code snippets plugin that prints the block in the head of one specific page does the same job, and keeps the markup out of the content, where someone could delete it while editing the text.

Duplicate FAQ markup is the most common FAQ schema fault on WordPress sites, and it nearly always happens by accident. These are the usual combinations:

Now that Google no longer reports on FAQ markup, nothing flags two FAQPage items on one page, which makes them easy to miss. The fix hasn’t changed: choose one source for the page, turn the others off, and merge any questions that only one of them had.

Keep the source tied to the visible text. If the FAQ is a Yoast or Rank Math block, keep that block’s markup and delete the pasted one. If the FAQ is an accordion with no markup of its own, keep the generator’s block, and update it every time someone edits the accordion.

Since June 2026 the Rich Results Test no longer reports FAQ items, and Search Console has no FAQ report or FAQ filter in the Performance report. Don’t read an empty result there as a sign your markup is broken. Google stopped looking.

Use the Schema Markup Validator at validator.schema.org instead. Give it the live URL rather than the code you pasted, so you test what WordPress actually serves after caching and plugins. It parses everything schema.org defines and shows each item as a tree. Expand FAQPage and check three things: the number of Question items equals the number of questions on the page, each Question has an acceptedAnswer with text, and FAQPage appears only once.

To confirm Googlebot receives the block, use URL Inspection in Search Console, run a live test and view the tested page’s HTML. If the FAQPage block is in that HTML, Google got it. If you tracked FAQ clicks with the old search appearance filter, that series has ended; compare clicks for the page itself instead.

An illustrative case. A software company’s pricing page has six questions in an accordion built with the theme. Rank Math is installed, but the FAQ isn’t a Rank Math block, so Rank Math adds no FAQ markup. Two years ago someone pasted FAQ markup with eight questions into a footer widget, including two about a plan that has since been discontinued.

So the markup disagrees with the page on two questions, and because it lives in the footer, it prints on every page of the site, from the blog to the contact page. Both are real problems even with FAQ rich results gone, because the markup now describes content that isn’t there.

After the fix, the Schema Markup Validator shows a single FAQPage with six Question items on the pricing page, and no FAQ markup on any other page of the site.

Match what you see to the likely cause before changing anything. Most FAQ markup faults come from where the block was pasted, not from what is inside it.