Search Intent and the Job to Be Done
Search intent is the job behind a query. Map content to what the searcher is hiring it to do, and you build pages that convert, not just pages that rank.

People do not search for words, they hire a result to do a job
The most useful idea I have borrowed from product thinking is the job to be done: people do not buy products, they hire them to make progress on something. Search works the same way. Nobody types a query because they want a list of links. They type it because they have a job, and they are hiring a result to get that job done. Search intent is just the name for that job. When you map content to the underlying job behind a query instead of to the literal phrase, two things happen: your pages start matching what people actually want, and your conversions climb, because the right job satisfied at the right moment is what moves someone forward. This post is about doing that mapping deliberately.
I have spent fifteen years moving numbers in large programs, and the single most common reason a page underperforms is not a technical flaw. It is an intent mismatch: a page built for one job, ranking for a query that carries a different one. Fix the mismatch and the page fixes itself.
The four jobs behind a query
Search intent has four classic shapes. You should be able to look at any query and name which job it is hiring for.
- Informational. The job is to learn or understand something. The result it hires is a clear, complete explanation. Sell here and you lose them.
- Navigational. The job is to get to a specific place or brand. The result it hires is the fastest route there. Do not get clever.
- Commercial investigation. The job is to decide between options before committing. The result it hires is an honest comparison, criteria, and evidence. This is where most buying decisions are actually made.
- Transactional. The job is to do something now, usually buy or sign up. The result it hires is a frictionless path to completion.
The trap is assuming you know the intent from the words. You do not. The same phrase can carry different jobs in different markets, and intent drifts over time. The only reliable way to read the job is to read what currently ranks, because the results page is the engine's verdict on which job the query carries.
How to diagnose the real job
Here is the diagnostic I run before briefing any page.
- Read the live results as evidence. If the page is dominated by guides, the job is informational. If it is comparisons, the job is commercial. If it is product pages, the job is transactional. The results are the answer key.
- Look for mixed intent. Some queries pull a blend of result types. That is the engine telling you the job is ambiguous, and it is an opportunity to serve more than one job on a well-structured page.
- Trace the job backward and forward. What did this person do before this search, and what do they need to do next? The job is rarely a single isolated moment. It sits in a sequence, and the best page acknowledges where the searcher is in that sequence.
- Name the progress they are trying to make. Write it in one sentence: "This person is trying to ___." That sentence is your brief.
This way of thinking is the practical successor to old keyword research, and it is exactly why the keyword stopped being the unit of work. You are no longer matching strings. You are matching jobs.
Map the job to the page
Once you know the job, the page almost designs itself. The job dictates the format, the depth, the tone, and the call to action.
- An informational job wants completeness and clarity. The conversion is not a sale, it is trust and a next step.
- A commercial job wants criteria, honest tradeoffs, and proof. The conversion is confidence to choose.
- A transactional job wants speed and reassurance. The conversion is the action, with every obstacle removed.
The most common failure is forcing a transactional outcome onto an informational job. Someone arrives to learn, hits a hard sell, and leaves. Serve the job they came with first, earn the right to the next step, and the conversion follows. This is also where intent work meets conversion rate optimization for organic traffic: the highest-leverage conversion fix is usually not a better button, it is a page that finally matches the job the visitor actually had.
The Job-to-Page Framework
Here is the framework I use to turn a query into a page that earns its ranking.
- Name the job in one sentence. If you cannot, you are not ready to write.
- Diagnose intent from the live results, not from intuition.
- Locate the searcher in their sequence: what came before, what comes next.
- Choose the format the job demands, guide, comparison, or action page.
- Cover the entities and questions a credible answer to the job requires.
- Place one next step that fits the job, never one that jumps ahead of it.
- Measure on the job, engagement and the right downstream action, not just position.
That fifth step matters more than teams expect. Satisfying a job completely means addressing the related questions the searcher has not even typed yet, which connects directly to building topical authority through a hub-and-spoke structure. A page that answers the job and its neighbors becomes the obvious result for the whole cluster.
A checklist for intent-mapped content
- Write the one-sentence job statement before anything else.
- Confirm intent by reading what currently ranks.
- Match page format to the job, not to your funnel goals.
- Cover the questions a searcher with this job would naturally ask next.
- Offer exactly one next step, appropriate to the job.
- Review pages quarterly for intent drift, because jobs change.
That last item catches a quiet killer. A query that was informational last year can become commercial as a market matures. When the results shift, the job shifted, and your page needs to follow. Intent is not a one-time decision. It is a thing you maintain.
Serving the job is what makes you the answer
As more queries get answered by AI rather than by a list of links, serving the real job becomes even more decisive, because generative systems are built to satisfy the underlying need directly. A page that nails the job is exactly the kind of source those systems retrieve and cite, which is the heart of generative engine optimization. Whether a human reads your page or a machine quotes it, the win comes from the same place: you understood the job and got it done.
Stop optimizing for what people type and start serving what they are trying to accomplish. Name the job, read the intent honestly, match the page, and place the right next step. Do that consistently and your content stops chasing rankings and starts earning them.
If you want help auditing your top pages for intent mismatch, the channel is open by introduction. Bring your highest-traffic, lowest-converting pages and we will find the jobs they are missing.
Written by Joseph Carroll, Carroll Consulting Services.