Classic Google Sites shutting down by September 2021
support.google.com
support.google.com
A few weeks ago, we activated GSuite for our organization, and from then on could no longer access our Classic Sites. After a long and confusing support chat session, it turns out that our Classic Sites were simply wiped without a warning when we activated our GSuite for the same domain, because of a bug due to some funky deprecation-stuff of Classic Sites.
So yeah, we're pretty pissed that us subscribing to another Google product caused our old stuff to be deleted because of a bug. But it's not that surprising given the rush Google is apparently in to deprecate Classic Sites.
Oh, and I don't think Google's gonna take the time to fix this until the final ditch, so be wary if you still have Classic Sites and are getting GSuite soon!
Also they require £30 payment (well $30 dollars with no other info on how to pay it in any other currency) to allow your org to create YouTube accounts now for some reason otherwise it throws an error. This is a policy decision.
Whole thing feels like an incoherent poorly designed mess.
I use O365 now which actually works properly so fuck ‘em.
You can say this about the majority of Google products. They gain momentum because Google, but under the hood they're crap.
One of the best decisions I made was dropping Google and self-hosting my public-facing services. In this day and age, it's much easier to set up reliable, available services without needing an in-house data center. IMO, it's worth the small extra hosting cost to be the master of your own domain (heh).
The converter theoretically converted the sites, but they went from being a perfectly useful, although basic looking site to looking fucked up and broken.
It’s an anti-feature to do this. It’s sort of free, so I can’t make too much of a complaint.
But it’s a reminder that nothing Google lasts. I just needed a simple list of google docs 10 years ago for a project. The saddest part is remembering how I felt to have that tool available to me back then. I never expected that Google would turn into whatever they are now.
“Organize the world’s information, in a Zip file, in a private cloud folder, making it not useful at all.”
I wish I had thought to save the old URL in the Internet Archive beforehand, but it never occurred to me that Google's conversion process would just destroy it.
Just have to hope people notice before their sites go offline.
The cost would be a rounding error for them.
Any idea if Google donates to The Web Archive Project? I hope so. That would absolve them to some degree.
I know a company shouldn't be responsible for storing people's content indefinitely but I hate the fact that human culture has become so transient.
In the end, it turned out to be extremely difficult to do as you describe. First, static sites, for us, aren't really static - there's dynamic content on a page, there's certain core components that we have to be able to serve, for example, we have to have a mechanism for people to report abusive sites, have to have a mechanism to remove those sites, and we also have to have the ability for users to request the deletion of these sites, and so on.
In the end, it was going to come with a significant amount of engineering cost to continue to deliver static sites, even with reduced fidelity and a worse user experience. We felt it was better to be clear with users that we are going to transition them to the new platform along with providing them with a backup of their content to insure nothing was lost.
I'll say that the vast majority of current classic sites are extremely old and inactive, and not receiving any traffic in the last two years (editors or visitors). In addition, more than 90% of users currently choose new sites when they are building a site, so we are giving users a long window of notice to decide how they want to handle their sites, whether active or inactive.
A few things to consider:
- The reputational damage of solidifying the narrative that Google drops projects without a good reason from the users' point of view.
- A bare-bones deletion/flagging UI does not seem like a huge undertaking (though as an engineer I realizing it's not exciting work); working things out with a non-profit such as the Internet Archive or a museum could be an even lower-cost solution.
- 90's websites are also hideous ("worse user experience") by today's standards, yet they have charm and are a product of their times. I don't think anyone would argue that they should be deleted on account of that, just like ancient pottery often has "badly drawn" human figures yet the value is in the cultural expression. There are digital conservation efforts by museums (e.g. restoring 80's arcade games); I'm sure that consulting with a digital conservator would have arrived at a very different treatment of this data.
That ship has sailed. Google's reputation for instability can't get any worse. At this point, it would take a complete 180° and a good 5-10 years of angelic behavior from Google for me to even consider relying on them in any capacity.
i stll giggle at my ignorance thinking they wouldnt do youtube and search.
i really mis search, it was such a nice product. Now it is so bad that internet natives who could slap together a website in 20 min dont understand when i ask them why they have no website of their own. "you mean like a resume?"
they are right of course. no one would ever find it.
Implementing flagging and deletion is easy-ish, the maintenance is hard.
There's maintenance for unit, integration, and web driver tests. Someone needs to be oncall when they fail or become flaky. Someone needs to keep them up to date as tools and infra are deprecated. What's the SLA and SLO? Someone will have to maintain that. Who responds to monitoring?
Regulatory changes require effort, tests need to be updated, legal needs to sign off, UX may need to be involved. Who will make sure the sites maintain regulatory requirements?
You're right that it may be better to partner with someone else for archiving.
This sounds like a money problem to me. The argument is that people have to do boring work.
Yes they do, and isn’t that what money is for?
“””Our company mission is to organize the world's information and make it universally accessible and useful.”””
Fixed. I have no use for Google any more.
They were relevant 10 years ago but no more.
That content is old does not make it worthless. That it's not receiving visitors (much less for as little as 2 years) does not make it worthless.
If you're ever looking for the historical reason of something, the answer is probably going to be in a source that nobody's laid eyes on for several, several years.
If you're looking for content to remove from the internet because it's old and static, why not start with Shakespeare? Seems to fit Google's definition of "worthless."
In general, I see this type of dismissiveness way too often - e.g. "What's the big deal? I could build this in a weekend." or "Why doesn't big company X just do this simple thing?" It's only when people actually try to build a business around even the most trivial of problem that they realize the complexities involved with long term support.
It's a different situation here. A lot of cultural objects' survival is now contingent on whether their continued existence happens to be profitable for whatever tech firm happens to be maintaining their material infrastructure.
But I won't really argue that preserving the public web should probably be done by public institutions rather than depending almost solely on one non-profit organization. Because it's not reasonable to expect, for example, a website that's been hosted on some provider to be saved forever by that provider once the monthly bill stops being paid. (And that provider will probably go out of business sooner or later anyway.) Do you even want to bet on Google or Facebook being around in 50 or 100 years?
Turning off a web server on its own isn't removing web history
When Google targets sites that are least likely to have a backup anywhere else, least likely to have active admins, least likely for an admin to notice an email notification in an old inbox, I'm pretty sure that's deleting web history.
Huh, must have been about something else.
There's your problem
We’re going to lose a valuable source of old data if former admins don’t show up, do the work, and rehost
They only gave me a "converted site" in my gdrive when I downloaded from the migration manager.
thanks for the AMA-like availability, really appreciate it.
One question from me: how would you pitch "new Sites" for a potential new customer willing to use it, but afraid his/her/their content might not last the next "modernization" sweep?
In other words: would you try to sell new Sites to a customer that values - and worries about - long term visibility of his/her/their content? If no: what is new Sites' value proposition, in terms of target market?
Thanks again.
Why do you (your team) really have do do this?
This is digital destruction. It's not about the features you shipped in 2008, and what those look like to a 2020 audience. It's about the content(!) which is part of the human creative endeavour.
Thanks for taking questions.
That being said, I hear the feedback, and I'll talk to the team about what we might be able to do, within legal and privacy constraints, to protect published sites.
Whether or not a site has had visitors recently isn't a fair measure of the importance of those sites -- for instance, there were examples of digital shrines in GeoCities and Yahoo still decided to eradicate them all. It was only thanks to projects like the Internet Archive that we haven't lost that period of internet history just to free up some disk platter space.
EDIT: I also am struggling to understand what this means:
> To me, archiving those sites doesn't feel like destruction, it feels like backing up unused content and protecting it for the user.
What does "archiving" mean here? Will the sites still be accessible or not? Is "archive" here a euphemism for "delete" -- in which case, how is it not like destruction and how is it like a "backup"? I'm not sure most people would consider "rm -rf" to be a backup strategy, but it definitely does have very good storage density.
My concern isn’t that the files don’t exist any more,I think it’s nice to zip it and add it to the owners gdrive, my concern is that the files are no longer accessible on the web. So all the links are broken, no longer in search, etc.
This seems like a much larger issue than archiving and it would be cool to hear how you all decided to take the sites offline.
Is it a cost issue? I imagine hosting a billion static sites shouldn’t cost much.
I'm having a hard time understanding why that would justify deleting that information forever. If anything, that suggests that providing static access would be enough and nearly zero-cost. Storage costs are a fraction of what they were.
I do a lot of searching for computer-related historical information, e.g., looking for rationales of "why something happened". Once information is destroyed it's often impossible to recover. No one might look at it for 30 years, and then there's only one retrieval but it was an important retrieval.
We've had a tremendous loss of recent information. This isn't the only example, but it's an important one. I'd like to see information retained, not lost.
I had forgotten about my Google site until seeing this posted. The last update of any kind was early 2013; most content was from 2011 or earlier. Some of the information on the site is wrong, a lot irrelevant, and worst of all, someone might not find my real site because of that one. I'd much prefer a dead site stop working to leaving it out there.
I mean.. if I don’t use my Facebook account anymore I wouldn’t expect Facebook to delete everyone else’s profile?
Yet when I visited the Classic Sites Manager it shows nothing. ("0 owned by you" and 0s all the way down the rest of the suggested filters.)
False positive, maybe? The email sounded like y'all were pretty certain: "We’ve identified that you own one or more ACTIVE classic Sites."
I tried the conversion tool on a dummy site and it opened a Google doc. I am not sure how an HTML page with embedded Google form with a script will be converted to new Sites.
UPD: I assume Google Sites has lots of customers (we were one of them)
Every page in the zip backup, no matter how simple, is around 59K because of all the Javascript Google wraps around simple text. My plan is to convert everything to some flavor of Markdown, but parsing this mess is not going to be exactly easy.
I appreciate that the goal of this backup was to allow me to host it "as is" somewhere else - with no possibility to edit it, which seems rather useless.
What would be really nice is to also get a zip file with some simple Markdown pages that include user editing (font sizes, bolding, etc), without everything being wrapped in Google's Javascript.
We first announced this gradual plan in 2017, with an update in 2019, and now we're providing the detailed plan. The goal was to provide adequate notice for people to figure out whether migration, export, or deletion of their classic sites makes the most sense.
EDIT: to the multiple people that are highlighting that 12 years is not a long time, I should clarify. I agree that 12 years in Internet time is not a long time, but it is a very long time in "how websites work" time.
One of the big challenges in the website builder space, something that Google. Wix, Squarespace, have all dealt with - is that when a user publishes a website, there's an expectation around the fidelity and look-and-feel of that website. The data model and architecture for how you represent a rendered page, how you render embedded content, all are very dependent on how browsers work at that time, and the maintenance of those things can become very challenging.
There was a big shift about ~7 years ago, moving away from a "pixel perfect" layout/raw html approach (Wix, Old wordpress, SQSP 5, Classic Sites), to one where there's some sort of grid-and-box approach where the render is responsive, there's reflow, there's padding and spacing and styling relative to the browser experience. It separates out content from layout to a certain degree in a way that is much more future-proofed and modern. This is how Wix ADI, Squarespace 6+, Wordpress Gutenberg, and new Sites work.
For all of those transitions, there was a platform shift, that required a complete rework of how the system works. My point about "12 years" was that the model of how classic Sites works is 12 years old, and new Sites was intended to match the modern way of how websites are built and delivered.
In this particular case, with Google Sites, maybe the decision was totally justified, I don't know. But, as a general trend across the technology industry, this type of explanation really bothers me, and I think it speaks to a serious mindset problem.
The fact that X is old and Y is new is not a reason to replace X with Y. Hammers are old, but they're also exceedingly useful tools. Users are familiar with how hammers work, and companies have become good at manufacturing them.
The question should be whether the new tool is better than the old one, and if it is, whether it's so much better that forcing every user to re-learn the new tool will be worth their while. And even then, it's worth asking why some of the largest companies in the world can't let both tools coexist, perhaps with the older one kept semi-hidden to avoid confusing new users.
Anyway, sorry for picking on you, I appreciate your willingness to pop into a somewhat-hostile thread. :)
A website maintained with raw HTML still works just fine on modern web browsers. In fact, it works much better. Web pages built with some CMS systems often take 5-20 seconds to load, while the "raw HTML" sites load in fractions of a second. In fact, the speedups continue; JavaScript parsing is slow, while HTML parsing is fast, and HTML compresses like magic. So a "big" HTML file is transferred and displayed in remarkably fast time.
I wouldn't use raw HTML in all cases, but I also wouldn't use a fancy CMS in all cases.
It's okay to use different platforms for different purposes.
This mobilification is a fad, and like many fads it will, too, disappear and have to be replaced (requiring many work hours) because ultimately it’s less usable especially for largely static content. There’s no option to keep a similar look and feel. “Mobile first” has been forced upon us and is now, with reflow, “mobile only.” Imagine if Arxiv required PDFs to be replaced by mobilified versions? So annoying and impractical.
Really disappointed. Google made a bunch of work for themselves just to reduce the usability of older web pages.
Google's misson is "to organize the world’s information and make it universally accessible and useful". Dropping sites on the cutting room floor because information in them isn't in a convenient format does not make that information accessible or useful.
Anything I can say would only detract from this.
This is modern Google.
Also RHEL support lifecycles are 11+ years, so for RHEL 8 released in 2019, that's a commitment to ~2030 right here and there & with doing this for many years for the past releases proving the point.
No wonder the most critical stuff (Bank, Stock exchnages, etc.) run on RHEL and not on some half baked Google stuff that will get deprecated from under them at a moments notice.
What should have happened is to turn Classic Sites (and new Sites) itself into Squarespace competitor.
I just see this as a massive failure of vision and execution.
Why didn’t they improve classic sites and added yet another product called Sites? May be I am seeing some internal politics surface as fragmentation of product line.
To your Squarespace comparison, Squarespace went through a similar transition - Squarespace 5 worked very similar to Classic Sites, and was replaced with Squarespace 6, which was a complete end-to-end rewrite.
Also, people have technical knowledge here, even if they've never been hired by someone as "the best of the best," or having graduated from a top 10 CS school, so handwaving "fundamentally works differently" is not actually likely to be the enlightening description you might hope it would be.
Huh? Did that 10 years ago. Perhaps we have a different definition of a "classic site".
To me a "classic site" is another name for a static site, that is, a website where the HTML to be served is pregenerated. Static sites are now coming back, not going away. But I always assumed that a website should reflow.
Perhaps when you say "classic site" you mean "site that assumes that all users have the same display size". I agree that such classic sites are nonsense today. But they were always nonsense. At no time was there a guarantee of any particular screen size for HTML, and it's always been easy to write HTML that just reflows. If you do that, your site works just fine.
GP didn't say “classic site” they said “classic sites website”. You seem to be interpreting that as intended to be a somewhat redundant and mispunctuated rendering of “classic site’s website”, but given that the context is a discussion for the shutdown of Google’s classic Sites in favor of only supporting Google’s new Sites mode, I think that it's just a capitalization-omitted rendering of “classic Sites website”, that is, a website using classic Google Sites as opposed to new Google Sites.
Could have called it Classic Sites 2.
My belief has always been "no". Google could kill off the entirety of GMail tomorrow, and I'd be disappointed, but totally understanding.
I know others have done this, but if Google built it and tied it into their Maps product and then ads it would theoretically make it extremely easy for a local barber to control it all in Google and Google would see incremental ad spend.
Instead Sites has been ignored, Blogger has languished, and Squarespace and WordPress are now the defacto tools for SMBs.
Kind of a head scratcher.
I might even use the new version for however long it lasts.
I suspect sites, at some point, didn't make enough money to maintain a separate team with a skill set that wasn't common at Google.
It take 16 months after the purchase before they relaunched it, though. So perhaps they had already rewritten it in a Google tech stack?
(Source: worked at Google 2006 - 2010, was very slightly involved in helping the Jotspot team integrate)
Could we update to use the original title? "Transition from classic Sites to new Sites"
> Google will notify Customer at least 12 months before a Significant Deprecation [1]
1. https://gsuite.google.com/terms/2013/1/premier_terms.html