Who Killed RSS? The Year Google Closed Reader, the Internet Broke a Little

Google never hated RSS.

It loved RSS — loved the millions of users RSS brought in.

Then it shut every door. One by one.

2005: the door opened. 2013: it closed. Eight years, and Google got everything it came for.

The timeline: every step is a textbook move

This wasn’t accidental. It’s a nameable commercial strategy: Embrace, Extend, Extinguish. The term was originally coined to describe Microsoft’s operations against Java and web standards. Google’s treatment of RSS is one of the cleanest executions of that strategy on record.

2005: Google Reader — herding RSS users into a single corral

In 2005, Google launched Google Reader: a free, clean, cross-platform RSS aggregator tightly integrated with Google accounts.

At the time, RSS readers were mostly desktop software. Google Reader moved the paradigm to the web and used Google’s scale to crush every competitor.

Result: millions of users handed Google custody of their subscription lists.

Users’ subscription relationships became Google’s data asset.

2007: Acquiring FeedBurner — controlling the supply side

In 2007, Google acquired FeedBurner, a service that let content creators manage and distribute their RSS feeds.

FeedBurner’s mechanism: it replaced your raw RSS URL with a FeedBurner-proxied one, which injected advertising, tracking code, and analytics. Bloggers using FeedBurner gave Google their readers’ subscription relationships too.

This meant Google now controlled both ends of RSS:

• Consumer side: Google Reader held readers’ subscription data
• Supply side: FeedBurner held publishers’ audience data

2012: FeedBurner API shutdown — cutting off developers

Five years after the FeedBurner acquisition, Google shut down FeedBurner’s API in 2012, severing all third-party integrations built on the platform.

No announcement, no transition period, no explanation.

Countless tools and scripts went dark overnight.

2013 (part one): Google Reader closes — users with nowhere to go

In 2013, Google announced the closure of Google Reader.

The official reason was “declining usage.” A Google engineer who had worked on the project later said: “It felt like during my entire time on the project, there were always various people who wanted to kill it.”

Users were furious. Fury changed nothing.

The deepest impact of closing Google Reader wasn’t losing a tool — it was stranding millions of users with no default path back to RSS.

When Google Reader shut down, there was no suggested replacement, no export tutorial, no guidance toward alternatives. Users didn’t actively abandon RSS; they just lost the on-ramp.

HN user @betenoire:

“Google Reader going away felt like the beginning of the end of the internet as I knew it. I miss websites.”

@adamm255:

“I realise the only place pushing me to an actual website these days are my RSS feeds (self hosted FreshRSS), and HN.”

2013 (part two): Google Alerts RSS removed

The same year, Google deleted RSS subscription support from Google Alerts, forcing users to email-only notifications.

It was later partially restored after user backlash — by which point most users had already left RSS.

Chrome: from “native support” to “quietly removed”

Early Chromium builds had a native feature: if a page had an RSS feed, the address bar displayed an orange RSS icon; clicking it jumped to the feed URL.

That feature disappeared at some point — no announcement, no explanation.

Google later shipped a Chrome extension to replace it. Offered it for a while. Then removed it. Claimed it was a mistake. Then restored it under user pressure.

This cycle of delete → restore → delete is itself a signal: RSS carries zero priority at Google. When users know this, they stop depending on it.

2017: Google News completely removes RSS support

Google News had supported RSS since 2002 — users could subscribe to any Google News search result as an RSS feed.

In 2017, Google killed this entirely. No reason given.

Every RSS subscription users had built inside Google News became invalid. Proprietary Google News links kept working. The open format was gone.

This isn’t a conspiracy theory — it’s ad logic

Some argue this was carelessness, not intent.

But one fact checks the intent hypothesis cleanly: wherever Google cannot sell ads, it does not maintain the feature.

RSS’s structure is inherently hostile to advertising:

• Users read in their client of choice; Google can’t track behavior
• Content is delivered complete in the feed; users don’t need to click through
• No page to inject ads into; no cookie to plant

Google’s core business model is “control how users consume information, then monetize that behavior.” RSS’s design philosophy is the direct inverse: the user decides what to subscribe to, reads wherever they choose, and isn’t tracked by any middleman.

These two philosophies are structurally incompatible.

@tommek4077 on HN, with one sentence:

“You couldn’t put ads easily in RSS feeds.”

@goldenarm, more acidly:

“They killed Google Reader and RSS to push Google+, which was a brilliant decision.”

Google+ closed in 2019.

RSS today: not dead, but marginalized

The reason this article hit HN’s front page this week isn’t that the content is fresh — the original post is from 2023. It’s that it arrived alongside two other articles:

• “A directory of people who love RSS” — a site where people register their RSS support
• “Atom is better than RSS, in ways that matter” — why Atom is technically superior to RSS

Three RSS-topic pieces forming a cluster. Together they signal: RSS is still here, its users are still here, they’re still arguing about which format is better and who’s to blame.

In reality, RSS/Atom remains a daily tool for the technical community. Almost every blogging platform generates feeds by default. Hugo, WordPress, Ghost, and Substack all do. Developers, researchers, and journalists use RSS readers heavily.

What’s gone is the general user. When Google Reader closed, that cohort — the ones Google had brought into RSS — never came back.

@dabinat on HN:

“I don’t understand why many sites with news updates / blogs don’t offer an RSS feed. Are they expecting me to keep visiting the site over and over to see if there is new content?”

That confusion is itself the answer: sites that don’t offer RSS do want you to keep coming back. Every visit is an impression, a behavior data point, a trackable session. RSS subscribers become invisible to the platform — that’s a net loss.

The real lesson

This isn’t a story about Google being bad. It’s a story about the structural fragility of open protocols in commercial ecosystems.

RSS never had a company maintaining its adoption. It’s a standard, not a product. Standards need products to carry them.

Google used products to carry RSS, and then when the product stopped serving commercial interests, it killed the product and took the users.

This pattern repeats across the internet:

• Google RSS / FeedBurner: used RSS to acquire users, then killed it
• Twitter API: used openness to acquire developers, then closed it
• Facebook Instant Articles: used traffic to acquire publishers, then wound it down
• Apple iCloud Shared Albums: used convenience to acquire user data, then deprecated it

Any open protocol that’s adopted by a single commercial entity as a user-acquisition tool faces the same fate: used up, then discarded.

The only defensive move users have: don’t host your use of an open protocol on a single platform. Run an open-source RSS reader, manage your own subscription list. Then no matter which company shuts down, your data stays.

What you can still do today

These tools are good, open-source, and running right now:

• FreshRSS: self-hosted RSS reader, full-featured, Docker image available
• Miniflux: minimal, fast self-hosted RSS service, written in Go
• NetNewsWire: Mac/iOS RSS reader, completely free, no ads

If you run a blog or publish technical content: make sure your RSS feed is valid. Hugo generates index.xml by default; if you’re on another platform, check.

@jjordan on HN mentioned he’s building a new RSS feed directory, “stemmed from a frustration of outdated and broken RSS feed collections, and the long slow death of the orange RSS subscribe button across the web.”

That’s the healthy response. Not condemning a company — rebuilding infrastructure that doesn’t depend on any single commercial actor.

Summary

Google was never RSS’s enemy. It’s just an advertising company, and RSS can’t carry ads. That fact is more sobering than any conspiracy theory — and more worth remembering.

📡 Still using RSS?

• If you have a blog: verify your feed URL is valid and accessible.
• If you want to start: FreshRSS + self-hosted, up in 5 minutes.
• If you’re already using it: export your subscription list as OPML and back it up locally.

📬 Follow 梦兽编程 for more internet tech history and engineering analysis.

Sources:

• Open RSS: How Google helped destroy adoption of RSS feeds External link
• HN discussion: How Google helped destroy adoption of RSS feeds External link (494 pts)
• HN: A directory of people who love RSS External link (169 pts)
• Chris Morgan: Atom is better than RSS, in ways that matter External link