Where Should This Keyword Live: Category, Product or Guide for Product Teams
For B2B SaaS product teams: decide whether a keyword belongs on a category, product or guide page by reader task and provable facts, and check the choice in Search Console.
Brand promotion: this article introduces Guangsuan's keyword mapping method for B2B product teams.
Assign each query to the page that can resolve its job end-to-end with evidence you hold; create a new page only when no existing page can do that. This rule applies when you can supply the specifications, scope and service facts that the page needs. It does not measure demand and does not promise ranking or AI citation.
Start from what the team can prove
Product teams often start with a scattered list: interview notes, support tickets, NPS comments and analytics events living in different tools. Sorting that list by word length or by site depth leads to forced internal links. Sort it first by what the business genuinely supports: offers, models, plans, regions, languages and support limits.
Good mapping combines query ideas with live URLs, groups by task, assigns groups to pages, builds answers, then checks real results. Put ideas, sales questions, internal searches and current addresses side by side in one sheet. Where you have access, add queries and landing pages from the GSC Performance report with dates, countries, devices and search types kept on the record. Because anonymized queries and truncated data mean GSC is not a complete market keyword list, keep missing counts marked as unknown rather than zero.
When you use a tool for background, write tool name, country set, collection date and metric name beside the row. Paid rivalry, difficulty grades, volume bands and past clicks answer separate questions and cannot replace each other.
Test whether two queries need one page or two
Do not group by shared words alone. Ask whether one finished page would let both groups finish without another search, then open representative results in the target language and market and read them fully. Buying phase, model scope and required proof usually matter more than vocabulary overlap.
The following is a hypothetical teaching example, not a real ticket and not an observed query: how to triage trial feedback by theme and where to keep tagged notes might share one workflow note when the same triage steps close both. By contrast, why tags differ across tools and how long EU interview records may be kept need separate notes, because diagnosis and retention proof call for different evidence and different next moves.
- Same task expressed differently: keep together around one answer.
- Extra detail inside one task, such as size, fit or delivery terms: add a section to the page that owns the task.
- Different proof or different next step: consider a separate page with a clear link back to the broader topic.
The same wording appearing on more than one URL does not by itself prove harmful overlap. Do not merge pages on wording alone.
Decide: category, product, or guide
Start with page jobs: homepage introduces the offer, category supports choice, product explains one item, guide supports selection or use. Final placement turns on search intent and what you can actually support, not on word length or a volume cutoff.
| What the reader must finish | Which page should carry it | What to confirm before writing |
|---|---|---|
| Compare several options in one set | Category or collection | Live items, real differences, paths to detail |
| Settle on one exact model, plan or service | Product or service page | Exact version, limits, stock or scope, cost and handover terms where applicable |
| Measure, check fit, or follow steps before deciding | Guide section or linked guide | Inputs, conditions, limits and method you can document |
Repair the intended page before minting another address. If a category draws choice questions but shows only tiles, add selection rules and limits there. If one item lacks a specification, add it to that product page where a document supports it. Looks alone do not prove fit. Open a new URL only when a distinct task has no complete home and you hold enough material.
For the full method behind this triage, see Guangsuan's keyword mapping guide from search intent to useful pages.
Connect pages for readers, not to push terms
Use crawlable links with descriptive anchors so readers can move between related pages; do not chase a fixed link count. Let product records point to setup or sizing help, let care notes name the models they cover, and let categories point to further selection advice. Keep the structure reachable by links, because structure is not inferred from directories alone.
Do not add links to force a term onto a page. Links move readers between category, item and guide; they do not register a phrase to one address.
Keep the technical signals consistent before judging the map. Give new addresses a stable readable form and do not move old ones only to insert a word. A canonical tag states a preference among near-duplicates; it does not force an unrelated page to rank. Keep links, sitemap entries and canonical hints in agreement, and do not point separate pages at the homepage as canonical. For filter combinations, decide which views should act as search entries and which only aid on-site narrowing, then choose crawl and index handling. A crawler must be able to fetch a page to honour its noindex rule.
Confirm the choice against real impressions
After release, filter Search Console with steady dates, one search type, country and device, then compare addresses receiving impressions with the intended address. If an unexpected address appears, check whether it answers better or the intended page lacks facts, discovery paths or access. Two addresses lighting up for one query may serve separate tasks and may not need merging. Note change date and parallel edits before further moves. Getting discovered, getting indexed and winning qualified enquiries remain separate stages.
What to bring if you need implementation help
If the sheet shows missing specifications, unclear page roles or template gaps, bring live addresses, target markets and records you may share. For coordinated technical, content and external-resource work, see Guangsuan's Google SEO service scope.
FAQ
Does each wording need its own page?
No. Share one page when one complete reply closes the task. Add only when model, version, fit, place or buying step changes what must be shown.
Tools and Console disagree. What first?
Align country, language, span and metric label on both sides. Console shows what your property logged in that window; a tool shows an estimate under its settings.
What if there is no figure?
Treat absence as unknown, not zero and not a hidden win. Weigh reader task and proof in hand, then watch real queries and enquiries after release.
The best product decisions are no longer the loudest in the room — they are the most evidenced.— Obivu Research Note, 2024
See your own customer signals, ranked.
Turn fragmented interviews, tickets, and verbatims into a single feed of validated insights. Full feature access, white-glove onboarding, no credit card.