FAQ Schema Markup: How to Add It, When It Helps and What Google Now Shows

Quick answer

FAQ schema is structured data that labels questions and answers on a page so machines can read them. Google now shows FAQ rich results only for a few authoritative sites, but marking up genuine FAQs still helps search engines and AI tools understand your content and can support voice and AI answers.

Last updated: November 2026

Few SEO tactics have changed as much as FAQ schema. A few years ago, adding it could earn extra space in search results with expandable questions beneath your listing. Then Google cut back how often these rich results appear, and many sites removed their FAQs altogether.

That was a mistake for most businesses. Well-written FAQs remain one of the best ways to capture long-tail questions, answer customers and give AI systems clean, quotable content.

This guide explains what FAQ schema is, what Google currently does with it, how to write FAQs that are worth marking up, how to add the code in WordPress, and how to test it.

What FAQ schema is

Schema markup is code, usually in JSON-LD format, that describes the content of a page in a way machines can understand. FAQPage schema tells a search engine that a page contains a list of questions and the answers to them.

The code does not change how the page looks. It sits in the background and says: this text is a question, and this text is its accepted answer. That makes the content easier to extract for features such as rich results, voice assistants and AI-generated summaries.

What Google shows today

In 2023 Google reduced the visibility of FAQ rich results, limiting them to well-known, authoritative government and health sites. For most businesses, an FAQ listing will not appear as an expandable result in Google search any more.

However, the structured data is not harmful, and valid markup can still be used by other search engines, assistants and AI tools. Google continues to recommend marking up content that is genuinely on the page. So treat schema as a helpful signal, not a guaranteed visual reward.

Why FAQs are still worth publishing

They answer real customer questions, which reduces enquiries that stall because of uncertainty.
They capture long-tail searches phrased as questions, including People Also Ask style queries.
They give AI Overviews and chat assistants concise, self-contained answers to quote.
They support voice search, where users ask natural questions.
They let you address objections such as price, timescales and risk on the pages that convert.

How to write FAQs worth marking up

Source questions from real life: sales calls, emails, live chat, Google Search Console queries, People Also Ask and reviews. Avoid inventing questions just to hit a keyword.

Answer directly in the first sentence, then add context in one or two further sentences. Keep each answer between 40 and 80 words where possible. Be specific and accurate, including real numbers and conditions, and avoid sales language.

How to add FAQ schema in WordPress

There are three main routes. Many SEO plugins such as Yoast and Rank Math include FAQ blocks for the block editor that output valid markup automatically. Elementor users can use an FAQ or accordion widget that generates schema, or add a JSON-LD script in an HTML widget. For a custom approach, a developer can add the markup in the page template.

Whichever route you use, the markup must match the visible text. Never add questions and answers to schema that are hidden or do not appear on the page, as this breaches Google guidelines and can lead to structured data issues.

Example FAQs for a UK service business

A strong FAQ section for a boiler servicing company might include: “How much does a boiler service cost?” with a clear range and what is included, “How long does a service take?” with a typical duration, “Do I need a Gas Safe registered engineer?” with a plain explanation of the legal requirement, and “How often should my boiler be serviced?” with the usual annual recommendation.

Each answer opens with the direct answer, adds one useful detail such as what the engineer checks, and ends with a gentle pointer, such as a link to a booking page. That structure works for humans scanning the page and for machines looking for a clean, quotable response.

For an accountancy firm, the equivalent questions might be about fees, deadlines, switching accountants and what records to keep. For an e-commerce store, they would cover delivery times, returns and sizing.

The key point is that these are all genuine concerns that stop people from buying or enquiring. Answering them well improves conversion, supports SEO and gives AI assistants accurate, quotable information about your business.

When you update prices or services, update the FAQ text and the schema together. Out-of-date answers in structured data are an easy way to lose trust, so build a small review step into your regular website maintenance.

A simple FAQ schema example

A minimal block of JSON-LD for two questions looks like this in concept: a FAQPage containing a mainEntity list, where each item is a Question with a name and an acceptedAnswer containing a text field. You paste it into a script tag of type application/ld+json. Most plugins create this for you, which is the safer option for non-developers.

After adding it, check that the plain text of each answer is clean. HTML such as links and lists is allowed in answers, but keep it simple, and make sure the final text reads well if extracted on its own.

How to test and monitor your markup

Use Google’s Rich Results Test to confirm the page is eligible and the markup is valid.
Use the Schema Markup Validator for general structured data checks.
Check the Enhancements report in Google Search Console for errors or warnings.
Re-test after theme, plugin or page builder updates.
Monitor Search Console for impressions on question-style queries.

Where to add FAQs on a business website

Service pages: price, timescales, process and what is included.
Location pages: local questions, areas covered and travel.
Product and category pages: delivery, returns, sizing and compatibility.
Pricing pages: what is included, contracts and payment options.
Blog posts: related questions at the end of each article.

Mistakes to avoid

Using FAQ schema for promotional content, such as lists of offers disguised as questions.
Duplicating the same FAQs across many pages.
Marking up questions that visitors cannot see.
Writing very long answers that are hard to quote.
Forgetting to update answers when prices or processes change.

Done properly, FAQs are among the lowest-cost, highest-value additions you can make to your key pages.

A quick implementation checklist

Collect the real questions your customers ask.
Write concise, accurate answers.
Add them visibly to the page.
Generate matching FAQPage schema using your plugin or page builder.
Test with the Rich Results Test.
Review every six months and update.

Technical SEO Services

Crawling, indexing, speed and schema fixed properly.

Learn more Get an instant quote

Frequently asked questions

Does FAQ schema still work in 2026?

The markup is valid and useful for machine understanding, but Google rarely displays FAQ rich results for ordinary business sites. The real value is clearer content for search engines, assistants and customers.

How many FAQs should a page have?

Between five and eight genuine questions is usually enough. Quality and relevance matter more than quantity.

Can I use FAQ schema on every page?

Only on pages that genuinely contain a list of questions and answers visible to users. Do not add it as a blanket tactic.

Is FAQ schema the same as HowTo schema?

No. FAQ schema marks up questions and answers. HowTo schema marked up step-by-step instructions, and Google has also reduced its visibility.