Review a page before publishing it
The pre-publication review reads a page of your website at that moment and runs ten rules on it: whether its title is the right one, whether it has a query to own, whether it overlaps another page of yours, whether it is in Google as it should be… The result is a traffic light (green, amber or red) with each finding and what to do. It is in Marketing → Search visibility, Map tab, on each page’s record.
How do I review a page?
- In the Map tab, click the page in the grid: its record opens.
- In the Pre-publication review panel, click Review.
- Wait a few seconds: the ERP reads the page from your website at that moment.
- Read the traffic light and, below it, the findings: first the red ones, then the amber ones and finally the green ones.
The review is saved with the page. The grid shows, next to each page’s status, a dot in the colour of its latest review.
To review you need the Changes permission on Search visibility. With View you can see the reviews, but you can’t start a new one.
Why does it read the website again if the map already has it?
Because the review is done just before publishing, and what the map has may be from yesterday. When you click Review, the ERP reads:
- The WordPress post: its current title, status and categories. If it is a draft, also its text (the website needs to be connected with the application password of an Editor user).
- The published page, just as Google sees it: the SEO title, the meta description, the robots, the canonical, the H1s, the hreflang and the links. What the theme template or Elementor adds is only there.
- The other versions in other languages that the page annotates, to check that they annotate it back.
Reviewing changes nothing on your website or on the map. The synchronisation keeps the map up to date.
How do I read the traffic light?
The traffic light is the colour of the most serious finding:
| Traffic light | What it means |
|---|---|
| Red | There is something to fix before publishing. As it is, the page loses visits or takes them from another page of yours. |
| Amber | It can be published, but it is worth fixing what it says. |
| Green | Nothing to fix with the rules your website has turned on. |
A green finding isn’t a problem: it tells you something worth knowing, for example that the page is a draft and there are things that can only be checked once it is published.
Each finding says which rule found it, what is happening and, with a light bulb, what to do. If it mentions another page of yours (the one with the same title, the one targeting the same query), Open the other page opens it in the record.
What happens if it reviews a draft?
For a draft there is no published page to read. What can already be checked is checked: the title, the target query, whether it overlaps another page, the cluster category, and in the draft’s text its H1s and whether it links to its pillar.
The SEO title, the meta description, the robots, the canonical, the hreflang and what the template adds (the title as H1, the related articles blocks) only exist once it is published. A green finding reminds you of this. Review it again as soon as it is published.
What happens if the page couldn’t be read?
If the website doesn’t respond in time, or WordPress doesn’t allow a draft to be read, the review is done with the last thing the synchronisation read and an amber finding says so, with the date of that reading. Review again in a while.
The same applies if your website has an anti-bot (the hosting’s protection or Cloudflare’s) that, instead of the page, gives the ERP its waiting page (‘One moment, please...’, ‘Just a moment...’). The ERP recognises it, doesn’t review it as if it were your page, and the finding says which protection it was and how to avoid it: whoever looks after the website should add the ERP server’s IP or its identification (PowergestERP-Posicionamiento) to its allowlist.
A page that responds with an error (for example, a 404 because it no longer exists) isn’t a reading failure: it is a red canonical finding, because for Google it is a broken page.
What is checked on a page that isn’t in Google?
A published page with ‘noindex’ doesn’t appear in Google, so it doesn’t compete with anyone. For it, the title according to scope, the target query, the similarity with other pages, the repeated H1, the SEO title and the meta description aren’t checked, and it doesn’t need to declare a canonical.
What is checked is whether it should be in: if it is a sales page, a pillar, an article, a glossary definition or a help guide, Indexable according to scope comes out red. If it really shouldn’t appear in Google, change its scope to Other.
What does ‘Title matches the scope’ check and what do I do if it is flagged?
That the title says the right thing for its scope:
- A Sales page sells: its title doesn’t explain ‘how’ to do something.
- A Help guide teaches: its title doesn’t sell (‘… software’).
- A Blog article isn’t titled only with its cluster’s main query, which belongs to its pillar.
- A Sales page isn’t titled with a single word (‘Accounting’): it doesn’t say what it is looking for or for whom.
What to do: rewrite the title. If the page really teaches, perhaps its scope isn’t the one it has: change it on the record.
What does ‘Target query’ check and what do I do if it is flagged?
That the page has a target query and that no other page of yours in the same language targets the same one.
- Amber if it has no target query. If Rank Math has a keyword, the suggestion mentions it as a hint. It isn’t required of categories or of what is in Other.
- Red if another page targets the same query: the two take visits from each other.
What to do: decide on the record the query this page owns. If another one targets it, decide which one keeps it and change the other one’s, or merge them.
What does ‘Title similar to another page’ check and what do I do if it is flagged?
That no published page of yours, in the same language and that Google can show, has a title so similar that the two overlap. It is the same criterion as the conflicts tray: words in common that distinguish something and, if the ERP has the meaning model, titles that say the same thing in other words. A draft is compared as if it were already published: that is what it is reviewed for.
What to do: if they answer different queries, make the beginning of each title state its own. If they answer the same thing, merge them or make one stop targeting that query.
What does ‘Cluster category’ check and what do I do if it is flagged?
That a blog post belongs to a cluster and is in that cluster’s category. It is flagged if the post is in a cluster and isn’t in its category, if it is in a cluster’s category but has no cluster on the map, or if it doesn’t belong to any. As long as your website has no clusters, it isn’t flagged.
What to do: put the post in the right category in WordPress, or assign its cluster on the record.
What does ‘Link to the pillar’ check and what do I do if it is flagged?
That the page links to its cluster’s pillar page. Links are votes, and the pillar is the one that has to win the topic’s main query. On a published page all its links are checked, including the template’s; on a draft, those in its text.
What to do: link to the pillar from the text, with a few words that state its query.
What does ‘Indexable according to scope’ check and what do I do if it is flagged?
That each page is in or out of Google according to its scope:
- Categories are navigation: they must have ‘noindex’. If Google indexes them, they compete with the pages on their topic.
- Sales pages, Pillar pages, the Blog, the Glossary and Help must be in Google: they can’t have ‘noindex’.
What to do: change the robots in the website’s SEO plugin. If a page really shouldn’t appear in Google, change its scope to Other.
What does ‘Canonical’ check and what do I do if it is flagged?
That the published page responds, doesn’t redirect to another address, and that its canonical is a valid address that points to itself. It is red:
- If the page can’t be read (a 404, a server error).
- If the canonical is broken (for example, it contains spaces).
- If it points to another page or another website: Google will index that one, not this one.
- If it points to the version in another language: that version disappears from Google. Each language is its own canonical; the versions are joined with hreflang.
If the page redirects, or doesn’t declare a canonical (and doesn’t have ‘noindex’), it is amber.
What to do: correct it in the page’s SEO plugin. If it is a duplicate of another, merge them or set it to ‘noindex’.
What does ‘Hreflang’ check and what do I do if it is flagged?
Only if your website is in several languages. It checks that the page annotates its versions in other languages, that each annotation points to a page in that language, that the other version annotates this one back (if not, Google ignores both) and that there is an ‘x-default’ annotation pointing to the main language version. The annotations are read from the page, from the HTTP header and from the sitemap.
What to do: check the settings of the language plugin (Polylang and WPML add them by themselves) or of the SEO plugin.
What does ‘A single H1’ check and what do I do if it is flagged?
That the published page has an H1, only one, and that no other page of yours has the same one. Two pages with the same H1 compete for the same thing, or one is unnecessary.
On a draft its text is checked: if it already has an H1, once published it may have two, because the template usually puts the title as H1.
What to do: keep the main title as H1 and change the other headings to H2. If two pages say the same thing, merge them.
What does ‘SEO title and meta description’ check and what do I do if it is flagged?
That the page has an SEO title and a meta description, and that they fit in what Google shows: the title, between 30 and 60 characters, and the meta description, between 70 and 160. If they are longer, Google cuts them; if they are missing, it makes one up.
What to do: write them in the page’s SEO plugin, with the query at the beginning of the title.
Where do I see previous reviews?
In the same panel, Review history lists the page’s previous ones, with their date, their traffic light and who requested them (the screen, the assistant or a schedule). Click one to see it: the panel warns you that it isn’t the latest.
Can I turn off a rule?
Yes, for a specific website: in the Sites tab, open the website and, in Review rules, untick the one that website doesn’t need (for example, Link to the pillar on a website without a blog). The severity of each rule and what it requires (the lengths, the words a title can’t say…) belong to the company settings and apply to all its websites.
To change the website’s rules you need the Create permission on Search visibility.
Can I ask the assistant to do it?
Yes. The assistant reviews a page (‘review the draft of the Verifactu article before publishing it’, ‘is the time tracking page ready to publish?’) and tells you the traffic light and each finding. Like every assistant action, it shows it to you before doing it, and the review is the same as on screen: it stays in the page’s history.
Can it review on its own?
Yes, with the example schedules of the publishing board:
- Revisar al entrar en Revisión SEO reviews a page as soon as its task reaches that board column and leaves you a task with the traffic light and the findings.
- Explicar una revisión en rojo asks the assistant, when a review comes out red, to explain to the writer in a few sentences what to change and why. It leaves it for you in a task.
They start paused: you start them in Tasks → Schedules.
What doesn’t the review do?
- It doesn’t change your website. It says what to fix; the change is made in WordPress (or on your website).
- It doesn’t change the map. The synchronisation keeps it up to date.
- It doesn’t judge the intent with artificial intelligence. The rules look at the title, the map decisions and what the page publishes. If two pages answer the same thing with titles that aren’t similar, give them the target query: if it is the same, the review sees it. The explanation with the assistant is separate (see above) and uses credits.
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