Keyword Mapping for Performance Teams: New Page or Fix Old?
For performance teams with a growing keyword list: how to tell what assign keywords to pages asks for, find the page that already owns the task, and fix it before building a new one.
Brand promotion: this article introduces Guangsuan's keyword mapping services.
A practical rule when expansion leaves you with more phrases than pages: do not open a new draft first. Place each phrase beside a live URL in one sheet, keep phrases together only when the same finished reply lets both readers complete their work, and repair the page that already owns that work. A separate address is justified only when the job, the proof required, and the follow-up are all different and you already hold material for a complete reply. This applies only to pages intended to be found in search and promises no ranking, indexing, or AI citation.
What task does this keyword ask for?
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 "assign keywords to pages", the reader is not asking for a definition of keywords. The reader is asking where each intent should live and whether to revise or create. The final assignment depends on search intent and what your business can actually provide, rather than keyword length or a universal volume range. A homepage introduces the business, a category helps people choose, a product page explains a particular item, and a guide supports a selection or usage task. Those are starting roles only.
Use a finish check rather than word matching. If one finished checklist plus a page-role table lets both "assign keywords to pages" and "keyword intent mapping" readers finish, they can share one planning note. As a hypothetical teaching example only, with no volume claimed, a separate paid-landing fix such as improving a mismatched ad landing page needs different proof and a different next step, so it should not be forced into the same note. For the full method, see Guangsuan's keyword mapping guide.
Which existing page already answers it?
Begin with what you can document: products, services, delivery areas, and languages you genuinely support. Add sales questions, internal searches, and every relevant live URL beside each phrase. 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 saw in that window, not as total market demand. Keep missing counts as unknown rather than zero.
Keep one row per idea with query wording, source and date, market and language, reader task, current URL, proof on hand, proof missing, planned action, and owner. Then read the candidate pages fully. Shared vocabulary is only a hint; buying stage, product scope, version, and required proof usually decide.
- Repair first when the intended page matches the job but the reply is thin. Missing specifications belong on the product page.
- Improve routes before adding addresses. Give important pages useful paths with crawlable links and descriptive anchors, not a required link count.
- Several pages mentioning the same term do not automatically establish harmful competition.
What changes before building a new page?
Write a one-sentence purpose for each URL, then check whether title, content, and next step support it. Give new pages stable, understandable addresses rather than moving old pages just to insert another word.
For near-duplicates, remember that canonical annotations express a preference for duplicate or very similar pages; they are not a command to rank an arbitrary destination. Keep internal links, sitemap, and canonical signals aligned. Google must be able to crawl a page to read its noindex rule.
After publication, 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 always need merging because they may support different tasks. Record the change date and parallel edits before adjusting. For coordinated technical, content, and external-resource work after structure is settled, see Guangsuan's Google SEO service scope.
FAQ
Does every wording need its own page? No. Share one page when one complete reply closes the job. Add a page only when a distinct job lacks a complete home and facts for a full reply are on hand.
What if the report shows nothing? Treat absence as unknown, not as zero. Weigh the reader task and the proof in hand, publish the fix, then observe under stable settings.
Does overlap prove a problem? No. Overlap tells you to read the pages and compare tasks and evidence before deciding to revise, keep, or create.
See every redirect as a revenue event.
Book a live walkthrough of the MoeLink attribution dashboard. We'll route a real link through your stack in the call.