One Page, One Topic: How to Clarify Search Intent
What you’ll learn
- How too many topics on one page affect readers, search intent, and maintenance
- Criteria for defining one topic from the reader’s question and search intent
- How to preserve a page’s role when splitting or combining articles
Use One Page, One Topic to Narrow Search Intent
Content belongs on the same page when one reader needs it to answer one question. Adding a topic only because it is related makes search intent, update scope, and the reading path less clear. One page, one topic is therefore a policy for fixing the role of a page, not a word-count rule.
By the end of this article, you will have practical criteria for answering “Should related content remain on one page or become a separate article?” in your own context.
Define Article Boundaries from One Reader Question
Imagine an article combining “What is Astro?”, “How to install Astro,” and “How to create your first page.” A reader seeking only an overview needs different explanations from someone ready to install it. This is a hypothetical example for considering article boundaries, not a report of changes made on this site.
What the One Page, One Topic Policy Means
The one page, one topic policy gives each article one reader question to answer. Examples and prerequisites needed to answer that question can stay on the same page.
“What is Astro” and “How to install Astro” become separate articles. If a reader wants to understand the concept of Astro, they read that article. If they want to know how to install it, they read that one. The principle is to keep article units small so that readers can go directly to the article that matches their goal.
Split Articles to Separate Search Intent, Update Scope, and Reader Paths
Readers May Need to Search Within a Multi-Topic Article
When an article combines multiple topics, readers may need to scroll through it to find the information they want. A reader who only wants installation steps may not need the overview at the beginning.
With the one page, one topic policy, readers can select the relevant article from the sidebar or a link, and the entire article addresses their specific goal.
Matching an Article to What Readers Want from a Search
Search intent means what a reader wants to learn through a search. “What is Astro?” and “How do I install it?” ask different questions. Separate articles make sense when each question needs a substantial explanation.
Google also recommends content that helps readers achieve their goals and learn what they need. One topic per article does not, however, guarantee search rankings or how a search engine understands a page.[1]
Articles Are Easier to Update and Manage
If Astro’s installation procedure changes, an article combining several topics would need review that includes unrelated sections, such as the overview. Separating the topics can make the article requiring revision identifiable.
Criteria for Deciding What Counts as “One Topic”
There are boundaries where it is easy to hesitate about whether to split. The following criteria use the reader’s purpose to guide the decision.
“Why do it” and “how to do it” are separate topics
“Why I chose Astro” and “How to set up Astro” serve different purposes. The first is for readers who want to understand the reasoning behind a choice. The second is for readers who want to take action. When readers’ goals differ, separate articles are a candidate design.
“Explanation of a concept” and “steps for an operation” are separate topics
“What is frontmatter (information such as the title and date at the beginning of an article)” (concept) and “the fields to include in frontmatter” (reference information) can be combined in one page, but when an article becomes long, they become candidates for splitting. “Understanding a concept” and “carrying out an operation” are distinct goals for a reader.
When in doubt, compare the reader questions
When the boundary is unclear, check whether different questions have been combined and consider splitting them. Related content can still be connected afterward by adding internal links between articles. Once content is combined into one article, it becomes harder to split it later.
Check Search Intent and Update Scope in the Proposed Split
For a proposed split, check whether sidebar labels and links distinguish each page’s role. Increasing the number of articles or reducing word counts is not itself the goal.
For maintenance, check whether a procedural change has an identifiable update location. For example, if a version upgrade changes a command, compare the proposed pages to identify which parts of “Installation procedure” and “Upgrade procedure” would need revision.
Summary: Split Content That Cannot Be Explained Through One Reader Question
Focusing an article on one question makes it easier to align reader navigation, search intent, and the scope of updates. When the boundary is unclear, compare designs that separate different questions while retaining necessary prerequisites and short supporting explanations.
The first decision aid is the target article’s reader question, written in one sentence, with sections not directly needed for its answer marked as split candidates. Short supporting details and prerequisites for the same decision remain together; the dividing criterion is a different reader question, not length alone.
References
- Google Search Central, Creating helpful, reliable, people-first content (updated October 5, 2026)