The content map: what each page of your website targets
The content map is the list of all the pages of your website with two things next to them: what the website says about each one (its title, its status, what Google sees) and what you decide (its scope, its cluster, the target query it owns and its intent). It is in Marketing → Search visibility, Map tab.
What is the map for?
So that each Google query has a single page of yours targeting it. When two of your own pages compete for the same query, Google doesn’t know which one to show and both do worse: this is cannibalisation. It is avoided with a list of owners: this query, this page.
The map is that list. The ERP fills it by reading your website (see sync your website) and you complete it by deciding what each page targets. What you decide here changes nothing on your website: it is the plan.
What is a page’s scope?
The scope says what a page is written for and, with that, what its title can’t promise:
| Scope | What it is | Example |
|---|---|---|
| Sales | Sells a product or a service | The invoicing software page |
| Pillar | The main page on a topic: it sells at the top and teaches below | The time tracking page, with its full guide below |
| Function | Explains a specific product feature | The recurring invoices page |
| Product | A store product page | The annual licence |
| Blog | An article | ‘What changes with Verifactu’ |
| Glossary | Defines a term: answers ‘what is…’ | ‘Order’ |
| Help | A how-to guide | ‘Issue an invoice’ |
| Category | The listing of a blog or store category: it is for browsing | The blog’s ‘E-invoicing’ category |
| Other | Everything else: legal notice, contact… | The contact page |
A sales page isn’t titled ‘How to…’, and a help guide isn’t titled ‘… software’: each scope answers a different intent, and the title gives it away.
Who decides the scope?
First, the website’s scope rules: ‘posts are Blog’, ‘pages are Sales’, ‘whatever starts with /ayuda/ is Help’. They are applied by themselves each time the ERP reads the website, and they are changed on the site’s record (see sync your website).
When a rule gets it wrong, you choose the scope on the page’s record. From that moment it is set by hand: the rules no longer change it, and the grid marks it with a padlock. With Return to the rules the matching rule decides it again.
The listings of the website’s other taxonomies (the letters of a glossary, the categories of a custom content type) are also Category: they are for browsing, just like the blog categories.
The pillar page of a cluster has the Pillar scope as long as nobody sets it by hand.
What is the target query?
The target query is the Google query that page owns: ‘time tracking’, ‘what is Verifactu’, ‘invoicing software for the self-employed’. It is written the way the searcher would write it, and it is saved exactly as you type it.
If another page already targets the same query, the record warns you: Also targeted by:, with a link to the other one. The two overlap, and one of them has to target something else. The pair also appears in the conflicts tray the next time they are looked for (in each synchronisation, or with Detect now).
If your website has Rank Math and exposes its keyword, the record shows it as a hint. You decide the target query here.
What is the intent?
What the person making that search wants:
| Intent | The searcher… | Page that serves them |
|---|---|---|
| Purchase | wants to buy or compare | Sales, Pillar, Product |
| Learn | wants to understand a topic | Blog, Pillar |
| Question | has a specific question (‘what is…’) | Glossary, Blog |
| How-to | wants to do something step by step | Help, Blog |
| Brand | is looking for your company or your product by name | Home page, Sales |
Two pages with the same query and a different intent can coexist; with the same intent, they overlap.
What is a cluster and what is its pillar page?
A cluster is a topic of your website with all the pages that talk about it: the ‘Time tracking’ cluster brings together the sales page, the blog posts about clocking in and the help guides on clocking in. Each cluster has a pillar page: the one that sells at the top and teaches below, and that the others link to.
Each cluster has an axis:
- Product, for what is bought (‘invoicing software’, ‘time tracking’).
- Topic, for what concerns people (‘e-invoicing’, ‘Tax Agency forms’).
Clusters are created in the Clusters tab: name and axis. Then you type its corresponding Blog category and, with Add the pages from…, all the pages in that category that don’t have a cluster yet go in at once. The Pillar page is chosen from among its pages.
You can also let the ERP propose them from the queries of a topic, with their pillar query and their child queries: see proposed clusters. Right there, on each cluster’s record, are its queries and the actions to move them, split it, merge it with another or lock it.
How do I find what I still have to decide?
In the Map tab:
- The buttons at the top count the pages in each scope; clicking one filters by it.
- No target query leaves only the pages that don’t have an owner yet.
- With proposal leaves only the pages with an assistant proposal to review.
- The search box searches the address, the title, the target query and the proposed query, ignoring capitals and accents.
- The drop-downs filter by scope, cluster, status, content type and language.
One way of working: filter by a scope (for example, Sales) and tick No target query. Open each page and decide its query and its intent.
Another, faster on a large website: let the assistant propose the target query of the pages that don’t have one, and you accept or dismiss them in bulk (see let the assistant propose the intent).
How do I change a page’s decisions?
Click the page in the grid: its record opens on the right. In What the ERP decides you have the Scope, the Cluster (with Is the pillar), the Target query, the Intent and the Notes. Each field is saved when you leave it; if something isn’t valid, the ERP says why and the field goes back to what was saved.
Below, What the website says shows what the ERP read: status, dates, the title Google sees, the H1, the meta description, the robots, the canonical, the categories and the versions in other languages. That can’t be edited: each synchronisation brings it up to date.
At the top, the Pre-publication review panel reviews the page at that moment and shows its traffic light, what needs fixing and the previous reviews (see review before publishing).
To decide you need the Changes permission on Search visibility; with View you can see the map, but not change it.
Can I ask the assistant to do it?
Yes. The assistant looks things up on the map (‘which page owns time tracking?’, ‘which blog posts have no target query?’) and can set the target query, the intent, the scope and the cluster of a page (‘the time tracking page owns time tracking, purchase intent’). Like every assistant action, it shows it to you before doing it, and the result is the same as on screen.
It can also propose the intent of the pages that don’t have one and accept or dismiss its proposals (see let the assistant propose the intent).
What happens to a page that is no longer on the website?
It isn’t deleted from the map: it changes to Withdrawn, with its decisions and its history. If it is published again, it goes back to its status. That way, what was decided about it isn’t lost.
Back to search visibility.
More about Search positioning
- Guest posts
- Proposed clusters
- 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 Looker Studio dashboard: your content map alongside what Google measures
- The editorial plan