one faq page vs. many: which is better for seo?

the standard advice for years has been: build one faq page, list eight to ten common questions, wrap it in faq structured data, done. it's tidy, it's easy to maintain, and for a lot of small sites, it quietly underperforms — especially while the site is still building authority.

the problem with one page, many questions

a single page answering ten unrelated questions is, from google's perspective, a page about ten different things at once. when someone searches one of those specific questions, google has to decide whether this page is really "about" that particular question or just mentions it in passing among nine others. that ambiguity works against you.

split each question onto its own page, and there's no ambiguity left. the url, the title, the h1, and the content are all pointing at exactly one topic. there's nothing else on the page competing for relevance. that focus is what makes a narrow, specific page easier to rank than a slice of a larger, general one — even without any structured data at all, because the page's structure alone already makes the topic unmistakable. the same narrow-beats-broad logic applies to the url itself: a focused slug reinforces a focused page.

this doesn't mean every answer needs to be long

the instinct once you decide to split questions into separate pages is to pad each one out to justify having its own url. that's unnecessary and can backfire — a short, direct, accurate answer to a specific question is a completely legitimate page on its own. length isn't the signal that matters here; focus is.

a plumbing company doesn't need 800 words to answer "how much does it cost to reroute a drain pipe in ottawa." three well-written paragraphs with a real answer, maybe a price range, and a clear next step is a complete, rankable page — see put the answer above the fold for why leading with the direct answer matters even more on a page like this.

when a combined faq page still makes sense

this isn't an argument to delete every faq section. a general faq page still has value as a hub — a place someone lands after they've already decided to work with you and just wants quick reference answers to secondary questions (return policy, hours, payment methods). that page serves an existing visitor, not a search query trying to find you in the first place.

the split-page approach is specifically for questions that are themselves high-value search queries — things people are actually typing into google before they've heard of your business. those are the ones worth promoting to their own url.

how to decide which questions deserve their own page

• pull the questions from your general faq page that also show up, close to verbatim, in google's "people also ask" boxes or in your own customer emails.
• check whether that exact phrase has meaningful search volume on its own.
• if yes, give it a dedicated page with a title and slug that match the question closely, and link to it from your main faq page and any related service pages.
• leave the lower-value, purely internal questions ("what forms of payment do you accept") on the general faq page where they belong.

the takeaway

one faq page trying to cover everything dilutes itself across every question on it. a handful of focused, single-question pages, reserved for the questions people are actually searching, tend to do the actual seo work — while the general faq page stays useful as a reference hub for people who've already found you.

nanushi helps small businesses restructure content like this without a full site rebuild. if your faq page is buried and not showing up for anything, we can help you figure out which questions are worth splitting out.