When a Market Leader Shuts Down, the Winner Is Whoever Captures the Migration Traffic First. Feedly Did It in 2 Days.

The Play

When Google announced Reader's shutdown in March 2013, Feedly had 4 million users. They had been building slowly against the RSS giant for years.

Then Google made the announcement. Reader was shutting down on July 1.

Feedly published a migration guide within hours. They built a one-click importer that preserved every subscription from Google Reader. They emailed their existing users asking them to spread the word. And they owned the search result for "Google Reader alternative" before any competitor could respond.

In 48 hours, 500,000 Google Reader users migrated to Feedly.

Why This Works Every Time

Platform shutdowns create a predictable pattern:

1. Announcement drops

2. Users panic-search for alternatives

3. "Where to go" threads explode on Reddit, Twitter, Discord, HN

4. The first credible alternative in those conversations owns the conversion

Most competitors respond on day three or four, when the peak search traffic has already been captured. Feedly had already published their migration guide before the Reddit thread had 100 comments.

The search traffic from platform shutdowns is among the highest-intent traffic that exists. A user searching "Sora alternative" has a problem, a workflow, and a budget. They are not researching. They are deciding. The first landing page that answers "we have what you need, and here's how to migrate" wins.

The ARC-AGI-3 and TurboQuant Parallel

This playbook does not only apply when a competitor shuts down. It applies anywhere a previously dominant option becomes unavailable or undesirable:

• Google changes an algorithm, killing traffic to a category of sites
• A major API raises prices 10x and developers need an alternative
• An enterprise vendor gets acquired and customers start evaluating exit options
• A regulatory change makes a product unavailable in a jurisdiction

The displacement pattern is the same. The users need somewhere to go. The first product to raise its hand gets the bulk of the migration.

The Technical Setup

The migration play has three components, and you need all three:

The content layer: An "[X] Alternative" page that ranks organically. This needs to exist BEFORE the shutdown. The ideal is to already rank for "[competitors] alternative" before any shutdown is announced. When the shutdown happens, you move from page two to page one overnight because the search volume spikes 100x and the existing indexed page captures that spike.

The migration tool: Whatever reduces friction from "I was using them" to "I'm now using you." An importer that preserves data is best. A setup wizard that replicates the previous workflow is second best. A templated setup guide for the most common migration paths is the minimum.

The community play: Post in the displacement threads, not with ads but with the migration guide. When someone asks "what replaces Sora?" on Reddit, the response that links to a genuinely helpful migration guide gets upvotes. Those upvotes multiply the organic reach. The community does the distribution.

The Sora Moment

OpenAI shut down Sora on March 24. The HN thread had 1,119 points and 833 comments. Thousands of creators, developers, and marketers are looking for alternatives right now.

Kling, Runway, Pika, and Luma all have a version of this page. But they built them months ago and the SEO is stale. A new "Sora alternative" page, published in the first week after the announcement, targeting that specific search intent, will rank against content that was not optimized for this exact query.

The migration opportunity from Sora is live today. It will be significantly smaller by April 15.

What to Track

The metric that matters for this play is: how many new signups reference "Sora alternative" or equivalent search terms in the first 30 days after the shutdown?

If you are capturing 5% or more of your normal signup volume from displacement traffic, the play is working and worth investing in for future platform shutdowns in your space.

The best version of this strategy is a standing process: watch for platform shutdowns, have an "[X] Alternative" page template ready to deploy, and move within hours of any announcement. The competitive landscape does not change fast. But platform shutdowns happen several times a year in any category. Over three years, a systematic approach to capturing displacement traffic compounds into a significant acquisition channel.

Feedly used one shutdown to add 500K users. They became the default RSS reader for a decade. The same play works for any platform shutdown in any category. The only question is whether you are watching and ready to move.