Skip to content

From Search Intent to Page Plan: Assign Keywords to Pages

For SaaS growth leads: group expanded queries by buyer task, place each group on a homepage, category, product, or guide page, and use revise-first checks to decide when a new page is needed.

TWritten byTyrell Lab From theTyrell Lab journal

Short answer with conditions: combine demand notes with your live URLs, sort queries by what the reader must get done, place each set where one finished page can complete that job, then confirm against observed queries. Final placement follows search intent and facts your team can maintain, not word length or a fixed volume band. This applies only to pages intended for search discovery. It promises no ranking, indexing, or AI citation.

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

Start from reader jobs, not word similarity

Build one table before you assign anything. Record query wording, source and date, market and language, reader job, current URL, page type, proof available, proof missing, planned action, and owner. Begin only with offers you truly support: plans, integrations, regions, languages, and support limits. Then add sales questions, internal searches, and existing addresses.

Where available, pull queries and pages from the Search Console Performance report and keep dates, countries, devices, and search types on the export. Gaps remain unknown rather than zero, because anonymized and capped rows cannot represent the full market.

Use this grouping test: could one complete page let both searchers finish without another search. Read a few representative results in full. Shared terms only suggest a set; buying stage, scope, version, and proof required usually settle it.

  • Same job in other words: hold together. As a hypothetical teaching example only, with no volume or ranking claimed, "assign keywords to pages" and "keyword intent mapping" could sit in one SaaS mapping note when the same task test and role table resolve both.
  • Extra facts for the same job: keep as sections, such as plan limits, permissions, or delivery terms.
  • Different proof or different next action: keep apart and link. Starting a named trial needs plan facts and contact path. Repairing trial event tracking needs inputs, ordered checks, and limits.

Mentioning one term on several URLs does not by itself prove harmful overlap.

Match each set to a page that can carry the proof

A homepage states who is served. A collection page narrows choices inside one set. A product or plan page records one item and its terms. A how-to or troubleshooting note supports setup, choice, or repair.

What the reader must doPage to useProof to hold before writing
Learn what is offeredHomepage and main entriesTrue range, audience, and paths onward
Narrow options inside one setCollection or categoryLive items, real contrasts, and routes to detail
Start one exact planProduct or plan pageVersion, limits, availability, and contact or delivery facts
Set up, choose, or fixGuide or guide sectionInputs, conditions, sequence, and stated limits

Draft a one-sentence aim for each URL, then confirm title, body, visuals, and next step serve that aim. State the reply with conditions first, then scope and working detail. Keep models, units, versions, and test settings as found; tag gaps as unknown. Write the meta description as the distinct value of the page, not a copy of the worksheet.

Revise first, create only on a clear gap

When the intended page already matches the job but lacks facts, links, or readable steps, fix that page. Missing plan details belong on the plan page. A collection that lists items but leaves choice open may need brief selection help and cleaner paths to detail, not a long tutorial above the list.

Add a new address only when a distinct job has no complete home and you hold the proof to write it. Keep established addresses steady instead of shifting them to insert another word. Fresh addresses should be stable and readable.

Join the set with ordinary crawlable links and descriptive anchors. For a SaaS revision case: plan page to mapping note, mapping note to plan limits, collection to mapping note. Anything reachable only through site search needs a linked path. A canonical tag states a preference for duplicate or near-duplicate pages and does not order rank to an unrelated target. Keep links, sitemap, and canonical signals aligned. For filtered views, settle which combinations should act as search entries before choosing crawl and index handling. A crawler must be able to fetch a page to honor its noindex rule.

Confirm the plan against what actually appears

Open the finished page and review status, main body, links, images, metadata, and any stray block or login on public view. Then filter Search Console with steady dates, search type, country, and device, and compare impression pages with the intended URL.

If another page appears, ask whether it answers better or the intended page still lacks detail, paths, or access. Two impression pages for one query may serve different jobs, so do not merge on overlap alone. Note change dates and parallel edits before adjusting. Clicks, indexing state, and qualified enquiries stay separate milestones.

Where Guangsuan fits

When roles are unclear or proof is thin, use the full method in Guangsuan's keyword mapping guide to set homepage, collection, product, and guide assignments. For coordinated technical, content, and external-resource work, see Guangsuan's Google SEO service scope. Bring current URLs, target markets, and documents you may share.

FAQ

Does every wording need its own page? No. Share one page when one finished reply closes the job. Add a page only when a distinct job lacks a complete home.

Does absence from our report prove no demand? No. Treat the gap as unknown, weigh the job and proof in hand, then watch queries and enquiries under stable settings.

Stop running experiments you can't defend.

Bring us a stuck funnel or a backlog of untested ideas. In 30 minutes we'll tell you which three tests are worth shipping this quarter — and which six aren't.