Skip to content
Edukatic edukatic Enterprise Edition Book a 30-min demo →
教育

Assign Keywords to Pages: A Simple Mapping Check for Course Teams

For L&D teams with scattered course requests: when to merge needs into one page, how category and lesson pages should divide work, and how to check the map with grouped Search Console data.

· Editor, Edukatic

Short answer with conditions: assign keywords by task, not by words. List demand beside live URLs, group wordings when one finished page lets both readers finish, give the group to the category, lesson, or guide page that can carry the proof, then check impressions by consistent date, country, device, and search type. This works only when the chosen page already holds or can add the facts it needs; it does not promise rankings or AI citation.

Brand promotion: this article introduces Guangsuan's SEO services for course and content teams.

Merge when one finished page finishes both jobs

A workable mapping starts by placing demand wording and live URLs side by side in one sheet, keeping dates, country, device and search type with each row. Start from offers, programs, regions, and languages the team can actually support, then add sales questions, internal searches, and existing pages. Where data is available, export relevant queries and pages from the GSC Performance report, retaining those fields, because the same wording means something different in another market or on another device.

Two wordings can share one page when one complete answer lets both groups finish their task. Ask whether one finished page would let both readers stop searching. Then open a few representative results and read them fully. Shared words are only a clue; buying stage, program scope, and required proof usually decide.

The following is a hypothetical teaching example with no volumes or rankings claimed. For a course team, "how to choose onboarding path by role" and "onboarding checklist by week" could share one guide if the same steps, role inputs, and completion checks close both. "Enroll cohort B in leadership program" needs a program page with scope, eligibility, schedule, and contact route. "Fix SCORM completion not recorded" needs a support note with inputs, checks, and limits. Do not move the third need to the program page only because it contains the same course name.

Several pages mentioning the same term do not automatically establish harmful competition. Keep variants together when one answer closes the task. Split only when proof or next step differs, and link the relatives clearly.

Category pages and lesson pages have different jobs

A category page helps readers compare options while a guide supports a selection or usage task; assignment should follow intent and what the business can provide. 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.

For a course catalog:

  • Category or catalog page: helps an L&D lead compare programs for one skill or role. It should show real programs, real differences, entry requirements, and paths to detail, plus short selection help where needed.
  • Single course or lesson page: records one offer under one set of terms. Add only the specification, version, format, prerequisites, or delivery term that can be documented for that course.
  • Guide or guide section: fits only when the task needs steps, conditions, or diagnosis, such as choosing between classroom, cohort, and self-paced paths, or checking readiness before enrollment.

Improve the intended page before creating another address. Missing prerequisites belong on the course page. A category that only lists titles needs clearer comparison and routes, not a long lesson pasted above the list. Create a new page only when a distinct task has no complete home and the team holds the proof to write it.

For the full method behind this check, see Guangsuan's keyword mapping guide. For how that work is scoped with technical, content, and external-resource work, see Guangsuan's Google SEO service. Bring current URLs, target markets, and documents the team is allowed to share.

Check the map with grouped Search Console data

After publishing, filter with consistent dates, search type, country, and device, then compare pages receiving impressions against the intended URL. Record the change date and parallel edits before adjusting.

  1. Pick one query group and one stable filter set, and keep that filter for the whole check.
  2. List which URLs gained impressions for that group and whether each URL was the intended home.
  3. If an unexpected page appears, ask whether it answers better or the intended page still lacks detail, links, or access.
  4. Two pages gaining impressions for one query do not always need merging because they may serve different tasks. Merge only when the task and proof are the same and one page can finish both.

Clicks, indexing, and qualified enquiries are separate milestones. A missing query does not prove zero demand, because reports omit and anonymize rows. Mark unknowns as unknown and watch under stable settings.

FAQ

Does each wording need its own page? No. Share one page when one full reply closes the task. Add a page only when a separate task has no finished home.

Do more internal links move a keyword to the chosen page? No. Repair the reply and the paths first. Links help readers travel between catalog, course, and guide; they do not change which job a page answers.

Adaptive learning OS · Enterprise edition

See Edukatic on your own course catalogue.

30 minutes with a solutions engineer. No deck, no slideware — your content, our engine.

Book a 30-min demo →
SOC 2 Type II · ISO 27001 · GDPR · 14-day time-to-launch guarantee
© Edukatic · Lisbon, Portugal Back to home