Content teams often stall on structural decisions because they are searching for a rule that Google never wrote. John Mueller’s latest LinkedIn reply names that behavior directly, and it applies to a decision most SEO teams make weekly: whether a sub-topic gets its own page or stays folded into an existing one.
The exchange started with a specific question. Christopher Iwundu described an existing article that needed expansion, but noted a sub-intent within the topic that he felt deserved its own page. He asked Mueller whether to expand the current article or split off a connected, supporting piece.
Mueller’s answer avoided a formula. “Sometimes there is no absolute right answer,” he wrote, but “you can choose one, and make it the right answer.” The reply does not resolve the content-architecture question. It reframes it, treating the decision itself, not the search for a hidden correct choice, as the actionable step.
This is not a new position from Mueller. Search Engine Roundtable, which first reported the exchange, noted that the comment echoes a pattern in his public answers, including prior lines like “No SEO Is Perfect” and “No Such Thing As Perfect Formula For Ranking.” Each instance pushes back on the premise that ranking behavior reduces to a checklist Google will eventually confirm.
The pattern matters because it exposes a gap between what practitioners want from Google and what Google is structurally able to give. A ranking system built on hundreds of signals evaluated across billions of pages cannot produce a single binary rule for every content-architecture judgment call. Mueller’s comment is not new guidance. It is an acknowledgment that no guidance is coming for this class of question, delivered by the person publishers most often ask.
That distinction should change how teams read Google spokesperson comments generally. A statement that resolves ambiguity, like a specific technical requirement for structured data, is different in kind from a statement that tells you ambiguity is permanent. Treating both as equally instructive wastes cycles on the second type, where no future clarification is coming no matter how the question gets rephrased.
For split-versus-expand decisions specifically, the practical test is not Google’s preference but the user’s. If a sub-intent draws a materially different search intent, warrants its own set of ranking pages, or would bloat the parent article past what a reader scanning for one answer needs, it earns a standalone page linked back to the parent. If the sub-intent only adds depth to the same intent, it belongs in the existing article. Search Console query data, not a Google statement, is the tool that answers which case applies.
Teams stuck relitigating a settled content-architecture call should treat that repeated debate as the actual cost, not the absence of a rule. Every week spent re-arguing a defensible decision is a week not spent building the calendar, links, or structured data that the debated page still needs regardless of which side wins.
Editors managing shared style guides should write down the split-versus-expand threshold once, as an internal standard, rather than reopening it project by project. Mueller’s comment gives permission to do that: pick a defensible rule internally, apply it consistently, and stop waiting on Google to confirm it.
Search Engine Roundtable reported the exchange, sourced to a September 9, 2026 LinkedIn thread, in an article by Barry Schwartz.
