Fact-checked by Grok 2 weeks ago

Google Reader

Reader was a free web-based and feed aggregator service developed by , launched in 2005 to enable users to subscribe to and organize content updates from multiple websites in a unified . The service streamlined the process of monitoring blogs, news sites, and other publishers by pulling headlines, summaries, and full articles into a customizable , supporting features like tagging, starring items for later review, searching across feeds, and mobile access. It became a staple for power users seeking an ad-free, efficient alternative to fragmented browsing, fostering communities through public sharing of feeds and "liked" items that could be broadcast to followers. Despite its dedicated following, Google discontinued Reader on July 1, 2013, attributing the decision to declining usage trends and a strategic shift toward consolidating resources on core products with broader appeal. The abrupt announcement triggered widespread criticism from users who viewed it as a misstep, given the service's role in sustaining ecosystems; alternatives like rapidly absorbed hundreds of thousands of migrating subscribers in the immediate aftermath, underscoring Reader's entrenched utility among niche but active audiences. This shutdown exemplified Google's pattern of pruning under-monetized offerings, even those with loyal bases, prioritizing scalable services over specialized tools.

History

Development and Launch

Google Reader originated from an independent project called JavaCollect, initiated by software engineer Chris Wetherell around 2001, which aimed to aggregate and organize web content feeds. Wetherell joined and repurposed elements of this work into an internal prototype named "" during late 2004 to early 2005, leveraging 's 20% time policy for personal projects. This development occurred amid growing interest in technology, as ging proliferated and users sought efficient ways to track updates from multiple sources without constant manual checking. The product was formally developed by a small team at , with Wetherell as the lead engineer and Jason Shellen serving as the founding . Key engineering challenges included scaling feed parsing for high volumes and ensuring a responsive interface, achieved through rapid iteration in a short timeframe. On October 7, 2005, Google Reader launched experimentally via , initially accessible to a limited group of approximately 100,000 users described as "our closest friends" to test stability and gather feedback. The launch blog post by Wetherell emphasized its role in discovering and sharing content, positioning it as a tool for "power users" navigating the expanding web. Early adoption was driven by its web-based accessibility and integration with existing RSS/Atom standards, contrasting with desktop clients like those from NetNewsWire or Bloglines. Despite initial bugs, such as crashes during heavy use, the service quickly attracted developers and tech enthusiasts, laying the foundation for subsequent enhancements.

Expansion and Integrations

Following its launch on October 7, 2005, Google Reader underwent several expansions to enhance functionality and user engagement. In March 2006, the service introduced tag sharing, enabling users to share specific tagged items and embed them as widgets on external sites. By September 2006, a dedicated Share option was added, allowing users to mark and compile feed items on a personal sharing page. These features marked an early shift toward social capabilities, building on remnants of a "" tab present in the initial release's code. In January 2007, Reader expanded media support by enabling playback of embedded videos from and directly within feeds, with subsequent additions for platforms like and Yahoo! Video. September 2007 brought integrated search functionality, allowing users to query across subscribed feeds from a dedicated box above the reading pane. By May 2008, universal sharing and tools were implemented, facilitating content distribution beyond Google ecosystems to any web location. Integrations with other Google products further broadened Reader's scope. Starting in 2007, it handled feed serving for various internal Google services. In October 2008, deep integration with enabled a full Reader interface—including keyboard shortcuts, expanded/list views, and infinite scrolling—for any feed within the personalized homepage's canvas mode. February 2010 saw ties to , where shared items from Reader could be posted directly to the social layer, enhancing discoverability via Buzz profiles. As Google consolidated social efforts, October 2011 updates replaced Buzz-linked features with Google+ integration, including a redesigned and direct sharing to Google+ streams; this discontinued standalone friending, following, and commenting in Reader to prioritize the broader platform. These developments positioned Reader as a core aggregator within Google's ecosystem, though later shifts emphasized unified social tools over isolated enhancements.

Decline and Discontinuation

announced on , 2013, that it would discontinue Reader, with the service shutting down on July 1, 2013. The company attributed the decision to declining usage trends over the years, despite a dedicated user base, and an industry-wide pivot from aggregation toward social platforms for content consumption and sharing. The announcement triggered significant backlash from users, including online petitions that collected over 200,000 signatures within days, decrying the loss of a key tool for decentralized news aggregation. Google facilitated data export via , allowing users to transfer subscriptions in format to competitors like , NewsBlur, and FeedPress, which saw subscriber surges in the following months. Analysts and former Google employees later suggested additional motives, such as redirecting engineering resources to social features like Google+ and reducing support for non-monetizable, open protocols that bypassed ad-driven discovery. RSS usage had been eroding since the mid-2000s, with data showing search interest in "" peaking around 2005 and steadily falling, reflecting broader adoption of algorithmic feeds on platforms like and . The discontinuation marked a pivotal moment in access, hastening the shift to walled-garden ecosystems while leaving a niche but persistent community reliant on independent tools; by 2013, Google Reader served an estimated several million active users, though exact figures were not publicly disclosed.

Features

Core RSS Aggregation

Google Reader served as a web-based for and feeds, consolidating updates from subscribed sources into a single, accessible . Users subscribed to feeds by entering the direct or utilizing the built-in feed finder, which scanned websites for available links. This process, introduced at launch on October 7, 2005, enabled seamless integration of diverse content streams without requiring local software installation. The service operated on a server-side model, where Google's periodically fetched feed files from publishers via HTTP requests, typically polling at intervals determined by update frequency to balance efficiency and timeliness. Upon retrieval, the XML content—encompassing elements like titles, publication dates, summaries, and links—was parsed to identify new items, which were then stored in the user's account and flagged as unread. This approach minimized processing, allowing feeds to sync across devices and reducing bandwidth demands on end-users. Aggregated items appeared in a unified timeline sorted in reverse chronological order, either across all subscriptions or filtered by individual feeds, with visual indicators for unread status and options to mark items as read in bulk. The interface supported expanded views for partial feeds by linking to original articles or displaying full content when provided, alongside enclosures such as images or podcasts. algorithms further refined the viewing experience by highlighting potentially relevant updates based on user behavior.

User Interface and Organization

Google Reader's centered on a web-based with a left sidebar for subscription management and a central pane for feed content display. The sidebar listed subscribed feeds hierarchically, allowing users to create and nest folders—functionally equivalent to tags—to categorize sources by topic or preference, such as grouping technology news or personal interests. Feeds could be assigned to multiple folders, enabling flexible organization without rigid silos. Organization tools included drag-and-drop functionality for rearranging feeds into folders, introduced in late to streamline setup. Users accessed global views like "All items," "Starred items," and "Shared items" from the sidebar, facilitating quick navigation across unread content or user-curated selections. A persistent search bar at the top supported querying across feeds, with options to filter by tags or dates. The reading pane offered toggleable views: list view for compact title-only scanning to accelerate feed processing, and expanded view for previews including article excerpts, images, and metadata to aid without leaving the . shortcuts enhanced efficiency, such as 'j' and 'k' for item navigation, 's' for starring, and 'v' for opening links. In 2011, a redesign modernized the layout with sharper aesthetics, reduced visual clutter, and integrated Google+ sharing prompts, prioritizing content over social elements in core reading flows. Feed-specific settings, accessible via dropdowns, allowed customization like renaming, feed update frequencies, and inclusion in bundles for algorithmic grouping. This structure supported power users in managing hundreds of subscriptions while maintaining a minimalist, utilitarian design focused on rapid information consumption rather than ornate visuals.

Social Sharing and Collaboration

Google Reader incorporated social sharing features to enable users to disseminate and discover content beyond personal aggregation. Introduced in late , the sharing functionality allowed users to select items from their feeds and share them publicly or with designated contacts, generating a public feed of shared content that others could subscribe to or view via a link. This feature integrated with users' contact lists, permitting visibility of shared items among friends without requiring additional setup, thus creating a lightweight layered atop consumption. In May 2008, enhanced sharing by adding a "Share with " option, which let users append custom commentary or annotations to shared items, and introduced a called " in Reader" for clipping and sharing content from external sites directly into Reader. Users could also generate links to their shared feeds, accessible even to non- account holders, promoting broader dissemination. By July 2009, the platform added a "Like" mechanism distinct from starring (which was private) or sharing; liking publicly endorsed items and contributed to algorithmic recommendations of popular content tailored to user interests. These features supported collaborative discovery, as users could browse aggregated likes and shares from their network, though interactions remained asynchronous and feed-centric rather than conversational. In November 2011, Google discontinued these elements—including likes, notes, and friend-sharing visibility—in favor of integration with Google+, redirecting shared items to the latter's stream. Prior to this, settings allowed optional connections to external for broader posting, but core stayed within Google's . The features, while innovative for , emphasized curation and endorsement over joint editing or group feed management.

Integrations and Accessibility

Google Reader featured a public , introduced in December 2005, that facilitated integrations with third-party applications by enabling authentication, subscription management, feed retrieval, item marking as read, and sharing capabilities. This powered synchronization for numerous clients, including mobile apps such as Reeder for and gReader for , allowing users to access feeds across devices without duplicating subscriptions. Third-party services like initially leveraged the for backend compatibility before transitioning post-discontinuation. Within Google's ecosystem, Reader integrated sharing functions with , where users could post items directly to their Buzz stream via a "Share" button until Buzz's shutdown on December 15, 2011. Following this, social features migrated to Google+, incorporating Reader notes and shares into the Google+ activity stream to consolidate user interactions across services. For broader accessibility, Google Reader offered a mobile-optimized web interface and an official application, released around 2010, which supported offline reading, push notifications for new items, and gesture-based on touch devices. The service adhered to standard practices, including keyboard shortcuts for (e.g., 'j' and 'k' for item , 's' for starring), though it lacked specialized features like built-in optimizations or high-contrast modes tailored for visual impairments. The further extended accessibility by enabling custom client development for diverse platforms, including desktop and wearable devices.

Technical Aspects

Architecture and Data Handling

Google Reader employed a distributed backend architecture optimized for aggregating and serving vast numbers of and feeds to users. Feeds were fetched centrally using Google's Feedfetcher-Google crawler, which polled publisher endpoints at intervals determined by update frequency and historical patterns to minimize load while ensuring timely content delivery. To enhance update speed beyond traditional polling, the service integrated PubSubHubbub (PuSH) protocol support starting August 5, 2009, enabling real-time push notifications for shared items when publishers pinged compatible hubs, such as Google's own at pubsubhubbub.appspot.com. This hybrid approach—combining scheduled pulls with optional pushes—facilitated efficient data propagation across the user base. User-specific data handling involved storing subscriptions, item (titles, summaries, , publication dates), and interaction states (read/unread, starred, shared) in a scalable structure accessible via the undocumented Google Reader , which supported through Google accounts and enabled third-party clients for syncing and offline access. The exposed endpoints for streams of unread items, reading positions, and feed lists, indicating sharded per-user models to manage individualized views amid collective feed processing. For persistence and export, subscriptions were maintained in format for interoperability, while comprehensive archives—encompassing reading lists, shared items, and historical positions—were provided via as ZIP files containing JSON-serialized entities, often exceeding tens of megabytes for active users due to accumulated item histories. Post-discontinuation, the underlying feed backend persisted for public feed access but omitted user-specific states like read markers. This design prioritized scalability for millions of subscriptions but relied on Google's opaque infrastructure, with no public disclosure of exact storage layers or query optimizations.

API and Developer Ecosystem

Google Reader featured an unofficial application programming interface (API) that, despite lacking formal documentation from Google, enabled developers to access core functionalities such as user authentication, subscription management, feed retrieval, unread item counting, and state updates like marking items as read or starred. This API operated over HTTP using Google account credentials for authentication and supported Atom-based feeds, allowing programmatic interaction without official SDKs or endpoints published by Google. Developers reverse-engineered its endpoints starting as early as 2005, relying on community efforts to map request formats and responses, which included XML and JSON payloads for efficiency. The absence of official support did not hinder adoption; instead, it spurred a vibrant ecosystem centered on interoperability. Third-party applications, including clients like FeedDemon and NewsRack, mobile apps such as Reeder for , and plugins for platforms like , leveraged the to synchronize subscriptions and reading progress with Google Reader as a backend service. This compatibility extended to web services and browser extensions, fostering integrations with tools like gadgets for personalized feed dashboards. By 2013, the underpinned hundreds of -focused apps, with developers documenting protocols via s and libraries in languages like (e.g., pyrfeed) to handle tokens and batch operations. The API's design emphasized extensibility, supporting features like folder hierarchies (via tags) and shared item broadcasting, which encouraged collaborative tools and custom aggregators. Its discontinuation in 2013 disrupted this , rendering many apps inoperable and prompting migrations to self-hosted alternatives. Post-shutdown, the Google Reader spec emerged as a , with modern self-hosted readers like FreshRSS, Miniflux, and Tiny-Tiny RSS implementing compatible endpoints to maintain for legacy clients. This legacy underscores its role in sustaining developer tools beyond Google's involvement, as evidenced by ongoing community reimplementations as of 2025.

Reception and Impact

Popularity and User Adoption

Google Reader launched on October 7, 2005, initially available to a limited group of users as part of , and rapidly gained traction among early adopters interested in feed aggregation for streamlined content consumption. By 2007, it had surpassed competitors like Bloglines to become the top reader for subscribers to certain blogs, capturing up to 26% of readership for prominent sites. This growth reflected its appeal to power users, including bloggers, journalists, and tech enthusiasts, who valued its clean interface and features for organizing hundreds of feeds without the clutter of traditional browsing. Adoption metrics highlighted its dominance in the ecosystem: by 2011, Google Reader accounted for 16% of RSS feed readership tracked by Mediafed, a decline from 13% the prior year but still indicative of substantial among feed-based consumers. Subscriber counts for individual feeds underscored scale; for instance, CNN's feed had over 25 million subscribers in Google Reader as of April 2013, while the platform's most popular feeds exceeded 24 million subscribers each. Estimates placed monthly active users in the tens of millions by 2010, according to a product manager's statements, though exact figures remained opaque due to Google's lack of public disclosure. Despite these numbers, Google described usage trends as diminishing by the time of its March 13, 2013, discontinuation announcement, leading to its shutdown on July 1, 2013. The decision provoked widespread backlash, with alternatives like gaining three million migrants shortly after, signaling Reader's entrenched loyalty among a dedicated, albeit niche, user base that prioritized over emerging social media feeds. This contrasted with broader web trends favoring algorithm-driven discovery, yet Reader's influence persisted in driving significant referral traffic—far exceeding that of despite the latter's claimed 100 million monthly users.

Contributions to RSS Usage

Google Reader, launched in 2005, broadened adoption by providing a free, web-based aggregator that eliminated the need for desktop software installations prevalent in earlier tools like SharpReader or NewsGator. This accessibility drew in non-technical users, enabling seamless subscription to feeds via simple entry or automatic discovery, which streamlined from blogs, news sites, and podcasts. By 2011, it accounted for approximately 16% of tracked readership through services like Media Cloud, underscoring its dominance in aggregating and delivering feeds to a growing user base. The platform's organizational tools, including folders, tags, and search across subscribed content, facilitated personalized information diets, encouraging habitual RSS use over fragmented browsing or alerts. Features like "starring" items and full-text archiving preserved user data beyond site paywalls or changes, sustaining engagement with long-form amid rising alternatives. Integration with Google services, such as notifications and apps from 2008 onward, extended RSS to devices, boosting consumption during the smartphone era's expansion. Social functionalities, including public feed sharing and "like" buttons introduced in 2008, positioned RSS as a collaborative tool, allowing users to recommend and bundle feeds for networks, which amplified discovery and retention. This referral traffic to publishers—outpacing platforms like Google+ in 2013— incentivized websites to maintain and enhance RSS outputs, with estimates indicating Reader drove significant visits to independent creators before its 2013 shutdown. Overall, by centralizing RSS infrastructure at scale, Google Reader sustained the protocol's viability for power users and hobbyists, even as mainstream attention shifted to algorithm-driven feeds.

Criticisms of Functionality and Reliability

In February 2013, numerous users experienced a significant outage affecting Reader's core functionality, including subscriptions vanishing from accounts, feeds failing to mark items as read, and incessant refreshing loops that prevented normal use. Folders and settings also reverted unexpectedly to prior configurations for some users during this period. acknowledged the issue as a bug and resolved it within days, though it highlighted underlying reliability vulnerabilities in the service's backend shortly before its announced discontinuation. Performance complaints centered on slow loading times, particularly for users with expansive subscriptions or feeds containing lengthy articles, where the default expanded view exacerbated delays compared to list mode. High-volume feeds, such as those generating 300–400 items daily, overwhelmed the interface, making efficient difficult without external workarounds. Feed refresh delays compounded these issues; by July 2011, some updates lagged by up to 50 hours, rendering the unreliable for time-sensitive content monitoring. Mobile support drew consistent for inadequate and , with the service described as inherently poor on handheld devices and lacking a competent native application. Sporadic glitches, such as blank or missing articles and starred items, further eroded trust in display reliability across platforms. These functionality shortcomings persisted despite iterative updates, contributing to user frustration with and cross-device consistency.

Controversies

Discontinuation Decision

Google announced the discontinuation of Google Reader on March 13, 2013, stating that the service would cease operations on July 1, 2013. Users were directed to export their subscriptions and data via during a four-month window following the announcement. , Google's then-Senior Vice President of Technical Infrastructure, cited declining usage over the years as the primary rationale, noting that while the product—launched in to facilitate of website content—retained a loyal following, it no longer justified continued investment amid Google's shift toward fewer, more socially oriented products. This aligned with broader company efforts to streamline its portfolio, as the shutdown formed part of a "" initiative that had closed around 70 features or services since 2011. Internal reflections from Reader's engineering team, including leads Dolapo Falola and Mihai Parparita, later highlighted chronic under-resourcing and corporate prioritization of social platforms like over RSS aggregation, with usage peaking at over 30 million monthly active users but deemed insufficient at Google's scale. Earlier, in 2011, Google had removed Reader's native sharing functionality, redirecting it to integration, signaling a strategic pivot away from decentralized feed-sharing toward centralized social ecosystems. Observers such as developer speculated that RSS's open nature hindered monetization and control compared to proprietary social feeds, though Google maintained the decision stemmed from usage trends rather than competitive redirection.

Effects on RSS and Open Web Ecosystem

The discontinuation of Google Reader on July 1, 2013, prompted an immediate migration of users to alternative RSS aggregators, including , NewsBlur, and The Old Reader, which collectively absorbed millions of subscribers in the ensuing months. This shift revitalized competition in the RSS reader market, as evidenced by reporting over 500,000 new sign-ups within days of the announcement and a subsequent pivot to paid premium tiers to sustain development. However, the abrupt termination without robust data export guidance for non-technical users exacerbated fragmentation, with many casual consumers abandoning altogether in favor of centralized social media feeds on platforms like and . Long-term trends indicate a decline in mainstream RSS adoption following the shutdown, corroborated by Google Trends data showing searches for "RSS" dropping sharply from 2013 onward, reflecting reduced visibility and perceived obsolescence of the protocol among general audiences. Google's prior subsidization of Reader as a free service had suppressed innovation among paid competitors, creating dependency; its removal thus contributed to a contraction in the ecosystem, where publisher support for feeds waned due to diminished readership metrics from aggregated sources. Despite this, persisted in niche communities, with tools like Inoreader and self-hosted options such as FreshRSS gaining traction among developers and privacy-focused users, underscoring the 's resilience as an decoupled from proprietary services. On the broader open web ecosystem, the loss of Reader diminished a key mechanism for decentralized content discovery, as enabled users to bypass algorithmic curation and directly access diverse, unmediated publisher updates, fostering intellectual pluralism. The resulting vacuum accelerated reliance on walled gardens, where platforms prioritize engagement over syndication, potentially eroding incentives for sites to maintain open feeds and contributing to a siloed architecture. Empirical observations post-2013 reveal sporadic revivals, driven by privacy concerns and dissatisfaction with , yet overall, the event marked a causal pivot toward centralized distribution, with 's role in sustaining an interoperable web ecosystem notably weakened.

References

  1. [1]
    Google closes the book on Reader, announces July 1 sunset - CNET
    Mar 13, 2013 · So, on July 1, 2013, we will retire Google Reader. Users and developers interested in RSS alternatives can export their data, including their ...
  2. [2]
    How to Use Google Reader - Business Insider
    Mar 23, 2011 · Reader turns any website into a simple text and picture formula that you can browse through quickly. With Google Reader, all you see is a clean ...
  3. [3]
    A second look at Google Reader | Living Digitally
    Nov 30, 2006 · Sharing. My favorite feature of Google Reader is sharing. When you share a post, it adds it to your shared list which basically auto-generates a ...Missing: key | Show results with:key
  4. [4]
    Powering Down Google Reader
    Mar 13, 2013 · There are two simple reasons for this: usage of Google Reader has declined, and as a company we're pouring all of our energy into fewer products ...
  5. [5]
    More than 500,000 Google Reader users claimed by Feedly in two ...
    Mar 16, 2013 · Google's controversial decision to shut down Google Reader on July 1st has left its users searching for a new news-collecting homeland, ...
  6. [6]
    What Was Google Reader and Why Was it Discontinued? - Failory
    They informed users that the application was to close on July 1, 2013. Users and developers interested in RSS alternatives could export their data, including ...
  7. [7]
    Google Reader shutting down on July 1 | CNN Business
    Mar 14, 2013 · Reader will be shut down on July 1. Users wanting to port their content to another RSS (rich site summary) feed can use Google Takeout to move ...
  8. [8]
    Google Reader Social Retrospective - persistent.info
    Oct 31, 2011 · Late 2004 to early 2005: Chris Wetherell starts work on "Fusion", one of the 20% projects that serve as prototypes for Google Reader. Among ...
  9. [9]
    Who killed Google Reader? - The Verge
    Jun 30, 2023 · Reader launched in 2005, right as the blogging era went mainstream; it made a suddenly huge and sprawling web feel small and accessible and ...
  10. [10]
    The Evolution Of Google Reader Started With A Crash | TechCrunch
    Mar 23, 2013 · In October 2005, Google Reader launched to 100,000 of our closest friends. The team pulled off some amazing feats in a short amount of time. We ...
  11. [11]
    On Google Reader's Last Day, Looking Back At Its First - Forbes
    Jul 1, 2013 · The date was October 7, 2005 when a cheerful software engineer named Chris Wetherell took a moment to announce his experimental project to the ...
  12. [12]
    Google Reader - Digital Garden
    May 2, 2021 · It was created in early 2005 by Google engineer Chris Wetherell and launched on October 7, 2005, through Google Labs. Google Reader grew in ...
  13. [13]
    Google Reader changes for the better | Raoul Pop
    Sep 29, 2006 · Another cool feature is the Share option, which lets you mark feed items for sharing, and puts them onto a separate page, all your own, with a ...
  14. [14]
    Getting embedded in Google Reader.
    Jan 30, 2007 · Update on 2/7/2007: We now also support Odeo, Yahoo! Video, Brightcove, Dailymotion, blip.tv and MSN Soapbox embedded players. at 1/30/2007 ...
  15. [15]
    Google Reader Shows Embedded Videos
    Jan 30, 2007 · Google Reader Shows Embedded Videos ... Google's feed reader lets you view videos from YouTube and Google Video, if they are embedded in a post.
  16. [16]
    Google Adds Search To Google Reader | TechCrunch
    Sep 5, 2007 · The search box is located directly above the reading panel to the right of the Google Reader logo. Users can search all subscribed feeds or ...
  17. [17]
    Google Reader gets universal sharing and microblogging features
    May 6, 2008 · Google Reader gets universal sharing and microblogging features. Google Reader gets an important update for sharing.
  18. [18]
    No More Google Reader
    Mar 13, 2013 · Over the years, Google Reader integrated with iGoogle, added social features and handled feed serving for all Google products. Back in 2007, ...
  19. [19]
    iGoogle launches Reader integration
    Oct 16, 2008 · Now you can get the same powerful Reader interface for any feed in iGoogle, complete with keyboard shortcuts, expanded and list views, infinite ...
  20. [20]
    Readers: Get your Buzz on - Official Google Reader Blog
    Feb 9, 2010 · Head to our help center for more details about the Buzz integration in Reader, or leave us feedback in our forum, on Twitter or even using Buzz ...Missing: iGoogle | Show results with:iGoogle<|control11|><|separator|>
  21. [21]
    New in Reader: a fresh design, and Google+ sharing
    Oct 31, 2011 · Starting today we'll be turning off friending, following, shared items and comments in favor of similar Google+ functionality.
  22. [22]
    Google Reader Will Integrate With Google+
    Oct 20, 2011 · Now that Google Buzz will be discontinued, this feature will be available in Google+. Unfortunately, Google Reader will no longer have a ...Missing: iGoogle | Show results with:iGoogle
  23. [23]
    Google to shut Reader web feed application, users vent | Reuters
    Mar 14, 2013 · March 14 (Reuters) - Google Inc said it will shut Google Reader on July 1, citing declining usage for the application that compiles content ...
  24. [24]
    Why Google Reader Really Got the Axe - WIRED
    Jun 6, 2013 · When Google announced its plans to shutter Google Reader in March, the Internet freaked out. Twitter users raised their virtual pitchforks ...<|control11|><|separator|>
  25. [25]
    The death of RSS in a single graph - andrewchen
    RSS has been dying for years. First off, the image above is the Google Trends search on “rss” over the last few years. · RSS doesn't have a reply function
  26. [26]
    https://googlepress.blogspot.com/2005/10/google-reader_07.html
  27. [27]
    How does RSS reader know that a feed is updated? - Stack Overflow
    Dec 29, 2009 · The reader re-fetches the RSS feed now and then (for example two times per hour, or more often if the reader learns that it's an often updated ...
  28. [28]
    How I organize feeds in Google Reader
    Dec 25, 2008 · Now, go to Google Reader's Settings page. On the Preferences tab, select Everything-Feed to be your start page. On the Goodies tab, create a ...
  29. [29]
    How to Declutter and Streamline Your Google Reader Inbox
    Apr 5, 2010 · Since Google Reader lets you put feeds into multiple folders, you can also create a separate set of folders to arrange your feeds by ...
  30. [30]
    Google Reader Adds Recommendations, Drag-and-Drop Folders
    Nov 30, 2007 · The change Reader users will really appreciate is the ability to simply grab newly added feeds and place them in their folders—no more clicking ...<|separator|>
  31. [31]
    Practical 101s: Google Reader And Persistent Search - Dave Fleet
    Oct 16, 2008 · Select the feed you want to organize, in the left-hand column of Google Reader · Click the grey drop-down 'Feed settings…' box near the top-right ...<|separator|>
  32. [32]
    New Look for Google Reader - PHP Magazine Network
    Sep 29, 2006 · Folder-based navigation makes it easier to organize your subscriptions, and the new expanded view lets you quickly scan over several items at ...
  33. [33]
    Hands-on: Google Reader app for Android - Ars Technica
    Dec 3, 2010 · Although it has a very simple list-based user interface, it manages to capably expose most of Google Reader's features. In order to user the ...
  34. [34]
    And Here It Is: The New Google Reader Revealed | TechCrunch
    Oct 31, 2011 · Today, Google is rolling out its update to Google Reader which features the promised user interface overhaul, and, more importantly, the new ...
  35. [35]
    Google Reader redesign rolling out today with Google+ integration
    Oct 31, 2011 · Google Reader redesign rolling out today with Google+ integration ... The new design will roll out to all users by the end of the day, and ...
  36. [36]
    Requiem for Google Reader: an RSS behemoth shuts down
    Mar 14, 2013 · Google announced Thursday, though, that the utilitarian, RSS hose of Google Reader will be brought in line with the lighter, more “designed” UI ...
  37. [37]
    Google Reader Gets Social With Friends Shared Items
    Dec 17, 2007 · Your Reader shared items are being made available to your friends from Google Talk. You can see what these friends are sharing; they can see ...
  38. [38]
    Google Reader Gets More Social: Now With Notes | TechCrunch
    May 5, 2008 · Google has added support for Notes to Google Reader, allowing users to share notes or add notes to shared stories. The add a note feature is ...
  39. [39]
    Google Reader Gets More Social with New Sharing Features, and ...
    May 5, 2008 · Google Reader now lets us share anything using the handy bookmarklet “Note in Reader”. Just drag the bookmarklet into your browser's bookmark ...
  40. [40]
    Google Reader shared items: Your public feed for reading ...
    Jan 25, 2011 · In "Sharing settings," there are two opportunities to email a link to your shared feed to your friends. They don't even need a Google account ( ...Missing: collaboration | Show results with:collaboration
  41. [41]
    Google Reader's Social Evolution
    Jul 15, 2009 · In addition to starring, sharing and sharing with note, Google Reader users can "like" posts. Why would you like a post when you can star it? By ...<|separator|>
  42. [42]
    Google Reader Basics – Share, Like, and Add Star - 40Tech
    Aug 27, 2009 · When you click on "Add Star," which is located at the bottom of each feed item in Reader, that item will be added to your Starred items. Your ...Missing: notes | Show results with:notes
  43. [43]
    Google reader as a social network | NIC HARALAMBOUS
    May 7, 2019 · All you need to do to share an item in GR is click the little "Share" button at the bottom of any post in your reader. Simple, effective, ...
  44. [44]
    Read Your Shared Items in Google Reader
    Nov 1, 2011 · The latest Google Reader update removed all the social features, including the section that allowed you to read the items you've shared.
  45. [45]
    Google Reader Adds Social Sharing and Mark as Read Controls
    Aug 13, 2009 · Head to Google Reader's settings, click off the social networks you want to add access to (or manually add a URL, if you're hack-friendly like ...
  46. [46]
    Google Reader API - Niall Kennedy
    Dec 26, 2005 · The data technologies powering Google Reader can easily be used and extended by third-party feed aggregators for use in their own applications.
  47. [47]
    The Best Google Reader Replacement - Phil Gons
    Mar 15, 2013 · ... Google Reader API—which will be released before July 1. They promise ... third party apps (such as Reeder) will be able to use Feedly ...
  48. [48]
    Applications: Google Reader - Pocket
    Flipboard iPad News Reader · Reeder iPhone App · Reeder for iPad iPad App · Zite iOS News Reader · gReader Android App · Byline iPhone app · Mr Reader iPad App.
  49. [49]
    How to Subscribe to Google+ Users With Google Reader
    Aug 24, 2011 · When you click the "Share" button on Google Reader, it automatically shares to Google Buzz. You can also use the "Send to" button, and send a ...Missing: iGoogle | Show results with:iGoogle
  50. [50]
    Hands-on: Google Reader app for Android - Ars Technica
    Ars takes a hands-on look at the new official Google Reader client application for the Android mobile platform. It's nice on an Android phone, but...
  51. [51]
    Google Reader API developer | rubrain.com
    A Google Reader API developer is responsible for creating and maintaining software that allows third-party applications to access and interact with the ...
  52. [52]
    Google Feedfetcher | Google Search Central | Documentation
    You can prevent Feedfetcher from crawling your site by configuring your server to serve a 404 , 410 , or other error status message to the Feedfetcher-Google ...Missing: Reader | Show results with:Reader
  53. [53]
    PubSubHubbub support for Reader shared items
    Aug 5, 2009 · PubSubHubbub support for Reader shared items. Posted by Mihai ... real-time. If you want to learn more about PubSubHubbub and how it ...
  54. [54]
    Google Reader Speeds Up Sharing With PubSubHubbub
    Aug 5, 2009 · At our Real-Time Stream CrunchUp event last month, one of the most interesting things that was demoed was PubSubHubbub, a new protocol made ...
  55. [55]
    Export Google Reader Data in Google Takeout
    Nov 16, 2012 · Instead of downloading a small XML file, you need to download a large archive (34MB for my account).
  56. [56]
    How To Export Google Reader Subscriptions to OPML File
    In this tutorial, you will learn how to export Google Reader subscriptions into OPML file. You can import the XML file later in alternative feed readers.
  57. [57]
    Getting ALL your data out of Google Reader - persistent.info
    Jun 28, 2013 · Google's Feed API will continue to exist, and it's served by the same backend that served Google Reader. However it does not expose items ...
  58. [58]
    pyrfeed - GoogleReaderAPI.wiki - Google Code
    It's just 10 differents and incompatible xml formats (9 RSS formats according to Mark Pilgrim and 1 Atom format). ... atom/feed/http://xkcd.com/rss.xml .
  59. [59]
    Google Reader API | Kin Lane
    Sep 13, 2011 · Google has never made an API for Google Reader. It onlyallowsyou to use RSS feeds and sharing them publicly.
  60. [60]
    Has Google ever officially released documentation for the Google ...
    Jul 23, 2025 · I've been searching for information about Google Reader's API and came across some older blog posts from 2005 ... third-party apps constantly.
  61. [61]
    What are some alternatives to Google Reader? - Quora
    Dec 25, 2022 · Google announced today that they will be shutting down Google Reader. This is something we have been expecting for some time: We have been ...<|separator|>
  62. [62]
    Google Reader API | Drupal.org
    Jan 23, 2012 · This project exposes the Google Reader API for use within Drupal. It currently uses the library provided by Dmitrij Duhnich which he has shared ...<|separator|>
  63. [63]
    Google Reader - Wikipedia
    Google closed Google Reader on July 1, 2013, citing declining use. Google Reader.
  64. [64]
    Open Reader API - Overview
    Open Reader API. This is an effort to define a new common feed-syncing API protocol based (or not) on Google Reader. We recognise that we are many – many ...
  65. [65]
    The Death Of Google Reader Opens The Door To A ... - TechCrunch
    Jul 6, 2013 · We all know that Google Reader, which used to be the most obvious RSS subscription tool, is now gone. At the same time, we see “follow” buttons ...<|separator|>
  66. [66]
    FreshRSS - Google Reader compatible API implementation
    Before you can start using this API, you have to enable and setup API access, which is documented here, and then reset the user's API password.
  67. [67]
    Google Reader API - Miniflux
    Miniflux implements the Google Reader API. To activate the Google Reader API, go to the Settings > Integrations section and choose a username and password.
  68. [68]
    eric-pierce/freshapi: A FreshRSS / Google Reader API ... - GitHub
    FreshAPI implements the FreshRSS / Google Reader API to allow Tiny-Tiny RSS to be used with more third party apps, and with more features.
  69. [69]
    Re-Implementing the Google Reader API in 2025 - davd.io
    Feb 5, 2025 · The Google Reader API implementation is well-supported in most RSS clients, I set out to build an API compatible with the existing spec.Missing: protocol | Show results with:protocol
  70. [70]
    Google Reader Data Points - Google Operating System
    Mar 14, 2013 · It's hard to estimate the number of Google Reader users, but here are some data points: - the most popular feed has more than 24 million ...Missing: growth | Show results with:growth
  71. [71]
    Where Did Google Reader's Users Go? Check Your Phone
    Mar 14, 2013 · In 2011, Google Reader accounted for 16% of Mediafed RSS feed readership on March 14. On the same date last year, it accounted for 13%. And by ...
  72. [72]
    How Large Will the Paid Feed Reader Market Be?
    Apr 18, 2013 · ... Google Reader had “tens of millions of monthly active users." CNN had 25,120,973 subscribers on April 15th, 2013. Engadget had 6,840,662 ...<|control11|><|separator|>
  73. [73]
    Google Reader isn't dead, it was killed with *tens of millions* of ...
    Google Reader isn't dead, it was killed with tens of millions of users. Three million people have already migrated to Feedly, and that's just the more savvy ...
  74. [74]
    Google Reader Still Drives Far More Traffic Than Google+
    Mar 14, 2013 · But the relative numbers are still surprising: Despite claims that it has over 100m monthly active users, Google+ barely moves the needle for ...
  75. [75]
    How Google helped destroy adoption of RSS feeds
    Aug 14, 2023 · Users were left with no RSS reader application, no comparable alternative, and no education from Google on how to continue using their RSS feeds ...<|control11|><|separator|>
  76. [76]
    Google Kills Reader, Helps RSS - Forbes
    Jun 29, 2013 · On Monday, Google will turn off Google Reader, a product that allowed users to read RSS feeds, a way to get information quickly from ...<|separator|>
  77. [77]
    Google Reader Killed RSS - Dan McKinley
    Dec 18, 2019 · As long as Google Reader existed, the two available paths out of this were out of reach. Anyone with money who believed in RSS as a consumer ...Missing: impact | Show results with:impact
  78. [78]
    Google Reader Was Shut Down 10 Years Ago. What Happened to ...
    Mar 21, 2023 · Google Reader may be gone, but RSS is still all around the web. Here's a short history of RSS readers and which ones are available in 2023.
  79. [79]
    How RSS feeds lost the web - The Washington Post
    Jul 2, 2013 · Google Reader is dead, but it never really lived ... Many more people, though, never adopted RSS feeds in the first place; even Google's numbers ...
  80. [80]
    Google Reader goes haywire for many users - CNET
    Feb 11, 2013 · A number of the Web giant's RSS feed reader devotees notice disappearing subscriptions, feed issues, and other problems with their accounts ...
  81. [81]
    News: Speed Up Google Reader Load Times - Lifehacker Australia
    Apr 2, 2008 · ... Reader, but noticed Reader can take forever to load feeds with longer items. His solution? Switch to List View. The default view in Reader ...
  82. [82]
    My Complaints and Suggestions for Google Reader - Carlton Bale
    Only Show the Latest Stories: If Google Reader won't show me the most popular stories on “high volume” sites, at least ...Missing: slow loading
  83. [83]
    Google Reader now running up to 50 hours behind
    Jul 21, 2011 · I'm now looking at the RSS feeds from one of my blogs, and gReader neglected to update that feed for close to 50 hours. That is a new record.
  84. [84]
    No, I Don't Miss Google Reader - Flameeyes's Weblog
    Feb 11, 2024 · Google Reader was a feed reader that fetched content from websites. The author doesn't miss it because it wasn't their only feed reader and it ...
  85. [85]
    Anybody else seeing weird glitches with Google Reader? : r/google
    Anybody else seeing weird glitches with Google Reader? I am seeing articles and starred items not appearing properly (basically blank). Upvote 26. Downvote
  86. [86]
    A second spring of cleaning - Google Blog
    Mar 13, 2013 · So, on July 1, 2013, we will retire Google Reader. Users and developers interested in RSS alternatives can export their data, including their ...
  87. [87]
    A month after Google killed its beloved Reader, the market for paid ...
    Aug 2, 2013 · It's been a month since Google Reader shut down, breaking users ... In the weeks following the announcement, Feedly saw 3 million Google Reader ...
  88. [88]
    Did Google kill RSS? - Planet Argon Blog
    Mar 13, 2013 · The truth is this: Google destroyed the RSS feed reader ecosystem with a subsidized product, stifling its competitors and killing innovation.Missing: impact discontinuation
  89. [89]
    How The Shutdown Of Google Reader Threatens The Internet - Forbes
    Mar 14, 2013 · RSS plays a crucial role in fostering intellectual diversity on the Internet, and the shutdown of Google Reader potentially threatens the ...<|separator|>
  90. [90]
    The Death Of Google Reader And The Rise Of Silos - Techdirt.
    Jul 5, 2018 · Many people have pointed to the death of Google Reader as a point at which news reading online shifted from things like RSS feeds to proprietary ...
  91. [91]
    It's Time For an RSS Revival - WIRED
    Mar 30, 2018 · The platformization of the web has claimed many victims, RSS readers included. Google Reader's 2013 demise was a major blow; the company ...