How Many Questions Should an FAQ Page Have?

One thing has changed. FAQ rich results stopped appearing in Google Search on 7 May 2026, and Google removed the documentation on 15 June 2026. If you have been adding questions to win that expandable list under your result, the payoff is gone.

How many questions should an FAQ page have?

Towson University’s web guidelines suggest a limit of ten questions and recommend grouping related questions under headings if there are more. That is a useful house rule for its site, not a research finding that every FAQ stops working at eleven.

Two dated examples show how widely counts can differ. This article’s Stripe pricing and GitLab pricing source notes recorded 5 and 51 question entries respectively in their FAQPage markup on 23 September 2026. GitLab’s example used eleven topic headings. These are preserved historical observations, not a fresh count or proof that either number performs best.

The examples cover different buying questions. Stripe’s recorded list focused on payment fees, tax, refund fees and discounts; GitLab’s extended to licensing, usage and storage topics. Neither count alone tells you whether visitors found the answer. Use the examples to consider coverage and organization, not to select a target number.

Count your questions from real messages, not from a competitor page

Review a useful sample of support email, chat, DMs and call notes, such as the last 30 days. Include seasonal periods when relevant. Keep the customer’s wording, count repeated needs and separate meaningfully different questions. “Do you do same day?” needs a specific answer; it may sit alongside general delivery timing without requiring a near-duplicate FAQ entry.

1. Use recognizable customer language. Nielsen Norman Group recommends real concerns and visitors’ vocabulary. Group equivalent phrasings so you can write one clear answer rather than repeat it.
2. Prioritize frequency and consequence. Repeated questions are good candidates, but one report can reveal an important safety, accessibility or compatibility gap. Do not use “asked twice” as an automatic publication threshold.
3. Find the decision point. Put important fit, delivery or cancellation information on the page where people need it. A central FAQ can summarize and link to that answer.
4. Check gaps beyond your inbox. Search suggestions and related-question results can reveal possible needs, but do not measure their frequency or prove why someone never contacted you. The free Question Keyword Generator uses AI to draft ideas; it does not supply measured search volume. Validate useful ideas against real users and your product facts.

Do not pad it, and check you need it at all

Generating forty questions just to look thorough can bury the useful answers. Google’s scaled content abuse policy concerns many pages made primarily to manipulate rankings without helping users; it is not a forty-question limit or a ban on AI. On an individual FAQ, remove filler and duplicates because they make the page harder to use.

GOV.UK’s style guide tells its writers to avoid FAQs and start from user needs. That is GOV.UK’s content policy, not a universal ban. Its useful challenge is to check whether a repeated question points to missing information elsewhere. If people keep asking about delivery thresholds, improve the product, delivery or cart page too.

Fix the page where the question arises, which may mean rewriting unclear copy. Then use an FAQ where it provides a useful route to cross-cutting answers such as returns, data or support. Some small sites will not need a separate FAQ page at all.

Three checkpoints for reviewing an FAQ’s format

Question length, topic variety and the reader’s task matter as much as the total. Use the checkpoints below to prompt a usability review, not to force a redesign when a counter reaches a number. Ask a few representative readers to find specific answers on phone and desktop.

Around 10 questions: check whether a flat list still works

For short answers, clear headings in one column may be sufficient. If people struggle to locate a question, try an introductory question list with links to answers, or test an accordion. Nielsen Norman Group’s FAQ guidance recommends a question list followed by answers for shorter and medium-length FAQs. Its general-web reading research is not evidence for a ten-question breakpoint.

Around 25: review topic grouping

A longer list often benefits from meaningful topic headings and labelled jump links. Towson recommends grouping beyond ten questions; Nielsen Norman Group also supports topic chunks that readers can scan. Choose groups that make sense to your audience rather than forcing five questions into every category. The recorded GitLab example illustrates grouping; it does not establish a maximum count.

Around 40: consider whether a help centre would serve readers better

When answers become substantial, need screenshots, or are linked repeatedly from support, separate answer or topic pages may be easier to maintain and share. Nielsen Norman Group recommends that approach for longer or more involved FAQs. Categories and good search can help a larger collection, but forty is not a mandatory migration point and search should not replace useful navigation.

Accordion or a flat list?

Choose based on the task. Nielsen Norman Group’s accordion guidance favors visible content when people need most of it, and collapse when they need a few sections. An FAQ often fits the latter, but not always. Keep essential warnings or buying facts visible. Test the actual headings and interaction instead of making ten questions an automatic switch.

Native details with a summary provides a disclosure control without JavaScript. MDN explains that a shared name attribute groups controls so only one stays open. Omit that grouping if readers need to compare several answers, as NN/g recommends. For a custom accordion, follow the W3C pattern: a button in an appropriate heading, accurate aria-expanded and aria-controls, and keyboard operation. Native elements also need clear labels, visible focus and checks in your supported browsers and assistive technology.

Collapsed content can be eligible for indexing; it is not guaranteed to be indexed. Google’s mobile-first guidance allows equivalent content in accordions or tabs, but warns against loading primary content only after a click: Google does not interact to fetch it. Browser find-in-page is a separate concern. Chrome documents hidden="until-found" and beforematch for revealing custom hidden regions, with implementation and browser-support caveats. Test search, direct links, keyboard use and printing on your actual FAQ.

When a question deserves its own page instead

A question can deserve a dedicated answer page for any of these reasons; it does not have to pass all three:

• People need a direct link. Support, onboarding or internal navigation repeatedly sends people to this answer. Measured public search demand can be useful, but is not required.
• The answer needs room. Several paragraphs, steps, screenshots or exceptions may work better on a focused page. Towson suggests reconsidering complex, multi-paragraph FAQ answers. Four or five sentences is a review cue, not a limit.
• It is a substantial policy or task. Shipping, refunds, setup and warranty information may need a stable, maintained reference. Keep the key facts near the decision point too.

When you move an answer, leave a useful short response and descriptive link in the FAQ. Link the new page from relevant product or support pages. Include it in the sitemap if it is a canonical, indexable page you want in search; a sitemap is not a substitute for internal links. See which pages belong in a sitemap.

Where the FAQ block belongs: its own page, or the page that sells

A pricing or product page can carry a few answers to questions that arise there, while a central FAQ collects cross-cutting topics. Try three to five local questions as a drafting aid, not a quota; some pages need none or more. Keep a contact route for questions the page does not resolve. A 2017 HBR article reported 81% attempting self-service first. That historical figure does not prescribe today’s FAQ count.

Grigora’s pricing example in the article’s 23 September 2026 notes had 13 questions, including six Commerce topics. That is a historical editorial snapshot, not a current count. Some may help a plan comparison; others may work better beside Commerce details. The useful test is whether someone comparing plans can find what they need, rather than whether the count matches Stripe’s recorded five.

In Baymard’s 2017 product-page research, seller-authored FAQs and community Q&As helped with different needs. Test participants often found other users’ experiences more credible; its benchmark reported 55% without community Q&A and 70% without the recommended combination. Those are findings from that research, not a requirement for every small shop. Keep the seller’s verified essential facts prominent and moderate community answers. See how long a product description should be for organizing the full product information.

Schema markup, after Google switched FAQ rich results off

Google’s own records establish three useful dates:

• 8 August 2023. Google restricted regular FAQ rich-result display to well-known, authoritative government and health websites.
• 7 May 2026. The 8 May changelog entry says the feature would no longer appear in Search starting on 7 May.
• 15 June 2026. The same primary changelog records removal of the FAQ rich-result documentation because the feature was no longer shown. The former FAQPage guide redirects there.

FAQPage remains a Schema.org type for a page with frequently asked questions. That does not automatically make every JSON-LD block valid or mean a search engine uses it. Google’s 2023 post said unused structured data did not need proactive removal solely because it was unused. Keep any retained markup accurate and consistent with the visible questions; fix or remove misleading or broken markup.

Write answers for readers rather than an obsolete Google result format. If you retain structured data for your own content system or another documented consumer, the free FAQ Schema Generator creates FAQPage JSON-LD from complete question-and-answer pairs. Validate the output with Schema.org’s validator; that checks vocabulary and syntax, not factual accuracy or search visibility. FAQ markup does not guarantee rankings or AI citations.

Build the page

The free FAQ Page Generator turns your questions into an HTML and CSS block using one of six templates. Its native details and summary exports need no JavaScript for opening and closing. Load both HTML and CSS, check your site’s inherited styles, and test keyboard focus and phone layout. Link the FAQ from the pages that raise the questions.

On a classic template site, use a Custom HTML block for an export or the editor’s FAQ block where available. On a site made with Grigora’s AI builder, request an FAQ section and review its wording and behavior. Commerce settings and FAQ prose still need to agree: do not assume changing a shipping setting automatically rewrites an answer. Check the published page after updating either.

Review the list, cut it, and date it

An FAQ can become inaccurate when products or policies change. Assign an owner and update affected answers when a change goes live. Check related product pages and support guidance at the same time so customers do not receive conflicting answers.

A quarterly review is a practical starting schedule, with faster checks for changing policies. Review low-use entries before removing them; a seasonal question or an important rare issue may still belong. Merge duplicates, retire obsolete answers and add supported new needs. Display a review date only after actually checking the information. Include this in your routine to update a website.

FAQ page FAQs