The Pros and Cons of Google Sites

It's been a few years since I waxed poetic about the New Google Sites, and my love for them has not dimmed one little bit. They are so easy, so clean, integrated with Google docs, and simple to collaborate with multiple editors. I mean--sigh!--why can't all websites be like this?

Lately, as educators are looking for creative ways to put content online quickly, we have received a lot of questions about Google Sites. When are they a good idea? and when are they just adding to the web clutter?  Here, I'm going to describe when the web team thinks Google Sites are a good solution for making a website, and when something else in our web toolkit would be better. 

Here are a few guidelines that Extension's Web Team uses when deciding if a Google Site is fitting:

1. When your content is intended for a limited audience of stakeholders or a project team. For broader intended audiences, you will want to consider the main Extension site since it has better search engine optimization, content tie-in, and overall inclusivity of access.
2. When the content is only relevant for a limited time, it needs to be quickly changed or deleted, or is focused on “doing business.” 
3. When you need something like a program or project intranet. Google Sites can be a really nice way to organize team documents and information and control access.

Example. In which a Google Site saves the day (event)!

Remember the polar vortex of 2019? ELT had an open house planned for the day the University was closed, both an in-person event and a Facebook Live version. We had activities and food and a goal of having more people get to know us, and we were so bummed when it became obvious the day before that we would have to cancel. 

That day, in about two hours, I created a "Virtual Open House" Google Site. I was able to easily create separate stops on the tour (pages) and add photos from our team's shared Google Photos albums to make each page interesting. I shared it with the team, who made edits and suggestions, and we published it the next morning. VOILA! Lemons into (frozen?) lemonade. The format worked so well we did it again this year.

Why is this a good example of using a Google Site?

1. The audience is a limited group (staff members). There is no issue with this content being separate from a public main site.
2. The content is only relevant for a limited time. Google Sites are a great solution for temporary websites.
3. The content needed to be easily changed and collaborated on, and everyone involved had a Google account I could add as editor.
4. The content stands alone, without the benefits of tying into Extension's greater web presence (like broader navigation, related news feeds, etc.)

When not to use a Google Site

• When your content would be a great addition to the Main Extension site! 
• Educational Information
• Courses and Events information
• News blurbs
• When you have a lot of content
• When you are just using it to keep all of your web content in one place, for your own convenience
• When you're trying to avoid branding (I know you would never do this!!)

When in doubt...

The Extension Web Team would be delighted to talk over what website solution would be easiest and best in the long run for your content! Ask for your consultation anytime.