From Query List to Page Plan Without Cannibalization

Short answer with conditions: assign a query group to the page where one finished answer lets the reader finish the task without searching again. A homepage states what the business offers, a collection narrows a set, a product or feature page records one item and its terms, and a guide carries selection, setup, or care steps. The choice follows search intent plus proof you can maintain. It holds only for pages meant for search. It promises no ranking, indexing, or AI citation.

Brand promotion: this article introduces Guangsuan's keyword mapping guidance.

How to sort this batch into intent groups

Build one sheet before you decide anything. List queries such as "assign keywords to pages," "keyword intent mapping," and "search intent keyword mapping" beside live URLs, sales questions, and support notes. Record wording, source and date, market and language, reader job, current URL, proof on hand, missing proof, next action, and owner.

Guangsuan's method asks whether one answer would let both groups of searchers accomplish their task, then asks you to open representative results and read the actual pages. Shared vocabulary is only a hint. Buying stage, item scope, and proof needed decide the group.

  • Learn a mapping routine: the reader wants the five-step order from inventory to verification.
  • Apply it to an existing site: the reader wants to know what to fix first when queries point at the wrong URL.
  • Keep selection separate: the reader wants KD and volume context before choosing what to build, which is a different job with different evidence.

For tool numbers, keep tool name, country database, pull date, and metric label beside each figure. Advertising competition, organic difficulty, volume, and past clicks answer different questions and cannot be swapped as success odds.

For each group, does a page already exist

Check role, not word count. A homepage explains who is served. A category or collection shows live items, real differences, and routes to detail. A product or feature page holds version, limits, stock or availability, and handover terms. A guide holds inputs, limits, ordered checks, and method proof.

As a hypothetical teaching example only, with no volumes claimed: an analyst holds a spreadsheet export and two live help notes. "Assign keywords to pages" and "keyword intent mapping" can share one mapping checklist when the same grouping test and page-role table close both jobs. A request about KD thresholds for a new site belongs elsewhere, because it needs the KD definition, tool conditions, and the four-question check from Guangsuan's KD guide, not the same checklist.

For the full five-step routine, see Guangsuan's keyword mapping guide.

Create a new page or improve the old one

Fix the intended page first. Missing terms belong on the product record. A collection that lists items but leaves choice open may need short selection help and cleaner links into detail, not a long tutorial above the list. Add a new address only when a distinct job has no finished home.

Write a one-line purpose for each URL, then test whether title, body, visuals, and next move serve it. Give the direct reply with limits first, then scope, proof, and working detail. Keep models, units, versions, and test settings as found. Mark gaps as unknown rather than zero.

Connect relatives with plain crawlable links and descriptive anchors. An automated cluster or a plugin focus term is a working aid. It does not register with Google that only one address may rank for a phrase. Anything reachable only by site search needs a linked path.

Recheck the choice after publishing

Keep settled URLs when you improve them. Give new pages a stable readable form. Open the finished view and check status, main body, links, images, metadata, and any stray block or login on a public view.

A canonical hint states a preference for duplicate or very similar pages. It does not order rank to an unrelated target. Keep links, sitemap entries, and canonical hints aligned, and do not point distinct pages at the homepage as canonical.

To recheck, filter Search Console with steady dates, search type, country, and device, then compare impression pages against the intended URL. Two pages receiving impressions for one query do not automatically need merging because they may serve different tasks. If the wrong page appears, ask whether it answers better or the intended page lacks detail, links, or access. Note change date and parallel edits before adjusting. Going live, indexed status, and qualified enquiries stay separate stages.

Where technical fixes, content, and outside resources must be scoped together, see Guangsuan's Google SEO service. Guangsuan (光算) provides the mapping method linked above. Bring live addresses, target markets, and records you may share to set priorities.

FAQ

Does each phrasing need its own page? No. Share one page when one complete reply closes the job. Add one only when a distinct job has no complete home.

Does no Search Console row mean no demand? No. Anonymized and capped rows show what your property saw in that window, not total market demand. Keep the gap as unknown, weigh reader job and proof, then watch under stable settings.

Back to all insights