Manager, Content Marketing · Headout · October to November 2024

Recovering Traffic and Revenue After a Bottom-of-Funnel Keyword Ban

A supply partner required a bottom-of-funnel keyword to be removed from a page that ranked first for it. The page recovered to position 1.3 in 32 days without breaching the agreement.

Of the collection’s organic revenue

From this one page. A share of the collection, not a company figure.

Conversion rate on the page

Why a ranking drop here was not an SEO inconvenience.

Drop to full recovery

13 October to 14 November 2024. It has held position since.

Overview

High-Risk De-Optimisation: How We Recovered #1 Rankings After a Forced Keyword Removal

On 10 October 2024, a supply partner red-flagged a bottom-of-funnel keyword on a high-revenue collection and required us to remove every mention of it: from the page copy, from the metadata, and from the URL. We had been ranking first for that term, which was the reason the request existed.

Complying was not optional. The page carried 39% of the collection’s organic revenue at a 9.9% conversion rate, so the question was never whether to comply but how much of the ranking we could keep while doing it.

The problem

Ranking dominance became the restriction

The page had been ranking consistently at position 1, which was exactly why the supply partner and competitors could not rank for the same term themselves. Complying meant more than a word swap: removing every mention from content, metadata and the URL, deleting and redirecting the dedicated page, and accepting the risk of a significant loss in traffic and revenue along the way.

The changes went live on 13 October 2024. Average position moved from 1.1 to 3.8 the same day, and traffic followed it down immediately. Page one to the bottom of page one is not a small move when the page converts at nearly ten percent.

The approach

Five moves, inside what the restriction actually covered

The restriction was on a specific term, not on the intent behind it, and search engines resolve intent rather than matching strings. The recovery was built on finding somewhere else for the same intent to live, then carrying every ranking signal the old page had earned across to it.

  1. Step 1

    Find an alternate term

    Researched an alternate bottom-of-funnel term with the same search intent and real search volume, and no partner restriction attached to it.

  2. Step 2

    Redirect and rebuild the URL

    Built a new page at a URL carrying the alternate term and 301-redirected the old one, so accumulated ranking signals transferred rather than being abandoned.

  3. Step 3

    Rewrite content and metadata

    Replaced the banned term throughout the copy, meta title and meta description with the alternate term, with a short on-page note that the two mean the same thing.

  4. Step 4

    Keep the term in image alt text

    The restriction covered live page content, not image alt text, so the banned term stayed there, preserving a relevance signal in the one place the agreement did not reach.

  5. Step 5

    Update backlink anchor text

    Updated anchor text on external backlinks to the banned term and pointed them at the new URL, signalling that the new page answered the query the old one used to.

Impact

Impact and timeline

  1. 10 Oct 2024

    The supply partner issues the restriction, requiring the term’s removal from products, pages and the URL.

  2. 13 Oct 2024

    Changes go live. Average position drops the same day, and traffic follows it down.

    1.1 → 3.8

  3. 14 Oct 2024

    The alternate term is identified, the new page built, and redirects set up.

  4. 20 Oct 2024

    Content and metadata fully rewritten around the alternate term.

  5. 25 Oct 2024

    Image alt text and backlink anchor text updated.

  6. 14 Nov 2024

    Position recovers, and holds.

    Recovered to 1.3

  7. Since Nov 2024

    The page continues to hold its position, keeping the revenue channel stable while staying fully compliant with the partner’s restriction.

Average ranking position, after the forced change

3.8

Where compliance left it, 13 October

1.3

Recovered by 14 November, and holding

Before3.8
After1.3

Average SERP position

It had been at 1.1 before the change, so 1.3 is a recovery and not an improvement. Saying otherwise would be claiming credit for a problem we were handed.

Google Search Console performance chart for the affected page, showing average position recovering from the October 2024 drop back to 1.3 by mid-November 2024, with total clicks, impressions and CTR summarised above the chart.
Google Search Console data for the affected page: average position recovering from the October 2024 drop to 1.3 by mid-November 2024.

What I’d tell someone else

Read the restriction narrowly

Read the restriction narrowly and precisely, then work only inside what it actually says. The instinct is to treat a partner request as a blanket ban and give up the ranking, or to ignore it and hope. Neither is necessary. The agreement covered live page content, and everything we did to recover the position was in the places it did not reach.

Google Search Console, Google Keyword Planner, Ahrefs, Screaming Frog and Looker Studio did the measuring and the mapping throughout, alongside a few other standard SEO tools.