WordPress hosting for freelancers and small agencies: how to set it up properly

The questions to settle before you host anything

Most problems agencies have with hosting are not technical. They come from unclear ownership and responsibility: a client who cannot get into their own domain, a freelancer still paying for a site three years after the client stopped replying, or an emergency at a weekend nobody agreed to cover. Before choosing a host, decide your answers to these:

• Who owns the domain, the hosting account and the WordPress site?
• Who pays the host, and how is that cost passed on?
• Who is responsible for updates, backups and security, and how quickly?
• What happens when a client wants to leave, or stops paying?
• Which premium plugin and theme licences belong to whom?

Write the answers into your proposal or terms. A short, plain description of what is and is not included avoids most disputes.

Three common hosting models

1. The client owns the hosting account

The client signs up and pays the host directly, and gives you access. Ownership is clear and you carry no billing risk. The downside is that you depend on the client to renew, and you may end up working across many different hosts with different control panels.

2. You host on one account and resell

You run all client sites on your own hosting and charge each client a monthly fee that covers hosting and care. You gain consistency, one place to manage everything and recurring income. You also take on responsibility for uptime, renewals and support, and need a clear exit process for clients.

3. A mix

Many freelancers host smaller clients themselves and ask larger clients to hold their own accounts. This works if each arrangement is documented, so nobody forgets which model applies to which client.

Whichever model you choose, the domain should normally be registered in the client's name. Holding a client's domain in your own account creates friction and mistrust when they want to move.

What to look for in hosting for client sites

• Separate sites, separate risk. Each client site should be isolated enough that a problem on one does not take down the others.
• Backups you can restore per site, without affecting other clients. Check how restores work before you need one.
• Clear limits on how many sites a plan allows, and what happens when you add more.
• Updates handled or easy to manage. Keeping many sites updated by hand takes real time. A host that does updates, or tools that let you do them in one place, makes a big difference.
• Access for collaborators without sharing your main password.
• Support you can actually reach when a client's site has a problem, and a clear idea of what the host fixes versus what you fix.
• Predictable pricing. Introductory discounts that jump at renewal are hard to pass on to clients. Our guide on what to look for in WordPress hosting covers this in more depth.

Access and security across many sites

Every site you manage is a door into your business. Treat access with care.

1. Use individual WordPress accounts. Give yourself, colleagues and the client their own logins with the right role. Do not share one admin account.
2. Keep the client as an administrator on their own site, unless they ask otherwise in writing. It protects both of you.
3. Use a password manager and two-factor login for every admin account, including your own.
4. Remove access when people leave, whether staff, subcontractors or a previous agency.
5. Keep a register of each client site: domain, registrar, DNS provider, host, plugins with paid licences and renewal dates.

For the site-level measures, see keep your WordPress site secure.

Licences, page builders and themes

Premium plugins and themes often come with agency licences covering multiple sites. That is convenient, but if the licence is in your name, the client loses updates when they leave you. Decide in advance whether licences transfer, whether the client buys their own, or whether you bill for them per site.

A standard toolset helps a lot. Building every client site on the same builder and a small set of trusted plugins means fewer surprises during updates and quicker fixes. Many agencies settle on Elementor for this reason; the Elementor vs Gutenberg guide covers the trade-offs.

Care plans and what to include

If you offer ongoing care, be specific. A care plan might include:

• Updates to WordPress, theme and plugins on a set schedule.
• Backups, and a restore if something goes wrong.
• Uptime monitoring and a response when the site goes down.
• A fixed amount of small content changes per month.
• A short report, so the client sees the work being done.

Be equally clear about what is excluded: new features, redesigns, content writing and problems caused by plugins the client installs themselves. Price those separately.

Handover and offboarding

Plan for clients leaving from the first day. A good exit process includes a full backup in a standard format, a list of all accounts and licences, transfer of the domain if you hold it, removal of your access, and a date after which you stop hosting. Handled smoothly, clients often come back or refer others.

For freelancers and small agencies who want to stop running servers, WP Web Hosting's WP Business plan covers up to 5 WordPress sites with priority support from a real person, and includes moving your existing sites for you. Every plan has Elementor pre-installed, an optional Elementor Pro licence per site that is activated and kept updated for you, and one-click WordPress login from BonusFlow, so you can jump between client sites without juggling passwords.

Frequently asked