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
In the early days of building this site, I was writing articles that combined multiple topics — “What is Astro,” “How to install Astro,” and “How to create your first page” — into a single document. My reasoning was that combining information in one place would be more convenient. But as the number of articles grew, a problem emerged: readers had difficulty knowing which article covered what. This experience led me to introduce the “one page, one topic” design policy.
What the One Page, One Topic Policy Means
The one page, one topic policy means that a single article explains only one thing.
“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 Could Not Reach the Information They Needed Directly
In articles that combined multiple topics, readers had to scroll through the entire article to find the information they were looking for. For a reader who only wanted to know how to install something, the overview section at the top of the article was content they did not need to read.
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.
Search Engines Have an Easier Time Determining the Subject of an Article
When multiple topics coexist in a single article, it becomes harder for search engines to determine the main subject. An article mixing “What is Astro” with “Installation instructions” ends up partially addressing both search intents without fully addressing either.
Keeping each article to one topic allows search engines to accurately identify what the article is about.
Articles Are Easier to Update and Manage
When Astro’s installation procedure changed, updating an article that contained multiple topics meant reviewing the entire article, including sections unrelated to the change — the overview, for example. When topics are separated into individual articles, only the article that needs updating has to be reviewed, making the scope of revisions clear.
How I Decide What Counts as “One Topic”
There are boundaries where it is easy to hesitate about whether to split. Here are the criteria I actually use.
“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, I make them separate articles.
“Explanation of a concept” and “steps for an operation” are separate topics
“What is frontmatter (the metadata at the top of a Markdown article, such as title, description, and date)” (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, split” as a principle
When I am uncertain, I choose to split. 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.
Splitting Articles Made Search Intent and Update Scope Easier to Review
After introducing this policy, the number of articles in the sidebar increased, but the word count per article decreased. I have the sense that it became easier for readers to reach the article that matched what they were looking for.
In terms of managing articles, it became easier to identify which topic needed updating. When a command changed due to a version upgrade, the articles that needed updating — “Installation procedure” and “Upgrade procedure” — became clearly identifiable.
Summary: Split Content That Cannot Be Explained Through One Reader Question
The one page, one topic policy means a single article explains only one thing. I consider this approach effective from three perspectives: reader convenience, search engine compatibility, and the efficiency of article management. Keeping the principle “when in doubt, split” in mind speeds up the decision-making process.
Start by writing the target article’s reader question in one sentence and mark sections that are not directly needed to answer it. Do not mechanically split short supporting details or prerequisites for the same decision; use a difference in reader question, not length alone.