Everyone Says Google Killed RSS. Thirteen Years Later, That's Half Right.

Browse the web today and something feels off. Search results repeat the same three sentences in slightly different arrangements. Click through and you land on a page buried in ads, newsletter modals, and cookie banners. Somewhere in there you remember that we used to have a quiet way to read only the things we chose to read. What happened to it?

March 13, 2013

Google announced the shutdown of Google Reader on March 13, 2013. The service went dark on July 1 that year. The stated reason was short: usage had declined.

The reaction was not short. A petition to keep the service alive collected more than 150,000 signatures. Hacker News and the developer corners of Twitter talked about nothing else for days. Google didn’t blink. This was the height of the Google Plus era, when the company was betting its future on a social network, and Reader was a product that actively worked against that bet. A user scanning headlines in Reader and clicking straight through to the source is a user Google never gets to show an ad to.

The part that mattered most was structural. Reader wasn’t just an app. It was the de facto sync infrastructure for the entire RSS ecosystem. Most third-party readers — NetNewsWire, Reeder, dozens of mobile clients — used Google’s sync servers as their backend. When Google pulled the plug, everything sitting on top of it collapsed at once. That’s the predictable cost of a free product owning a market: by the time it leaves, the commercial alternatives that might have replaced it starved out years earlier.

The browsers quietly deleted it too

The shutdown wasn’t a single event. RSS got erased from browsers in slow motion.

Firefox removed Live Bookmarks in version 64, released in 2018. That orange RSS icon that used to sit next to the address bar? That’s when it disappeared. Chrome barely shipped native feed support at all, ran a “Follow” experiment in 2021, and shelved it quietly in 2023.

Losing the icon matters more than it sounds. For a mainstream user, a feature with no visible entry point does not exist. RSS kept working the entire time — but every door leading to it closed one by one. Today, checking whether a site has a feed often means viewing source and searching for a <link rel="alternate"> tag. That’s not a technology problem. That’s a discoverability death sentence.

The counterargument is stronger than you’d expect

Three objections deserve a real hearing.

The first: RSS might have been better off without Google Reader. A dominant free product left no room for anyone to test a paid model. And the evidence isn’t bad. In the two weeks after the shutdown announcement, Feedly added 3 million new users. Inoreader and NewsBlur grew fast in the same window. You can read 2013 as the moment the market reopened rather than the moment it died.

The second objection cuts deeper. People never wanted subscription. They wanted recommendation. RSS makes you do the work: pick your sources, prune them, maintain them. Let it sit for a week and you’re staring at 999 unread items and a low-grade sense of failure. The Twitter and Facebook timelines asked nothing of you and served something interesting anyway. For most people that trade was obvious. On this reading, Google didn’t push RSS off a cliff — it read the room and left.

The third is simply factual. RSS did not die. The entire podcast industry still runs on it. Apple Podcasts, Spotify, and YouTube Music all ultimately parse RSS feeds. Substack attaches a feed to every publication. Every WordPress install on earth still emits one by default. What died was never the protocol. It was the consumer-facing interface.

Why AI slop is dragging RSS back into the conversation

Here’s where 2026 gets strange.

The web’s dominant problem right now is machine-generated filler — slop, in the vernacular. Search results open with an AI summary, the links below it lead to pages assembled by other models, and referral traffic to original publishers keeps sliding as Google answers more queries without sending anyone anywhere.

Against that backdrop, RSS’s limitations start reading as features. There’s no algorithm. Items arrive from sources you chose, in publication order, with nothing inserted based on a guess about your interests and no ad injected between them. You judge the credibility of the source yourself. And when the practical test for whether something was written by a person has collapsed back to who published it, subscribing at the publisher level suddenly makes sense again.

There’s counter-pressure, though, and it’s real. AI crawlers scrape aggressively, so some publishers are cutting full-text feeds down to summaries or removing them entirely. The openness that made RSS useful is exactly what makes it exploitable. Right now the people trying to revive RSS and the people trying to close it off are moving at the same time, and it isn’t obvious which side wins.

The question that actually matters

“Google killed RSS” is half true. Google did kick out the last major piece of infrastructure supporting an already-fading technology, and that decision set the recovery back by more than a decade. But the migration to algorithmic feeds was underway before Reader shut down, and it would have happened without Google’s help.

The more interesting question is about us. We gave up the inconvenience of choosing for ourselves remarkably fast — and got a decade of algorithmic curation in exchange, which seemed like a good deal until the algorithms started serving us machine-written filler they can’t distinguish from the real thing. So: are we willing to take that inconvenience back? If you’re reading this in a feed reader, you’ve already answered.