FAQ Page SEO: When FAQs Help and How to Write Them

FAQ content helps when it answers real questions that readers ask, in plain words, close to the decision they are making. Put page-level FAQs on pages where doubts block action, and keep a central FAQ page only for general questions. Do not add FAQ markup hoping for a rich result, because Google no longer shows it.

Pew Research Center found that Google users clicked a traditional search result in 8% of visits when an AI summary appeared, compared with 15% of visits when there was no AI summary, so answers must earn the visit by offering more than a snippet can.

FAQ sections are among the most over-used and under-thought-out parts of a website. Many are written to hit a keyword or fill a schema template, with questions nobody asked and answers that repeat the page above them. Done properly, they remove the doubts that stop a reader enquiring, and they give you a natural home for long-tail questions that do not justify a full article.

This guide covers where questions should come from, page-level versus central FAQ pages, how long answers should be, what has happened to FAQ structured data, and how to build accordions that everyone can use. It sits within the wider work of on-page optimisation, where every element of a page needs a job, and it supports a wider plan to build topical authority.

What FAQ content is actually for

An FAQ has three legitimate jobs.

1. Reduce hesitation. Price, timing, process, guarantees, eligibility: the practical questions that sit between interest and action.
2. Answer secondary queries. Questions closely related to the page topic that do not warrant their own page.
3. Reduce repeat enquiries. Support and sales teams answer the same things again and again. A good FAQ saves them time.

If a question does not do one of these, it probably does not belong. And if a question needs more than a paragraph, it probably deserves its own article. Decide using the same intent logic as any other page; my guide to search intent explains it.

Where to find questions worth answering

Invented questions produce weak FAQs. These sources produce real ones, roughly in order of value:

• Customer conversations: sales calls, WhatsApp messages, emails, consultation notes. The exact wording matters.
• Support tickets and live chat logs: repeated questions are the clearest signal.
• Google Search Console: look for query reports where the query is phrased as a question and impressions show a page is relevant but not fully answering it.
• Search suggestions and related questions on the results page: useful for wording and gaps, but treat as prompts, not truth.
• Reviews and forum threads: where people describe what confused or worried them.
• Your own sales objections: the awkward ones, such as “why is it more expensive than…” are often the most valuable.

Write the question in the reader’s words, not yours. “How long does it take?” beats “Project timeline overview”.

Page-level FAQs versus a central FAQ page

My rule: put the question where the doubt happens. A question about pricing belongs on the pricing or service page, not buried on a general page. Use a central page for questions that apply across the business, and link to it from the footer and from pages where relevant. If a question keeps growing, graduate it to a full article and link back; an article plan helps here, and a content brief keeps it focused.

Avoid duplicating the same answer on several pages. Write it once in the best place and link to it from the others, or rewrite it for each context. Copying identical blocks across a site creates the kind of repetitive content I describe in thin content in SEO.

How to write the answers

Start with the answer

Give the direct answer in the first sentence, then add the reasoning or exception. “Yes, most projects take four to six weeks, depending on how quickly content is approved” is better than a paragraph of context before the number. This helps readers who scan and any system extracting a summary.

Keep answers short, but complete

There is no ideal word count. Aim for one to four sentences for simple questions and a short paragraph for complex ones. If an answer needs a list, a table or a warning, it is probably a section, not an FAQ item.

Be specific

Vague answers (“it depends on many factors”) frustrate readers. State the factors. If you cannot give a price, give the range drivers. If the honest answer is “we do not do that”, say so and point to an alternative.

Do not hide important information

Costs, limitations, delivery terms and conditions should be visible on the main page, not available only inside a collapsed FAQ. The FAQ expands on information; it should not be the only place it lives.

Link, but sparingly

Link to a deeper page where it genuinely helps, such as a related guide or the service page. Do not turn every answer into a link farm.

FAQ structured data: what has changed

For some years, FAQ markup was used to try to win expanded results in Google. That has ended. Google’s Search Central updates log records that the FAQ rich result feature is no longer shown in Google Search results and that its documentation was removed in June 2026. Treat that as the current status, and check the page again before relying on this.

What this means in practice:

• Do not add FAQ markup in the hope of an expanded result. It will not show.
• Write FAQs for readers. The value is in the content, not in the markup.
• If your site or plugin already outputs FAQ markup, there is no need to rush to remove it, but do not spend time maintaining it. Check the status in Google’s documentation and your plugin’s notes.
• If your tracking showed visits from FAQ rich results in the past, expect that source to be gone, and review the pages on content quality instead.

This is a good example of why I avoid building a strategy on a single display feature. Features come and go; useful answers remain useful.

FAQs and AI-generated answers

Question-and-answer formats can suit answer engines because they are clearly structured. But the click behaviour above shows that a short answer alone may satisfy a searcher without a visit. So write answers that are accurate and clear, and make sure the page offers something a summary cannot: examples, evidence, tools, a next step. Answer engines are a wider subject; the point here is only that an FAQ should add value beyond the snippet.

Build accessible accordions

Collapsible FAQ sections are common and not always usable. If you use them:

• Make each question a real button inside a heading, so keyboard and screen reader users can find and operate it. The W3C’s accordion pattern describes this structure, with Enter or Space expanding a collapsed panel and an aria-expanded state showing whether it is open.
• Do not rely on hover or on small icons alone to signal that something can be opened.
• Consider leaving short FAQ lists fully expanded. With four or five questions, an accordion adds clicks without saving space.
• Ensure content inside collapsed panels is still in the page for crawlers and can be read when printing or using a reader mode.
• Test with keyboard only: tab to each question, press Enter, and check that focus remains sensible.

Often the simplest approach, plain headings and paragraphs as I use at the end of this post, is the most accessible and the easiest to maintain.

A practical process

1. Collect twenty to thirty real questions from conversations, Search Console and support logs.
2. Group them by page: which page is the reader on when they ask this?
3. Pick the three to six that remove the most doubt for each page and drop the rest or plan articles for them.
4. Write answer-first responses and check each against facts, prices and policies.
5. Place them near the end of the page, after the main content, under a clear heading.
6. Review every quarter. Remove outdated answers and add new questions from the latest conversations.

If you are planning supporting content for a broad topic, FAQs can also be a feeder for new articles. A pillar page often ends with questions that link to deeper cluster posts, and an SEO content calendar is a good place to schedule those promoted questions.

Questions people ask about FAQ pages

If you want to see which questions your pages should be answering and where your current FAQs are wasting space, ask for a free audit and I will review them with you.

More in this series (Content strategy and writing): start with Topical Authority: The Ultimate Guide to Dominating Your Niche, then explore:

• How to Write an SEO Content Brief (Free Template Structure)
• Pillar Pages: How to Plan and Write One That Ranks
• Comparison Pages: How to Write X vs Y Content That Ranks