Skip to content

Content conflicts: your pages that overlap

A conflict is a pair of pages on your website that compete for the same Google query: they are so similar, or so clearly target the same thing, that Google doesn’t know which one to show and both do worse. This is cannibalisation. The ERP looks for them by itself each time it reads your website and leaves them in a tray so that you can decide what to do with each one. It is in Marketing → Search visibility, Conflicts tab.

And better than fixing a conflict is not creating it: each piece in the editorial plan is compared with what is published and with what is planned before it is written. See and a piece that isn’t on the website yet?.

How does the ERP know that two pages overlap?

In three ways:

If the ERP has the assistant’s meaning model installed, it also finds titles that say the same thing in other words: ‘Free Verifactu: can you get it?’ and ‘Is it possible to download Verifactu?’ hardly share any words, but they ask the same thing.

Which pages can conflict?

Only those Google can show:

And the blog categories (they are navigation, not destinations) and what is in Other (the legal notice, the contact page, what the rules couldn’t classify) don’t compete by title. By target query and by query shared in Google they do: if you give a category a query, it means you want it to target it, and if Google shows it instead of your pillar page, it is taking visits away from it.

How do I read a conflict?

The tray shows, for each conflict:

At the top, the buttons count the conflicts in each status and filter by it. The search box searches the titles and addresses of the two pages, ignoring capitals and accents, and the drop-down filters by conflict type.

Clicking a conflict opens its record with the two pages side by side: title, SEO title, scope, cluster, target query, intent, status and address of each one. It is what you need to decide which one keeps the query.

What do I do with a conflict?

You choose one of the four outcomes, which are the ways of ending a cannibalisation:

OutcomeWhat is done on the websiteWhen
DifferentiateEach page is rewritten towards its own query: different title, headings and approachBoth make sense separately, but they are written for the same thing
MergeOne absorbs the other and the other redirects to itThey say almost the same thing: two blog posts on the same topic
De-optimiseOne stops targeting the query: it is removed from the title and headings and links to the otherOne is the good one and the other has to keep existing for another reason
NoindexOne leaves Google’s index (‘noindex’): it stays on the website for whoever browsesA page that has no reason to appear in Google: a listing, a pricing page for another product

Marking the outcome in the ERP doesn’t change your website: it records what was decided. The change is made in WordPress (or on your website), and the next time the ERP reads it, it will check whether it was enough.

In addition:

To decide you need the Changes permission on Search visibility; with View you can see the tray, but not change it.

Can a conflict come back?

Yes, and that is how the ERP checks the fixes:

A conflict that is right on the limit doesn’t close and open with each new page you publish: to close by itself, its score has to drop clearly.

When are conflicts looked for?

Each time the ERP reads your website (see sync your website), after bringing the map up to date. And whenever you want, with Detect now in the Conflicts tab: it looks for them again with the map as it is, without reading the website. Use it, for example, after giving two pages the same target query.

When a new conflict appears (or one that was closed comes back), the ERP warns with the event ‘Two pages on the company website overlap’, to which a task schedule can be attached: create a task for marketing, send a notification… The first time a website’s conflicts are looked for, you aren’t warned about each one: they were already on your website, and they are all in the tray.

And a piece that isn’t on the website yet?

Each piece in the editorial plan is compared with what is published (the published and indexable pages in the same language), with what is planned (the other pieces in the plan that aren’t discarded, including the guest posts on your website) and with the guest posts you publish on other websites, by the query they target: an article of yours on a domain with more authority can take your piece’s position. Six signals are checked:

SignalWhat it looks atColour
Same search queryIts query is already the main query of another page, of another piece or of an article of yours on another website, or another one covers it in passingRed if it is the one the piece targets; amber if the piece or the other only covers it in passing
Already ranks in GoogleGoogle already shows a page of yours for that query (Search Console)Red up to position 30; amber further down
Similar titlesThe words in the titles, just as between pagesAmber; red if they say exactly the same words
Same meaningTitles that say the same thing in other wordsAmber
Shared Google resultsIts query and that of another owner share at least 4 of the top 10 results: for Google they are the sameRed
Same intent in the clusterAnother piece or page in the same cluster with the same intentAmber

The piece’s colour is that of its strongest signal (with no signals, green), and with it comes what to do:

Each signal comes with its proof (which query, which words, how many impressions, in what position, how many results in common) and a link to see what it conflicts with. If something couldn’t be checked —the website isn’t connected with Google, the query has no saved Google results, there is no meaning model—, the record says so: a green without that data isn’t the same as a green with it.

When is it checked? When you add the piece, when you change it (its title, its queries, its intent, its cluster), when you create it with Create the missing pieces, with Check conflicts in the editorial plan, with Detect now in this tab and every night if you turn on the example schedule ‘Comprobar los choques del plan editorial cada noche’ (it starts paused, like the others: see the publishing board). A page that is published or a query that Google starts showing you for changes the colour the next day.

Accept the conflict. If marketing decides the piece is written anyway (‘the page sells and the piece teaches’), on the piece’s record type the reason and click Accept the conflict: the column changes to Accepted and doesn’t warn again as long as the piece, or what it conflicts with and why, doesn’t change. If it changes (another title, another query, a new page that also conflicts), it warns again. Warn again withdraws the acceptance. The figures in the proof (a page gaining a few impressions) don’t count as a change.

Below the tray of conflicts between pages, this tab shows the pieces in the plan that conflict and haven’t been accepted, red ones first. They are dealt with on their editorial plan record.

The thresholds (the similarity of titles and of meaning, the Google results in common, the minimum impressions and the position that makes a conflict red) are changed by marketing in Guidelines → Weights and thresholds, Conflicts when proposing a piece group.

Can I ask the assistant to do it?

Yes. The assistant looks things up in the tray (‘which pages on the website overlap?’, ‘is there cannibalisation on the blog?’, ‘what conflicts does the time tracking page have?’) and can record what was decided (‘conflict 12 is resolved by merging the two pages’, ‘dismiss conflict 7’). Like every assistant action, it shows it to you before doing it, and the result is the same as on screen.

Before proposing a piece it can also check it: ‘if I write an article about what verifactu is, does it conflict with anything on the website?’, with a title, a query or a piece from the plan. It only looks: it doesn’t create the piece or save anything.

What doesn’t the detector see?

Back to search visibility.

More about Search positioning