The Redirect That Killed a Ranking

Organic traffic to their most important page fell 90% in a single week. They spent three months rewriting content before finding the real problem.

By WebSignalytics Inc.  ·  26 Jul 2026  ·  7 min read

The scenario

Farlow Migration Law is a boutique immigration law firm — three lawyers, one paralegal, a small downtown office. Their client acquisition model is almost entirely inbound: people searching for help with Canadian work permits find the firm through Google, read their content, and call. Sandra, the managing partner, built the firm's website herself over several years and understands, better than most small business owners, how much a single well-ranking page can be worth.

That page was a comprehensive guide to Canadian work permits — eligibility requirements, processing timelines, common mistakes, the works. Sandra had published it two and a half years earlier and refined it steadily since. It had earned its way to page one for several high-intent queries: terms like "Canadian work permit lawyer," "LMIA exemptions explained," and "how to apply for a Canadian work permit." Over time, it became the firm's primary lead source, driving roughly 480 organic sessions per month and a reliable stream of consultation requests.

When Sandra decided to clean up the firm's domain structure — consolidating a subdomain into the main site — she hired a freelance web developer to handle the technical migration. It was described as a straightforward job: no content changes, just URL restructuring and redirect setup. The freelancer completed the work over a weekend. Sandra checked the site Monday morning, everything appeared to be in place, and she moved on. Two weeks later, she opened GA4 and saw that organic sessions to the work permit guide had collapsed from 480 to under 40 in a single reporting week.

The confident wrong conclusion

The timing was suspicious in a way that felt almost explanatory: a significant Google core algorithm update had rolled out in the same window as the migration. Sandra had been following SEO news long enough to know that core updates sometimes reshuffled rankings dramatically, even for pages that had done nothing wrong. The content hadn't changed. She hadn't built any questionable links. But the timing aligned, and a 90% traffic drop is exactly the kind of damage a core update can inflict when Google reassesses a page's expertise and authority signals.

She hired a content consultant who spent three months on the guide: deepened the legal analysis, added a structured FAQ section, improved internal linking from related pages, refreshed the schema markup. The work was genuinely good. The traffic didn't move. The guide remained invisible in organic search. By month three, Sandra was beginning to wonder whether the page had been permanently demoted — whether two and a half years of ranking signals could simply be wiped out by a single algorithm cycle.

The overlooked redirect type

A second consultant Sandra brought in didn't start with the content. He started with the migration. Specifically, he ran a redirect check on the original URL — the old address the work permit guide had lived at before the domain restructuring. What he found was a 302 redirect pointing from the old URL to the new one. Not a 301. A 302.

The difference sounds technical and minor. In practice, it is catastrophic for SEO. A 301 redirect signals to Google that a URL has permanently moved — it transfers the page's accumulated ranking signals, its link equity, its PageRank, to the new destination. A 302 redirect signals that the move is temporary. Google treats this as an instruction to preserve the original URL as the canonical — keeping its authority anchored to the old address — while the destination URL starts fresh with none of that history. The freelancer had almost certainly used 302 as a default, possibly without understanding the distinction.

GA4 confirmed the picture once the consultant knew where to look. The new URL showed occasional direct traffic — visitors who had bookmarked the page or followed a link someone had shared — but zero organic sessions. The new URL had never ranked because it had never received the authority transfer. The old URL still held all the accumulated ranking signals, but it was now a redirect pointing somewhere else, so Google wasn't serving it either. The result was a stalemate: authority on a URL that no longer served content, and a new URL that Google had no reason to rank.

The corrected interpretation

There had been no algorithm penalty. Google hadn't reassessed the page's expertise or decided the content was thin. The work permit guide was exactly as authoritative as it had always been — but that authority was stranded on an address that no longer existed as a destination. The ranking had been transferred nowhere. A single character difference in a server configuration — a 3 instead of a 0 — had silently broken everything.

Once the 302 was corrected to a 301, Google reprocessed the redirect and began transferring the ranking signals to the new URL. Within about six weeks, the work permit guide had returned to page one for its primary queries and organic sessions had recovered to within 15% of the pre-migration baseline. The three months of content work hadn't been wasted — the improved guide likely performed even better than the original — but none of it would have mattered if the redirect type had never been corrected. A technical problem requires a technical fix.

What to do next

If you've changed any URLs on your site — through a migration, a restructure, or even renaming a single page — verify the redirects before you diagnose anything else:

• After any site migration or URL change, always verify the redirect type using a redirect checker tool — 301 transfers link equity permanently; 302 signals a temporary move and withholds authority from the destination URL.
• Use GA4 to check organic traffic by exact landing page URL in the Pages and Screens report after a migration — if the new URL shows zero organic sessions while the old URL had hundreds, the ranking transfer has almost certainly failed.
• Check both the old and new URLs in Google Search Console's URL Inspection tool to see which one Google considers the canonical; if the old URL is still being indexed, the 301 redirect either wasn't set or wasn't processed correctly.
• Treat content rewrites as a last resort, not a first response — a sudden organic traffic drop following a technical change is a technical problem until proven otherwise; diagnose the infrastructure before touching the copy.
• When briefing a developer or freelancer on any migration work, explicitly specify that all redirects must be permanent 301 redirects and request confirmation that the type has been verified after implementation.

For how to use GA4 to spot pages that aren't getting organic traffic and investigate why, see How to Use GA4 to Spot Pages Google Isn't Sending Traffic To.

Farlow Migration Law and Sandra are illustrative — a composite created to demonstrate a real and common pattern.