WordPress is cost-effective starting at three editors, four posts per month, and fewer than two native integrations. Six measurable thresholds and a 36-month cost breakdown.
WordPress remains a viable choice in 2026 for most content-driven websites in Spain. It pays off when you cross specific thresholds: three or more people editing, four or more posts per month, and fewer than two integrations with proprietary systems. Below these, you are paying for complexity you don't use. Above them, the cost shifts to maintenance, not licensing.
The question that almost everyone in the industry answers with an opinion has a numerical answer. WordPress is neither good nor bad: it is a tool with a specific point of profitability. We define it through measurable thresholds, not design studio preferences.
Let’s start with what is verified.
That number doesn't prove WordPress is the right choice for you. It proves there is a market of providers, templates, and people who already know how to use it.
A 58.9% market share is an argument for liquidity, not an argument for quality.
The thresholds, not the opinions
When a team asks us whether they should build on WordPress, we don't reply with a comparison. We ask six questions that can be quantified. If you cross three or more of these thresholds upward, WordPress is usually the right answer. If you don't cross any, you are paying for an engine to move a bicycle.
The first three cut-offs—three editors, four posts, two integrations—are our decision criteria, derived from projects we have built and dismantled. We haven't published them as a formal measurement yet, and until we do, we do not present them as industry-standard data.
Threshold 1 · Three or more content editors
With fewer than three editors, a static site or a simple builder will suffice. The real advantage of WordPress is not just publishing: it is that multiple people can publish without getting in each other's way, using different roles and without touching code.
We set the cut-off at three because that is when permissions become necessary: who writes, who reviews, and who publishes. A site managed by one pair of hands does not need an admin panel with twenty-three menus.
Threshold 2 · Four or more posts per month
Publishing four times a month means forty-eight pieces a year. At that rate, the cost of having a developer touch the repository for every text change is no longer reasonable.
Below one post per month, a compiled site with continuous deployment costs less and breaks less. Editing twice a year does not justify a database that requires weekly updates.
Threshold 3 · Fewer than two integrations with proprietary systems
This threshold works in reverse compared to the previous ones. WordPress pays off when content is the product and integrations are standard: forms, newsletters, analytics, payment gateways.
When you need two or more integrations with systems you already have in-house—your ERP, your warehouse, your billing software, a catalog living elsewhere—each one becomes a custom plugin or bespoke development built on top of a manager not intended for that purpose. In those cases, the initial savings evaporate by the second year.
Threshold 4 · Two or more languages with distinct content
Translating the same website is cheap on any platform. Maintaining two versions with different content, pricing, and legal notices is not.
WordPress solves this with mature extensions, but each one adds its own layer of updates. If you plan to operate in two markets with diverging content, count multi-language support as a project line item, not a checkbox.
Threshold 5 · Catalog with transactions
If you are selling, the question is no longer WordPress: it is WooCommerce versus Shopify, and the tipping point is determined by your revenue and commissions, not the platform. We cover this in WooCommerce or Shopify in Spain: the tipping point by revenue.
As context: WooCommerce appears on 19.8% of WordPress sites and Elementor on 31.5%, according to W3Techs (consulted 08-27-2026). Just because something is frequent does not mean it is cheap to maintain.
Threshold 6 · 36-month horizon
No platform decision should be based on one year. If the website must survive three years without being rebuilt, the criteria should be who will maintain it and with what budget. A site no one will touch for 36 months doesn't need a content manager: it needs a good static archive and a backup.
The industry norm: The average Spanish studio will propose WordPress with Elementor and fourteen plugins because that is what they know how to build and because it provides a monthly maintenance fee. The comparison is written after the decision is made.
Our criteria: We count editors, posts per month, and integrations before naming any tool, and if the count is fewer than three editors, we tell you—even if it means the project doesn't happen.
What WordPress charges that doesn't appear in the budget
The price of WordPress is zero. The price of keeping WordPress running for three years is not.
In 2025, 11,334 new vulnerabilities were registered in WordPress and its extensions, 42% more than in 2024. 91% were in plugins and 9% in themes. The core accumulated six, all of low priority.
Read that carefully: the problem is not WordPress. It is what people install on top of it. Each plugin you add is a dependency with its own patch schedule and its own risk of abandonment.
This makes maintenance a mandatory line item, not an optional extra. Here is the breakdown of a 36-month WordPress project as we structure it, with our real figures pending publication.
| Item | Figure | Note |
|---|---|---|
| Design, system, and grid | — | — |
| Theme development and templates | — | — |
| Content migration | — | — |
| Hosting and domain, 36 months | — | — |
| Plugin and theme licenses | — | — |
| Maintenance and updates | — | — |
— = data being measured; we will publish it once we have our own sample.
Regarding hosting, we do have verifiable public pricing. Raiola Networks, a Spanish provider with a data center in Madrid, lists its entry-level WordPress hosting plan at €8.95/month and its Pro plan at €29.95/month, excluding VAT (consulted 08-27-2026). Over 36 months, the entry-level plan is €322.20 plus VAT by direct estimation: 8.95 × 36. With the 21% general VAT, that is €389.86.
That number is small compared to human maintenance. And it is exactly the number that budgets use to appear cheap.
Our public rates include VAT. A brand, showcase, or corporate website starts at €3,000. A website with interactive experiences and automations starts at €4,500. Full branding with a proprietary CRM, AI, sales funnels, nurturing, and automations starts at €9,000. The industry advertises the number without VAT, and the invoice arrives 21% higher; we state the final number. No surprise hours and no surprise VAT. And if you see tiers below €3,000, that is the market, not an Aura offer: our floor is €3,000.
Technical requirements decide your hosting, not the other way around
WordPress 7.0 was released on May 20, 2026, and the 7.1 series on August 19, 2026. WordPress.org recommends PHP 8.3 or higher, MariaDB 10.11+ or MySQL 8.0+, and mandatory HTTPS (consulted 08-27-2026).
That is your hosting purchase criteria. Not rankings, not stars, not first-year offers.
- The provider offers PHP 8.3 or higher today, not "coming soon"
- There is a testing environment separate from the production one
- Backups are daily and can be restored without opening a ticket
- The contract assigns theme code, design source files, and documentation in the transfer
- The price explicitly says "plus VAT"
- It is written down how many paid plugins the project has and who renews each license
- You know who applies security updates and within what timeframe
Performance: the threshold is Google's, not the provider's
There is no room for opinion here. Google sets the Core Web Vitals thresholds at an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less, and a CLS of 0.1 or less, measured at the 75th percentile of page loads, separating mobile and desktop (web.dev, consulted 08-27-2026).
WordPress can meet these. A WordPress site with a visual builder, four loaded fonts, and fourteen active plugins almost never will. The platform does not determine the result: how much you hang on it does.
If your current site fails these three numbers, the problem is rarely fixed by switching platforms. It is fixed by removing.
Accessibility: WordPress does not exempt you
The accessibility requirements of Law 11/2023, of May 8 (BOE-A-2023-11022), which transposes the European Accessibility Act, have been applicable since June 28, 2025, for products and services within its scope, including e-commerce services. The text contemplates exceptions and a specific regime for certain smaller companies. Verified on 08-27-2026 against the consolidated text of the BOE.
No WordPress theme makes you compliant on its own. Nor does it make you non-compliant. Accessibility is decided by contrast, focus order, alternative text, and heading structure, and that is written by whoever builds the site, not who programmed the manager.
If you sell online from Spain, this obligation carries more weight in your decision than any platform comparison.
When we say no to WordPress
We reject WordPress when the project is a product and not a content site. If what you need involves users with accounts, states, organization-based permissions, and custom business logic, building that on top of a content manager is starting with technical debt.
We also rule it out when the team is not going to publish. A panel no one opens is maintenance cost without a return.
And we rule it out when the website is the face of a brand that rebuilds every eighteen months. There, the work is in the visual system and iteration speed, not in the database.
| # | Phase | What we do | Deliverables |
|---|---|---|---|
| 01 | Listen | We start by counting who edits and how many times a month, not by proposing a platform. | Interviews · Current site audit · Editor and post count |
| 02 | Define | We agree on which number needs to move before opening an admin panel. | Measurable thresholds · Scope · Success criteria |
| 03 | Map | We choose a platform when we already know what needs to be sustained. | Decision tree · Content architecture · Migration plan |
If after that count WordPress is the answer, we say so and we build it. If the project fits better on another platform or with another studio, we tell you that too.
WordPress remains worth it in 2026 for those who publish, not for those who just have a website. That is the boundary, and it is crossed with numbers you can count this very afternoon: editors, posts per month, integrations.
Tell us your three numbers—editors, posts per month, integrations—and we will tell you which platform you should use, even if we are not the ones who build it.
Frequently asked questions
Is WordPress secure in 2026?
The core is: it accumulated six low-priority vulnerabilities in 2025, compared to 11,334 in the entire ecosystem—91% in plugins and 9% in themes—according to Patchstack (data as of 02-25-2026). You introduce the risk with every plugin you install and leave unupdated.
How many plugins are too many?
The number that matters isn't how many you have, but how many are still receiving patches and who applies them. We do not install a plugin whose author has gone more than twelve months without publishing a version, and if we cannot guarantee maintenance, we do not install it.
Can I migrate from WordPress to something else later?
Yes: the content exports in standard formats and URLs can be preserved with redirects. What doesn't come out clean is what you built inside a visual builder, because that format is proprietary.
WordPress.com or WordPress installed on my hosting?
WordPress.com publishes plans from $9/month for Personal to $70/month for Commerce with monthly billing, and from $4/month to $45/month with annual payment—quoted in dollars also on their Spanish site (wordpress.com/es/pricing, consulted 08-27-2026); self-installation starts with hosting from €8.95/month plus VAT from Spanish providers. The real difference is not the price: it is that with self-installation, the code and data are yours from day one.
What if my current site is slow with WordPress?
Measure LCP, INP, and CLS at the 75th percentile first before changing anything. In most cases we audit, the problem lies with the theme and plugins, not the platform, and changing tools without removing weight just replicates the same result on a new site.
Keep reading
- Which platform to choose for your website in 2026: WordPress, builder, headless, or custom
- Which hosting to choose in Spain: criteria, not affiliate rankings
- WooCommerce or Shopify in Spain: the tipping point by revenue
- Total cost of a website over 36 months: the number almost no one gives you
Transparency note. Some of our own data in this guide is still being measured on real projects, with a single method. We will publish it with its sample size and date range once the sample is large enough; until then, every figure you see carries its source and date of consultation.
Sources
- https://w3techs.com/technologies/details/cm-wordpress — WordPress share: 58.9% among sites with a known CMS, 40.7% of all websites; Elementor 31.5%, WooCommerce 19.8%. Consulted 08-27-2026
- https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/ — 11,334 new vulnerabilities in 2025 (+42%), 91% in plugins, 9% in themes, 6 in core. Data as of 02-25-2026
- https://web.dev/articles/vitals — Core Web Vitals thresholds: LCP 2.5s, INP 200ms, CLS 0.1, measured at the 75th percentile
- https://wordpress.org/download/releases/ — WordPress 7.0 released 05-20-2026 and 7.1 series 08-19-2026
- https://wordpress.org/about/requirements/ — recommended requirements: PHP 8.3+, MariaDB 10.11+ or MySQL 8.0+, mandatory HTTPS
- https://wordpress.com/es/pricing/ — plans: Personal €9/mo, Premium €18/mo, Business €40/mo, Commerce €70/mo, with annual payment discount
- https://www.raiolanetworks.com/hosting-wordpress/ — Spanish WordPress hosting: entry-level plan €8.95/mo and Pro €29.95/mo, excluding VAT, data center in Madrid
- https://www.boe.es/eli/es/l/2023/05/08/11/con — Law 11/2023, of May 8 (BOE-A-2023-11022), transposition of the European Accessibility Act; application since June 28, 2025
Want to see this thinking applied to a real project?