FAQ Sections: Adding Value and Capturing SERP Features

Short answer

An FAQ section earns its place by answering questions real readers have that the rest of the page doesn't. The search feature it used to be built for is gone: Google limited FAQ rich results to well-known government and health websites in August 2023 and stopped showing them on May 7, 2026, so FAQ markup no longer produces anything in Google Search. What a good FAQ section can still do in search is supply clear question-and-answer passages that Google may use in featured snippets or "People Also Ask", which it chooses on its own. Build the section for readers first; any search feature is a by-product.

Sources

Ask next

What Changed for FAQ Markup

The full history is in FAQ schema. For an FAQ section today, three points matter:

No FAQ rich result. Adding FAQPage markup won’t expand your listing.
No FAQ report. Search Console’s rich result reports list the types it supports, from Breadcrumbs to Videos, and FAQ isn’t among them.
User answers are different. A page where visitors answer one question is a Q&A page, with its own markup; see user-generated content.

What an FAQ Section Can Still Do

Answer follow-up questions a reader would otherwise search for or ask support.
Address objections on product and service pages: returns, delivery, eligibility, what’s included.
Offer passages Google can quote. Google’s featured snippets documentation describes featured snippets as “special boxes where the format of a regular search result is reversed, showing the descriptive snippet first”, and says they “can also appear within a related questions group (also known as ‘People Also Ask’).” Asked how to mark a page as a featured snippet, Google answers: “You can’t.” See featured snippets and People Also Ask.

If the main content already answers a question, the FAQ shouldn’t repeat it. A repeated answer adds length, not information.

Finding Questions Worth Answering

Source	What it shows	Limit
Search Console Performance report	Question queries that already bring impressions to the page	Only queries the page already appears for
People Also Ask and autocomplete	Questions Google associates with the topic, on the day you look	May not fit the page's scope
Support tickets, chat and call notes	What customers actually ask after reading the site	Can be too specific for a public page
Sales questions	Objections before purchase	Commercial angle
Forums and social threads	How people phrase the problem themselves	Needs filtering
Competitor FAQs	What others answer	Copying their list doesn't add anything

In the Performance report, filter queries for words such as “how,” “what,” “why” and “can” to find questions the page is shown for but may not answer. Record the date when you note People Also Ask questions, since they change.

Writing the Answers

Answer in the first sentence. “Yes, you can return unused items within 30 days” works where a paragraph of background doesn’t. Use your own policy’s real terms.
Match length to the question. A yes-or-no question gets a short answer with its condition; a process gets steps or a link to the page that explains it.
Be specific and current. Put real numbers, dates and conditions in the answer, and review them when the underlying policy changes.
Use the reader’s words in the question and plain language in the answer.
Link out for depth. Answer the core question, then link to the full guide.
Skip promotional questions. “Why should I choose us?” isn’t a question readers ask in those words.
Keep the answer consistent with the page. An FAQ answer that’s broader, narrower or different from the main text can confuse readers and undermine the page.

Where to Put It

At the end of an article, for follow-up questions.
On product and service pages, for purchase questions.
On a dedicated help page, grouped by topic, when there are many questions across the site.
Near the section it relates to, when a question only arises at one point.

Don’t place an FAQ block above the main content on a page people visit for that content.

Expandable Answers

Accordions keep a long list scannable, but they hide the answers until clicked. Google’s snippet documentation says that for “read more” deep links to a section, content should be “immediately visible on the page to a human (and not hidden behind an expandable section or tabbed interface, for example)”. If a few answers matter most, show them open, and collapse only a longer tail.

Should You Keep FAQ Markup?

FAQPage remains valid schema.org vocabulary, and other systems may read it, but it no longer produces a Google rich result. If you keep it, it must match the visible questions and answers; Google’s structured data policies say: “Don’t mark up content that is not visible to readers of the page.” Don’t add it to new pages expecting a search feature. Whether to remove existing markup is covered in what to do with FAQPage markup now.

Measuring Whether It Helps

Clicks on expandable questions, tracked as events, to see which questions readers open.
Queries in the Performance report that match your FAQ questions, before and after adding them.
Support contacts on the topics the FAQ covers, compared over the same periods.
Conversion on pages where the FAQ answers purchase objections, with care: other changes can explain a difference.

If readers don’t open a question and no query matches it, remove it.

FAQ Section Pitfalls

Adding an FAQ to every page by template.
Inventing questions to fit keywords; “What are the best running shoes for running shoe buyers who run?” isn’t how anyone asks.
Answers that say “Contact us for more information” and nothing else.
Repeating the main content in condensed form.
Copying People Also Ask questions that don’t fit the page.
Letting answers go out of date after a policy or price changes.
Adding FAQ markup for a rich result Google no longer shows.

Leave open the answers readers most need before deciding, and collapse only the longer tail; Google’s snippet documentation says content for “read more” links should be immediately visible, not hidden behind an expandable section.