What Google's Free Website Builder Is
Google's free website builder is a hosted page tool attached to a Google account. You pick a template, drop in text and images, hit publish, and a page exists on a Google-owned domain or on a domain you connect. You pay $0 to start. That part is true and it is not a trick.
What you get is a page. What you do not get is the file. The HTML, the routing, the customer list, and the checkout logic live on Google's servers under Google's terms. Google Business Profile sites were a clear version of this. A free site that lived inside your profile. In 2024 Google shut that tool down and told people to move. Everyone who had built a business on it moved on Google's schedule, not theirs.
That is the whole trade in one sentence. Free access to a page, no ownership of the asset. The builder is a rental. Rentals end.
People ask what free website builders are there, and the list is long. Google, Wix, Squarespace's trial tier, Carrd, GitHub Pages, Netlify, Cloudflare Pages. Two of those let you keep the code. The hosted ones do not. That distinction matters more than the template gallery does.
Here is the number that matters. $0 to publish. $0 to leave, until leaving costs you every page you wrote. I built four products over 13 years, and the ones that survived were the ones where I held the files.
The Control You Hand Over Without Noticing
Start with the domain. A Google-hosted site lives on a Google URL unless you connect your own. Connect your own and you have moved one layer out, but the page still renders through Google's system. Google can change the rendering rules. Google can change what shows on mobile. Google can put its own chrome around your content.
Next is the customer. On a hosted builder, the visitor is a Google analytics row, not your contact. You may see traffic numbers. You rarely see an exportable list of names and emails unless you bolt on a form tool that collects them somewhere else. Your customer perception survey analysis runs on data you cannot pull.
Then there is the checkout. A hosted builder ties payments to a processor it approves. Changing processors means rebuilding the store. Adding a subscription tier means finding out which one the plan supports. You are not designing the purchase flow. You are selecting from the flows Google decided to allow.
And the exit. Ask any builder who used a discontinued free site tool how that went. The answer is always the same. You get a notice, a deadline, and a redirect. Your brand experience mapping customer journey work starts over at step one.
Control is not a slogan here. Control is the export button. If there is no export button, you are a guest on the page, not the owner of it.
What You Keep When You Own the Files
Your AI worker just crawled all 12 chapters and 85 files while you were on a customer call. That is the Free Builder model in one line. The kit is free. A 206-page PDF or the token your AI worker uses to pull the live files off the server. 85 files, 12 module specs, updated as the kit changes. You direct the worker. You keep the customer and the invoice.
The token is not a download link. It is a crawl token valid for 30 days. The worker hits the server, pulls the 206-page kit, the 12 module specs, and the 85 files, and starts assembling your SaaS against them. If the kit updates while your token is live, the worker sees the current version. The PDF is a static snapshot if you want one.
The kit is free. The token is free. The course is free. The only paid item is the $19 PDF, and you do not need it to start. Say that out loud before you spend anything. The fear of missing what the token does is real and the answer is that nothing is gated behind a form without the word free on it.
What you end up holding is a codebase, a customer list, a Stripe account, and a domain in your name. Nobody can shut it down with a policy update. Nobody can put ads on your checkout. When you need more, you direct the worker again. That is the difference between renting a page and owning a product.
Your customer perception survey analysis, your brand experience mapping customer journey notes, your brand voice tone guidelines examples. All of that lives in your repo, not in someone else's dashboard. You can hand it to a contractor, move hosts, or sell the thing. Try that with a Google page.
The Cost, Line by Line
Google: $0 to start. You give up exports, payment control, and the schedule. Cancellation is not yours to choose. Course, kit, token. $0. PDF. $19 if you want the static copy. Code, customer list, invoice. Yours. Server: $0 to $25 a month depending on how far you take it. Domain. About $12 a year. Stripe. 2.9% and 30 cents per charge. Time. About 3 weeks part-time while you keep the day job.
Put the two columns next to each other and the free one is not free. It is cheap up front and expensive at the exit. The owned one asks for a few weeks of evenings and then stops asking.
The three weeks is the part people stall on. Three weeks of evenings while the customer calls keep coming and the invoices keep going out. The kit plans that. 12 module specs cover the modules you would otherwise spend a month designing from scratch. Your job is to pick the order and answer the questions the worker asks. You are not writing code. You are deciding.
That is why the price matters and why it stays visible. The kit is free, the token is free, the course is free, and the $19 PDF is the only thing with a price tag. If you never pay it, you still have everything you need. The article on the difference between the PDF and the token already covers the mechanics. This one is about the decision.
Run the math on one product at $19 a month. Eleven customers clear $200 a month. That is Stripe fees and a domain, and the rest is yours because there is no platform slice. A Google page cannot get you there. It can only get you a page, and it keeps the rest.
How to Decide in an Afternoon
Ask one question. If this page works, do I keep the customer, the code, and the invoice? If the answer is yes, keep going. If the answer is no, you are renting a storefront on someone else's street.
Use the free site tool for what it is good at. A landing page that validates a price in a weekend. Nothing wrong with that. Just do not put the product there. Put the product where you can export it.
The token is a live channel, not a file. When the worker pulls the 206-page kit, the 12 module specs, and the 85 files, it is reading the current version of every one of them. Update the kit, and the next crawl sees the update. That is how you keep pace without chasing downloads.
Start with the free path. Request the kit or the token. Pick one module out of the 12. Give the worker a concrete first task, like a signup form that writes to your database. See the working file land. Then decide whether the $19 PDF is worth having on the shelf.
Your customer keeps the product you sell them. You keep the business that sells it. That is the last line, and it is the only one that matters when a free host changes its mind.