Google, Please Don’t Disrupt the Continuity of Google Page Creator Sites

closeThis post was published 13 years 5 months 12 days ago. A number of changes have been made to the site since then, so please contact me if anything is broken or seems wrong.

Don’t worry, I’m working on a post about my summer at Northwestern University. It’s just a lot of writing, thinking, and recalling, so it’ll take some time. Meanwhile, this post has a very important message I wanted to get out.

All right, someone needs to think. Hard. Someone at Google, that is. Why? Because a lot of people, including me, will be potentially made unhappy when Google Sites takes over for Google Page Creator.

Google Blogoscoped published “Google Slowly Closing Page Creator” a few days ago, which got me thinking. How much do I use Google Page Creator? For its intended purpose (creating pages), not much. But I use it quite a bit for hosting miscellaneous images and bits of XML (like gadgets and FeedFlare units) that I use all over the Web. So what will happen if Google migrates me to Google Sites?

The Bad

The bad possibility—one that I sincerely hope they avoid—is that I will be moved from to Links all over the place will break. Images will be missing. My blog feed will be missing FeedFlares. Countless emails will no longer look right. Sure I can fix much of the damage, but that assumes Google will migrate my files, too.

The Hope

My hope is that, using the custom domain feature of Google Sites, migrated Google Page Creator users will simply have their back-end replaced, while the public-facing part of the site (pages and files) appear to remain the same. No broken links, no discontinuity, no user aggravation.


I guess my point in writing this (there are other discussions, too; here’s one from FriendFeed and one from Labnol) is to try and get Google’s attention. Please, Google, please let us know more details about your migration plans. If migration is going to break links and change URLs, please tell us now so we can begin preparations!

Update (12:51): I nearly forgot about files! Of course accessing existing files is covered under not breaking links, but I totally forgot to mention that there’s a possibility of them being deleted in the move or (worse, I think) migrated but hidden in the interface, making deletions, changes, and new uploads impossible. (Thanks, Tony!)

Update (17:46): Ionut at Google Operating System posted on this a few hours ago, and I see he found a Google Groups thread that explains in a bit more detail what will be happening. Google Page Creator sites will be redirected to their Google Sites counterparts. However, it still doesn’t mention how files will be handled…


I am an avid technology and software user, in addition to being reasonably well-versed in CSS, JavaScript, HTML, PHP, Python, and (though it still scares me) Perl. Aside from my technological tendencies, I am also a theatre technician, sound designer, violinist, singer, and actor.

One Comment:

  1. With Google Page Creator you could upload HTML files and it was much easier to make your pages look exactly the way you wanted using uploaded HTML files and CSS files (or CSS in HTML). With Google Sites you can’t use uploaded HTML files with CSS and you can’t use scripting either.

    When I tried moving my Google Page Creator pages to Google Sites, I had to copy and paste the HTML source from the HTML files and change and tweak the HTML and it still looks disgusting. Also, my week old Google Sites website got banned, because its spam filter sucks so I had to contact the Google Sites team to get my Google Sites website back. Now my pages are back to Google Page Creator and I’m not sure what I should do. Google Sites is definitely Beta and should be told on every page on that service.

Leave a Reply

Your email address will not be published. Required fields are marked *

Notify me of followup comments via e-mail (or subscribe without commenting)

Comments are subject to moderation, and are licensed for display in perpetuity once posted. Learn more.