TL;DR: One page, one intent means every URL on your site answers one question for one audience and maps to one service. AI engines retrieve passages per sub-question through query fan-out, so a page spread across five intents rarely wins any of them. Audit for pages whose titles need the word "and" to be honest, split them with proper redirects, and give every service its own page.
What does "one page, one intent" mean?
One page, one intent is a page architecture rule: each URL on your site exists to answer exactly one search intent and to sell exactly one service. A page that covers your web development services, your pricing, your SEO packages, and why the reader also needs an app is a kitchen-sink page. It serves four intents at once and gets cited for none of them.
The rule has two halves. The intent half says the page matches one type of query: informational ("how much does a website cost in Egypt"), commercial ("best web development company in Cairo"), transactional ("hire a web developer"), or navigational (your contact page). The service half says the page maps to one offer in your catalog, so both the reader and the engine know exactly what the page is for.
This is the first of the five structure rules we covered in our guide to page structure for AI search, and it earns that position. The other four rules are almost impossible to apply on a page that has no single job.
Why do kitchen-sink pages fail in AI search?
Because AI engines no longer rank whole pages against one keyword. They retrieve passages against many narrow sub-questions at once. Google confirms that AI Overviews and AI Mode use a query fan-out technique: issuing multiple related searches across subtopics and data sources while the answer is being generated.
Google describes the mechanic plainly in its AI Mode announcement: the system breaks a question down into subtopics and issues a multitude of queries simultaneously on the user's behalf. Every one of those background queries carries its own narrow intent, and every one retrieves the passages that answer it most directly. A focused page can win a branch outright. A diluted page competes in every branch with a fraction of its relevance and usually loses all of them.
The research points the same way. The Princeton GEO study demonstrated that content-level optimization can lift visibility in AI-generated answers by up to 40%, and every method that produced the lift made a passage answer its query more directly: adding statistics, citing sources, sharpening the answer itself. A multi-intent page moves in the opposite direction. Its passages answer everything a little and nothing completely.
Classic Google adds its own penalty on top. When two intents live on one URL, the page competes with itself for position, the snippet matches neither query well, and click-through suffers on both. The kitchen-sink page was already a bad deal. AI search just raised the price.
How do you map a page to a single intent?
Start from the query, not from the page. Before writing a word, put the exact target query at the top of the brief, classify its intent, and name the one service the page supports. Any planned section that answers a different parent question gets cut or moved to its own URL.
The nuance that trips teams up is depth versus drift. Question H2s that break the target query into its natural sub-questions are depth, and they mirror the exact fan-out branches you want to win. H2s that introduce a new parent question are drift. On a page targeting "how much does a website cost in Egypt", an H2 asking "what affects the price of a website?" is depth. An H2 pitching "our mobile app packages" is drift, and it belongs on the app development page.
The test is simple. Could this H2 be a real query typed by the same person, in the same moment, on the same buying journey? If it belongs to a different person or a different moment, it belongs on a different page.
When should you split an existing page?
Split when the data shows two lives inside one URL. The three signals: the page earns impressions for two unrelated query clusters in Search Console, its H2s answer questions from different buyer stages, or its title needs the word "and" to describe the page honestly.
Splitting done right is a small migration, not a copy-paste. Each new page fully matches its own query, a 301 redirect covers the fragment it replaced where relevant, canonicals are set cleanly, and internal links are rewired so the equity the original page earned flows to its successors. We cover the redirect and canonical mechanics in the page structure guide.
One-intent page vs kitchen-sink page
| Signal | One-intent page | Kitchen-sink page |
|---|---|---|
| Target query | One named query at the top of the brief | "Everything about our services" |
| Fan-out coverage | Wins its branch outright | Competes weakly in every branch |
| Title | States one promise | Needs "and" to be honest |
| H2 structure | Sub-questions of the same intent | A new topic per section |
| Call to action | One clear next step | Three competing next steps |
| AI citability | An extractable answer under every H2 | Nothing clean enough to lift |
How we apply this at HBS
We rebuilt our own catalog on this rule. Every service at HBS lives on its own dedicated page with its own pricing, process, and FAQ, and no service shares a URL with another. Before we write a service page or a pillar post, we run fan-out research first: we ask the AI engines the buyer's actual question, extract the sub-questions they generate, and those sub-questions become the H2s. The page is designed to win one intent's entire fan-out, nothing else.
That discipline is also why this article covers one checklist item instead of five. The full pre-publish checklist lives in the page structure guide. This page has one job.
The cheapest fix on the checklist
One page, one intent costs a content audit and some discipline, and it multiplies the value of everything you do afterward: content capsules, front-loaded answers, schema. If your pages are trying to do three jobs at once, our Advanced SEO Solutions team can audit your architecture, map every URL to a single intent, and handle the splits and redirects without losing the rankings you already earned. Get a free audit and find out which of your pages are working against themselves.
