Search intent: what the results page tells you to build

Every query asks for one of four things. Your job is to give the same thing, in your own way.

• Informational: the searcher wants to learn. They click guides, how‑tos, definitions, checklists and tools. Example: “what is webhooks”. Page to build: a guide like /guides/what-are-webhooks with diagrams and a short example.
• Commercial investigation: the searcher is comparing options. They click lists, comparisons, “best” roundups and alternatives. Example: “best error tracking tools”. Page to build: /comparisons/error-tracking-tools with criteria, a table and picks.
• Transactional: the searcher wants to act. They click pricing, signup, downloads, docs for a specific task. Example: “yourproduct pricing”. Page to build: /pricing with plans, inclusions and a clear start button.
• Navigational: the searcher wants a specific site or page. They click brand homepages, login, docs. Example: “yourproduct status page”. Page to build: a clean /status or make sure your brand homepage ranks for your name.

Your words matter, but the kind of page matters more. A landing page will not win a “best tools” query. A comparison will not win “how to”.

The results page already tells you what to build. Look at what wins there today. Match that on your site, with your product and audience in mind.

1. 1

   Search the exact query

   Use a fresh browser profile or a private window to reduce personal bias. Type the query as a user would, for example “invoice template” or “stripe vs paypal”.

2. 2

   Scan the top ten

   Write down the dominant page kinds. Are they tools, templates, lists, guides, comparisons, docs, or product pages? Count the pattern, not the brands.

3. 3

   Note special blocks

   Look for video carousels, image packs, People also ask, local packs, site links or shopping blocks. These hint at the task behind the query.

4. 4

   Open three results

   Skim structure. What format do they use, and what they cover above the fold? Do they lead with a tool, a list, a how‑to, a table, or pricing?

5. 5

   Decide the match

   If nine of ten are lists, you need a list. If they are tools, you need a tool or a usable template. If mixed, see the next section on mixed intent.

Example: search “best uptime monitoring”. You will likely see list posts with criteria and short blurbs, sometimes a comparison table. A single product landing page will struggle here.

Example: search “open api spec”. You will see docs, definitions and examples. A top result is not a roundup. A helpful guide or a validator tool can win.

Intent mismatch wastes impressions. Your page gets shown but looks wrong for the job, so searchers skip it. Search Console will show high impressions, low clicks and a flat position.

1. 1

   Open Performance in Search Console

   Filter by a weak query with many impressions. For example, find queries where your /features page shows but click‑through rate is low.

2. 2

   Compare your page kind to the SERP

   Search that query and write down the dominant kind on page one. If it clashes with your page kind, you have mismatch. Example: your /landing-page vs a SERP full of /comparisons.

3. 3

   Check your title and promise

   Your title should match the job, not just the keyword. If the SERP rewards “Best X in 2026”, your “Ultimate guide” title will underperform, even if useful.

4. 4

   Decide: rework or rebuild

   If the query is core, rebuild in the right kind. If not, stop chasing it and target a closer query where your existing page kind fits.

A fixed page looks like this: the URL stays, but the format flips to what the SERP rewards, and clicks rise without any net new links.

You cannot pad a landing page into a listicle and expect to rank. Change the job the page does. Then rewrite to fit that job.

• From landing to list: your /error-tracking shows features but the query is “best error tracking tools”. Build /comparisons/error-tracking-tools. Include criteria, picks, a table and links to rivals, plus your own tool in context.
• From blog to comparison: your /blog/stripe-vs-paypal is a think-piece. The query wants a side‑by‑side. Add a clear table above the fold, use scenarios, and end with who should choose which.
• From guide to tool: your /guides/invoice-template is ranking on page 2 for “invoice template”. The SERP is full of generators. Ship a simple generator at /tools/invoice-template, and link the guide for context.
• From catch-all to specific: your /features page chases “project management software”. The SERP wants long lists and brand domains. Target “project management for agencies” on a focused landing page and link it from /solutions/agencies.

Build the format the SERP rewards, but make it useful, fast and easy to scan. Here is a template for each intent. Adapt to your product and audience.

• Informational guide: title that mirrors the query, a summary answer in 2 to 3 sentences, step‑by‑step with screenshots, a worked example, links to related terms, and one soft product mention where it helps.
• Commercial investigation list: selection criteria first, a ranked or grouped list, 1 to 2 lines of who each is for, a clear comparison table, fresh screenshots, and outward links. Include yourself with the same rigour.
• Transactional page: specific headline, short proof, plan or version choices, what is included, a fast signup path, and links to docs and legal. Keep it light and quick to parse.
• Direct comparison: intro stating who each suits, a table above the fold with key differences, three scenarios, migration or switching notes, and a clear “choose X if…” summary.

Example of a good fix: your /pricing used to rank for “yourproduct cost” with a vague headline. You switch to plans, inclusions and a simple FAQ. Click‑through and signups rise together.

Do not write at random. Map what you already show for, then decide where a new kind of page will help you grow or convert.

1. 1

   Export your queries

   In Search Console, in Performance, export queries for the last 28 days. Keep query, clicks, impressions, page and position.

2. 2

   Tag each query with an intent

   Add a column for intent. Use four tags: info, commercial, transactional, navigational. If unclear, search it and decide based on the top ten.

3. 3

   Group by current page kind

   List your pages by kind: guides, comparisons, tools, product, docs. Join the export to see which kinds show for which intents today.

4. 4

   Spot mismatches and gaps

   Highlight queries with many impressions, low clicks and a page in the wrong kind. Also list intents you have no page for at all.

5. 5

   Plan builds and reworks

   Create tickets for new pages in the right kind. For reworks, state the new job in the title, for example “Comparison: Stripe vs PayPal” or “Tool: JSON formatter”.

Name your pages clearly. A URL like /comparisons/crm-for-startups helps you and your users. It also helps you avoid two pages chasing the same job.

Some queries mix intents. The first results are lists, then a few tools, then a guide. You will not satisfy all jobs with one page. Choose a lane.

• If the SERP is 70 percent one kind, build that kind. Do not fight the tide.
• If it is split, create two pages for two jobs, and interlink. Example: a /tools/uuid-generator and a /guides/what-is-a-uuid.
• If intent shifts over time, track it. Searches like “GA4 tutorial” changed shape as new features shipped. Revisit your page kind when you next refresh.

Searchers scan titles, descriptions, headings and tables. So does Google. Use elements that make the job obvious at a glance. Do not bait and switch.

• Titles: match the job and the year only if the SERP shows it. Example: “Best uptime monitoring tools in 2026” or “Stripe vs PayPal: fees, features, limits”. Keep to about 60 characters.
• Meta descriptions: summarise the job in one line. Promise the format: guide, list, comparison, template, tool. Keep to 120 to 155 characters.
• Headings: lead with the format. H1 of “Comparison: Stripe vs PayPal” beats a vague “Which payment processor”.
• Tables and checklists: put them high on the page for comparisons and how‑tos. Make them readable without scrolling on a laptop screen.
• Internal links: connect each intent cluster. From /guides/getting-started link to /pricing and /comparisons/yourproduct-vs-rival. From /pricing link back to the guide for learners.

A fixed comparison looks like this: the table is visible on load, it answers the key question, and the rest of the content supports that judgement in detail.

After you rework or ship a new page, check that it fits the job. Use Search Console and your own product analytics to confirm behaviour lines up with intent.

• Queries: your page should begin to show for terms that match the job. A comparison page should pick up “x vs y” and “best x” terms.
• Position and CTR: if you matched the dominant kind, expect a lift in position and click‑through over the next few weeks. Watch 28‑day windows.
• On‑page actions: transactional pages should see signups or trial starts. Informational guides should see scroll depth and clicks to related guides or product pages.
• Cannibalisation: if two of your pages are splitting clicks on one job, consolidate to the stronger URL and redirect the weaker.

If fit is poor after a fair test, revisit the SERP. The lead results may have changed kind or angle. Adjust and retest, or choose a different query to chase.

AI Overviews appear on some queries, often informational and commercial. The same rule holds: match the job of the query with the right page kind. Make the core answer easy to extract.

• Lead with a clear summary and the format. This helps both users and systems that form summaries.
• Keep facts consistent and visible. Put key comparisons in a table, and key steps in a list.
• Build the page you would want quoted. If the SERP rewards tools, a working tool page has a better chance than a text‑only article.

Pair this with your People also ask research. Those questions reveal sub‑jobs. Cover them on the right page or on linked child pages, not all crammed into one.