Query groups and page tasks
Query Grouping: Match Searches to Shared Answer Needs
Group the answer needs before assigning URLs.
Query grouping organizes search phrases around a proposed reader task. Similar wording can describe different work, while different wording can lead to the same useful explanation. A group is a planning hypothesis to test against evidence and the existing website.
Free learning from Semantec SEO. Examples are illustrative unless a source states otherwise.
What makes a useful query group?
Keyword grouping brings phrases together when one coherent answer can serve the same reader task under compatible conditions. The group records an interpretation to check. The URL assignment comes after the editor has compared that interpretation with existing answers.
Different wording can ask for the same explanation. The same wording can also conceal a change from learning to preparing or requesting work. Compare the expected answer, evidence, conditions and next action before naming the group.
Keep the topics, queries and keywords distinct: the topic names the subject, the query supplies particular wording, and the group proposes a shared answer need. A similarity score can suggest candidates for review; it cannot decide their meaning or appropriate destination.
Prepare the phrase list without losing provenance
Keep an untouched raw phrase field. Add separate fields for the source, country or market, language, collection date, dataset and measurement state. A working version can tidy spacing or casing while preserving the original wording and its reference.
Do not silently erase a spelling variant or assumed typo. It may be harmless formatting, a separate entity or a clue that the meaning is uncertain. Keep the changed spelling beside the raw phrase and state why the editor proposes it.
Record a reported numeric zero as zero. A missing or blank estimate, or a response marked as no data, remains UNKNOWN. A larger reported volume does not establish a closer fit to the business or a distinct answer. Use reader intent and query context to identify the task and its constraints before deciding what to group.
Write the task before naming the group
Record the reader’s immediate need, required answer, relevant constraints and useful next action. Compare those statements before deciding which phrases belong together.
Spelling variants and synonyms may share an answer. A change from learning about a service to requesting it can require a different destination even when most words stay the same. Query volume, if available, is a separate observation rather than proof of task identity.
Keep the raw query list and its provenance. Do not present invented examples or suggested phrases as measured customer searches. The example below is synthetic and carries no search volume claim.
A useful task statement identifies an action, its object, the reader, relevant conditions and a next step. For the fictional bicycle lesson, the three statements below require different facts. They do not describe measured searches or a real workshop offer.
Compare the three task statements
Understand a service
- Task
- A bicycle owner wants to understand what a service may include and what its scope does not establish.
- Needed answer
- Explain the checks and their qualified scope using a verified provider or suitable subject source.
- Next action
- Read the explanation and identify the remaining question before requesting work.
Prepare an appointment request
- Task
- A bicycle owner wants to gather the details a provider requires before accepting an appointment request.
- Needed answer
- State the verified request details, conditions and what happens after the request.
- Next action
- Use the correct service route with the required information; an enquiry is not a confirmed appointment.
Request work
- Task
- A person wants to find a provider serving the relevant location and request suitable bicycle work.
- Needed answer
- Confirm the offer, location, contact route, request process and any conditions.
- Next action
- Request the work through the verified route. Do not imply the provider has accepted it.
Compare the answers rather than only the words
Write the smallest complete answer each phrase needs. Compare the facts that must be true, the conditions that change the answer and the next action the reader can take. The phrases can share a candidate group when the same explanation can answer both without losing those differences.
- State each proposed reader task without using the group name as the explanation.
- List the facts, evidence and conditions that each answer requires.
- Check if one explanation can satisfy both tasks without an abrupt change of audience, action or proof.
- Keep any unresolved difference visible and name the research that could resolve it.
Synonyms and shared entities support the comparison, but they do not settle it. An automated embedding or tool suggestion remains a candidate until this answer comparison has been made.
Test the bicycle example phrase by phrase
Two almost identical phrases can imply a material change in the task. These proposed readings need audience and result research before use in a real plan.
The four original phrase records below preserve each proposed answer and its condition. Their destinations describe page jobs, not new permalinks or verified provider services.
Keep all four proposed readings
bike service checklist
- Proposed answer need
- Understand what checks a service can include
- Grouping decision
- Candidate explanatory resource, with qualified scope
bike service booking checklist
- Proposed answer need
- Prepare details needed to request an appointment
- Grouping decision
- Candidate content block to prepare a request on a verified service route
bicycle servicing explained
- Proposed answer need
- Understand the service and its limits
- Grouping decision
- May join the explanatory group if the scope matches
arrange bicycle servicing
- Proposed answer need
- Find a provider and request work
- Grouping decision
- May join the service route if location and offer match
Use search observations and audience records carefully
A dated search sample can reveal the page types and answer formats shown for a phrase in a stated context. Record country, language, date and collection method. Similar results can support a grouping hypothesis but do not establish identical needs for all users.
Add appropriate customer questions or interviews when available. A business can also identify which requests it can fulfill. Keep conflicting evidence rather than forcing every phrase into an existing group.
Google’s helpful content guidance centers the audience and its purpose. This grouping method is an editorial planning approach; it is not an official clustering algorithm or ranking guarantee.
Record the exact query and enough of the sampling method to repeat the observation. Compare the jobs of the returned pages and the answers they offer, rather than counting matching URLs alone. A result sample concerns its stated date and context; it cannot establish every searcher’s intention.
No fixed overlap percentage proves a shared reader task. Keep a conflicting support question or business constraint even when a search sample looks consistent. Missing audience research remains a limit; no tool estimate supplies it.
Handle mixed, uncertain and tiny groups
Keep “bike service cost” unassigned when the needed repair, bicycle details and location are missing. The phrase could lead to an explanation of price factors, a provider’s current terms or a request for an assessment. Each reading needs different evidence. Record the missing context rather than choosing the most convenient existing group.
If later context identifies a general question about what changes a price, reconsider an explanatory owner with suitable evidence. If it identifies a particular provider, locality and confirmed service, inspect that service owner. This is a conditional teaching decision, not a claim that a real query has one fixed meaning.
A group containing one phrase can still represent a necessary task. An outlier can remain outside all groups when it does not fit the declared scope. A large group can also be irrelevant. Use resolve ambiguous search phrases to examine missing context before assigning the answer.
Choose an answer owner after grouping
A phrase may fit different plausible tasks. Keep it in an ambiguity record, identify the missing context and connect it to the relevant candidate groups. Do not use a vague phrase as the sole justification for a new URL.
Compare each proposed group with the existing page inventory. A current destination may already answer it, need a new content block or need a clearer title. Preserve a useful established route when it can serve the task accurately.
Use query clarification for competing meanings and page or content block decisions for the content boundary.
Grouping, page ownership and a URL migration are separate decisions. First identify a shared answer need. Then inspect the inventory for a page that can own it, including its full explanation and the role of nearby content. A small dependent answer may belong in a block on an existing page; a separate task needs a documented boundary decision.
Use assign each answer to its owner for the ownership record. If two published pages appear to compete, diagnose competing answers before treating shared vocabulary as a search performance problem. Do not redirect a route merely because a research group was renamed.
Keep a reviewable grouping record
The two filled teaching records use the same fields. G1 gives a provisional grouping decision with its limits. G2 is deferred because a missing condition can change the answer. The raw phrases remain synthetic, and no search volume, provider result or reader test is asserted.
In a live project, enter the responsible reviewer and completed review date after the review occurs. G1 uses a labelled fictional reviewer and date to demonstrate a filled teaching record; G2 keeps its unresolved state. No real audience research or business approval is represented.
Compare a grouped record with a deferred record
G1: explanatory service group
- Group ID
- G1, filled teaching record under a declared assumption that the scope matches
- Raw phrases
- “bike service checklist”; “bicycle servicing explained”
- Reader task
- Understand what a bicycle service can include and recognize its limits.
- Shared facts
- The explanation needs a qualified service scope, checks and exclusions; it does not confirm a particular provider’s offer.
- Constraints
- The example assumes matched service scope and audience. In a real project, verify that condition before combining the phrases; retain the original wording.
- Evidence
- The supplied phrases and answer comparisons are synthetic teaching inputs. Real audience and result research remain pending.
- Proposed owner
- Inspect an existing explanatory resource. A final live URL assignment is pending the inventory and evidence checks.
- Rejected interpretation
- Do not treat a checklist for preparing an appointment request or booking request as the same complete task.
- Uncertainty
- The grouping is a hypothesis outside this example; business facts and reader evidence remain unverified.
- Reviewer
- Fictional editorial reviewer role, used only to demonstrate the teaching record; no real reviewer identity or approval is claimed.
- Review date
- 1 October 2026, an invented date for the completed teaching record. The real business review remains unperformed.
- Next action
- Inspect the existing explanation and verify the service scope before accepting the live assignment.
G2: unresolved cost phrase
- Group ID
- G2, deferred for missing context
- Raw phrases
- “bike service cost”
- Reader task
- Unresolved: understand price factors, check a named provider’s terms or request an assessment.
- Shared facts
- No shared answer has been accepted. Price factors and a provider’s offer require different evidence.
- Constraints
- Bicycle details, requested work and location are missing.
- Evidence
- Synthetic phrase only. No customer record, provider price or measured demand supports a choice.
- Proposed owner
- Unassigned. Connect the uncertainty record to the plausible explanatory and service owners for later review.
- Rejected interpretation
- Do not force the phrase into G1 or create a new price page from the wording alone.
- Uncertainty
- The missing context can change both the required answer and the next action.
- Reviewer
- Editorial reviewer requests suitable customer or business context.
- Review date
- Pending; the missing context has not been supplied.
- Next action
- Obtain the work scope, bicycle details and location, then compare the answer needs again.
Reassess when the evidence changes
Maintain a record of phrases, task statement, shared answer, source evidence, candidate owner and unresolved conflicts. Name the reason for combining or separating each disputed item.
Review a group when new reader questions emerge, a business offer changes or a page no longer matches the promised answer. Separate the change itself from any later performance result. A rewritten group does not prove a ranking or conversion improvement.
Return to the topical mapping overview for the wider planning sequence or the learning overview for related subjects.
Read the reader task overview for the wider context of intent and answer needs.
Keep both the earlier and revised group record. State what changed, what evidence prompted it, which phrases moved and why the new answer remains coherent. A merge or split proposal does not by itself authorize deletion, redirects or replacement of a useful established route.
A changed business offer, a newly documented reader task or a conflict in later observations can reopen the decision. Keep the grouping revision separate from later traffic, rankings and completed requests. Use the topical map process to carry the accepted record into briefs, drafting and website review.
Source and method
This lesson uses Google’s helpful content guidance for its broad audience and purpose checks. The examples and planning records are editorial methods, not measured research or search requirements.
The compatibility test, phrase records and review fields are Semantec SEO editorial methods. They do not describe Google’s internal grouping, an independently tested tool, a provider comparison or measured business outcomes.