
Which Website Builder Is Safest? Who Protects What on WordPress, Wix, Squarespace, GoDaddy, Shopify and Webflow
Every hacked site we cleaned up this year ran self-hosted WordPress. That is not because WordPress is bad. It is because on WordPress, almost everything is your job. Here is who protects what on the six platforms our clients ask about, and where a Cloudflare edge can and cannot help.
Every platform splits security differently between itself and you. AI-generated illustration.
In one paragraph
Website builder security is the split of protection between the platform and the site owner. Hosted builders such as Wix, Squarespace, Shopify and Webflow run and patch the servers for you. Self-hosted WordPress leaves the server, the plugins and the updates to you and your host. On every platform, passwords, two-step login, add-ons and the domain stay the owner's job.
Check your account
Your security duties on any website builder: an 8-point check
These stay your job whichever platform you use. Tick what you have done. It counts what is left and sends nothing anywhere.
0 of 8 duties covered
Based on each platform's own security and help pages and Cloudflare's docs, read October 23, 2026. Platforms change; check your own plan's terms.
01 / 05
Why did every hacked site we cleaned up run WordPress?
Because self-hosted WordPress puts the most on the owner's plate. You choose the host, install the plugins and keep everything updated. Plugins carried 91% of the 11,334 new WordPress vulnerabilities found in 2025, and heavily targeted ones were first exploited after a weighted median of 5 hours (Patchstack, 2026). That is a lot of doors to keep shut.
This is the fifth guide in our series on hacked websites. The four sites behind the earlier guides, a professional services firm, a real estate brokerage, an art gallery and a plumbing company, all ran self-hosted WordPress. Our cases are not a survey; they are the sites that came to us. But the pattern matches what WordPress security researchers report.
Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025. Of those, 91% were in plugins and 9% in themes, with "only 6 vulnerabilities reported in the WordPress core", and 46% were not fixed in time for public disclosure (Patchstack, 2026). WordPress itself is not the weak point. The add-ons are, and on self-hosted WordPress, managing them is your job.
WordPress's own handbook says it directly: "The most important thing to do for WordPress security is to keep WordPress itself and all installed plugins and themes up to date" (WordPress security handbook, 2026). It also says security "is also about making sure your hosting environment is secure", which is the other half of the owner's job.
02 / 05
Who protects what on each website builder?
Hosted builders protect the platform: servers, patches, encryption and attack mitigation. Wix, Squarespace, Shopify and Webflow all describe that on their security pages. You still own your password, two-step login, apps and domain. Self-hosted WordPress hands you the platform too. WordPress.com sits in between, with scanning and a firewall included.
| Platform | What the platform says it covers | What it says stays with you |
|---|---|---|
| WordPress (self-hosted) | Core software updates are published; hosting is your choice | Keeping WordPress, plugins and themes updated; a secure hosting environment |
| WordPress.com | Daily scans, a web application firewall, automatic core updates | Your password, two-step login, deleting unused plugins and themes |
| Wix | "Fully managed, 24/7 site protection", automatic SSL, SOC 2 Type 2 and PCI DSS Level 1 | Strong passwords and two-factor login |
| Squarespace | Free SSL, denial-of-service mitigation, no handling of card data | Reviewing your account's login sessions |
| GoDaddy | A separately sold Website Security product with malware scans, a firewall and DDoS mitigation | Strong passwords, two-step verification and keeping your site software updated |
| Shopify | PCI DSS Level 1, SOC 2 Type II and SOC 3 reports | Not set out on its security page |
| Webflow | Global CDN with DDoS protection and rate limiting, automated patches, TLS and HSTS | Two-factor login and account activity tracking are offered |
The hosted builders are clear about the platform side. Wix promises "fully managed, 24/7 site protection" (Wix Trust Center, 2026). Webflow lists a "Global CDN with DDoS protection and built-in rate limiting for all sites" and "Automated patches and updates with no customer maintenance" (Webflow, 2026). Shopify says it "is certified Level 1 PCI DSS compliant" (Shopify, 2026). Squarespace says domains on its sites "are automatically protected with free SSL certificates" (Squarespace, 2026).
WordPress.com, the hosted version of WordPress, adds services the self-hosted version leaves to you: "Jetpack Scan checks every WordPress.com site daily for dangerous plugins, themes, malware, and other vulnerabilities," and its firewall "examines incoming traffic to all WordPress.com sites" (WordPress.com, 2026).
GoDaddy is different again. Its malware scanning and firewall come as a separate Website Security product, and on the Standard tier, "Malware Cleanup and Blacklist Removal" is listed as "Once per year" (GoDaddy Help, 2026). Check what your plan actually includes.
03 / 05
What stays your job on every platform?
Your logins, your add-ons and your domain. Wix, WordPress.com, GoDaddy and Webflow all describe two-step login on their security pages. Every one lets you add apps or extensions it did not write. And none of them controls your domain registrar account, which decides where your visitors end up. WordPress.com puts it plainly: security "is really up to you" (WordPress.com, 2026).
Logins come first. WordPress.com says the security of your password and your website "is really up to you" (WordPress.com, 2026). Wix says it offers "two-factor authentication via email, SMS or authenticator app" (Wix Trust Center, 2026). GoDaddy says "Strong passwords and 2-step verification are the best ways to protect your account" (GoDaddy Help, 2026). Wherever your platform offers it, turn it on for everyone with access, today.
Add-ons come second. Apps from a marketplace, plugins and custom code are written by someone other than the platform. WordPress.com tells owners to "Delete plugins and themes that are no longer required for your site" (WordPress.com, 2026), and the same advice holds for apps on any builder. We could not find a statement on Wix, Shopify or Webflow's security pages about who is responsible for third-party apps, so assume it is you.
The domain comes third, and it sits outside every builder. In our cleanup guide, a plumbing company's domain settings were reset at the registrar and visitors were sent to an old hacked server for almost 17 hours. No builder could have stopped that. Two-step login on the registrar account, and knowing who holds it, is the defense.
04 / 05
Can you put a Cloudflare edge in front of any website builder?
No. Wix says it "does not support proxied DNS records for domain connections" (Wix Help Center, 2026). Shopify's help center says Cloudflare proxy setups "aren't supported", although Cloudflare documents a setup that works. Webflow works through Cloudflare's Orange-to-Orange setup. Squarespace is documented only by Cloudflare. Self-hosted WordPress can always be proxied.
A Cloudflare edge works by sitting in front of your site. Cloudflare explains that when a record is proxied, "Cloudflare sits between your visitors and your server" (Cloudflare proxy status docs, 2026). That is where firewall rules, bot filtering and any managed layer on top of Cloudflare do their work. If a platform will not allow the proxy, none of that can sit in front of it.
| Platform | What the documentation says |
|---|---|
| Self-hosted WordPress | Yes. Proxying is the standard Cloudflare setup. |
| Webflow | Yes, through Cloudflare's Orange-to-Orange setup, on any Cloudflare plan (Cloudflare docs) |
| Squarespace | Cloudflare documents a proxied setup; Squarespace's own help does not mention it |
| Shopify | Shopify's help center says no, including Orange-to-Orange; Cloudflare's docs say Orange-to-Orange works |
| Wix | No. Wix says proxied records are not supported. |
| GoDaddy builder and Managed WordPress | Not documented in the pages we could read |
Wix is the clearest: "Currently, Wix does not support proxied DNS records for domain connections" (Wix Help Center, 2026). Shopify's help center says "Cloudflare proxy setups, including Orange-to-Orange, aren't supported" (Shopify Help Center, 2026), while Cloudflare's own Shopify guide says "Shopify uses O2O, which allows proxied records to work correctly" (Cloudflare Shopify guide, 2026). When two vendors disagree, we follow the platform's own help and treat it as unsupported.
For Webflow, Cloudflare says "Webflow customers can enable O2O on any Cloudflare zone plan" (Cloudflare Webflow guide, 2026). For Squarespace, Cloudflare's vendor page says "All A records should be Proxied", and warns that Squarespace's own panel will then report a settings problem, which Cloudflare calls expected (Cloudflare vendor DNS records, 2026).
This matters for any edge protection, including the RankShield edge, which runs on Cloudflare. It can sit in front of a site only where the platform allows Cloudflare's proxy. RankShield, our founder's security company, runs that kind of layer on Cloudflare, which it describes as "a managed filtering layer on Cloudflare's global network that sits in front of your whole site". It is $39 a month, added on top of a RankShield plan; details are on the RankShield edge page. It is an option we offer, never a condition of working with us.
05 / 05
So which website builder is safest?
It depends on what you need, but the trade is consistent. Hosted builders take the platform off your hands and limit what you can add in front. Self-hosted WordPress gives you full control and the full job. A static site on Cloudflare removes the server, the plugins and the site login entirely, and keeps the edge in front.
If you sell products, Shopify's PCI DSS Level 1 certification handles a hard problem, card data, that most small businesses should never handle themselves (Shopify, 2026). If you want a site you can edit yourself with little upkeep, Wix and Squarespace take patching off your plate, at the cost of what you can put in front of them.
If you run self-hosted WordPress, you can make it much safer: fewer plugins, updates on, two-step login, a proxy in front and origin access locked to that proxy. Our guides to plugins as the attack surface and auditing your WordPress site cover that work. It is real, ongoing work, and the four sites in this series show what happens when it slips.
There is a fourth option, and it is the one we build most business sites on now: a static site on Cloudflare. There is no server-side code at request time, no plugins and no site admin login to steal, and the whole site sits behind Cloudflare's network. We explain how it works, and its limits, in why we build sites as static pages on Cloudflare.
We recommend the platform that fits the business, not the one we prefer. Our website design services page shows how we decide, and our free SEO audit is a good place to start if you are weighing a move.
Watch it work
Turn on what makes AI recommend you.
AI recommends the businesses it can read, trust and quote. Flip on the four signals we engineer, and watch your visibility climb and the answer rewrite itself.
THE FOUR SIGNALS WE ENGINEER
Illustrative · the four signals are the real system we build
Questions
This article, answered.
Jamie Kloncz · SEO Elite Agency, Naples
There is no single answer, because the platforms split the work differently. Hosted builders such as Wix, Squarespace, Shopify and Webflow run and patch their own servers, so there is less for you to keep updated. Self-hosted WordPress gives you full control and puts the updates, plugins and hosting on you; plugins carried 91% of new WordPress vulnerabilities in 2025 (Patchstack, 2026). A static site on Cloudflare removes the server, plugins and site login entirely. On every option, your passwords, two-step login, add-ons and domain stay your job.
Jamie Kloncz · SEO Elite Agency, Naples
Wix takes more of the work off your hands. It describes "fully managed, 24/7 site protection" (Wix Trust Center, 2026), so you do not patch servers or plugins the way you would on self-hosted WordPress. The trade-off is control: Wix says it "does not support proxied DNS records for domain connections" (Wix Help Center, 2026), so you cannot put your own Cloudflare edge or firewall in front of it. Self-hosted WordPress can be very secure, but only if someone keeps plugins, themes and the host up to date and watches the site.
Jamie Kloncz · SEO Elite Agency, Naples
You can use Cloudflare for your domain's DNS, but the vendors disagree on putting Cloudflare's proxy in front. Shopify's help center says "Cloudflare proxy setups, including Orange-to-Orange, aren't supported" (Shopify Help Center, 2026). Cloudflare's guide says Shopify uses Orange-to-Orange, "which allows proxied records to work correctly" (Cloudflare Shopify guide, 2026). Because Shopify supports your store, we follow Shopify's help and treat the proxy as unsupported. Shopify handles card security itself through its PCI DSS Level 1 certification.
Jamie Kloncz · SEO Elite Agency, Naples
Both protect their platforms. Squarespace says domains on its sites "are automatically protected with free SSL certificates" and describes protection against denial-of-service attacks (Squarespace, 2026). Wix describes "fully managed, 24/7 site protection" and holds SOC 2 Type 2 and PCI DSS Level 1 certifications (Wix Trust Center, 2026). Neither can protect a weak or reused password, an account without two-step login, an app you installed or a domain account someone else controls. Those stay your job on any platform.
Jamie Kloncz · SEO Elite Agency, Naples
Mostly through add-ons and missed updates, not WordPress itself. Patchstack found 11,334 new vulnerabilities in the WordPress ecosystem in 2025, with 91% in plugins, 9% in themes and only 6 in WordPress core, and heavily targeted ones were first exploited after a weighted median of 5 hours (Patchstack, 2026). WordPress also runs a huge number of sites, so attackers automate their searches for it. Fewer plugins, automatic updates, two-step login and a proxy in front of the site close most of the common doors.
Jamie Kloncz · SEO Elite Agency, Naples
Your logins, your add-ons and your domain. Turn on two-step login for every person with access, wherever your platform offers it. Remove apps, plugins and extensions you no longer use, and know who wrote the ones you keep. Protect your domain registrar account with two-step login too, because whoever controls the domain controls where visitors go. WordPress.com sums it up: the security of your password, and your website, "is really up to you" (WordPress.com, 2026). Check Search Console monthly as your free early warning.
Sources
- 1Patchstack: State of WordPress Security in 2026, updated February 25, 2026 - 11,334 new vulnerabilities in 2025; 91% plugins, 9% themes; 6 in core; 46% not fixed by public disclosure; weighted median 5 hours to first exploit
- 2WordPress security handbook: Security, WordPress Advanced Administration Handbook - keep WordPress, plugins and themes up to date; secure hosting environment
- 3WordPress.com: Keep Your WordPress Site Safe and Secure, WordPress.com Support, modified October 2, 2026 - daily Jetpack Scan; firewall; security of your password is up to you
- 4Wix Trust Center: Security Framework and Compliance - fully managed, 24/7 site protection; two-factor authentication
- 5Wix Help Center: Request: Cloudflare Proxy Support - Wix does not support proxied DNS records for domain connections
- 6Squarespace: Security - free SSL certificates; denial-of-service protection; card data never handled by Squarespace
- 7GoDaddy Help: What is Website Security? and How do I secure my website? - Website Security plan features; strong passwords and 2-step verification
- 8Shopify: Shopify Security - Level 1 PCI DSS compliant; SOC 2 Type II and SOC 3 reports
- 9Shopify Help Center: Connecting a Cloudflare domain to Shopify - Cloudflare proxy setups, including Orange-to-Orange, are not supported
- 10Webflow: Webflow Security and Compliance - global CDN with DDoS protection and rate limiting; automated patches and updates
- 11Cloudflare Shopify guide: Shopify, Cloudflare for Platforms docs - Shopify uses O2O, which allows proxied records to work correctly
- 12Cloudflare Webflow guide: Webflow, Cloudflare for Platforms docs - Webflow customers can enable O2O on any Cloudflare zone plan
- 13Cloudflare vendor DNS records: Vendor-specific DNS records, updated April 16, 2026 - Squarespace A records proxied; Wix setup differs
- 14Cloudflare proxy status docs: Proxy status, updated April 21, 2026 - proxied records put Cloudflare between visitors and your server
Check this page has not changed
Every article is hashed when the site is built. This recomputes the hash of its text in your browser and compares it with the published record.
Related services



