Google Sites Review: Features, Limits, and Use Cases

Google Sites is free, takes about an hour to learn, and is the correct answer for a narrow set of jobs: internal team pages, resource hubs, and anything that exists to put live Google Drive files in front of people who already have Google accounts. For a public marketing site, a store, or a blog, it runs out of room long before your content does.

Buyers land in one of 2 camps. The first treats it as a real website platform, builds 40 pages of customer-facing content, then learns a year later that none of it can be optimized or moved without a rebuild. The second writes it off as a toy and pays for intranet software that does less than a free product already in their Workspace.

The useful question is not whether Google Sites is good. It is which jobs it actually finishes.

What Google Sites Actually Is

Google Sites is a drag-and-drop page builder attached to your Google account. You add sections, drop in text, images, Drive files, YouTube videos, Forms, and Calendar embeds, then publish. The editor borrows its toolbar and shortcuts from Google Slides, which is why someone who has never built a website gets a usable page on the first attempt.

That familiarity is the entire product strategy.

Google launched Sites on February 28, 2008 using JotSpot technology bought in 2006, and shipped the rebuilt version in 2016. Classic is not winding down. It is finished: editing stopped December 1, 2022, viewing stopped January 1, 2023, and Google replaced the remainder with Takeout archives.

One version left to evaluate.

What Google Sites Costs

Nothing, for the builder. Any Google account, including a free Gmail one, can create and publish sites.

• Publishing is free, and the default address is sites.google.com/view/your-site-name
• A site owner can connect a domain they already own under Settings, Custom domains, up to 5 per site
• Buying a new domain through Sites needs a Workspace plan; admin-console URL mapping applies to work and school accounts
• Restricting a site to your organization needs Workspace; a personal account shares publicly or with named Google accounts
• Embedded files draw on your Drive quota, 15 GB shared across Drive, Gmail, and Photos on a personal account
• Google advertises no bandwidth cap on published sites

The custom-domain rule is the one most roundups get wrong.

Owning the domain already is enough.

Workspace buys 3 other things: a domain purchased through Google, admin-console URL mapping, and a site kept private inside a company.

No subscription.

If you do need Workspace, price it on Google’s own pricing page. A Business Base tier now sits below Business Starter, and the page quotes in local currency, so any dollar figure in a comparison post is regional and stale.

What Google Sites Does Well

It wins on one axis, and it is not design.

It wins on live data: an embedded Sheet keeps updating, a Doc stays current, a Calendar stays bookable, each carrying the permissions its file already has.

Internal team pages. Policies, contacts, holiday calendars, onboarding checklists, with nobody updating the same fact twice.

Resource hubs. Course libraries, reading lists, new-hire packets. Replace the file in Drive and the page reflects it.

Project and event one-pagers. A Form for signups, a Calendar for dates, a folder for documents, shipped in an afternoon.

Permissions that match the org chart. Domain-restricted, group, and named-person sharing reuse the Google identity your team signs in with anyway.

All 4 have the same shape: the page is a window onto files that already exist.

If the real content lives in Drive and the audience already has Google accounts, Google Sites is the cheapest correct answer. If either half of that sentence is false, it is the wrong tool.

That test ends most internal arguments about it.

Where Google Sites Breaks

The failures cluster around one thing: anything the page must do for an audience that did not already know it existed.

SEO Controls

This is the real ceiling. Google exposes no setting for the fields an optimizer edits first.

• No per-page meta description; pages fall back to the site description
• No title tag field separate from the page heading
• No structured data or JSON-LD control
• No per-site sitemap; sites.google.com/sitemap.xml returns a 404
• No robots.txt of your own; sites.google.com serves one Google-controlled file for the whole host
• One documented search setting, a publish-time toggle asking public search engines not to display the site

That toggle is the whole surface. It can hide a site and it cannot help one rank, so your page competes against rivals editing a title, a description, a canonical, and a schema block, the baseline every one of the best SEO plugins for WordPress assumes.

Design Control

The 6 preset themes get quoted as proof there is no design control. That stopped being true in September 2021, when Google shipped custom themes to personal and Workspace accounts alike, covering fonts and text styles, colors, brand images, navigation, and buttons.

What survives is the level you work at. You control the theme, not the element, so a layout needing one section to behave differently has nowhere to say so.

Theme level only.

Custom Code and Tracking

The claim that Google Sites blocks custom code is wrong, and it is the easiest thing here to check yourself. Google Sites Help documents Insert, Embed, Embed code for HTML, CSS, and JavaScript, with one rule:

“JavaScript code must be within <script> tags. CSS code must be within <style> tags.”

Google Sites Help

So the code goes in. Where it lands is what matters.

Embedded code runs inside a sandboxed frame. It renders a widget, a chart, or a third-party form, and it cannot restyle the site chrome, override the theme, or read the page around it.

That is why tracking stops where it does. Settings, Analytics accepts a Google Analytics property ID and nothing else, and a pixel inside an embed measures the iframe, not the visit.

Sandboxed, not absent.

Blogging and Ecommerce

New Google Sites has no blog page type. None. The reverse-chronological Announcements template belonged to classic Sites and never carried over; the Announcement banner in the current product is a notification bar wearing a similar name.

No RSS, no categories, no tags, no comments. A Sites blog is a stack of ordinary pages you reorder by hand.

Ecommerce is the same story with money attached. A Gumroad button, a Stripe payment link, or a Shopify buy button each takes a payment, and none gives you a cart, shipping rules, tax handling, or customer accounts. Different starting point from the WordPress ecommerce plugins built around product types.

Google Sites Alternatives Worth Comparing

Four tools cover almost every case where someone starts here and regrets it. Prices come from each vendor’s own pricing page.

Tool	Entry cost	Custom domain	Best job
Google Sites	Free	Connect a domain you own, up to 5 per site	Internal pages built on live Drive files
Carrd	Free tier; Pro Lite $9/year	From Pro Standard, $19/year	One-page personal sites and landers
WordPress	Software free; you pay for hosting	Yes, any registrar	Content sites, blogs, stores, anything search-led
Webflow	Starter free; Basic $15/mo billed yearly	Yes	Brand sites where the design is the product
Notion Sites	Publishing included on any plan	Add-on, $10/mo per domain, paid plan required	Public docs and knowledge bases

Read the third column before the second. Three of the five charge separately for the thing Google Sites hands you free.

Carrd

Carrd is the better answer for a personal site, a portfolio, or a single-page lander. Its Pro ladder runs Pro Lite at $9/year, Pro Standard at $19/year, and Pro Plus at $49/year, with higher site-count variants at each tier.

• Custom domains start at Pro Standard; Pro Lite gets only Carrd’s Premium URLs
• Pro Standard adds Local Fonts and Meta Tags, the meta control Google Sites never exposes
• Deeper custom code sits under Advanced Settings and Site Files on Pro Plus, not the $19 tier
• Form integrations go to email tools including Mailchimp, Kit (formerly ConvertKit), Brevo, Klaviyo, and HubSpot; there is no Google Sheets destination

Carrd buys editable meta tags and a page that looks chosen rather than assigned, and gives up Drive entirely. It sits alongside the other portfolio website builders.

WordPress

WordPress wins any site whose purpose is to be found. Title tags, meta descriptions, canonicals, schema, and robots directives are all editable fields, and the directory currently offers over 69,000 free plugins covering categories Google Sites treats as out of scope.

The cost is hosting plus your attention, and both vary too widely for one number. A brochure page on shared hosting and a 500-page site on managed WordPress are not the same purchase, and renewal pricing on cheap hosting plans is where first-year budgets go wrong.

Updates, backups, and security become your calendar entries rather than Google’s.

Webflow

Webflow wins when the design is the product. Its current site plans are Starter (free), Basic at $15/mo billed yearly, and Premium at $25/mo billed yearly, with Team and Enterprise above them, and Ecommerce plans starting at $29/mo billed yearly.

You get real CSS layout, scroll animation, CMS collections, and markup a developer can pick up. You give up hosting choice, since a Webflow site stays on Webflow. The rest runs through the WordPress vs Webflow comparison.

Notion Sites

Notion Sites, which shipped in June 2024, is the closer match for public documentation. Every workspace member can publish a Notion page as a site on any plan, free included.

The catch is the domain. Notion’s help center puts it behind a paid plan plus an add-on at $10/month per domain, or $8/month billed annually.

Two line items.

Mobile Behavior

Pages are responsive in the narrow sense. Sections stack and columns resize on a small screen, and the editor has a mobile preview. What it lacks is a separate mobile layout, so you cannot fix a phone problem without changing the desktop version too.

One layout only.

• Holds up on phones: single-column stacking, embedded Drive files, YouTube videos, Google Forms, buttons and links
• Struggles on phones: multi-column image grids, wide tables, and any custom embed whose iframe carries a fixed width

For an intranet read on company laptops, none of this matters. For a public page where phones are half the traffic, you want a platform that treats responsive web design as a decision, not a fallback.

The Limits

Three constraints survive every workaround.

Export is not portability. Google Takeout does export Google Sites, and Google leaned on Takeout archives when it retired the classic product, so nothing is trapped. What the archive is not is a file another CMS reads. No importer, no feed to map, so moving 30 pages means rebuilding 30 by hand.

Rebuild, not migrate.

The site is downstream of the account. A published Site depends on the Google account that owns it, with no second copy on infrastructure you control. Inside a company already running on Drive and Gmail, that is a risk you accepted years ago. For a revenue page, it is a single point of failure outside your reach.

You cannot see what happened. No server logs, no request-level data, no tracking past that one Analytics property ID. When a page underperforms, you are troubleshooting a public page with the instrumentation of a private one.

One thing nobody can confirm: Google publishes no page cap and no per-site storage figure. Undocumented is not the same as unlimited.

What Quietly Ruins a Google Sites Build

Putting customer-facing pages on Sites because the internal ones are already there. It feels like consolidation, and every page added that way is one more to rebuild later, none carrying a title tag worth optimizing.

Treating “we can embed anything” as design flexibility. Each embed is its own frame with its own scrollbar, load time, and breakpoint behavior, so 5 on a page is 5 independent things failing at 5 widths.

Buying Workspace to get a custom domain. Connecting a domain you own costs nothing, and the subscription you just approved was for private sharing and admin control.

Waiting for Google to ship the missing pieces. Blogging, meta control, and structured data have not arrived since the 2016 rebuild, and planning around an unannounced feature costs you the months you spend not switching.

Final Remarks

Google Sites is not a weak website builder. It is a strong Drive front end that people keep mistaking for one, and the mistake is easy because the free tier lets you build for a year before the ceiling appears.

The trade is honest once you say it out loud. You give up search control, element-level design, and any migration path that is not manual, and you get a page that maintains itself because the content lives somewhere you update anyway.

Pick it when the files are the point. Pick something else the moment the page is.

Continue reading: CMS Selection Criteria · Portfolio Website Builders · Website Creation Tips