Which Questions Deserve Their Own Page, and Which Belong in a Section

A question deserves its own page when the person asking it wants something materially different from the person asking the parent question, and when the full answer would not fit as a paragraph without crowding out everything else. Everything else is a section, a sentence, or nothing. Most sites get this backwards: they spin up a thin page for every phrasing a keyword tool spits out, then wonder why none of them rank and the site feels like a help centre nobody asked for.

The test below has held up across a lot of content plans.

Where the questions come from, and what each source is telling you

Four places give you most of the raw material, and they are not equal.

People Also Ask boxes show what Google thinks is adjacent to the query you typed. They are useful for finding the second and third thing a reader will wonder about, less useful for judging demand, because the same handful of questions tends to appear across many related searches.

Forum threads, especially Reddit and niche communities, show how real people describe the problem before they know the vocabulary. The phrasing is messy and the questions are often compound ("is X worth it or should I just do Y"), which is exactly the kind of question a well-written section can answer and a keyword page cannot.

Your own inbox and phone calls are the most honest source. The question a customer asks three times a week is one you should answer in writing, whether or not any tool shows volume for it.

AI assistants add a fourth. Ask ChatGPT or Gemini your core question and look at the follow-ups it offers, or at the sub-questions it visibly searched for. Google describes this expansion as query fan-out: one question becomes several related searches. Those related searches are a decent map of what a complete answer needs to cover.

Collect all of it into one list before deciding anything. The decision is easier when you can see the whole shape of the topic.

The three-part test

For each question, ask three things.

Does the asker want a different outcome? "How much does a kitchen extension cost" and "do I need planning permission for a kitchen extension" come from the same person at different moments, but they want different things: a number versus a yes-or-no with conditions. Different outcome, probably separate pages. "How much does a kitchen extension cost" and "kitchen extension price" want the same thing, so they are one page, full stop.

Would the complete answer overwhelm the parent page? Planning permission for extensions is a topic with rules, exceptions and regional differences. Answering it properly inside the cost page would hijack that page. Give it its own home and link between the two. "Do I need to move out during the work" can be answered honestly in a paragraph, so it stays a section.

Would anyone arrive at this page directly and be satisfied? Picture someone landing on the page from a search with no other context. If the page only makes sense as a footnote to something else, it is a section pretending to be a page.

Two yeses out of three and you have a page. One or none and you have a section, which is the right answer far more often than keyword tools suggest.

Why the section usually wins

Google's guide to generative AI features is unusually direct here. It says there is no requirement to break content into small pieces, that its systems can understand several topics on one page and show the relevant piece, and that creating separate content for every variation of a question, including fan-out queries, "primarily to manipulate rankings" falls under its scaled content abuse spam policy. It also notes the obvious: a high quantity of pages does not make a site more relevant.

There is a reader-side reason too. A good section sits inside context. The person reading about extension costs gets the planning permission summary where they need it, with a link to the full page if they want it. A thin standalone page gives them a 200-word answer and a dead end.

And there is a maintenance reason. Every page you create is a page you have to keep accurate. Twenty questions answered as sections of three strong pages is a manageable estate. Twenty standalone pages is twenty things that will quietly go out of date.

What a question page should actually contain

When a question does earn a page, resist the urge to pad it to a word count. Google has said for years that it has no preferred length, and its helpful content guidance lists "writing to a particular word count" as a warning sign of search-engine-first content.

A strong question page has:

• The answer in the first two or three sentences, including the honest caveat if there is one ("usually no, but yes if your house is listed or in a conservation area").
• The conditions that change the answer, as a short list or a few sub-headings.
• A worked example or two. Numbers, a before-and-after, a situation you have actually dealt with.
• The next question the reader will have, answered briefly, with a link to the page that answers it fully.
• Where it comes from. If you are quoting a regulation, a manufacturer's spec or a study, link to it. Readers trust it more and so do search systems looking for reliable sources.

That is often 500 to 800 words. If it runs longer because the topic needs it, fine. If it runs longer because you are stretching, cut it.

Grouping sections into pages that hold together

Once you have sorted questions into pages and sections, the remaining job is deciding which sections go on which page. A rule that works: group by the moment in the reader's journey, not by keyword similarity.

Someone deciding whether to do a thing has one set of questions (is it worth it, how much, how long, what are the risks). Someone who has decided and is choosing a provider has another (how do I compare quotes, what should the contract include, what questions should I ask). Someone mid-project has a third (what if it overruns, what do I do about a dispute).

Three pages, one per moment, each with its sections in the order the questions actually occur to people. Internal links carry the reader forward. That structure is also what makes a site easy to summarise: an assistant asked "should I build a kitchen extension" finds a page that was written for exactly that moment.

The questions you should not answer

Some questions in your list will be about things you do not do, places you do not serve, or topics where you have no real knowledge. Leave them. Google's helpful content guidance asks, pointedly, whether you decided to cover a topic "mainly because you thought you'd get search traffic" rather than because your audience would expect it from you. A plumber's blog post on choosing a kitchen worktop is a traffic grab, and readers and ranking systems both tend to notice.

The other category to drop is the question with no real answer. "When will interest rates fall" and "what will my house be worth next year" invite confident nonsense. Say what is known, say what is not, and move on.

Questions people ask

Should every H2 be phrased as a question?

No. Phrase a heading as a question when the section genuinely answers one and the question is how people would say it. A heading like "What a survey checks" is clearer than "What does a survey check?" for a section that is a list, and nothing is lost. Mixed headings read as human; uniform question headings read as a template.

What about an FAQ block at the bottom of the page?

It is fine for genuinely short questions that do not fit the flow of the page. Keep it short and make sure each answer is real rather than a pointer back into the page. Note that Google stopped showing FAQ rich results in Search in May 2026, so the block is for readers, not for a search feature.

How do I know if I split a topic wrongly?

Search Console will tell you over a few months. If two of your pages keep trading places for the same queries, they are competing with each other and probably belong together. If one page ranks for a question but people leave quickly and search again, the answer is probably on the wrong page or missing.

Doing this at scale

Sorting questions into pages and sections is the part of content planning that pays off for years, and it is the part most businesses skip because it is slow. It is also how the weekly content in Ranked's SEO service is planned: a topic map first, pages that each own a moment, and sections that answer the rest. If you want a second opinion on a plan you have already drafted, get in touch.