Proposed clusters
In the Clusters tab of Marketing → Search visibility, the ERP proposes how to group the queries of a topic into clusters: a pillar query, the broad one, and its child queries, the more specific ones. The groups come from data —what Google shows, what Search Console already sees and the meaning of the queries— and you decide: you accept, change or reject each proposal. No cluster is created without your accepting it.
What is it for?
A well-built cluster is a pillar page that sells at the top and teaches below, and several child pages that answer more specific queries and link to the pillar. Deciding by eye which queries go together is slow and gets it wrong: two queries that look different can be the same for Google, and the other way round. The proposal gives you the grouping already done, with the reasons, so that you only have to fine-tune it.
How do I request the proposals?
- Have the topic’s queries in the Keywords tab.
- In Clusters, click Propose clusters and choose the topic.
- If you want, tick Also propose again the queries that are already in a cluster: if you don’t tick it, what you have already accepted isn’t touched. Those in a locked cluster are never proposed.
- If any query is missing its Google results, the Real search data query panel appears: it warns that it uses credits and has a switch for Google results (top 10) for those that don’t have them and, with them, for their Volume and seasonality, their Difficulty and the Refined volume, with what each one costs and your balance. With the results switched on, they are requested from the real search data before grouping (only what goes into the bank is charged) and it goes to the background job queue; switched off, nothing is requested. If there are more than three, they go by the cheapest route and take a few minutes. More in query real search data.
- Before running it, the form says how many queries are grouped, what it costs and whether it is done straight away or in the background job queue (System → Background jobs). Click Suggest.
The proposals appear on the Proposed clusters card, above the list of clusters.
How does it decide which queries go together?
With three criteria, from strongest to weakest:
| Criterion | They go together if… |
|---|---|
| Google results | They share at least 4 addresses among their top ten Google results: for Google they are the same intent. If both have results and don’t share enough, they don’t go together, even if they are alike in everything else |
| Search Console | The same page of yours is the one that appears most in Google for both. The home page doesn’t count: it appears for all kinds of queries |
| Meaning | They are alike in what they mean (by default, 0,88 out of 1), even if they use other words |
A query left on its own joins the group most like it if it is only just short of getting in (half the results in common, or a similarity slightly below the threshold). If not, it stays unassigned: it isn’t proposed on its own.
The two thresholds —the results in common and the meaning similarity— are changed in the Guidelines tab, in SEO weights and thresholds, Proposed clusters group.
Why do some Google results end in «…»?
Because Google doesn’t give their full address. Many results arrive as a Google link that leads to the page, and all that can be seen of the page is what Google shows under the title: the domain and part of the path, cut short (https://domain.es › services › plumber-24h-v...). What is known is stored (https://domain.es/services/…).
When comparing two queries, an address like that counts as shared with any other that starts with that path. If only the domain is known, it only counts if the other query has the same incomplete result: «some page» of a domain appearing isn’t enough to say it is the same one.
The results of a query are a snapshot of the day they were requested. If two queries that should go together come out unassigned, request their Google results again: the proposal is redone with the new snapshot.
Which is the pillar of each proposal?
The group’s broad query: the one with the fewest words and, among those, the one with the most searches per month, with purchase or comparison intent, or general informational (not a question like ‘what is…’ or ‘how…’). The others are its child queries.
If a published page on your website already owns the pillar query, it is proposed as the pillar page.
What does each proposal say?
- Its name, which you can change right there. The AI sets it if available (AI name appears); if not, it is named after its pillar query.
- The topic it comes from, the criteria that form it and who proposes it: the grouper, the assistant (see below) or marketing, if you have already adjusted it.
- The reason, in one sentence: why they go together, which is the pillar and, if there is one, which page is proposed as pillar.
- Its queries, the pillar one with a star, each with its searches per month.
What does the AI do and not do?
The AI only sets the name: it sees the groups already made, with their queries, the topic, the clusters you already have (so as not to repeat a name) and the notes from the marketing guidelines. It never creates groups, never moves a query from one group to another and never adds queries. Each name request (up to 30 clusters) costs 5 credits of artificial intelligence, only if it returns a valid name. If the AI isn’t there, or fails, each cluster is named after its pillar query.
What can I change in a proposal?
- The name: type over it.
- The pillar: Make pillar (the empty star) on another query. If a page of yours already owns that query, it becomes the proposed pillar page.
- Move a query to another proposal: the query’s Move to… drop-down. If it takes the pillar, the proposal chooses another with the same rule; if it is left empty, it disappears.
A proposal you adjust is now yours: even if you request proposals for the topic again, it isn’t replaced.
What happens when I accept a proposal?
Choose in On accepting whether it creates a new cluster (with the proposal’s name) or joins a cluster you already have, and click Accept. Then:
- The queries are placed in the cluster. The pillar, as the main query; the child queries, as secondary ones.
- What was already decided is respected: a query that already has an owner page keeps it, and one that is already in another cluster stays where it was (to change its cluster, move it from there). The summary tells you.
- A query that its page targets as its target query follows the page: if the page changes query, the old one stays in the cluster without an owner and the new one goes into the same cluster. The same with a child query created when accepting: if a page takes it as its target query and then drops it, it stays in the cluster without an owner again.
- The pages without a cluster that already target those queries go into it, and the proposed pillar page becomes its pillar if the cluster didn’t have one.
You can’t create a cluster with the name of one that already exists: join the proposal to it or rename it.
And if I reject it?
Reject removes it and remembers it. As long as the data that led to it don’t change —the same queries, together for the same reason—, it isn’t proposed again. If they change (a new query, other Google results), it may come back.
What can I do with a cluster that has already been accepted?
Open the cluster in the list. Below its details, Cluster queries shows its queries, the pillar one with a star and the owner page of each one.
- Make pillar query: a query’s empty star.
- Move to another cluster: the query’s drop-down. A page whose queries in the cluster all leave goes with them (except the pillar page). And the piece in the editorial plan whose main query leaves goes too, unless it has queries in other clusters: then it stays and the summary tells you.
- Split: tick the boxes of the queries, type the name of the new cluster and click Split. They take their pages and their pieces just as when moving. To take all of them, it is enough to rename it.
- Merge with: choose another cluster and click Merge. Before doing it, the ERP tells you which cluster is deleted and what goes to the other (how many queries, pages, editorial plan pieces and marketing guidelines), and you have to confirm it. All of that goes to the other one, and this one is deleted. If the other one had no pillar page, it keeps this one’s. This cluster’s marketing guidelines go to the other one as they are.
- Lock: the ERP doesn’t propose any more changes to it and its queries don’t move (not even to split, merge or move) until you unlock it.
- Create the missing pieces: a piece in the editorial plan, as an idea, for each query in the cluster that doesn’t have an owner yet (and didn’t belong to a piece you discarded). The pillar, as a pillar piece; the child queries, as articles.
If you delete a cluster (only possible without pages), its marketing guidelines aren’t deleted: they are deactivated, and their text says that their cluster was deleted. Its editorial plan pieces are left without a cluster, and so are its queries: the one with an owner keeps it; the one without an owner was only there because of the cluster and leaves it.
After each change, above the tab you see what has changed in the scores of the queries, as in Keywords.
And the new cluster the assistant proposes for a page?
When the assistant proposes the intent of a page, it may suggest a cluster that doesn’t exist yet. When you accept that proposal, the cluster isn’t created: it appears here, as a pending proposal, with that page as pillar and its query. If another page brings the same new cluster, it is added to the same proposal. If you reject it, the assistant doesn’t slip it in again.
And if I don’t have real search data?
Everything keeps working: it groups with Search Console and meaning, and the reason for each proposal says so (‘No Google results’). If the meaning model isn’t there either, that criterion doesn’t count and the summary says so.
Which queries don’t go into the cluster proposals?
- Only queries from a topic in the bank are grouped: those without a topic don’t go in.
- What marketing has vetoed, or marked ads only, doesn’t go into any proposal.
- A topic with more than 300 queries, or requesting the Google results first, goes to the background job queue: the proposals appear when it finishes. If the Google results don’t arrive in time, the job stops without proposing anything and can be resumed in System → Background jobs: what was already ordered is collected without paying for it again, and what already went into the bank isn’t requested again.
- You can’t request two proposals for the same topic at once: while one is being made (straight away or in the background job queue), the second is rejected with a warning.
- At least two queries are needed to group.
- Topics and queries live with the Google Ads dashboard’s bank: in an installation without it, there are no proposals.
Back to search visibility.
More about Search positioning
- Guest posts
- Connect your website with Google: Search Console and Analytics
- Query real search data: what it costs
- Cross-checks between SEO and ads
- Add your website and test the connection
- Search data: volume, difficulty and Google results
- Marketing guidelines: what marketing tells the plan
- The editorial calendar
- A piece’s brief
- The content map: what each page of your website targets
- The Looker Studio dashboard: your content map alongside what Google measures
- The editorial plan