Cannibalization resolution

What it is: when two of your published articles compete for the same keyword, BurstWriter recommends ONE best fix for that specific pair and shows its reasoning, alongside a transparent strength score for each article (content depth, links, real Google Search Console traffic, age, freshness) so you can see which is the stronger page to keep. When Search Console is connected, the page actually earning the clicks and impressions weighs heavily — and a weaker page still pulling real traffic is preserved with a canonical rather than merged away.

The three fixes: Consolidate + redirect (merge the weaker into the stronger and 301-redirect the weaker URL); Differentiate (re-target the weaker page to a distinct keyword/angle so they stop competing); or Set canonical (point the weaker page at the stronger one so ranking signals combine without removing it).

Why it is safe: it is ADVISORY. BurstWriter only prepares its own data — a draft edit, the canonical field, or a "superseded" marker — and snapshots the prior state so any change can be undone. It never 301-redirects, deletes, or edits a live page. Any live-site step (a republish, or a redirect in your CMS) is spelled out for you to do, and only you trigger it.