# Keyword intent: read it from the results page, then match the page

You rank when your page matches the intent Google assigns to the query. Read that intent from the results page, not from a tool. Then build, pick or tune the page that fits. This guide shows the signals to read, the page types to use, and six worked examples.

Updated 2026-09-14 · Source: https://porteur.ai/guides/keyword-intent

## Read intent from the results page first

Start with the results page. Search the query in a clean browser or an incognito window. Use the location your customers search from.

Scan what ranks. The kinds of pages tell you the intent Google assigned. Guides and videos suggest informational. Lists and comparisons suggest commercial investigation. Product pages and shopping suggest transactional. A homepage or sitelinks suggest navigational.

Note the features at the top. An AI Overview or a featured snippet soaks up clicks. People also ask and related searches show adjacent queries Google associates. Both shape what your page should cover, but they do not change the base intent.

Use the results page over a tool for intent. Tools guess. The page in front of you is the assignment. That is what you build for.

## The four classes and the page you ship

| Intent | SERP patterns | Page to build | What success looks like |
| --- | --- | --- | --- |
| Informational | How-to guides, explainers, videos, featured snippets, People also ask | A clear guide or explainer at /guides/topic with steps, diagrams, FAQs | Satisfies the question fast, earns snippet eligibility, internal CTAs to deeper guides or product |
| Navigational | Brand homepage, sitelinks, knowledge panel | Your homepage or a branded hub, make sitelinks clean | Owns your name and key brand terms, strong CTR |
| Commercial investigation | Lists, comparisons, "best X", "X vs Y", category roundups | /best-x listicles, /x-vs-y pages, /alternatives pages with criteria and tables | Matches comparison intent, captures clicks from lists and "vs" queries |
| Transactional | Product pages, category grids, shopping units, prices, availability | /pricing, /product, /signup with evidence, specs and clear CTAs | Loads fast, shows price, converts from search traffic |

Write title tags to match. For a list: "Best note taking apps for Mac". For a how-to: "How to migrate from CSV to Postgres". For a product page: "Time tracking software for agencies". Keep titles about 60 characters.

## Map each query to a page kind

1. **Classify from the results page** Open the query. Write the intent you see. Count the first ten results by type: guides, lists, product pages, brand homepages. Pick the majority.
2. **Pick the right page pattern** Choose the pattern from the table above. Do not try to make one page do two jobs. Give each intent its own URL.
3. **Check competing angles** List the recurring angles and entities you see: "free", "for teams", "2026", "mac", "api". Your page should speak the same language and cover the same entities, in your own structure.
4. **Scope the depth** The top pages set the depth. If they carry a table of criteria, you need one. If they add short videos, consider one. If they answer five common questions, add an FAQ.
5. **Wireframe before you write** Outline H2s that match the searcher’s journey. Example for a comparison: intro, who it is for, criteria, head-to-head table, strengths, drawbacks, verdict, FAQs, sources.
6. **Decide the URL** Put comparisons at /x-vs-y and /alternatives/x. Put lists at /best-x. Put how-tos under /guides/. Keep product intent to /pricing and /product.

Set expectations on clicks. A query with an AI Overview or a featured snippet sends fewer clicks than its volume suggests. That is normal for head informational terms.

## How SERP features steer your build

- AI Overview present: answer the core question in one or two clear paragraphs near the top. Add supporting sections that go deeper. Use precise headings that match the sub-questions you saw.
- Featured snippet present: structure a concise answer in 40 to 60 words under an H2 that matches the question. Follow with detail. Use ordered steps if it is a how-to.
- People also ask prominent: pick the two or three that are on-topic and answer them on the page. Do not chase every tangent. It can bloat and hurt clarity.
- Shopping units: if you see product tiles, this is transactional. Show price, variants, specs and reviews. Load fast. Target /product or /pricing, not a blog post.
- Video carousel: add a short video that mirrors your core steps. Host on YouTube and embed. It earns a second surface without changing the base intent.
- Sitelinks or brand pack: navigational. Make your homepage title and meta crisp. Ensure key subpages are linked and titled well so sitelinks are meaningful.

> Rule: build for the intent Google shows, not the one you wish to rank for.

## Avoid the mismatch that wastes rankings

A mismatch is when your page type does not fit the intent. Example: a salesy /pricing page for "how to import CSV to Postgres". You may get impressions but no clicks or low time on page.

- Symptoms in Search Console: high impressions, low clicks, low click-through rate, average position outside top 5, queries do not match your H1 or title shape.
- Fix by fitting the page to the intent. If most top results are guides, build a guide. If they are lists, build a list. If they are products, ship a product page.
- Split mixed pages. Move how-to content from /pricing to /guides/how-to-x. Keep /pricing focused on buying. Link both ways with descriptive anchors.
- Merge near-duplicates. If you have two guides for the same intent, merge into the stronger URL. 301 the weaker page. Update internal links.
- Tighten titles. If you target "best note taking app", do not title "Our product features". Say "Best note taking apps" and add criteria in the H2s.

Expect reindexing time after changes. Watch the query mix on the page in 28 days. You should see more aligned queries and a higher click-through rate if the fit improved.

## A worked mapping: six queries, six page kinds

| Query | SERP read | Page kind | Your URL | What to include |
| --- | --- | --- | --- | --- |
| "keyword intent" | Guides from suites, definitions, AI Overview, People also ask | Informational guide | /guides/keyword-intent | Explain the four classes, show SERP signals, a mapping workflow, one worked example, FAQs |
| "best time tracking software" | Listicles, "best" roundups, comparison tables | Commercial investigation list | /best-time-tracking-software | Selection criteria, a ranked list, short blurbs, pricing snapshots, who each suits, update date |
| "harvest alternatives" | "Alternatives" lists, brand comparisons, ads | Commercial investigation alternatives | /alternatives/harvest | Switching criteria, 7 to 12 options, quick pros and cons, migration notes, CTAs |
| "time tracking app pricing" | Pricing pages, category pages, shopping units are rare | Transactional pricing | /pricing | Clear plans, inclusions, price, FAQs, comparisons to rivals’ plans, trust signals |
| "how to track billable hours" | How-to guides, featured snippets, videos, People also ask | Informational how-to | /guides/track-billable-hours | Step-by-step with screenshots, a template, pitfalls, a short video, links to product feature docs |
| "toggl vs harvest" | Head-to-head comparisons, tables, brand sites | Commercial investigation head-to-head | /toggl-vs-harvest | A comparison table, criteria, strengths, drawbacks, a verdict based on use cases |

On yourproduct.com, each URL serves one intent. Internal links connect related intents. Example: the how-to links to /pricing and /best-time-tracking-software with clear anchors, not "click here".

## Use autocomplete, People also ask and related to scope

Autocomplete suggestions come from real searches, weighted by popularity and freshness, and vary by language, location and history. Treat them as what people type, not volumes. Collect them for angles and modifiers like "free", "for agencies" and the current year.

People also ask and related searches at the foot of the page come from queries Google associates with the one searched. Use them to pick two or three sub-questions to cover. Do not pad the page with every branch. Stay on intent.

- Collect modifiers into clusters. Example: "for freelancers", "for agencies", "for mac". The cluster’s volume is the sum of its members across close variants.
- Write one page per cluster per intent. Example: /best-time-tracking-software-for-agencies is a separate list from the general "best" page if the SERP shows agency-focused results.
- Remember 15% of searches are new as of 2026. Keep structure flexible. Update pages as new modifiers appear in autocomplete and People also ask.

## Rival research without a suite

Open rival sitemaps. sitemap.xml shows what they publish and how they structure it. Note their /best- pages, /alternatives, /vs and /guides. That is their intent map.

Scan title tags. They state the queries a page targets. A title like "Best payroll software for contractors" is not an accident. Save these for your own map.

Use site:rival.com searches to see what Google holds. Try site:rival.com best, site:rival.com alternatives, site:rival.com vs. It surfaces pages by intent quickly.

Your own Search Console shows where you already appear. The Queries table is a goldmine. Sort by impressions. Group queries by intent. Prioritise pages you can fix by matching intent better.

For volume, use Google Ads Keyword Planner if you have spend for figures. Without spend, you get ranges. Bing Webmaster Tools’ keyword research shows volumes for free. Third-party tools estimate from Ads data, panels and models, so expect disagreements. Treat volumes as directional.

> Warning: keyword difficulty is a link-based estimate. It does not tell you if your page fits the intent.

## Build pages that fit and convert

- Informational guides: open with the answer. Use H2s that mirror the sub-questions from the results page. Add steps, images and a short summary. Link to your product where it helps, not as a pitch.
- Commercial lists: set criteria first. Be explicit on who each option suits. Update the list date. Use a scannable table. Show pricing snapshots with a source note.
- Head-to-head comparisons: define criteria, show a side-by-side table, then explain the context. Add "who should choose X" sections. Declare your bias if you are a rival.
- Alternatives pages: lead with switching reasons. Put 7 to 12 options with a line on pros, cons and price. Add migration notes and FAQs.
- Transactional pages: show price above the fold. Put features in outcomes language. Add evidence like quotes and badges. Load fast. Keep content stable so sitelinks make sense.
- Navigational pages: make your homepage clear for your name. Ensure sitelinks point to /pricing, /docs, /guides and /contact. Clean up duplicate titles that confuse sitelinks.

A fixed page looks like /best-crm-for-startups with a criteria section, a top 10, a table, a "who should choose" grid and dated updates in the intro. It reads like a buyer’s note, not a brochure.

## Track intent fit and iterate

Use Search Console to watch query mix and click-through rate per page. Open the page report. Filter by the URL. Scan the Queries tab for fit. Do this every 28 days.

- If queries look off, change the title and H1 to match the dominant intent. Adjust H2s to cover the sub-questions that show in People also ask.
- If you gain impressions without clicks, rewrite the title to match how the top results phrase it. Keep about 60 characters. Align your meta description to the searcher’s job.
- Use internal links to steer Google. Link from related pages with anchors that reflect the query class, like "best x", "x vs y", "how to x".
- Prune sections that chase a different intent. Move them to a new URL designed for that intent and link between them.
- Revisit speed and clarity. If the page is slow or jumpy, people pogo-stick. Keep LCP under 2.5 seconds, CLS under 0.1 and INP under 200 ms where you can.

## Questions

### What is keyword intent?

It is the job the searcher wants done when they type a query. You read it from what ranks: guides mean learn, lists mean compare, product pages mean buy, brand homepages mean navigate. Build the page that matches.

### What are the four types of intent in SEO?

Informational to learn, navigational to reach a known site, commercial investigation to compare before buying, and transactional to do or buy. The results page shows which one Google assigned through the kinds of pages and features it shows.

### How do I tell intent without a tool?

Search the query and read the results. Count page types in the top ten. Note features like People also ask, shopping units and video carousels. That mix is your intent signal. Use autocomplete and related searches to scope angles and modifiers.

### What are the three C’s of search intent?

Some use content type, content format and content angle. Type is the page kind, like a guide or a list. Format is the structure, like a step-by-step or a comparison table. Angle is the hook, like "for agencies" or "free". Match all three to what ranks.

### What is the difference between a keyword and intent?

A keyword is the phrase typed. Intent is the purpose behind it. Many keywords can share one intent. Build one page for the intent, not one page per slight wording change. Group close variants and focus on the page that fits the job.

### Why do impressions rise without clicks?

You may be close to fit but miss the angle or format. An AI Overview or a featured snippet can also reduce clicks for informational terms. Tighten your title to the dominant angle, add the sections top pages cover, and accept that some head terms are zero-click heavy.

## Read next

- [Search intent: what the results page tells you to build](https://porteur.ai/guides/search-intent): Learn the four intents, read intent from the results page, and fix pages that will never rank by changing their kind, not just the words.
- [People also ask: turning Google’s questions into sections](https://porteur.ai/guides/people-also-ask): See what People also ask is, where questions come from, how to collect them, write two-sentence answers, add FAQ markup, and track results.
- [The Search Console performance report, column by column](https://porteur.ai/guides/search-console-performance-report): Every column in the Google Search Console performance report explained with the traps that trip small sites, and how to act on each.
- [How to use Google Search Console in ten minutes a week](https://porteur.ai/guides/how-to-use-google-search-console): A quick weekly routine: set four filters, compare 28 days, check pages then queries, and fix three findings, without getting lost in noise.
- [Keyword research without a paid tool: five free sources that are enough](https://porteur.ai/guides/keyword-research-without-tools): Do keyword research for free with Search Console, Google’s own pages, rivals’ sites and Bing volumes. A simple method, a worked example, clear steps.
- [Keyword difficulty: what the number means and when to ignore it](https://porteur.ai/guides/keyword-difficulty): Treat keyword difficulty as a links proxy, not a gatekeeper. Learn when the score helps, when it misleads, and how to read the results page yourself.
- [Keyword mapping](https://porteur.ai/glossary/keyword-mapping): Keyword mapping assigns each cluster of searches to exactly one page. The table, how to build it, and the cannibalisation it prevents on a small site.

Paste your homepage URL to get a free check that reads your site, the searches around it and the rivals on them in about thirty seconds, and shows three findings whole before you decide if Porteur is useful. Free check: https://porteur.ai/