One of the most common content-architecture questions in SEO sounds as if it should have a precise technical answer: when a topic develops a distinct sub-intent, should you expand the page that already ranks for the broader subject or publish a separate article?
Google’s John Mueller has offered a useful answer precisely because it refuses to turn the decision into a formula.
Responding to an SEO who described an existing article that needed expansion but also contained a sub-intent substantial enough to potentially stand on its own, Mueller said: “Sometimes there is no absolute right answer -- but you can choose one, and make it the right answer.”
The exchange was reported by Search Engine Roundtable on September 9. It is not a new ranking rule, and Mueller did not say Google treats every possible site architecture identically. The more useful interpretation is that content structure often involves multiple defensible implementations, and execution can matter more than searching for a universal SEO template.
The question was not simply whether longer content ranks better
The original question came from Christopher Iwundu, who had found an existing article that clearly needed more depth. Within the broader topic, however, he identified a sub-intent that appeared capable of supporting its own page.
The choice was therefore between two reasonable structures.
One option was to expand the existing article and cover the sub-intent inside it. The other was to publish a dedicated supporting article and connect the two pages.
Mueller did not declare either architecture inherently superior.
That distinction matters because the question is sometimes reduced to simplistic SEO rules such as “one keyword per page,” “always build topic clusters,” or “consolidate everything to avoid cannibalization.” None of those slogans can decide every real content problem.
A sub-intent does not automatically require a new URL
The existence of a distinct sub-intent is useful evidence, but it is not by itself proof that a new page is necessary.
A section can serve a meaningful secondary need while still fitting naturally within the primary purpose of a larger article. If users searching the broad topic are likely to benefit from the additional explanation during the same reading journey, expanding the existing page can create a more complete resource without forcing readers to navigate elsewhere.
This approach also keeps closely connected information in one place. Updates can be simpler, internal competition between nearly identical pages is less likely, and the publisher does not need to manufacture enough material to justify another URL.
The important question is whether the new section strengthens the original page or changes what the page is fundamentally trying to accomplish.
A separate article can make sense when the sub-intent has its own job
The opposite structure can be equally defensible.
If the sub-intent requires a substantially different explanation, audience, format or decision process, giving it a dedicated URL can make the site easier to navigate and the content easier to focus.
Consider a broad guide that introduces a subject and a narrower question that requires a detailed tutorial, comparison, calculator, dataset or troubleshooting workflow. Forcing all of that into the parent guide may make the original page harder to use.
A dedicated supporting page can then address the narrower need while the parent page explains the relationship and links users to the deeper resource.
That is not automatically “better SEO.” It is a different information architecture that can be better suited to a particular content set.
Search intent is evidence, not a mathematical rule
SEO tools can make the split-or-merge decision appear more objective than it really is.
Analysts may compare ranking URLs, inspect SERP overlap, cluster keywords or calculate how often the same pages rank for two query groups. Those techniques are valuable because they reveal whether Google currently treats queries as closely related.
But a SERP-overlap percentage is still evidence rather than a law.
Search results change. Query wording can conceal different user needs, while apparently different keywords can lead to essentially the same task. A publisher also has to consider its own content, audience and navigation rather than reproducing the architecture of whichever competitors happen to rank today.
Mueller’s response is useful because it leaves room for that judgment.
Execution is what can make either choice succeed
The second half of Mueller’s comment is more interesting than the first.
He did not merely say there is no absolute answer. He said an SEO can choose an approach and “make it the right answer.”
For an expanded page, that means integration matters. The new section should have a clear relationship to the page’s main purpose, useful headings, enough depth to satisfy the secondary need and a structure that does not bury the primary answer beneath unrelated material.
For a separate article, differentiation matters. The new URL needs a genuine purpose of its own rather than being a slightly rewritten version of the parent page. The relationship between the two pages should also be obvious through contextual internal links and site navigation.
Either architecture can be implemented badly.
Internal links become more important when the content is split
Creating a separate supporting article introduces another requirement: Google and users need to understand how the pages relate.
Google’s guidance on crawlable links says links help its systems find pages and can provide information about the destination through anchor text and surrounding context.
A supporting article should therefore not exist as an isolated URL discovered only through a sitemap.
The broader page can link naturally to the detailed article at the point where a reader would benefit from going deeper. The supporting article can link back to the parent resource when broader context is useful.
This is not about mechanically creating a hub-and-spoke diagram for every topic. It is about making the information relationship visible in the actual site experience.
Site hierarchy should make sense to people as well as crawlers
Google’s documentation repeatedly frames site organization as a user-navigation issue, not only a ranking tactic.
Its breadcrumb guidance, for example, says a breadcrumb trail indicates a page’s position in the site hierarchy and can help users understand and explore a site.
That principle is useful when deciding whether to split content.
If a new article has an obvious place in the hierarchy and users can understand why it exists separately, the architecture is probably easier to defend. If the publisher struggles to explain why two URLs are different, users and search engines may face the same ambiguity.
The URL count itself is not the goal. Clear information structure is.
“Avoid cannibalization” is not enough reason to split or merge
Keyword cannibalization is often invoked as an automatic reason to consolidate related content.
The concept can be useful when two pages genuinely compete for the same purpose and neither has a clear role. But two pages mentioning the same topic do not necessarily constitute an SEO problem.
A broad guide and a specialized tutorial can share vocabulary while serving different needs. Conversely, two articles targeting slightly different keyword phrases can still be functionally identical.
The more useful diagnosis is not “Do these pages share keywords?” but “Would a user understand why both pages exist?”
If the answer is no, consolidation may improve the architecture. If the answer is yes, overlap alone is not enough to prove that one page should disappear.
The opposite mistake is manufacturing thin supporting pages
Topic-cluster strategies can create another problem: publishers sometimes decide in advance that every subtopic deserves its own URL.
That can lead to collections of pages that differ only by a phrase, modifier or narrowly sliced question.
Google’s spam policies specifically warn against doorway abuse, including substantially similar pages created to rank for similar queries when they lead users toward essentially the same destination or experience.
That does not mean ordinary topic clusters are doorway pages. It does mean “more URLs” is not inherently a sign of stronger topical coverage.
If a sub-intent can be answered completely in three useful paragraphs inside an existing article, turning those paragraphs into a padded standalone page may create a worse result.
Consolidation can also go too far
The reverse failure is the giant page that tries to satisfy every possible query connected to a subject.
A publisher may keep adding sections because the page already has backlinks, rankings or history. Eventually, the resource becomes difficult to navigate and individual user needs are buried inside a document designed to do too many jobs.
Preserving an existing URL is valuable only when that URL remains a coherent destination.
Sometimes splitting a mature section into a dedicated resource improves both pages: the parent becomes clearer, while the child can go deeper without overwhelming readers who only wanted the overview.
Again, there is no universal word count or traffic threshold that determines when that point has been reached.
The SERP can help, but it should not make the decision alone
One practical way to investigate the choice is to search the primary intent and the proposed sub-intent separately.
If essentially the same pages dominate both result sets, Google may currently understand the needs as closely connected. If the two SERPs consistently reward different page types, formats or levels of specificity, a separate page may be easier to justify.
That is useful research, not a guarantee.
The final decision can also depend on whether the site already has relevant content, how much unique information is available, whether the subtopic changes frequently, how users navigate the site and whether maintaining two pages will actually improve the experience.
SEO architecture is partly retrieval engineering and partly editorial design.
The right answer can change over time
Mueller’s comment also leaves room for a reality that rigid SEO frameworks often ignore: the architecture that works today does not have to be permanent.
A subtopic might begin as a section inside a larger guide because there is not enough demand or material to justify a standalone resource.
Six months later, the section may expand, accumulate specialized questions and become useful enough to separate. The publisher can create the dedicated page, replace the original section with a concise introduction and link readers to the deeper treatment.
The reverse can happen too. Two standalone articles may prove too similar and be more useful when consolidated into one authoritative resource.
Content architecture can evolve with the content.
This is guidance, not a new Google ranking rule
Mueller’s LinkedIn reply should not be turned into a new ranking-factor headline.
Google did not announce an algorithm update saying split pages and consolidated pages receive equivalent treatment. Mueller did not provide a test showing that architecture has no effect on search performance.
He responded to a strategic question by pointing out that the decision does not always have one objectively correct SEO solution.
That is a narrower claim, and a more useful one.
There are cases where one option is clearly poor: duplicate pages, confusing navigation, doorway-like variations or a giant article containing unrelated intents. But there is also a large middle ground where two architectures can both be reasonable.
SEO strategy needs decisions, not formulas
The appeal of universal rules is understandable. “Always split when intent changes” is easy to put into a checklist. “Always consolidate overlapping keywords” is easy to automate.
Real websites are less tidy.
A page can serve several related intents elegantly. A single sub-intent can also become substantial enough to deserve its own destination. Both structures can produce clear, useful content, and both can produce confusing sites when executed mechanically.
Mueller’s answer is therefore less about choosing between one page and two than about how SEO decisions should be made.
Start with the user need. Examine how distinct the sub-intent really is. Consider the depth of the material, the navigation, internal links and maintenance burden. Use search results and keyword data as evidence rather than commandments. Then commit to an architecture and execute it coherently.
Sometimes SEO does not offer one absolutely correct answer.
The work is choosing a defensible one — and building the site well enough to make that choice make sense.