The editorial plan
The editorial plan is the pieces you are going to publish that aren’t on your website yet: articles, pillars, sales pages, glossary entries or guides. Each piece is the planned owner of its Google queries, even if it doesn’t have an address yet. When the synchronisation finds its page on the website, it links it by itself and the piece changes to published. It is in Marketing → Search visibility, Editorial plan tab.
What is it for?
To plan without treading on your own toes. A piece that is still an idea already takes up its query: nobody else targets it in the meantime. That way marketing sees at a glance what is going to be written, who is in charge of it, who writes it, when it is due and with which query.
What does each piece say?
| Column | What it is |
|---|---|
| Piece | Its working title. Below it, its page if it is already on the website, or the page proposed for it |
| Cluster | The website topic it belongs to |
| Main query | The Google query it targets. Below it, how many secondary ones it covers in passing |
| Type | Article, pillar, sales, glossary, guide or incoming guest post |
| Owner | The person in your company who is in charge of it |
| Author | Whoever writes it if they are from outside: a CRM contact |
| Expected date | The day it is planned to be published. The spread of the dates can be seen in the editorial calendar |
| Status | Idea, planned, in progress, published or discarded. Below it, its column on the publishing board and, for a published one, its 30-day and 90-day measurement |
| Conflict | Whether the piece conflicts with what is published, with what is planned or with an article of yours on another website: No conflict (green), Review (amber), Conflicts (red) or Accepted (grey). Hovering over it shows what to do. See content conflicts |
An article written by a guest on your website is also a piece, of type Incoming guest post: it is created when you register it in the Guests tab and it is handled like the others. See guest posts.
How do I add a piece?
In the bar at the top, type the title, the main query (if you know it) and the type, and click Add. If you want, also choose the cluster and the expected date. The piece starts as an idea (or planned, if it has a date), with you as the owner. If the query wasn’t in the query bank, it is added.
From a gap in a marketing goal in the editorial calendar, Create a piece here brings you here with the cluster and the date already filled in.
If that query is already the main query of another page, of another piece or of an article of yours on another website, it isn’t taken away from it: the warning tells you whose it is, and the piece covers it as secondary, so that its conflict keeps it in mind. You can merge them or change the query of one of the two.
When you add it, the ERP checks its conflicts with what is published and planned, and the warning tells you what is best to do (‘You already have /blog/verifactu/ in position 14 for that query: improve that page instead of creating another’).
How do I create a cluster’s pieces in one go?
With Create the missing pieces. It is in the plan’s bar (choose the cluster) and on each cluster’s record, in the Clusters tab. It creates a piece, as an idea, for each query in the cluster that doesn’t have an owner yet:
- The cluster’s pillar query, as a Pillar piece.
- Each child query, as an Article. On taking it, the piece makes it its main query.
It doesn’t create a piece for a query that already has an owner (a page or a piece), nor for one that marketing has vetoed or wants for ads only, nor for one whose piece you discarded: marketing already said no to that piece. If you want it again, tick Include discarded ones before clicking. Each piece’s title is its query: change it afterwards. Clicking it again doesn’t repeat anything: it only creates the missing ones. Each new piece comes with its conflicts already checked.
How do I change a piece?
Click its title (or the pencil) and its record opens. Change whatever is needed and click Save: everything is saved at once.
- Working title, type, page intent and cluster.
- Owner (a person in your company) and outside author: a CRM contact, with its magnifying glass (F2).
- Expected date: with a date, an idea changes to planned; without a date, it goes back to being an idea.
- Main query and secondary queries, one per line. The ones you remove become free.
- Planned address (the full address, the path or just the slug) and WordPress draft ID: with them the synchronisation links the piece to its page as soon as it appears. See below.
- Notes for whoever writes it.
The status is changed in its drop-down on the record, and it is saved straight away.
If the piece has a date, when you save the warning also says what the calendar warns about: another piece from the same cluster too close, a week with too many pieces or the same intent repeated in the cluster. Warning doesn’t stop you saving. To see the whole spread, drag pieces from one day to another or skip a warning with its reason, use the editorial calendar.
When you save, its conflicts are checked again. The record shows them at the top: the colour, what is best to do and each signal with its proof. From there you can Accept the conflict with a reason, go to the page that already exists or Check again. See content conflicts.
And the piece’s brief?
At the bottom of its record, Piece brief: what the piece has to say to win its query without overlapping its sibling pages in the cluster —SEO title, H1, meta description, sections, questions, internal links with their anchor text and what it shouldn’t cover—. Prepare brief requests it from the AI with your website’s data (the cost is shown next to the button: 60 credits, only if it is saved); you can change it by hand, Save brief and Copy to pass it on to whoever writes it. If you changed it by hand, preparing it again asks you before replacing it. See a piece’s brief.
What statuses does it have?
| Status | What it means |
|---|---|
| Idea | No date. It can be removed, merged or changed |
| Planned | With an expected date |
| In progress | It is being written, reviewed or is ready to go out |
| Published | It is already on the website |
| Discarded | It isn’t going to be written. Its queries were freed |
What do I do with several pieces at once?
Tick their boxes. A bar appears with:
- Move to and Change status.
- Send to the board: one task per piece on the publishing board.
- Merge all into: choose the piece that remains and click Merge. The queries of the others pass to it as secondary ones, and the others are discarded. That is how two queries are brought together in one piece: one main and the other secondary.
- Discard: they stop counting in the plan and their queries become free. A query in a cluster stays in its cluster, without an owner, waiting for another piece or page. A piece that is already on the website isn’t discarded.
A discarded piece can be recovered from its record (filter by Discarded to see it), but its queries don’t come back by themselves: give them to it again. While it is discarded, it remembers which queries it had: Create the missing pieces doesn’t propose them again.
What happens to the pieces if I change the clusters?
- Moving or splitting queries to another cluster also takes the piece whose main query leaves, if that leaves all its queries in the same cluster. If the piece has queries in different clusters, it doesn’t move by itself: the warning tells you and you change it yourself.
- Merging two clusters passes their pieces to the one that remains.
- Deleting a cluster leaves its pieces without a cluster (they stay in the plan) and its queries too. A query that was only in the cluster, without an owner, leaves it.
How is the piece linked to its page?
By itself, in the website synchronisation. The ERP recognises the piece’s page like this, from most to least reliable:
- By the WordPress draft ID, if you put it on the record.
- By the planned address: the full address or path, or just the slug (valid if only one page has it).
- By a very similar title, only among the new pages. This is only a proposal: the piece says ‘Is this it?’ and you decide on its record with Yes, link it or It is not this one (and it isn’t proposed again).
When it is linked, the page becomes the owner of the piece’s queries, with everything you decided unchanged (role, cluster). If the page had no target query, it takes the piece’s main one. The piece is published as soon as the page is published on the website; if it is still a draft, the next synchronisation that sees it published marks it.
No synchronisation changes what you decide in the plan: it only links the piece and marks it published. If the piece is the one for a guest’s article, the guest post also changes to published, with the page’s address.
How do I know whether a published piece is ranking?
By its 30-day and 90-day measurement, below its status: what Google said about its page for its main query when it reached 30 and 90 days since publication. For example, ‘At 30 days (data up to 27/09/2026): position 41,6 · 120 impressions’ or ‘Google wasn’t showing it for its main query’.
It is recorded by itself, once, and doesn’t change after that: it is the snapshot of that moment. It is recorded by the ‘Medir a los 30 días’ schedule, the weekly maintenance review and opening the Maintenance tab (with the Changes permission). The website needs to be connected with Google.
If after 90 days it isn’t in the top 10, the maintenance of published content proposes refreshing it.
And the publishing board?
A piece can be sent to the publishing board even if it has no page: it goes into Idea (or into the column for its status). From there:
- Moving its task on the board changes the piece’s status: to Idea, idea (or planned if it has a date); to Borrador, Revisión SEO or Listo, in progress; to Publicado, Refrescar or Medido, published.
- Changing the piece’s status moves its task to the matching column, if it isn’t already in one for that status.
- Discarding the piece cancels its task.
- The piece’s date goes to the task when it is sent to the board; changing the task’s date afterwards doesn’t change the piece’s.
- When the piece is linked to its page, the page stays in the same task: no other one is created.
If you don’t have the board, Create editorial board, top right, creates it; if you already have it, the button is called Complete the editorial board and it adds the columns and example schedules it is missing.
Can I ask the assistant to do it?
Yes. ‘Which articles do we have planned for the website’ or ‘which pieces in the verifactu cluster are still ideas’ reads the plan, and ‘plan an article about what verifactu is for 15 November’ adds a piece. ‘If I write an article about what verifactu is, does it conflict with anything?’ checks the conflicts of a title or a query before creating anything, and ‘what is going out on the blog this month’ reads the calendar with its warnings and the gaps in the goals. ‘Prepare the brief for the verifactu article in the editorial plan’ prepares its brief (and uses credits). Like every assistant action, it shows it to you before doing it, and it does the same as the tab.
What permissions are needed?
To see the plan and each piece’s brief, View on Search visibility. To add, change, merge, discard, create the missing pieces, check and accept conflicts, and prepare or change the brief, Changes. To create or complete the board, Create.
What doesn’t the editorial plan do?
- Queries live in the Google Ads dashboard’s bank: in an installation without it, pieces have no queries and their conflicts only look at the title and the intent.
- Discarding a piece frees its queries, it doesn’t veto them: with Include discarded ones, Create the missing pieces creates one for it again. If you never want a piece for a query, veto it in Guidelines or take it out of the cluster.
- By title, only the pages that appeared after the piece was planned are proposed. A draft started earlier in WordPress is linked by its ID or its address.
- A piece already linked to its page has no Conflict column: from that moment on, the conflicts between pages watch over it.
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 content map: what each page of your website targets
- The Looker Studio dashboard: your content map alongside what Google measures