Back to the blog

Statistics

Discontinued Google Products: Verified Dates and Counting Limits

Check documented shutdown dates for Reader, Google+, Cloud Print, Stadia and Glass. Learn why product counts vary and how to plan for service changes.

Justin McGill5 min read

Current BrandWell RankWell editor showing article content, search preview, SEO recommendations, and growth-tool navigation
RankWell in the live BrandWell app, captured September 22, 2026. The article and score shown are an example from this workspace.
On this page
  1. Which Google products were discontinued?
  2. What should not be counted as a shutdown?
  3. How many products has Google killed?
  4. Why do services close?
  5. A practical continuity checklist for marketers
  6. Where the current BrandWell workflow fits
  7. Frequently asked questions

Updated October 3, 2026. Google Reader, consumer Google+, Cloud Print and Stadia are documented examples of discontinued Google services. Their closure dates are verifiable; a universal total or average product lifespan requires a defined inventory and counting method. This article uses selected examples rather than presenting an unaudited graveyard count as an official Google statistic.

Which Google products were discontinued?

A useful list names the exact product or edition, identifies the affected users and links to the original shutdown notice. Ending sales, ending support and switching off a hosted service are different events. A renamed product or a feature incorporated into another service also needs a different label from a complete shutdown.

  • Google Reader: Google announced retirement for July 1, 2013. Its announcement cited declining usage and a decision to concentrate on fewer products. Read the original Reader announcement.
  • Consumer Google+: account and page shutdown began April 2, 2019. The notice concerned the consumer service; it should not be interpreted as the closure of every Google account or Workspace product. Read the consumer Google+ notice.
  • Google Cloud Print: Google’s migration guidance states that the service was deprecated in January 2021 and is no longer supported. It discusses alternative printing configurations. This is a printing service, not the whole Google Cloud business. Read the Cloud Print migration guidance.
  • Stadia: Google announced that its servers would turn off January 18, 2023. The service notice also explains the treatment of purchases and refunds. Do not infer another product’s refund policy from this case. Read the Stadia availability notice.
  • Glass Enterprise Edition: sales ended March 15, 2023, with support ending September 15, 2023. Those are separate milestones, and neither should be used as the date of the earlier consumer edition’s sales change. Read the Glass Enterprise Edition FAQ.

What should not be counted as a shutdown?

The previous version of this article incorrectly treated broad brands such as Google Fiber and Pixel as discontinued. A device generation reaching the end of sales or support is not the same as an entire product family ending. Google Fiber’s current internet page continues to describe available service. Check availability for the particular location rather than assuming a universal shutdown.

Cardboard also needs a narrower description. Google maintains an open-source Cardboard SDK page for Android and iOS experiences. An open-source software project can continue after changes to a hardware sales program. Calling all of Cardboard “dead” would obscure that distinction.

Similarly, an acquisition followed by a sale is not necessarily a shutdown. Acquisition price, sale proceeds and retained assets do not by themselves establish the buyer’s net loss. Avoid ranking the “most expensive failures” without audited, comparable financial evidence.

How many products has Google killed?

There is no single verified total established by the selected primary sources above. Third-party inventories can be useful starting points, but their totals depend on whether they count apps, features, device generations, editions, integrations, acquisitions and replacements separately. The number also changes with the observation date.

To publish a defensible count, provide the underlying rows and define inclusion rules. Record product name, launch date, announcement date, final service date, support date, replacement and source. Deduplicate renamed services and label uncertain dates. State the inventory’s cutoff date and limits next to the number.

The same discipline applies to an average lifespan. Decide whether the endpoint is the announcement, sales stop or service closure. Explain which products have usable dates and whether still-active products are excluded. An average among discontinued products cannot establish how long a newly launched Google product will last.

Why do services close?

Use the explanation in each product’s original notice where one is provided. Reader’s explanation is evidence about Reader, not a universal explanation of Google’s decisions. A closure alone does not prove that the technology failed, users disliked it or a competing service caused the decision.

Do not add anonymous employee quotations without a traceable interview or publication. This revision also removes unsupported estimates about abandoned data centers, hazardous materials and e-waste. Quantifying environmental impact requires an identified study, system boundary, measurement period and attribution method.

A practical continuity checklist for marketers

These are proposed operating checks, not a prediction of any vendor’s future:

  1. Inventory dependencies. List the services behind publishing, analytics, lead capture and customer communication. Identify which workflow stops if one integration fails.
  2. Keep usable copies. Confirm the actual export options for content, assets and configuration. Test a permitted export and restore instead of assuming portability.
  3. Document ownership. Assign a person to review deprecation notices, access permissions and renewal dates.
  4. Plan a fallback. Specify the replacement workflow, what data can move and the manual steps needed. A backup file is not a tested migration.
  5. Review dates. Distinguish an announcement from the deadline for exporting data. Recheck instructions before acting.

Where the current BrandWell workflow fits

RankWell supports the content workflow, including briefs, drafts and editorial review. AIMEE helps execute configured work through connected tools. Neither product removes the need to verify integrations, keep appropriate copies and review platform notices.

Current RankWell content workspace
RankWell workspace captured September 22, 2026. Review current capabilities and publishing connections for your workflow.

Use a content brief to record the shutdown source and cutoff date, then have an editor check the claim against that source before publication. Product history is most useful when readers can distinguish a documented event from a prediction. See the current RankWell workflow.

Frequently asked questions

Does a discontinued product mean all related services are gone?

No. Check the named edition, affected accounts, service deadline and replacement. Cloud Print’s closure does not mean that Google Cloud closed.

Is a product graveyard count a reliable statistic?

Only within the inventory’s stated rules, sources and date. It should not be presented as a complete official total without evidence.

Can a marketer eliminate shutdown risk?

No vendor choice guarantees permanence. Document dependencies and test appropriate exports and fallback workflows.

Reviewed and updated October 3, 2026.

Written by

Justin McGill

Put your next growth opportunity to work.

Start with the product you need. Connect the work with AIMEE.