In recent years, a wave driven by AI-based coding tools has been pushing more and more agencies to offer clients static sites as a replacement for WordPress. Astro, Hugo, Eleventy: names that circulate in meetings as if they were the new frontier. And in many cases the client, who knows little about technology, is won over by two magic words: "faster" and "more secure."
We, as WordPress supporters, believe it's time to say things as they are. Because behind this trend there's a lot of marketing and very little substance, and the price is paid by those who end up with a site they can no longer grow.
Static sites aren't "the new thing" — they're the old thing in disguise
Let's start with a fact that many static-site salespeople prefer not to mention: a static site is, conceptually, a return to the web of the 1990s. No PHP, no database, no server-side interaction. Pages are pre-built files, immutable until the next deploy.
Yes, modern generators use components, Markdown, and templates. But this doesn't change the substance: you're buying a product that does less than WordPress, presented as if it does more. It's the classic salesman's trick of telling you the car without air conditioning is "lighter and therefore faster."
The truth is that the dynamic web wasn't a random evolution. It was the great evolution. From the moment it became possible to generate pages on the fly, interact with the user, and manage content without touching code, the web stopped being a flyer and started being a tool. Going back means giving up all of this in the name of a few tenths of a second less in load time.
And let's say it clearly: nobody cares about that tenth of a second. Not your client. Not their visitors. Not Google, which has made it clear for years that speed is one factor among many, not the only one. They're selling it to you as if it were the most important thing in the world, but it's just the easiest thing to measure to justify an invoice.
The fairy tale of "you don't need a CMS"
We often hear: "Your site is just a showcase, you don't need WordPress." Or: "You change the content once a year, it's not worth having a CMS."
Well, this statement is simply false, and whoever makes it either hasn't understood how businesses work, or is pretending not to.
There is no such thing as a site that never changes its content. There isn't. If a company has a website, that website will change. Always. Phone numbers will change, addresses will change, the price list will change, team photos will change, a new service will arrive, there'll be a promotion, a regulation will change and a legal page will need updating. Even the most static site in the world, the one the client swears they'll never touch, needs a change after six months.
And when that change comes, what happens with a static site? What happens is that the client has to call the developer. They have to open a ticket, wait, pay. Or, if they're lucky, they have access to a Git panel and have to make a commit — something 99% of clients don't know how to do and don't want to learn.
This isn't independence. This is total dependence on the provider. And it's exactly why some agencies push static sites: because they turn you into a client for life, tied to them for every single comma you want to change.
With WordPress, the client opens the browser, logs into the backend, changes the text, saves. Done. No ticket, no invoice, no waiting. This is independence.
The security myth
"No PHP and no database means a smaller attack surface." True. Too bad it's an argument that only holds if you ignore two things.
First: a static site isn't a secure site, it's a site that does nothing. There are no vulnerabilities because there's nothing to exploit. It's like saying a house without doors is safer: true, but you can't live in it.
Second: WordPress security is a matter of management, not architecture. An updated WordPress, with reliable plugins, serious hosting, and good practices, is perfectly secure. Hacked WordPress sites are the ones abandoned for years, with pirated plugins and "admin123" passwords. The same negligence applied to a static site would still produce a disaster, just in a different way (expired domain, unrenewed SSL certificate, obsolete content).
Selling static as "more secure" is scaring the client to sell them less. It's not a technical proposal, it's a commercial tactic.
The hybrid? Worse than the disease
Someone will now say: "But you can do a hybrid — the main site static and the blog on WordPress in a subdomain." This solution makes us shudder, and here's why.
A hybrid means two infrastructures to maintain, two hostings, two domains, two update systems, two backups, two different mindsets. It means the client has content split across two places, fragmented SEO, an inconsistent user experience, and a higher bill.
It's the worst possible solution: it takes the complexity of static and adds the complexity of WordPress, without taking the advantages of either. Whoever proposes it does so for one reason only: they don't have the courage to tell you they're selling you a static site, but they don't want to give up the WordPress maintenance fee either. It's a compromise at the lowest common denominator that only serves the person selling it.
If you're going to use WordPress, use WordPress. Everywhere. For everything. There are no half-measures that benefit the client.
What you really lose with a static site
Let's make a concrete list of what you give up when you accept a static site instead of WordPress. This isn't theory, it's what you'll miss the day after launch.
Contact forms. They don't work natively. You need an external service, with a free plan that limits you, or a paid plan that costs more than WordPress hosting.
Internal search. It doesn't exist. You have to add a service like Algolia, which is great, but it's another thing to configure, pay for, and maintain.
Comments. They don't exist. And if the client wants a blog with comments, you open up a world of external services that dump data onto third parties.
User logins. They don't exist. If one day you need a members' area, a subscription, a small e-commerce, you start from scratch.
Technical SEO. Plugins like Yoast or RankMath have no equivalent. Sure, you can write meta tags by hand, but we're talking about going back to working like it's 2005.
Multilingual. Plugins like WPML or Polylang have no real equivalent. Static solutions are fragmented, immature, often tied to a single generator.
Content updates. The client depends on the developer for every change. Every time.
Plugins. They don't exist. Every feature has to be built from scratch or integrated with an external service.
Revision history. It doesn't exist natively. If the client messes up an edit, there's no clickable "restore previous version."
Media management. No media library, no automatic thumbnails, no centralized image management.
All of this is the reason WordPress exists. And all of this you're giving up to gain a few tenths of a second in load time that nobody will notice.
Conclusion: static is a downgrade disguised as an upgrade
The dynamic web won for a simple reason: it's more useful. WordPress conquered 40% of the web for the same reason: it puts power in the hands of those who create content, not those who code it.
Whoever proposes a static site for a corporate site, a showcase site, a services site, a portfolio, a corporate blog, is doing one of three things:
- They haven't understood what the client needs;
- They've understood but prefer to sell what's technically more convenient for them;
- They've understood and want to tie the client to themselves for every future change.
In all three cases, the client loses.
There is no such thing as a site that never needs to change its content. There is no such thing as a client who wants to depend on their provider for a comma. There is no such thing as a company that in two years won't need one more feature it hadn't anticipated today.
WordPress is the answer to all of this. It's the answer that works, that lasts, that grows with the client, that leaves them in control.
The rest is marketing. And we, as WordPress fans, prefer to say things as they are: if they're selling you a static site, they're selling you a downgrade. With a nice name, a nice design, a nice story about the web of the future. But still a downgrade.
At Sitista, static websites don't exist. WE are the real Web. Contact us—we can bring you back to the future 🙂