01
Fast by construction
Squarespace and Wix carry a mass-market platform into every site. WordPress needs server, database, theme, plugin, and caching layers. Static pages are built before anyone visits, so visitors get useful HTML immediately.
Build on the open web
Leave the website builder. Keep the website.
I think Squarespace, Wix, and WordPress are a poor deal for most local businesses. They are built for everyone, carry more machinery than an ordinary business website needs, and make the platform part of the site. Static changes that: your pages become files you own, hosting becomes a destination you choose, and every extra tool has to earn its place.
The fundamental change
A builder is a bundle. A static site is a foundation.
Squarespace and Wix put the design, content, hosting, editing tools, integrations, and billing inside proprietary systems. WordPress is open source, but the working site still depends on its database, host, theme, plugins, configuration, and updates. That convenience makes the platform stack part of the website.
Leaving rarely means carrying the same working website somewhere else. Wix cannot be externally hosted. Squarespace only exports some content. WordPress can export content, but the theme and plugin behaviour still has to be recreated. With a static site, the complete source is the stable layer: copy it, choose another host, and deploy the same website.
Inside a platform stack
- The editor is part of the architecture
- Design depends on templates or themes
- Features add platform or plugin code
- Speed depends on optimising the stack
- Moving usually means rebuilding
On a static foundation
- Content lives in portable files
- Design belongs to the site
- Hosting can be changed
- Specialist tools do specialist jobs
- One layer can change at a time
01 — Why static
Build the durable part once. Keep everything else replaceable.
02
Yours in a useful format
Your words, design, and structure live in files you can open, copy, version, and host elsewhere. Ownership becomes practical, not a clause in some terms of service.
03
Fewer moving parts
No database or admin dashboard is required to serve the site. That means fewer updates, fewer dependencies, and a much smaller surface for things to break.
04
Flexible where it matters
Forms, bookings, analytics, search, and content editing can still be added. Each capability is a deliberate layer rather than a reason to put the whole site inside one platform.
This is not really a story about free tools. Lower running costs are a welcome side effect. The real advantage is leverage: you stop renting the foundation of your online presence.
02 — The replacement stack
One closed platform becomes a handful of excellent tools.
You do not need every tool on day one. Start with the core, then add a capability when the website needs it. Many of these services have generous free tiers, but price is not the point: each one does a clear job and can be replaced without taking the whole site with it.
Pages and components
Astro
Builds the site into clean HTML and only sends browser JavaScript when a feature genuinely needs it.
Design system
Tailwind CSS
Keeps spacing, type, colour, and responsive behaviour consistent without tying the design to a commercial template.
Writing and editing
VS Code or Cursor
A proper home for the site files, with excellent Astro support and optional AI help when you want it.
Portable content
Markdown and content collections
Store articles and structured content in readable files, or connect a content system later without rebuilding the public website.
History and collaboration
GitHub
Keeps every change, gives you a reliable backup, and becomes the source that publishes the live site.
Global publishing
Cloudflare Pages
Builds from GitHub and serves the finished files around the world. The host is a destination, not the owner of the website.
Image performance
Astro image tools
Resize and optimise source images during the build so visitors receive the right format and dimensions for their screen.
Search feedback
Google Search Console
Shows how the finished site appears in search, which pages are indexed, and where people are finding you.
Your website does not need to own every job.
Website builders make their feature list feel like the product. In a static stack, the site communicates clearly and the best available service handles each specialised task.
Forms
Connect a focused form service or a small endpoint. Your contact page does not need an entire website platform behind it.
Bookings and payments
Link or embed the system that already runs that part of your business instead of accepting whatever your builder happens to offer.
Analytics
Choose lightweight, privacy-aware measurement—or choose none. The website still works perfectly without a tracking bundle.
Content editing
Keep content in files for simplicity, or add a headless editor if several people need to publish frequently. The public site stays static either way.
03 — The move
Leave the platform without throwing away the value you built there.
The goal is not to export Squarespace and call it done. Builder exports rarely contain a clean, portable website. The useful migration is to preserve the content, URLs, search equity, and business functions while rebuilding the foundation properly.
- 1
Inventory what already works
List the pages, search rankings, URLs, forms, images, domain settings, and third-party services worth carrying forward. A migration should preserve value, not just appearance.
- 2
Build the new foundation
Create the Astro project, shared layout, navigation, and core styles. Rebuild the design cleanly instead of copying the builder's generated code.
- 3
Bring across the content
Move the words and images into pages or content collections. Improve structure and accessibility while the content is in your hands.
- 4
Connect only the capabilities you need
Add forms, bookings, email, analytics, or a content editor as separate services. Each one can be changed later without replacing the site.
- 5
Protect findability
Keep valuable URLs, add redirects where needed, and carry across titles, descriptions, structured data, sitemap coverage, and social sharing metadata.
- 6
Test, point the domain, then leave
Check the production build, mobile layout, links, forms, and search files. Move the domain only when the replacement is ready, then cancel the old platform after the live site is verified.
04 — What to learn
A small toolkit, not a second career.
You do not need a computer science degree or a deep knowledge of JavaScript. Learn enough HTML to understand the page, enough Astro to organise it, enough CSS to shape it, and enough Git to keep changes safe. AI can help write code, but understanding the structure is what keeps you in control.
That is the lasting benefit of doing this yourself: you learn how the web works rather than how one company's dashboard works. The knowledge moves with you.
HTML basics
Headings, paragraphs, links, images, lists, and forms: the durable language underneath every website builder.
Astro tutorial
Build a complete content site while learning pages, layouts, components, and content collections.
Tailwind CSS
Learn enough utilities to turn a design system into responsive pages without inheriting a template.
Git and GitHub
Learn add, commit, and push so every change is recorded and your repository can publish the site.
05 — The honest trade-off
Static does not mean frozen, but it does mean choosing how changes happen.
A static website does not automatically include a visual block editor. Small changes happen in the site files; frequent publishing can use a connected content editor. Interactive features can use Astro islands or specialist services. That separation is the strength, but it asks you to make a few architectural choices up front.
Static architecture is an excellent fit for most content-led business websites, portfolios, blogs, directories, and service sites. A large transactional application, member dashboard, or constantly changing catalogue may need more server-side infrastructure. The point is not that every website must be static. It is that an ordinary business website no longer needs a permanent platform wrapped around it.
So, can you do it for me?
Yes. I build static websites that help businesses grow and get found.
You do not have to learn Astro, plan a migration, or work out which tools fit together. That is what I do. I combine static web technology with clear strategy, useful content, careful design, SEO, schema, and search visibility to build a website that does more for your business.
Tell me about your business, your current website, and what you want to achieve. I'll reply within one business day.