Query-to-page mapping: one page, one job.

Query-to-page mapping is the practice of assigning each page on your site one search intent to answer. One page, one job. When you get this right, Google knows exactly which page to rank for which search, and so does the person doing the searching.

Most small business sites break this rule without knowing it. They have three pages half-answering the same question, or one page trying to answer six. Both problems come from the same missing step — nobody decided, in advance, what job each page does. This post is about doing that step properly.

What does "one page, one job" actually mean?

One page, one job means each page targets a single search intent and answers it completely. Not a keyword. An intent — the real thing a person wants when they type words into a box.

Someone searching "personal injury lawyer San Diego" wants to hire a firm. Someone searching "how long do I have to file a personal injury claim in California" wants an answer, not a sales pitch. Those are two jobs. They belong on two pages. If you jam both into one page, you serve neither well. The buyer scrolls past the legal explainer to find your phone number. The researcher hits a contact form when they wanted a paragraph.

The job of a page is defined by what the reader wants to do next. Buy. Book. Learn. Compare. Decide. A page with one job points the reader at one clear next step. A page with three jobs makes the reader choose, and a reader who has to choose usually leaves.

This is where positioning and keywords meet the actual structure of your site. You can have the right words on the page and still lose because the page is trying to do too much.

Why does one page trying to do two jobs fail?

A page with two jobs fails because it splits its own ranking signal and confuses the reader at the same time. Google reads a page and tries to work out one main thing: what is this page about. When the page is about two things, the signal gets thin. You rank for neither term as well as a focused page would.

Here is a common version. A downtown San Diego dental practice has one page titled "Services." On it: teeth whitening, root canals, Invisalign, emergency dentistry, new-patient offers. Five services, five different searches, one URL. Google cannot tell whether this page answers "emergency dentist near me" or "Invisalign cost San Diego." So it ranks the page weakly for both, and a competitor with a dedicated emergency-dentist page takes the call.

The reader side is worse. Someone with a cracked tooth at 8pm does not want to read about Invisalink financing. They want to know you're open and how to reach you. A single crowded page makes them hunt. Every second of hunting is a chance to hit the back button and try the next result.

One job per page fixes both problems at once. The signal concentrates. The reader lands on exactly what they searched for. The next step is obvious.

How do I map queries to pages?

You map queries to pages by listing the real searches your clients make, grouping them by intent, and assigning one page to each group. It is a spreadsheet exercise, not a technical one. Any owner can do a first pass in an afternoon.

Here is the process we use inside a Search Foundations engagement, stripped to the parts you can run yourself.

1. List the searches. Write down every question and phrase a client might type before they need you. Pull from your own inbox, your intake calls, and the "People also ask" boxes on Google. A family lawyer might have forty of these.
2. Group by intent, not by word. "Divorce lawyer San Diego," "best divorce attorney near me," and "family law firm San Diego" are the same intent — hire someone. They belong to one page. "How is child custody decided in California" is a different intent — learn something. Different page.
3. Name the job for each group. Write one sentence per group. "This page convinces a person ready to hire a divorce lawyer to call us." "This page explains California custody rules to someone researching." If you cannot write the sentence, the group is not clean yet.
4. Match each group to a page. Some groups already have a page. Some need one built. Some are duplicates you can merge or kill.
5. Check for collisions. If two pages both claim the same intent, you have cannibalization. Pick a winner. Redirect or rewrite the other.

The output is a simple table: query group, intent, the one job, the page that owns it. That table is your site map for search. It tells you what to build, what to fix, and what to delete.

What is keyword cannibalization and how do I spot it?

Keyword cannibalization is when two or more of your own pages compete for the same search, so Google splits attention between them and ranks both lower than one strong page would rank. You are your own competitor.

It happens quietly. A firm writes a service page for "estate planning San Diego" in 2021. In 2023 someone writes a blog post titled "Do I need an estate plan in San Diego" that also targets the term. Now two pages chase one search. Google sees two candidates, trusts neither fully, and both slide.

You can spot it in three ways. First, search your own site: type site:yourdomain.com estate planning into Google and see how many pages come back for the same phrase. Two strong candidates for one term is a warning. Second, look at your search data — if the same query drives clicks to two different pages, they are splitting the signal. Third, run the mapping table above. Collisions show up the moment you write down which page owns which job.

The fix is a decision, not a tool. Pick the page that should own the intent. Make it the best answer on the topic. Point the weaker page's content into it, then redirect the weaker URL. One job, one owner.

This was a large part of the work we did with McShanes Solicitors. They had overlapping pages competing for the same practice-area searches. We mapped the intents, assigned one page to each, and merged the rest. Rankings on the core terms rose because the signal stopped being split three ways.

What if I have gaps — searches with no page?

Gaps are searches your clients make that no page on your site answers, and they are the most valuable finding in a mapping exercise. Every gap is traffic going to a competitor by default.

When you build the query list properly, you find questions you never wrote about. A plumbing company might discover that "why is my water heater leaking" gets searched hundreds of times a month in their area, and they have no page for it. That search is a person with a problem you solve, looking at someone else's answer.

Fill gaps in priority order. Buying intent first — searches where the person is ready to hire. Those pages earn revenue fastest. Then high-volume research questions, because they build trust and pull people into your site before they need you. A person who read your water-heater explainer in March calls you in June when the tank fails.

Each new page gets one job, same as the rest. Do not fill a gap with a page that also tries to sell three other services. The discipline holds all the way down.

Worth naming: a well-mapped page still fails if the page itself is slow or broken. Intent gets you the right visitor. The page has to hold them. If your pages take four seconds to load, the reader leaves before your perfect intent match ever registers — which is why a slow site is a sales problem, not an IT problem. Mapping and speed work together. One without the other leaks.

Where this breaks down

Query-to-page mapping does not fix a site with no authority or no reviews. You can map every intent perfectly and still lose to a firm Google trusts more, because trust is earned over time and mapping is only the structure. Mapping also does not help if your pages load slowly or fail Google's technical checks — the three numbers in Core Web Vitals still decide whether Google bothers ranking you at all. And we won't pretend one page per job means one page forever. Intents shift. New questions appear. The map is a living document, not a monument. You revisit it when your services change and once a year regardless.

What mapping does is remove the self-inflicted damage. Split signals, crowded pages, gaps you didn't know you had. Fix those and the rest of your search work compounds instead of fighting itself. Foundations first.