Google Sites for Schools: What It Actually Does
I spent about three years helping schools set up student websites before I burned out on it. Google Sites is the simplest tool in G Suite for building basic web pages. It comes free with a Google Workspace for Education account. The interface is essentially a drag-and-drop block system. You add text, images, embeds, and navigation elements. That is the entirety of it. It is not WordPress. It does not have plugins, themes, or real customization options. It does not need them for its intended purpose. The whole concept of "unblocked" Google Sites usually comes from school IT departments that filter internet access on their networks. Google Sites itself is not blocked by default in most districts, but related services like Google Drive sharing, embedding external content, or publishing to a public URL can trigger filters. Teachers and students work around this because some assignments require publishing websites for portfolios or group projects. Go to sites.new and pick a template. The blank template is usually the better choice if you want the page to look anything like what you actually intended. Templates come with preset layouts that are hard to modify without rebuilding sections. Fill in a page name, add a navigation structure through the Pages panel on the right, and insert content blocks from the Insert menu.
The publish process works like this: click Publish, enter a site name, and choose your web address. The URL format is typically sitename.site or uses a custom domain if your school has one configured. Once published, the site goes live instantly. There is no approval workflow unless your admin has enabled it through the Workspace controls. That matters more than people realize.
What People Get Wrong About Google Sites
The biggest mistake I see is assuming Google Sites can handle complex functionality. It cannot. No forms that collect data into a spreadsheet without linking to Google Forms. No member logins or role-based access control beyond making the site private to your organization. No blog-style post management. If you try to build something beyond a basic informational page, you will hit walls within an hour. Switch to Google Workspace Sites alternatives like Squarespace or even a simple WordPress install through your school's tech department if you need more capability. Another issue is the mobile editing experience. It is not functional. I tried to adjust a layout on my phone once and spent twenty minutes failing to drag a block into the right position. Always edit on a desktop or laptop. Publishing from mobile is possible but editing existing pages is not worth the frustration.
Get the Full Details
Embedding Content Without Breaking Filters
When your school filters are active, embedding YouTube videos, Google Maps, or external documents can fail silently. The content shows up as a blank box or an error message. The workaround I ended up using regularly was to host the content through Google Drive first, generate the proper embed code from there, and then paste it into the embed block. Sometimes you need to adjust the permissions on the Drive file to "Anyone with the link" for it to display correctly inside the Site. I ran into a specific problem last year where a teacher's Google Slides embed was blocked by the school filter even though the presentation was shared publicly. The slides worked fine when accessed directly. Inside the Site, the iframe got stripped. The fix was to export the Slides as HTML and upload that as a file instead. Not elegant, but it worked immediately.
Permissions and Who Can See Your Site
By default, published Google Sites are accessible to anyone on the internet if you set the sharing to "Public." If you are using a Workspace for Education account, you can also restrict access to only people within your organization. This is useful for internal class pages that should not be indexed by search engines. Check the Publish settings carefully before going live. I once published a student portfolio page and forgot to verify the visibility setting. The site was searchable on Google for about six hours before I caught it. Students' full names and project links were visible. It was not a disaster but it was unnecessary stress. Google Sites does not support custom CSS or JavaScript. You cannot inject tracking codes except through the Google Analytics integration, and that requires a Workspace admin to enable it. Page speed is generally fine but you have no control over it. Large image uploads slow down loading times and there is no built-in compression or lazy loading. Keep images under two megabytes each and resize them before uploading. Images above that threshold tend to render poorly on mobile devices. There is no native version history for published sites. If you make a mistake and publish, you have to unpublish, fix the content, and republish. There is no draft state that publishes automatically on a schedule. For basic educational use this is tolerable. For any project requiring frequent updates or A/B testing, it falls apart quickly.
Download or Access Information
Google Sites is included with any Google Workspace for Education account at no additional cost. There is no standalone download. It runs entirely in the browser. The free personal Google account also provides access with some feature limitations compared to the education tier. Students without a school account can use a personal Gmail account but lose access to admin-controlled sharing policies and certain integrations. If your school has not set up Workspace for Education yet, contact your IT department. They usually already have a license or can request one. The setup takes about a day for a standard district deployment.
