DaylytixKeyword cannibalization means several of your own pages compete for the same search. Google has to choose between them, the choice can change from week to week, and none of the pages ranks as well as one strong page would. Daylytix flags likely cases from your Search Console data so you know where to look.
How detection works
Daylytix takes your top 25 queries from Search Console and, for each one, looks for crawled pages whose URL or title contains one of the query's words of 4 letters or more. When two or more pages match, the query is flagged, up to 15 queries per audit.
This is a quick heuristic based on wording, not Search Console's own query-and-page data. It finds most real conflicts, but it can also flag pages that only share a word. Always confirm before you change anything (see below).
Where to find it
In the audit: the Search Console tab has a Keyword Cannibalization table with each flagged query and its competing pages.
In the Cannibalization tool (sidebar, Content group): choose an audit from Select an audit to see the full view.
- Summary cards: Total Conflicts, Critical (high traffic), High Priority and Need 301 Redirect.
- Filters by suggested action: All, Critical, 301 Redirect, Add Canonical, Merge, Differentiate, Check First.
- One card per query, with the winner and the weaker page side by side (position, clicks, CTR, impressions), the suggested action, and buttons for Fix Workflow and View in GSC. Cards that suggest a 301 also have Copy .htaccess Rule.
- Export CSV downloads the list.
Severity follows how much traffic is involved: queries whose pages together have 100 or more clicks are critical, 20 or more are high priority.
What each suggested action means
| Action | When Daylytix suggests it |
|---|---|
| 301 Redirect | The winner ranks at least 6 positions higher, or gets at least 4 times the clicks of the weaker page and 30 clicks or more. |
| Add Canonical | The winner ranks at least 3 positions higher, or gets at least twice the clicks. |
| Differentiate | The pages rank about the same, and one looks like a product or shop page while the other is a blog post or guide. |
| Merge & Redirect | The pages rank about the same and look like the same kind of page. |
| Check First | One or both pages have no Search Console figures, so there is nothing to compare. |
Why "Check First" appears. A page can be flagged only because its URL or title contains the query's words, without any Search Console figures behind it. Its position and clicks then show a dash, because they are unknown, not zero. Daylytix does not suggest a redirect, a canonical or a merge on that basis. The card tells you which page has data, if any, and asks you to confirm the conflict first. Use the steps below, and if only one page shows for the query, there is nothing to fix.
Confirm before you fix
- Click View in GSC, or open Search Console's Performance report and filter by the query.
- Open the Pages tab. If more than one of your URLs gets impressions for that exact query, the conflict is real.
- If only one page shows, the pages just share a word and there is nothing to fix.
How to fix it
Merge and redirect. If both pages cover the same topic, move anything unique from the weaker page into the stronger one, then 301-redirect the weaker URL to it and update your internal links.
Differentiate. If the pages serve different needs, make that clear: give each its own focus query in the title, headings and copy, for example a guide for "how to" searches and a product page for buying searches.
Canonical. If you must keep both pages, such as filtered or paginated versions, point the secondary page to the main one:
<link rel="canonical" href="https://example.com/main-page/">Noindex. For thin tag or archive pages competing with real content, keep them out of the index:
<meta name="robots" content="noindex, follow">Use internal links to show the winner
- Link to the page you want to rank more often than to the secondary page.
- Use the query's wording in the anchor text of those links.
- Remove or redirect links that still point to a page you merged.
After the change, run a new audit in a few weeks and check whether the query is still flagged and whether the remaining page climbed.