Two of Your Pages Competing for the Same Keyword? Find and Fix It

By Idea to Traffic Editorial Team · Published October 26, 2026 · Last updated October 26, 2026

A site that stalls after a few months of steady publishing usually gets the same diagnosis: not enough backlinks. Sometimes that is right. Just as often the real problem is closer to home. Two or three of your own pages target the same search, Google keeps switching between them, and none of them builds enough strength to hold a good position. This guide shows how to confirm that in Search Console in about ten minutes, how to tell a real conflict from a harmless one, and which of four fixes to use.

What competing pages actually look like

Keyword cannibalization is not a penalty. Google does not punish you for having several pages about similar things, and plenty of healthy sites rank two URLs for one query. The trouble starts when Google cannot decide which of your pages is the best answer. You will usually see three symptoms together:

• One query shows two or more of your URLs in Search Console, and the clicks are split between them instead of going mostly to one.
• The average position for that query swings by 5 to 20 places from week to week, and the swings line up with the ranking URL changing.
• Neither page reaches the top 5, even though each one alone looks like it should.

On a new site this happens for a predictable reason: you wrote a broad guide early, then wrote a narrower post later that answers the same question in more detail. Both now say the same thing to Google.

Find it in Search Console in 10 minutes

You do not need a paid tool for this. Search Console has the data, it just hides it one click deep.

1. Open Search Console and go to Performance > Search results.
2. Set the date range to the last 3 months. A shorter range is too noisy on a small site.
3. Switch on all four metric cards: Total clicks, Total impressions, Average CTR and Average position.
4. Click + Add filter > Query, choose Queries containing, and type your main keyword. Use the shortest phrase that still means the topic, for example unscramble rather than best word unscrambler online.
5. With the filter on, open the Pages tab below the chart. Every URL listed there got impressions for queries containing that phrase.

If one URL holds 80% or more of the clicks, you are fine. If two URLs each hold a meaningful share, say 30% or more, write both down. That pair is your candidate.

To confirm it, click one of the two URLs in the Pages tab to add it as a second filter, then switch to the Queries tab. Note its top 10 queries. Remove that page filter, add the other URL, and compare. Heavy overlap in the top queries, with both pages sitting between positions 8 and 30, is a real conflict.

For a sitewide sweep, export the data instead. In the Performance report click Export > Download CSV. The export from the web interface is capped at 1,000 rows per table, which is plenty for a site under a few hundred pages. If you want to pull query and page together in one table, the Search Console API returns both dimensions at once. A short request body looks like this:

{
  "startDate": "2026-07-26",
  "endDate": "2026-10-25",
  "dimensions": ["query", "page"],
  "rowLimit": 5000
}

Load the result into a spreadsheet, sort by query, and highlight every query that appears with more than one page. A pivot table with query as the row and a count of pages as the value gives you the list in one step.

Harmless overlap or real damage

Not every pair needs fixing. Before you merge anything, check these three things:

• Intent. Search the query yourself. If Google shows a mix of guides and tools, a calculator page and a how to article can both rank without hurting each other. They answer different needs.
• Volume. If the shared query has fewer than about 50 impressions over 3 months, the conflict is too small to matter. Spend the time elsewhere.
• Positions. If one page sits at position 3 and the other at 40, Google has already chosen. Leave the winner alone and improve the loser for a different query instead.

The pairs worth fixing are the ones where both pages sit on page one or two, the query has real impressions, and the intent is the same.

Four ways to fix it, from strongest to lightest

1. Merge and redirect. This is the right fix most of the time. Pick the stronger page, using clicks and backlinks as the tiebreaker. Move anything useful from the weaker page into it, then send the weaker URL to the stronger one with a permanent 301 redirect. On Cloudflare Pages that is one line in a _redirects file at the root of your build output:

/word-unscrambler-tips /how-to-unscramble-words 301

Then update every internal link that pointed at the old URL so it points straight at the new one, and remove the old URL from your sitemap. Redirects pass signals, but direct internal links are cleaner and faster for Google to process.

2. Re-target the weaker page. If the weaker page has its own value, keep it and change its job. Rewrite its title, H1 and opening paragraph around a narrower query that the main page does not cover well. Look at that page's own query list in Search Console for a hint: it often already gets impressions for something more specific.

3. Canonical tag. Use this when both pages must stay live for users, such as a print version or a filtered listing. Add this to the head of the duplicate page:

<link rel="canonical" href="https://example.com/how-to-unscramble-words">

A canonical is a hint, not a command. If the two pages are not close to identical, Google may ignore it, so it is a poor tool for two different articles.

4. Fix internal links only. Sometimes the conflict is self made through anchor text. If ten posts link to page A with the words "word unscrambler" and five link to page B with the same words, you are telling Google both pages are about that phrase. Pick one target and point every exact match link at it.

Whatever you do, avoid the two common mistakes: deleting a page without a redirect, which throws away its signals and leaves a 404, and setting the weaker page to noindex while still linking to it heavily from your menu.

What to expect after the fix

After a merge, use the URL Inspection tool on the winning page and click Request indexing. Then give it time. On a small site Google usually processes the redirect within a few days to two weeks, and the position settles over the following 2 to 6 weeks. During that time it is normal for the query to dip before it climbs.

Track it properly. In Performance > Search results, keep the query filter, then click the date control and choose Compare with 28 days before the change against 28 days after. You want to see clicks concentrated on one URL and the average position line flattening out. If the old URL still shows impressions a month later, check that the redirect returns a real 301 and not a 200 or a chain of hops:

curl -sI https://example.com/word-unscrambler-tips | head -n 3

The first line should read HTTP/2 301 and the location header should point at the winning page in one step.

If you are not sure whether your redirects, canonicals and sitemap agree with each other, the free Site Checker reads those signals on any URL and flags conflicts like a canonical that points at a redirect. Fix the structure first, then decide whether you still need links.

Prevent it next time

Keep a one tab spreadsheet with two columns: the main query each page targets, and its URL. Before you write a new post, search that sheet for the query. If it already has an owner, either update the existing page or choose a clearly different angle. Five seconds of checking saves a merge three months later, and on a young site every page you consolidate gives the survivors a better chance to rank.

Where this question came from

• The unglamorous checklist I run before touching backlinks on a stalled site (r/juststart)
• Google answers SEO question about keyword cannibalization (Search Engine Journal)

Questions about pages competing for one keyword