WordPress is still a useful choice when your business needs flexible content and control over its site. Its value depends on the build, the hosting and who maintains it. Compare those jobs with other platforms before you choose. If you already run WordPress, diagnose the real problem before replacing it.
- Flexible content and a choice of implementation partners
- Dependencies and operating work need active ownership
Bottom line Worth it when every ongoing job has an owner
A content management system (CMS) is the software you edit the site with. Picking one doesn't write your offers, make customer tasks work or bring visitors. That work sits around it. What a content management system does explains the basics.
WordPress can suit trades, professional firms and content led businesses. That doesn't mean every business in those groups should choose it. For the wider picture, start with planning a useful business website.
Which WordPress option are you considering?
There are two options: WordPress.com, a hosted service, or self hosted WordPress on hosting you choose. WordPress.com's own comparison says both run the same open source software. The main difference is hosting.
The last two both run WordPress you host elsewhere. Managed describes a scope to check, not a promise that every task is covered.
WordPress.org hands out the software and community resources. WordPress.com is a commercial managed hosting service built on it. A separate managed WordPress host is a third route.
Self hosted doesn't mean a server in your office, or doing every technical job yourself. A host or specialist can carry out agreed work.
WordPress.com includes hosting. What you can do depends on the plan. It lets you install plugins and custom themes on any paid plan. Developer tools come at higher tiers. Backups, developer access and support can also differ, so check the plan page.
Route | Hosting from | Site level work | Exit questions |
|---|---|---|---|
WordPress.com | WordPress.com, by plan | You, within plan limits | What exports, what stays |
Managed WordPress host | The host | Depends on the host's scope | Migration help and terms |
Other self hosted | Your chosen host | You or your specialist | Access, backups, licences |
A common mistake is treating free software as a free business website. You'll still pay for a domain, hosting and any paid licences. Setup, content and specialist help cost time or money too. Community forums aren't a supplier's response commitment either.
WordPress is released under GPLv2 or later. You don't get exclusive ownership of WordPress itself. Record who owns your custom work and content, including images and fonts. Track paid support and cloud licences separately.
What has changed and what should owners watch?
Market share figures get quoted a lot. None of them shows whether WordPress suits your site. WordPress.org's own directories say more about what you'd actually be choosing from:
The plugin directory lists over 76,000 free plugins. The theme directory says it has over 15,000 free themes. That's choice, not a reason to install more. A listing doesn't prove a plugin is maintained, secure or free of paid add ons.
The WP Engine and Automattic dispute
WP Engine, a WordPress host, is suing Automattic in a US federal court. In December 2024, the court granted a preliminary injunction. It ordered WP Engine's access to WordPress.org restored to its 20 September 2024 state.
On 24 September 2026, the court ruled on motions to dismiss. WP Engine's antitrust claims can proceed. Some other claims were dismissed or narrowed. The court's published orders, checked in October 2026, show no final judgment. Statements from either company are their positions, not court findings.
The practical lesson is ours, not the court's. Open source software can still depend on central update services, maintainers and suppliers. Ask how your site gets its updates. Ask how you'd recover or switch supplier if one dependency disappeared.
Don't migrate in a panic because of the dispute. The project keeps shipping releases, including WordPress 7.1.3 on 6 October 2026.
What WordPress does well
WordPress earns its place through six strengths. Each one comes with a condition, so check it before you rely on it.
Capability | Useful business task | Condition to check |
|---|---|---|
Content models | Manage services and articles | A clear structure and editing process |
Extensions | Add a booking system, shop or integration | Capability, licence and upkeep checked |
Search controls | Manage pages, links and settings | The build and content meet the need |
Hosting choice | Pick infrastructure that fits | Migration access and terms understood |
Supplier choice | Let a qualified new team take over | Documentation and access available |
Publishing workflow | Let staff update approved content | Real staff tasks tested |
Adding pages doesn't always mean rebuilding the site. New functions, layouts or business rules can still take real work. Don't expect unlimited growth without new costs.
A big ecosystem can widen the pool of available help. It won't make another developer understand an undocumented custom theme. Nor does it pass on an agency's paid licences.
Think of a service business with a knowledge base, or a team with several editors. A store might need a suitable WooCommerce extension. Each is a task to test, not a promise.
The real downsides and dependencies
Overlapping plugins, uneven builds and ongoing security work are real risks. A plugin count alone tells you little. Review each dependency instead:
Component and purpose: [what it does and why it's needed]
Maintainer and source: [supplier and trusted update channel]
Compatibility: [supported versions and known constraints]
Licence: [account owner, renewal date and continuing rights]
Data: [what it stores and where]
Critical task: [what stops working if it fails]
Evidence: [update test, performance or support record]
Replacement route: [alternative, export and migration work]
Responsible person: [who reviews and acts]
One slow query or an abandoned critical plugin can matter more than several small maintained ones. Not every plugin adds weight to the front end. Thirty plugins doesn't prove a bad build either. Check compatibility and the real journey before removing anything.
Vulnerabilities can sit in core, plugins or themes. Or in server software, accounts and integrations. WordPress's hardening guide calls security risk reduction, not risk elimination. The October release above fixed seven security issues in core.
Maintenance lowers risk. It doesn't make any platform immune. Someone has to own:
deciding which updates to apply, and when
testing after each update
backups and restores
reviews of who has access
checks that forms and key journeys still work
Urgent security fixes may need faster action than a monthly cycle. Testing first shouldn't mean delaying an important patch for weeks.
Find out who notices a failed update or a broken form. Then confirm who can act, and when. Managed hosting may cover infrastructure and some WordPress tasks. Content, integrations and business testing can still sit with you.
For the detail, see WordPress security for small business and planning website backups and recovery. The real question is whether you can fund or supply the work.
A common mistake is installing a plugin for every small job, then never reviewing them.
How to choose suitable hosting
Choose hosting for the site you actually run. Traffic, checkout and outside connections all change what you need. Cheap hosting isn't automatically unsuitable.
WordPress recommends PHP 8.3 or later, MariaDB 10.11 or MySQL 8.0 or later, and HTTPS. Older versions still run it. They're past end of life, though. Ask the host about:
supported PHP and database versions
resource limits, and what happens if you outgrow the plan
a staging copy for testing changes, plus backup retention and restore help
access controls and how to escalate problems
who updates core and plugins, and any banned plugins
a supported way to deploy changes
renewal prices, not just the first term
For Australian audiences, think about where visitors are, caching and delivery together. Caching serves stored copies of pages so they load faster. Local servers don't guarantee speed. Where data is stored doesn't settle privacy questions on its own either. For the full comparison, see choosing suitable website hosting.
Here, agency means your host or the specialist you've hired. Replace the generic roles with your actual agreement. An outsourced task still needs a business contact who's accountable. DNS is the set of records that points your domain at the site and email. For each area, record who's responsible and what proves the job is done:
Area | Responsible | Evidence it's done | Escalation |
|---|---|---|---|
Domain and DNS | Business | Registrant and renewal confirmed | Registrar support |
Hosting | Host | Plan, limits and renewal in writing | Host support |
Core updates | Named owner | Update log after each release | Host or developer |
Theme | Named owner | Supported version recorded | Theme vendor |
Plugins | Named owner | Dependency review kept current | Plugin vendor |
Backups | Host or specialist | Dated restore test | Specialist |
Enquiries | Business | Regular test enquiry received | Developer |
Recovery | Shared | Recovery steps written down | Host and developer |
Set up account control and a working recovery route before launch. Use individual logins and multi factor authentication (MFA). A hosting backup only counts once someone has checked that a restore actually works.
What does WordPress cost to run?
Keep setup and build costs separate from running costs. Business website costs deals with the build side. Here's the example service site ledger our cost and maintenance guides use, in Australian dollars excluding GST:
Recurring item | Assumption | Annual ex GST |
|---|---|---|
Domain | Annual retail assumption | $35.00 |
Hosting | $50 a month, separate from care | $600.00 |
Care | $120 a month, with set backup and security tasks | $1,440.00 |
Plugin licences | Annual renewals outside care | $240.00 |
Two Starter Flexible users, 2 x $11.80 x 12 | $283.20 | |
Total | $35 + $600 + $1,440 + $240 + $283.20 | $2,598.20 |
This is an example, not an Elev8d care plan offer or a typical WordPress bill. The email rate comes from Google's AUD plan table. Recheck it before you rely on it.
The monthly equivalent is a planning figure. The actual monthly charges are $193.60 for hosting, care and email. Domain and licence renewals add $275 on their due dates. If every item were taxable at 10%, the cash total would be $2,858.02. Real tax treatment depends on the supplier and your situation.
The ledger leaves out the build and content. It also leaves out new features, marketing and incident work. Providers sometimes bundle lines. Count each once, and ask what a care plan actually does.
Comparing platforms fairly
For a fair platform comparison, match the requirements, users and support level over the same period. Include migration and training where they apply. Don't call the gap between a basic hosted plan and a managed custom build a platform premium.
If you do routine work yourself, price the subscriptions and track your time. Keep any reserve and your own time separate from paid invoices. Dropping the care fee doesn't remove the work. WordPress maintenance costs and duties has the full detail.
Our free audit checks your WordPress setup, plugins and running costs, then tells you what to fix first.
Which editing approach suits your team?
WordPress has three native editing pieces. The block editor is built into core. The Gutenberg plugin, listed in the directory above, is an optional way to test beta features. A business site doesn't need it to use blocks.
The Site Editor only works with an active block theme. Elementor, Divi and Bricks are add on builders with their own architectures, licences and workflows. For versions, prices and migration, compare WordPress editing options in our builder guide.
Test with the person who'll actually do the work. Ask them to update a service description, swap a permitted image and change a contact detail. Preview the result on mobile. Include a small mistake they can safely reverse.
Staff member and role: [the person who'll do the work]
Task: [a real routine content change]
Permissions: [access needed without unnecessary control]
Preview: [desktop, mobile and any shared content]
Recovery: [reverse an authorised test mistake]
Help required: [what the person couldn't do unaided]
Global effects: [anything that changed on other pages]
Handover: [instructions and a named support contact]
Decision: [accept, improve or choose another approach]
Check their permissions fit the job. Reusable templates can protect essential layouts. Someone who only updates opening hours doesn't need unrestricted design control.
No editor is always the fastest, most accessible or easiest. If you compare builds, document the test conditions. Never present made up scores as measurements.
A common mistake is giving the person who updates opening hours full design control.
Is WordPress still good for SEO?
WordPress gives you control over pages, metadata and site settings. That control depends on how the site is built. It doesn't produce rankings on its own.
A suitable site still needs crawlable important pages, useful content and sensible internal links. Canonical settings matter too. They tell search engines which version of a page is the main one. SEO plugins help configure or inspect some of this. They don't replace SEO strategy, accurate content or a technical review.
Google's Search Essentials says meeting its requirements doesn't mean Google will crawl, index or show a page. Moving to WordPress won't automatically lift rankings. A migration can change URLs, content and links, so assess the whole change.
Before launch, check any blocks from the test copy are gone and public pages can be indexed. Protect private material with real access controls. A search engine setting isn't privacy protection.
A common mistake is launching with the staging site's search engine block still switched on.
When WordPress or another platform fits
Match the platform to the requirement that changes the decision:
Situation | Why consider WordPress | What else to compare |
|---|---|---|
Service and content site | Flexible content, supported editing | A simpler hosted option for the same tasks |
Online store | WooCommerce and suitable extensions | Shopify on catalogue, checkout and operations |
Design focused marketing site | Suitable themes and custom work | Webflow on design, CMS and handover |
Small brochure or short term offer | A bounded setup on existing hosting | Wix, Squarespace or one focused page |
Custom workflow or portal | A supported extension or bespoke work | A dedicated application |
No scores, no universal winner. WooCommerce is commerce software that runs on WordPress. Its setup guide covers the store from products to orders. A working store also needs operations and testing.
The core plugin is a free download. Some extensions need a paid subscription, and running costs still apply.
Product count alone doesn't settle the platform. Variants and staff workflows can matter more. Our guide on Shopify or WooCommerce for the store helps with that decision. For the wider matrix, compare website platforms in our platform guide.
We build on WordPress, Shopify and custom code. If you're on Squarespace and WordPress fits better, see planning a move from Squarespace.
How to start a WordPress business site well
Here's a planning route, not a full installation manual or a promised timeline.
Essential agreed tasks must work before launch. In more detail:
Agree the business task, the main action and the content scope. Prepare the website brief before anything else.
Decide the hosting route, the budget and the owners before buying any plugins.
Choose a supported theme and editing approach. Test one representative page and one staff edit.
Prepare accurate content and permitted assets. Add only functions you can justify, and document them.
Set up the enquiry path, privacy controls and measurement. Record how a real enquiry gets identified.
Test the customer and staff tasks on mobile and with a keyboard. Check errors, recovery and access too.
Get launch approval and monitor key functions. Hand over the task list, licences and renewal dates. Protect logins and personal data throughout.
A phone button click isn't automatically a completed call or a qualified lead. Before launch, confirm these pass:
Enquiries
A test reaches the intended inbox
Editing
The owner can edit and reverse a change
Public pages
They load and can be indexed
Private areas
Real access controls protect them
Backups
A restore has been tested
Ongoing care
Someone has agreed to maintain the site
The website launch checklist helps with the final checks. A supplier can do these steps for you. Know what evidence of completion you'll get. There's no universal launch time.
Should you keep, repair or replace an existing site?
Start from the problem you can actually see:
customer tasks that are slow or break
fragile integrations
editing that's hard for staff
unsupported software
unclear access to accounts
costs that keep rising
If the platform supports the work and the issues are local, compare a targeted repair or different support. If a critical dependency is unsupported or the workflow fits badly, compare a rebuild and a migration.
Compare future costs, disruption and likely outcomes. Money already spent isn't a cost of keeping the site. An expensive past build doesn't justify a failing setup. A cheap past build doesn't demand replacement either.
Before migrating, list the content, URLs and data that must survive. Website migration checks cover the full process. A new platform can carry the same unclear content and broken journey if nobody fixes them. No convenience outweighs an unsupported essential function or a missing recovery route.
What we recommend at Elev8d
Choose WordPress for what your site needs to do, not for its market share. Write down the customer and staff tasks. Name who'll own the ongoing work. Then ask each supplier to show how their build handles those tasks. Ask us the same question about our own website design and implementation support.
Frequently asked questions
Should a beginner use WordPress.com or self hosted WordPress?
WordPress.com bundles hosting. That means less to set up. Self hosting gives more choice but needs a named person for the operating work.
Is WordPress free?
The software is free under its licence. A business site still needs a domain, hosting and someone's time.
Who handles updates?
Whoever you agree in writing: you, your host or a specialist. Urgent security updates need someone who can act quickly.
Do I need WooCommerce for a service site?
Not at all. Add it when you actually sell online. A site that might grow doesn't need a store yet.
Can another developer take over my WordPress site?
Yes, if the documentation, access and licences are handed over. An undocumented custom build takes longer to learn.
Does my existing site need replacing?
Not necessarily. Diagnose the problem first. Then compare keeping, repairing and replacing, as covered above.
Next steps
Pick the step that fits where you are.
Write the tasks
List the customer and staff tasks the site must handle.
Name the owner
Decide who'll own updates, backups and fixes.
Ask for a demonstration
Ask suppliers to show the fit against your tasks.