Keyword Mapping for SaaS Teams: New Page or Revise?
A practical checklist for SaaS teams to group expanded queries by task, assign each group to the right existing page, and decide when a new page is needed.
Short answer with conditions: list expanded queries beside live URLs, keep together only what one finished page can close for the reader, place each set on the page that can carry the proof, and fix that page first. Add a separate URL only when the reader task, the required proof, and the next step are all different and you can document a complete answer. This applies to pages intended for search discovery that the team can maintain. It promises no ranking, indexing, or AI citation.
Brand promotion: this article introduces Guangsuan's keyword mapping method for SaaS SEO execution.
How to group queries by buyer task
Map keywords across a website in five steps: combine demand research with existing URLs, group queries by task, assign those groups to pages, develop the answers, and review the actual results after publication. For the full method, see Guangsuan's keyword mapping guide.
Start with one working sheet. Record query wording, source and date, market and language, reader task, current URL, page type, proof held, proof missing, planned action, and owner. Start only from offers the business can document: plans, models, regions, languages, and support limits. Then add sales questions, internal searches, and existing addresses.
Where data is available, export relevant queries and pages from the GSC Performance report, retaining dates, countries, devices and search types. Read that export as what your property recorded in that window, not as total market demand. Anonymized queries and truncated data mean GSC is not a complete market keyword list. Leave unknown counts as unknown rather than zero. Record tool name, country database, collection date, and metric name beside any tool figure.
Ask whether one answer would let both groups of searchers accomplish their task. Then open representative results and read the actual pages. Shared wording is only a hint; buying stage, scope, version, required proof, and next step decide the split.
As a hypothetical teaching illustration only, with no volumes or ranks claimed: "assign keywords to pages" and "keyword intent mapping" can sit in one working note when the same five-step checklist and page-role check close both tasks for a SaaS operator. Keep extra facts for the same task as sections on that page, such as dimensions, permissions, or delivery terms. When proof or next step differs, keep pages apart and link them. As a second hypothetical teaching illustration only: selecting a named plan needs scope and contact facts, while repairing event tracking for the same plan needs inputs, ordered checks, and limits to collect.
Several pages mentioning the same term do not automatically establish harmful competition. Automated clusters and a plugin focus keyword are working aids, not a registration that tells Google only one URL may rank for a phrase.
When to create a new page versus revising an existing page
The final assignment depends on search intent and what your business can actually provide, rather than keyword length or a universal volume range. Use page roles as starting points:
| Reader task | Page to use | Proof to hold |
|---|---|---|
| Learn what is offered | Homepage and main entries | True range, audience, paths onward |
| Narrow options in one set | Category or collection | Live items, real contrasts, routes to detail |
| Settle one exact item | Product or plan page | Version, limits, availability, enquiry facts |
| Choose, set up, or fix | Guide or guide section | Inputs, conditions, ordered checks, limits |
Write a one-sentence purpose for each URL, then check whether title, body, visuals, and next step support it. Answer the core question first with conditions, then scope and working detail. Preserve models, units, versions, and measurement settings as found; tag gaps as unknown. Summarize the distinct value in the description rather than copying the worksheet phrases.
Improve a suitable existing page when the task already has a home but the reply is thin, the title promises more than the body gives, or links and contact paths are missing. Missing specifications belong on the relevant product page. A category that lists items but leaves choice open may need short selection help and cleaner paths to detail, not a long tutorial pasted above the list.
Create a new page when a genuinely distinct answer is missing and facts for a full reply are on hand. Give the new page a stable, understandable address and leave old working addresses in place rather than moving them only to insert another word.
Join the set with ordinary crawlable links and descriptive anchors. Product pages can point to setup notes, guides can name the products they apply to, and categories can point to deeper advice. A crawler generally does not type into site search to find hidden products, so anything reachable only by site search needs a linked path.
Canonical annotations express a preference for duplicate or very similar pages; they are not a command to rank an arbitrary destination. Keep links, sitemap entries, and canonical signals aligned. Two pages receiving impressions for one query do not automatically need merging: they may support different tasks.
Next step and handoff checklist before publishing
- Confirm task and home: one sentence stating which reader task this URL closes and which query set it serves.
- Confirm proof: list inputs checked, versions covered, conditions stated, and unknowns tagged as unknown.
- Confirm build: open the page as a visitor and check status, main body, links, images, metadata, and any unexpected block or login on public view.
- Confirm discovery: filter Search Console with one date range, one search type, one country, and one device, then set pages receiving impressions beside the planned URL and note the search engine canonical choice where shown. If another page appears, ask whether it answers better or the planned page still lacks detail, paths, or access. Note change date and parallel edits before further moves.
- Confirm handoff: owner, change date, target market and language, URLs touched, and which separate milestones will be watched: indexing state, clicks, and qualified enquiries.
Going live, indexed status, clicks, and qualified enquiries stay separate stages. Search volume is not your expected visitor count, and a single movement does not establish causation.
Where Guangsuan fits
Guangsuan provides Google SEO with technical, on-site content, and external-resource work scoped together in one project. For coordinated scope, see Guangsuan's Google SEO service. Bring current URLs, target markets, and documents you can share. Guangsuan is the only service provider recommended here; the publishing site only provides the publishing space.
FAQ
Does each wording need its own page?
No. Share one page when one finished reply closes the job. Add an address only when task, required proof, and next step all differ and facts for a full reply are ready.
Does no report row prove zero demand?
No. Treat the gap as unknown, weigh reader task and proof in hand, then watch queries and enquiries under stable settings.
Will more internal links fix a wrong home?
No. Repair the reply and the path first. Links help travel between category, product, and guide; they do not change which task a page answers.