← Back to VeloCMS Learn

websites · Nov 18, 2026

What is Google Sites used for?

Google Sites builds simple team, project, class and event sites that embed Docs, Sheets and Forms. What it does, where it stops, and what to try next.

Google Sites is used to put together simple, mostly static websites for a team, a project, a class or an event, with live Google Docs, Sheets, Slides, Forms, Calendar and Maps dropped straight into the pages. Google's own product page describes it as a way to "create sites for your team, project or event that look great on any device." It's a page builder, not a blogging system or a store, so it suits information that people read and look things up in, and it starts to creak when you need a news feed, a checkout, a newsletter or fine control over search listings.

Disclosure: this guide is published by VeloCMS, one of the options compared near the end. Its weaknesses sit right beside its features.

Last verified: 2026-11-18. Everything about Google Sites below comes from Google's own help and product pages, and every price or limit for the alternatives comes from each vendor's own page, all read on 18 November 2026. Where a page was silent, contradicted itself or showed prices in a currency I couldn't confirm, I say so and leave the number out. Google's help pages are often written without dates, so a few details may have drifted since they were last edited.

What does Google Sites actually do?

It lets you build a small website in a drag-and-drop editor, with no code and no server to look after. You start from a template, add text, images and sections to a page, arrange pages in a menu, press Publish and pick a web address. Google's help page says you "can publish your site and decide who can see it," and the two choices that matter are Restricted (specific people and groups) and Public (anyone on the web).

The part that makes it different from most builders is the plumbing underneath. Google describes "deep integration with Google Workspace," and says you can embed content from apps such as Docs and a shared Calendar. Several people can edit the same site at once ("real-time co-editing" in Google's words), and the owner chooses who can edit. People outside your organisation can open a published site even without a Google Workspace account, so you aren't forcing every reader to sign up for anything.

Google's page also says you can use premade templates or create your own, customising elements such as images, fonts and menus, and it mentions creating custom themes. In practice that could let a company hand every team the same look and let each one fill in its own content.

Who uses Google Sites, and for what?

Google names three kinds of site in its product copy: team sites, project sites and event sites. The page's navigation points to Workspace for individuals, small businesses, new businesses, start-ups and enterprises, and its copy promises you can "build secure and reliable sites without IT support." That's the official picture.

The rest of this section is my reading of what that design suits, not a statistic about who actually uses it. I don't have usage numbers and I'm not going to invent any.

Internal team sites and intranets are the most natural fit. A page that links to the shared drive, the team calendar, the onboarding checklist and the request form is exactly what the tool is built around, and access can be restricted to the people who should see it. Nobody outside needs to find it through search, so the thin search controls (more on those below) don't hurt.

Class and school sites come next. A teacher can put the syllabus, a calendar, embedded slides and a sign-up form on one page without begging IT for a server. A club, a parent group or a volunteer project works the same way.

Project and event pages follow. A conference microsite, a wedding page with a map and an RSVP form, a product launch hub for an internal team: one page of facts, a few embeds, a date, done. These sites often live for a few weeks, which is where a low-maintenance tool shines.

Simple portfolios and small-business information pages are the edge of the range. A tradesperson or a consultant who needs an address, opening hours, a map, a few photos and a contact form can get there with Google Sites. It's when that same person wants a regular blog, bookings or an online shop that the tool stops being the right one. We'll get to those limits shortly.

How do you make and publish a Google Sites website?

Google's help center says to open Google Sites on your computer, choose a template under "Start a new site," edit it and use the Publish button in the top right corner. When you publish you "enter the web address for your site." You can preview the site before publishing, and you can choose whether it's Restricted or Public.

Two small rules are worth knowing. Web addresses containing terms that violate Google's Acceptable Use Policy aren't allowed, and to reuse an address that's already taken or was used before, you have to change it or delete the existing site. Also, Google Accounts managed by parents can't create sites, though they can view and edit existing ones.

A published site gets a Google address on sites.google.com unless you connect your own domain. For work or school accounts, Google's custom domain help says "to use a custom domain from your work or school account, contact your administrator."

Is Google Sites free?

I can only answer this half-way from Google's own pages, and I'd rather say that plainly than guess.

Google's Sites product page doesn't state a price. It offers a "Try Sites for work" route for small business and enterprise, and links to a comparison page. Google's Workspace pricing page shows the "Sites website builder" in the feature comparison for the lowest plan, Business Starter. The page rendered in pounds for me: £5.90 per user per month on the annual-commitment price, not including tax (it also showed a time-limited introductory discount, and its own billing wording is a little ambiguous, so check the live page).

Whether a plain personal Google Account can build a site at no charge isn't something I could confirm. None of the Google product or help pages I read states a price or says "free" for personal accounts. Google's custom domain help does mention importing sites "from your consumer account" into a Workspace plan, which suggests personal accounts can hold sites, but that is an inference, not a pricing statement. Check it yourself at sites.google.com before you rely on it. One difference does show up in Google's help: for work or school accounts, a custom domain means contacting your administrator.

What can you embed in a Google Site?

This is where Sites earns its keep. According to Google's help article, you can add:

  • Docs, Slides, Sheets, Forms and Charts, from the Insert menu
  • YouTube videos, calendars and maps
  • Files from Google Drive
  • Other web content by URL (Google lists examples such as Google Apps Script, Data Studio reports and App Maker apps)
  • Pages embedded as a full page through the Pages panel
  • Your own HTML, CSS or JavaScript through an embed code box (JavaScript must sit inside script tags, and CSS inside style tags)

The big benefit is that embedded Docs and Sheets are live. Edit the spreadsheet and the page shows the change, with no republishing. That's why a Sites page works so well as a front door to a living document.

The catches are in the fine print. Files in shared drives or with restricted sharing are only visible to people who have access, so you must share the underlying file with everyone who needs to see it when you publish. Google also warns that some websites won't let you add their content to your site. Images uploaded from your computer are limited to .jpg, .png and .gif; anything else has to go through Drive. And a file embedded in too many sites can trigger a "File indexing issue" error. There's also a note in the custom domain article that Google Groups embeds won't render properly on a custom domain and that features relying on Google Account sign-in may not work there.

How do you use your own domain with Google Sites?

Google's custom domain help page lays out the flow. In Settings you open Custom domains, start setup and enter your domain. If Google asks you to verify ownership, you add the domain to Google Search Console as a "Domain (not URL prefix)" property and copy the TXT record it gives you into your DNS settings. Then you follow the instructions for your registrar to connect it. The page also mentions a CNAME entry in its troubleshooting section.

The limits, quoted from that page: "Only the owner of a site can connect it to a domain." You can connect up to five custom domains to one site. There's a limit of 20 mappings per week for your URL. Changes "may take up to 48 hours" to show up. And the site must be shared publicly, otherwise the domain redirects to the sites.google.com address.

Where do you get a domain? The setup steps tell you to follow the on-screen instructions "to connect to a third-party domain registrar," so a domain bought elsewhere works. The same page says you can purchase a new domain for Google Sites through a Google Workspace plan, and the product page says Google can help you buy one through a domain-host partner at sign-up.

The Google Domains angle trips people up. Squarespace announced on 7 September 2023 that it had completed its acquisition of the assets of the Google Domains business and would transfer Google Domains accounts to its Squarespace Domains platform. Squarespace's own help page, "About the Google Domains migration to Squarespace," now says "If you had a Google Domain, you now manage it with Squarespace." The Sites help page says that if you previously integrated a Google Domain with Sites, the domain stays linked to your Google Site and you have to verify ownership to make edits. That Sites page doesn't mention Squarespace at all. If your domain used to live at Google Domains, log in to Squarespace, check the DNS records and verify ownership before you touch anything.

Can you track visitors on Google Sites?

Yes, in a basic way. Google's help article says "you can collect basic data from your website with Analytics." In the Sites editor you click Settings, go to Analytics and enter a valid Analytics ID, and the page warns it can take up to 24 hours for data to show up. Google's page says only "Enter a valid Analytics Property ID." It doesn't spell out the ID format, so look at what the Analytics field accepts today instead of trusting an old screenshot.

That's visitor counting. The help page describes nothing beyond pasting an ID, so for anything deeper, such as funnels or search reports, you'd work in Analytics and Search Console themselves.

What are the real limits of Google Sites?

Here I'm going to separate what Google's pages say from what I'm inferring from their silence.

Search: the one search setting Google documents is an opt-out. The help article says the option to ask search engines not to show your site is "a request" that "doesn't guarantee that your site won't show up in public search engines," and that it's only available when the site is Public. I found no help page about page titles, meta descriptions, canonical tags or structured data in the help-center topic list I read. That doesn't prove the controls don't exist, but if they matter to you, test the editor before you commit.

Blog, store, newsletter: the help center's topic list I read covers creating sites, adding pages and content, publishing, sharing, custom domains, analytics and accessibility. It has no topic for a blog, a store, payments or a newsletter, and Google's product page describes team, project and event sites, not publishing platforms. So the sensible reading is that Sites doesn't have a post feed with archives, categories and RSS, a product catalogue with checkout, or an email list. You can embed a Form to collect addresses and link out to a payment page elsewhere, and you can embed another website's page by URL (if that site allows it), but that's gluing, not a feature.

Design: templates and themes exist, and you can add HTML, CSS and JavaScript through embed code. But Google documents a template-and-theme model, not free-form layout, and I'd expect that to feel restrictive if you want a distinctive, branded layout.

Storage: Google's pages don't agree with each other here. The Workspace admin documentation says "Sites and the content you embed in sites count toward your Drive storage quota," and that images and other content added to a site are stored within that site. The general "How your Google storage works" help article, on the other hand, doesn't list Sites among the things that count toward your quota, and says its over-quota policy doesn't apply to Google Sites. I can't tell you which rule governs your account type, so check Google's current documentation for it.

None of that makes Sites a bad tool. It makes it a narrow one, and narrow is fine when your job fits the narrow thing.

When should you use something other than Google Sites?

Move when one of these shows up.

You want to publish regularly. A blog needs posts, dates, categories, an index page, an RSS feed and search listings per article. Sites isn't built around any of that.

You want to sell something. Even a few products need a cart, payments, tax, shipping and order emails.

You want an email list that you control. A form embed collects addresses. Sending a newsletter to them is a different job.

You care about being found. If search traffic is how customers will reach you, you want control over titles, descriptions, URLs and structured data.

You'd like your site to outlive your Google Account. Sites belong to an account, and the edit rights, the sharing and the domain mapping are all tied to it. That's a fair price for a free tool, but it's still a dependency.

Which alternatives are worth a look?

These are the tools I'd actually compare for someone leaving Google Sites. The list is deliberately mixed: small and simple, general builders, a writing-first tool and a bundle. It isn't a ranking. Prices are what each vendor's own page showed on 18 November 2026.

Carrd

Carrd describes itself as "simple, free, fully responsive one-page sites for pretty much anything." Its homepage says you can "build up to three sites per account" on the free plan and quotes Pro "from just $19 / year" (it also offers a 7-day free trial, and its Pro page says no card is required for it). The Pro page is a little more granular and prices plans yearly, in dollars with no currency code shown. Pro Standard ($19 a year) lists a custom domain, forms including payment-enabled forms, and Google Analytics support, while the cheapest tier, Pro Lite ($9 a year), lists no custom domain, forms or analytics. Every Pro tier lists removal of Carrd branding.

It's the cheapest step up from Google Sites for a single landing page, a profile or a link hub, and the one with the lowest ceiling: it's a one-page tool. A blog or a multi-page site isn't what it's for.

Wix

Wix has a Free plan listed with "No credit card required," plus paid plans called Light, Core, Business and Business Elite, and a 14-day money-back guarantee. Its ecommerce depth varies by plan: Core lists "Basic ecommerce," Business "Standard ecommerce," Business Elite "Advanced ecommerce." I'm not quoting its prices. The page says "Prices and currency vary by location. USD prices displayed for reference only," that the figures are for yearly subscriptions paid in full up front, and that its promotional pricing changes, so whatever I printed here could be wrong for you.

Wix is the broad, all-purpose builder: its page advertises "1000s of templates" and a drag and drop editor. The trade-off is the usual one for hosted builders. You hand over server work in return for less control, and you should check its export options before you build anything you'd hate to rebuild elsewhere.

Squarespace

Squarespace starts every site with a 14-day free trial, and its FAQ says no credit card is required. The page rendered in pounds for me: Basic at £16 a month billed monthly or £12 a month billed yearly, Core £24 or £17, Plus £36 or £29, Advanced £89 or £79. Read the fee columns before you plan to sell anything: the online store fee is 2% on Basic and 0% from Core up, and the digital content and memberships fee runs 7%, 5%, 1% and 0% from Basic to Advanced. The page says annual plans include a free domain for the first year.

It's good-looking out of the box and suits portfolios, small shops and service businesses who care about design. Weaknesses: there's no free plan beyond the trial, and fees on stores and memberships are tied to the tier.

WordPress.com

WordPress.com is the hosted version of WordPress. Its Free plan gives you 1 GB of storage, a WordPress.com subdomain, unlimited pages and posts, and shows ads to visitors; it doesn't allow plugin installation or a custom domain. The paid plans (Personal, Premium, Business, Commerce) list yearly-billed prices from $4 up to $45 a month in US dollars, and every paid plan lists plugin installation, with "over 60,000 plugins" mentioned. The Commerce plan lists full WooCommerce store tools.

That's the strongest answer if you want a real blog and the biggest ecosystem of themes and plugins. Weaknesses: the free plan carries ads and the page's own transaction-fee table and FAQ don't agree on Business-plan fees, so read the checkout screen. Power comes with more things to configure than Sites ever asks of you.

Notion

Notion turns pages into websites: its Sites page calls it "the easiest way to get a website up and running." The pricing page (shown in pounds) lists Free at £0, Plus at £8.50 and Business at £16.50 per member per month. Free includes "Basic sites" on one notion.site domain with basic indexing. A custom domain costs "$8/month/domain paid annually" ($10 billed monthly), and the page says editing title and description metadata requires a paid plan.

It's a natural step if your content already lives in Notion and you want a clean, document-style public site. Limits: you're building on a workspace tool, not a website platform, and the title and description control is a paid-plan feature.

VeloCMS

VeloCMS is a hosted blog and publishing platform that bundles a visual page builder (listed as "70+ blocks"), a newsletter with tag segmentation, paid memberships and a store behind one subscription. Pro is $9 a month ($86.40 a year), Business $29 and Agency $69. Each plan carries a 14-day trial that needs a card unless you have a trial code, with the first charge on day 15. There is no free plan. VeloCMS states a 0% platform fee on Stripe sales (Stripe's own processing fees still apply), and Pro includes a custom domain, 5 GB of storage and up to 5,000 subscribers.

Its weaknesses are plain. It's a newer product than everything else here, so there are fewer tutorials, templates and freelancers who know it. The homepage says WordPress imports don't bring comments across. It's a better fit for someone who wants to publish and sell than for a team that wants an intranet with live Sheets. Compared with Google Sites, the missing piece is the Workspace integration; the gain is a blog, email list and checkout that exist as features.

Who is each option best for?

  • Google Sites: best for internal and class sites, event pages and small projects where the content already lives in Google Docs, Sheets and Forms. Not for anyone who needs a blog, a store or tight control over search listings.
  • Carrd: best for a single landing page, a link-in-bio style profile or a quick signup page on a tiny budget. Not for multi-page sites.
  • Wix: best for a small business owner who wants a visual editor, one bill and a way to start for nothing. Not for anyone who wants a self-hosted site.
  • Squarespace: best for designers, photographers and service businesses that want polish with little effort. Read the store and membership fees first.
  • WordPress.com: best for a blog that could grow into something bigger, thanks to its plugins. Not for people who don't want to make a lot of decisions.
  • Notion: best if your notes and docs are already in Notion and you want a quick public site from them. Not a full website platform.
  • VeloCMS: best if you want a blog, newsletter, membership and a small store under one login and can live without a large ecosystem. Not for you if you need self-hosting or a mature community.

FAQ

Is Google Sites a good website builder? For simple internal, class, project and event sites, yes. Google describes it as a builder for team, project and event sites, and the integration with Workspace files is its main strength. For blogs, shops and search-driven business sites it's a thin fit, based on the help-center topics I read.

Do you need Google Workspace to use Google Sites? Not to connect a domain. Google's custom domain article says domain connection happens at your third-party registrar, and that you can purchase a domain through a Workspace plan if you want. Whether a personal account can create sites free of charge isn't stated on any Google page I read, so confirm it at sites.google.com.

Can Google Sites have a blog? The help-center topic list I read has no blog feature, and Google's product page describes team, project and event sites. You can embed content from elsewhere, but there's no documented feed of posts with archives and categories.

Can you sell things on a Google Site? Google's help topics list no payments or store features. You could link out to a payment page elsewhere, but checkout isn't something Sites does itself.

Can I use my own domain name? Yes. Open Settings, then Custom domains. Google's page says up to five custom domains per site, 20 mappings per week, up to 48 hours for changes to appear, and the site has to be shared publicly for the domain to work.

Does Google Sites support Google Analytics? Yes, in a basic way. You enter an Analytics ID under Settings, then Analytics, and Google says data can take up to 24 hours to appear.

What happens to my site if I switch tools? You can use the "Export your data" help topic, which lists Sites among the Google products it covers, but a site's layout won't carry over to another builder as a finished design. Expect to rebuild the pages and set up redirects if the addresses change.

Last verified: 2026-11-18.

Sources (all accessed 2026-11-18)

Share this post
Report