Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

On-page SEO · 17 Nov 2026 · 7 min read

FAQ SEO: real questions, good answers and markup

An FAQ section helps a page when it answers questions your customers really ask. It does not work as a place to hide extra keywords.

The short answer

FAQ sections help readers, and that is where the SEO value comes from. Write real customer questions, answer each in a few self contained sentences, and keep the markup in line with the visible text. Google has limited FAQ rich results to a small set of sites, so do not count on a special display.

Do FAQ sections help SEO?

Indirectly, yes, and mostly through the reader. A page that answers the follow up questions a visitor would otherwise search for separately keeps that visitor on the page and lowers the chance they go back to the results. Questions phrased the way customers speak also help a page match the wording of longer searches. There is no setting or markup that makes an FAQ rank higher on its own.

For faq seo, the useful way to think is this: each question and answer is a small, quotable unit. Search engines and AI assistants often lift a short, direct answer from a page to respond to a query. An answer that starts with the fact and stands alone, without needing the paragraphs around it, is easier to quote correctly.

What does not work is writing an FAQ for search engines instead of people. Lists of questions nobody asked, repeated with minor changes, add length and no value. Google's guidance for several years has been to write for readers first, and a padded FAQ is a visible sign of the opposite.

Where good questions come from

Your own business already holds the best list. Start there before opening any tool.

  • Sales and support messages. Read the last fifty emails or chat transcripts and note which questions repeat. Repeated questions are the ones worth a place on the page.
  • Phone and in person conversations. Ask whoever answers the phone what they explain most often.
  • Objections raised before a sale, such as how long a job takes or what is included. Your page should answer these before the visitor has to ask.
  • Search Console. The performance report shows queries that already bring impressions to a page. Questions among them, or near them, are strong candidates.
  • The People also ask boxes under a search result for your topic, which show how others phrase related questions.
  • Reviews and comments on your own pages and social posts.

Choose questions that suit the page. A service page should handle questions about scope, process and what to prepare. A product page should handle size, care, delivery and returns. A question that belongs on another page should be answered there, and linked from here. Questions about areas served, for instance, belong on location related pages; see local SEO for service area businesses.

Check that no question is answered in full elsewhere on the site. Two pages answering the same question in the same words is wasteful: a link works better than a copy, as the simple rules for internal linking explain.

How to write answers that stand alone

Each answer should make sense if someone reads only that block. Begin with the answer, then add the condition or detail. Two to four sentences is usually right. Longer answers belong in the body of the page, with the FAQ giving the short form.

Compare two answers to the same question. The first: "That depends on many factors and we would be happy to discuss your needs." The second: "It depends on the number of pages, if you need an online store, and how much copy and photography you provide. A written quote lists these so you can compare." The second tells the reader what decides the answer. The first tells them nothing.

Be honest about limits. If the answer is that it varies, say what it varies with. Avoid invented figures, and avoid promises about results you cannot control. If a rule differs by country, say so and point to the official source.

Write the question the way a customer would type it, in plain words, with no brand slogans. Use the full question in the heading or text, not a fragment. Keep the order logical: general questions first, then specific ones, then the questions about problems and refunds.

What FAQ markup needs

FAQ markup is structured data, usually written in JSON-LD, that labels a block of visible text as a list of questions with their answers. It uses the FAQPage type from schema.org. Each question is a Question item with a name, and each answer is an Answer item with text.

The rules that matter are simple to state. The questions and answers in the markup must appear on the page for visitors to read, in the same words or very close to them. Markup for content that is hidden or not on the page goes against Google's structured data guidelines. Each question should have one answer written by you, not a thread of user replies, because that is a different type. And the markup is for pages that really are lists of questions with answers from the site owner.

You can test the markup with Google's Rich Results Test, or the Schema Markup Validator, before publishing. Fix any errors it reports, such as missing fields, and check that the page text and markup match exactly after any later edit. A common fault is editing an answer in the page but leaving the old text in the markup.

Markup is not a ranking tool. It helps machines understand what the page contains, and that is the whole of its job.

What Google shows for FAQ markup now

Be careful here, because this has changed. Google used to display expandable question and answer lists under some search results. In 2023 it said it would limit that display to a small number of well known government and health sites, and it stopped showing it for most others. Check the current documentation on Google Search Central before you plan around any rich result, as these features change.

That does not make the markup pointless. Other search engines and tools may read it, the discipline of marking up real questions keeps a page tidy, and nothing suggests it harms a page that follows the guidelines. But do not promise anyone a special display as a reason to add it, and do not spend a large part of a project on it. The visible questions and answers are what carry the value.

The same idea applies to other markup. Structured data helps most when it describes something visitors can already see. Our guide on breadcrumbs and structured data follows the same rule.

Where to put the FAQ on a page

Place it near the end of the page, after the main content, under a plain heading such as the page topic followed by questions. Visitors who have read the page will use it to check details. Visitors who skip to it will find a fast summary.

Do not use accordions that hide the answers if they load content late or fail on slow connections. If you do use a collapsible layout, make sure the text is in the page source and works with a keyboard. Slow or heavy scripts for a simple list do not pay off; our guide on Core Web Vitals explains how page weight and scripts affect the experience.

Keep the list short: four to eight questions is plenty for most pages. If you have fifty questions, build a help section with a page per topic and link into it. A single page with a huge list is hard to scan and often drifts from the page's main purpose.

A review routine

Look at each FAQ twice a year. Remove answers that are out of date, add the questions that appeared in recent customer messages, and check that markup still matches the text. Look at Search Console for queries with impressions but few clicks, which may point to questions your page does not yet answer well.

A site-wide approach belongs in a wider plan. Our guide to an SEO strategy for a small business shows where FAQ work sits next to other tasks, and the search engine optimisation service page explains how Liftup Technologies can help review the questions on a set of pages.

Related guides

Questions and answers

Do FAQ sections help SEO?

They help when the questions are real and the answers are useful, because they keep readers on the page and match longer searches. FAQ markup alone does not raise rankings, and padded questions add length without value.

Where do good FAQ questions come from?

Start with customer emails, chats, calls and sales objections. Add queries from Search Console and the People also ask boxes for your topic. Choose questions that fit the page and answer each one in plain words.

What does FAQ markup need?

Use the FAQPage type with a Question and an Answer for each item. The text must also appear on the visible page, and each answer should come from the site owner. Test the markup before you publish.

Will FAQ schema give me a rich result in Google?

Probably not. Google has limited FAQ rich results to a small set of sites. Check the current documentation before relying on any special display.

How many FAQs should a page have?

Four to eight is plenty for most pages. If you have many more, build a help section with separate pages and link to them.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote