WordPress Hosting for Freelancers and Agencies

Why Hosting Requirements Change When You Manage Client Websites

An individual website owner may only need to manage one WordPress installation. A freelancer or agency must often coordinate:

• Multiple websites
• Different client accounts
• Separate domains and DNS records
• Development and staging environments
• Plugin and theme licences
• Website migrations
• Backups and restorations
• Security incidents
• Team access
• Client access
• Billing and renewals
• Support requests
• Website handovers

Each additional website increases the potential administrative burden.

A hosting provider may therefore be valuable because it reduces repeated work rather than because it offers the largest storage allowance. A central dashboard, reliable restoration process or well-designed permission system may save more time than a plan advertising very high traffic limits.

WordPress-specific hosting providers may include features such as backups, updates and developer tools, although the precise service varies between providers.^[1]

The word managed should not be treated as a guarantee that every website task is handled for you. Review the provider’s documented responsibilities, support boundaries and plan limitations.

The Main Hosting Models Available to Freelancers and Agencies

1. The client purchases and controls the hosting

The client opens the account, pays the provider directly and grants the freelancer or agency access.

This model can provide a clear separation between:

• The client’s hosting contract
• The freelancer’s development service
• Ongoing maintenance work
• Domain ownership
• Email services

It is often suitable for project-based work where the website will be handed over after launch.

The main disadvantage is administrative inconsistency. Every client may choose a different provider, control panel and support arrangement.

2. The freelancer recommends a provider and the client signs up

The freelancer may recommend one or more suitable hosting services while allowing the client to remain the account owner.

This can provide a more consistent technical environment without making the freelancer financially responsible for the hosting account.

Where an affiliate relationship exists, it should be disclosed clearly. A recommendation should remain based on the client’s requirements rather than the commission available.

3. The freelancer or agency manages hosting on the client’s behalf

The agency purchases a multi-site or agency plan and places client websites under one central account.

The client may pay:

• A separate hosting fee
• A monthly website-care fee
• A combined hosting and maintenance subscription
• An annual management fee

This approach can create recurring revenue and a consistent workflow. It also gives the agency greater control over backups, staging, updates and support.

However, it introduces additional responsibilities. The agency must determine what happens when:

• A client fails to pay
• The client wants to leave
• The agency relationship ends
• A site exceeds its resource allowance
• A security incident occurs
• The hosting provider raises its prices
• The agency account is suspended
• A client requests access or a complete export

The arrangement should be documented in the client agreement.

4. The agency operates its own server infrastructure

Some agencies rent cloud servers or virtual private servers and configure the hosting environment themselves.

This can provide greater flexibility and control, but it can also require responsibility for:

• Server configuration
• Security patching
• Monitoring
• Backups
• Resource allocation
• Web server software
• Database administration
• Failure recovery
• Email delivery
• Incident response

This model may suit an agency with genuine infrastructure expertise. It is less appropriate when the team wants to focus primarily on design, marketing or WordPress development.

Managed hosting can be more expensive per site, but part of that cost may replace infrastructure work the agency would otherwise perform internally.

Hosting Priorities for Freelancers and Agencies

Centralised website management

When several sites are managed from one account, the dashboard should make it easy to:

• Identify each website
• See its environment and status
• Access backups
• Open staging
• Review resource usage
• Add collaborators
• Locate domains and IP addresses
• Request migrations
• Transfer ownership

Labels, search and client-based organisation become increasingly valuable as the website portfolio grows.

A plan supporting 50 sites is not necessarily efficient if managing those sites requires navigating a confusing or poorly structured interface.

Separate environments for every client

Client websites should be logically separated.

Depending on the platform, separation may involve:

• Separate WordPress installations
• Individual containers
• Separate databases
• Distinct SFTP credentials
• Independent backups
• Site-level user permissions
• Separate staging environments

Avoid creating one shared WordPress installation for unrelated clients merely to reduce costs.

A problem affecting one client should not unnecessarily expose or disrupt every other client website.

Ask the provider:

• How are websites isolated?
• Can each site have separate access credentials?
• Can one website be restored without affecting others?
• Can one site be transferred out of the account?
• Are resource limits applied per site or across the complete plan?

Staging and Development Workflows

A staging environment is a separate version of a website used to test changes before applying them to the public site.

WordPress recognises local, development, staging and production as possible environment types. Its developer documentation also recommends using a development copy when modifying a website so changes can be tested without interrupting the live installation.^[2][3]

Staging is useful for:

• WordPress core updates
• Plugin updates
• Theme changes
• PHP upgrades
• Custom-code testing
• Database changes
• Checkout testing
• Troubleshooting
• Redesign work
• Client approval

What to look for in a staging system

A useful staging feature should make it clear:

• How the environment is created
• Whether it uses the same software versions as production
• Whether it has separate access credentials
• How changes are pushed to the live site
• Whether files and database tables can be moved separately
• Whether a backup is created before deployment
• Whether staging consumes additional plan resources
• Whether staging is publicly accessible
• Whether search engines are discouraged from indexing it

Some managed platforms provide a staging environment for each WordPress installation and allow selected files or database data to be moved between environments.^[4]

Staging is not a complete deployment strategy

A one-click staging button does not remove the need for care.

For example, copying a staging database over a live WooCommerce store could overwrite:

• Recent orders
• Customer accounts
• Product changes
• Stock information
• Form submissions
• Membership activity

The agency should understand exactly which data is being replaced.

For dynamic websites, a safer deployment may involve:

• Moving files only
• Deploying version-controlled code
• Running controlled database changes
• Scheduling maintenance
• Taking a fresh backup
• Testing the live website immediately afterwards

Backups and Restoration

Backups are essential when an agency manages websites on behalf of clients.

A complete WordPress website normally includes both files and a database. WordPress’s administration guidance describes backing up the database and WordPress files and explains the order in which they may be restored.^[5]

Questions to ask about backups

Before selecting a hosting service, establish:

• How frequently backups are created
• Whether both files and databases are included
• How long backups are retained
• Whether backups are stored separately from the live website
• Whether they can be downloaded
• Whether individual sites can be restored independently
• Whether restoration is self-service
• Whether restoration costs extra
• Whether backups can be restored to staging
• What happens to backups after account cancellation

Daily backups may be suitable for a brochure website. A busy ecommerce or membership website may need more frequent backups because its data changes throughout the day.

Some managed WordPress platforms create automatic daily backups and offer restoration directly into a staging environment.^[6][7] These are provider-specific examples rather than universal managed-hosting features.

Maintain independent recovery options

An agency should consider retaining a backup that does not depend entirely on the hosting provider.

Provider-managed backups can be convenient, but they may become unavailable if:

• The account is closed
• The provider suffers a serious failure
• The plan is suspended
• Retention expires
• A billing dispute occurs
• The agency accidentally deletes the site
• The client relationship ends unexpectedly

The appropriate backup strategy depends on the client contract, website value and sensitivity of the stored data.

User Access and Permissions

Freelancers and agencies frequently need to provide access to:

• Developers
• Designers
• Content editors
• SEO specialists
• Clients
• Contractors
• Hosting support teams

Sharing one master password between everyone is poor practice.

A more appropriate platform should allow individual accounts or credentials with the minimum access required for each person’s role.

Look for:

• Separate user accounts
• Site-level permissions
• Company-level permissions
• Two-factor authentication
• Activity or audit logs
• Separate SFTP access
• Easy access removal
• Client-specific access
• Temporary collaborator access

A developer working on one client’s website should not automatically receive access to every site managed by the agency.

When a contractor leaves, their access should be removed promptly without changing every other team member’s credentials.

Client Ownership and Website Handover

One of the most important questions is who owns and controls the hosting account.

This should be agreed before work begins.

Client-owned hosting

Advantages include:

• Clear ownership
• Direct billing between provider and client
• Easier separation at the end of a project
• Reduced financial responsibility for the freelancer
• Less risk if the freelancer stops trading

Potential disadvantages include:

• Inconsistent hosting platforms
• Clients changing settings unexpectedly
• Delays obtaining access
• Difficulty standardising processes

Agency-owned hosting

Advantages can include:

• Centralised control
• Standardised tools
• Easier maintenance
• Consistent backups
• Recurring revenue
• Quicker support workflows

Potential disadvantages include:

• Greater contractual responsibility
• Billing administration
• Migration obligations
• Dependence on one provider
• Potential disputes about ownership or access
• Greater impact if the central account has a problem

Plan the exit process

The agreement should explain:

• Whether the client owns the website files and database
• Whether the client owns premium-plugin licences
• Who controls the domain
• Whether hosting fees are refundable
• How much notice is required
• Whether migration assistance is included
• Whether an exit fee applies
• How long backups are retained
• What happens to email services
• When the agency may suspend the website
• How personal data will be handled after termination

A provider that supports individual site transfers can simplify handovers. However, the agency should verify whether transfers preserve domains, DNS, backups, billing and collaborator access.

Migrations

Website migrations are a routine part of freelance and agency work.

You may need to migrate a site when:

• Taking over from another developer
• Moving away from unsuitable hosting
• Launching a rebuilt website
• Separating a client from an agency account
• Consolidating several websites
• Improving performance
• Changing ownership

Migration features worth evaluating

Check whether the provider offers:

• Automated migration tools
• Staff-assisted migrations
• Multiple free migrations
• Migration of multisite installations
• Migration of ecommerce sites
• Temporary domains
• Search-and-replace tools
• DNS guidance
• Post-migration testing
• Rollback arrangements
• Help with email migration

Provider-assisted migration may save time, but the agency remains responsible for verifying the result.

After migration, test:

• Page rendering
• Forms
• Login
• Ecommerce checkout
• Customer accounts
• Scheduled tasks
• Redirects
• SSL
• Analytics
• Search-console verification
• Transactional email
• DNS
• Caching

Do not cancel the former hosting account until the new site has been tested and a recoverable backup has been retained.

Developer Tools

Not every freelancer requires advanced development access. A designer building brochure websites may need a different toolset from an agency maintaining custom plugins or complex WooCommerce stores.

Potentially useful tools include:

• SFTP
• SSH
• WP-CLI
• Git
• Deployment keys
• Database access
• Error logs
• PHP version selection
• Cron management
• Environment variables
• Redirect management
• Local-development support

WordPress provides wp-env for creating local environments used to build and test plugins and themes.^[8] It also includes debugging systems intended to help developers identify errors during development.^[9]

GitHub documents deploy keys as SSH keys that grant a server access to one repository. This can support automated deployment workflows while avoiding the use of a developer’s personal account credentials.^[10]

Do not pay for tools you will not use

Advanced tools are valuable only when they support a real workflow.

A freelancer who edits pages using the WordPress dashboard may not benefit significantly from:

• Git-based deployments
• Several premium staging environments
• Command-line access
• Complex observability tools
• Custom container configurations

Choose a platform that matches your current capability while allowing reasonable room for growth.

Updates and Maintenance

WordPress websites require ongoing maintenance involving:

• WordPress core
• Plugins
• Themes
• PHP compatibility
• Backups
• Security monitoring
• Functional testing

WordPress can apply minor and security updates automatically in many configurations. Plugin and theme automatic updates can also be enabled, but the site should still be checked because compatibility problems remain possible.^[11][12]

Hosting management is not website maintenance

A managed host may maintain:

• The server operating system
• Hosting infrastructure
• Server-level security patches
• Platform caching
• Backup systems

That does not necessarily mean the host will:

• Repair custom code
• Fix a plugin conflict
• Update website content
• Correct a broken page design
• Test forms
• Maintain third-party integrations
• Manage licences
• Resolve every security issue

Freelancers and agencies should define which tasks are included in their own maintenance service and which remain the client’s responsibility.

Security Responsibilities

A hosting platform can provide infrastructure protections, but the agency remains responsible for the way client websites and accounts are managed.

Agency responsibilities may include:

• Applying WordPress updates
• Maintaining plugins and themes
• Removing unused software
• Enforcing strong passwords
• Using two-factor authentication
• Controlling user access
• Securing custom code
• Monitoring suspicious behaviour
• Testing backups
• Protecting API credentials
• Responding to incidents

Keeping WordPress core, themes and plugins updated is an important part of site security.^[13]

Agency-wide risk

Centralised hosting improves convenience but can also concentrate risk.

If one account controls many websites, compromise of that account could affect several clients. Protect it with:

• Unique passwords
• Two-factor authentication
• Individual staff accounts
• Restricted permissions
• Secure recovery details
• Access reviews
• Documented offboarding
• Independent backups
• Incident-response procedures

Do not store hosting passwords in unsecured spreadsheets, chat messages or shared documents.

Performance and Resource Allocation

A multi-site hosting plan may advertise support for a particular number of websites, but that number does not guarantee that every combination of sites will perform well.

Ten lightweight brochure sites may require fewer resources than one busy WooCommerce store.

Important workload factors include:

• Uncached requests
• Concurrent visitors
• Ecommerce activity
• Membership logins
• Database queries
• Search features
• Background tasks
• Scheduled imports
• External APIs
• Page-builder complexity
• Plugin quality

Ask the provider whether limits are based on:

• Monthly visits
• Bandwidth
• Storage
• CPU
• Memory
• PHP workers or threads
• Concurrent processes
• CDN usage
• Number of installations

Also determine whether resources are shared across the whole account or assigned separately to each site.

Handling traffic spikes

Establish what happens if a client website receives a sudden increase in traffic.

The provider may:

• Absorb the spike
• Apply overage charges
• Require an upgrade
• Restrict requests
• Contact the account owner
• Temporarily reduce performance

The agency should understand these policies before launching a large advertising campaign or promotional event.

Email Hosting

General shared-hosting packages often include email mailboxes. Specialist managed WordPress platforms may not.

This affects both cost and client expectations.

When email is separate, the client may use:

• Microsoft 365
• Google Workspace
• A specialist email provider
• An existing corporate mail system

Separating website and email hosting can reduce the likelihood that a website-hosting migration disrupts business email. It also means the agency must account for:

• DNS configuration
• Mailbox licensing
• Migration responsibility
• Spam filtering
• Account recovery
• Support boundaries

Do not promise email hosting unless the selected platform includes it and the service is covered by your client agreement.

Should Agencies Resell Hosting?

Reselling or managing hosting can create recurring revenue, but it should be treated as an ongoing service rather than passive income.

The agency may be responsible for:

• Client invoicing
• Renewals
• Support triage
• Provider communication
• Resource monitoring
• Backups
• Security
• Migrations
• Account suspension
• Data export
• Service termination

Potential advantages

• Predictable recurring revenue
• Standardised infrastructure
• Closer client relationships
• Easier maintenance
• Greater control over technical quality
• Opportunities to bundle care plans

Potential risks

• Clients expect unlimited technical support
• Hosting-price increases reduce margins
• One failure affects several clients
• Late-paying clients create difficult decisions
• The agency becomes responsible outside working hours
• Migration requests consume time
• Unclear contracts create ownership disputes

A sustainable hosting package should include enough margin to cover administration, support and unexpected work—not merely the provider’s wholesale cost.

Hosting Costs and Agency Pricing

An agency should not necessarily charge the client exactly what the hosting provider charges.

A managed hosting fee may also cover:

• Account administration
• Backup monitoring
• Restoration assistance
• Security checks
• Update management
• Support coordination
• Reporting
• Migration help
• Licence management
• Emergency availability

For example, an agency paying £20 per month for the client’s allocated hosting resources may charge more when it also provides an active care service.

The invoice and agreement should distinguish between:

• Hosting
• Maintenance
• Content changes
• Development work
• Premium licences
• Domain registration
• Email services
• Emergency support

This helps prevent a client from assuming that a small monthly hosting fee includes unlimited website work.

Hosting Features Worth Prioritising

Essential

• Reliable backups
• Straightforward restoration
• Individual website isolation
• Secure access
• Current PHP support
• SSL certificates
• Clear resource limits
• Website export options
• Responsive technical support

Highly valuable

• Staging
• Site-level user permissions
• Migration assistance
• Error and access logs
• SFTP or SSH
• Centralised management
• Resource-usage reporting
• Easy ownership transfer

Workflow-dependent

• Git deployment
• WP-CLI
• Multiple premium staging environments
• White-label dashboards
• Client billing tools
• Agency directories
• Reseller functions
• Advanced application monitoring

Choose workflow-dependent features only when they will genuinely be used.

Shared Hosting vs Managed WordPress Hosting for Agencies

These are common characteristics, not guaranteed differences. Compare actual plan documentation before purchasing.

When Shared Hosting May Be Sufficient

A reliable shared-hosting plan may be appropriate when:

• You manage only a few lightweight websites
• The sites receive modest traffic
• Most projects are simple brochure sites
• Clients own their individual accounts
• You are comfortable managing backups and updates
• Staging is not regularly required
• Cost sensitivity is high
• Email hosting is important
• The websites are not operationally critical

The lowest price should not be the only selection criterion. Review resource limits, backup procedures and support quality.

When Managed WordPress Hosting May Be Worth It

Managed WordPress hosting may be appropriate when:

• You manage several client websites
• You need a consistent workflow
• Sites generate important revenue or leads
• Staging is regularly used
• Restoration speed matters
• Multiple team members need controlled access
• You frequently migrate websites
• WordPress-specific support is valuable
• Infrastructure management is reducing billable time
• You offer ongoing care plans

Kinsta, for example, documents agency-oriented features including individual staging environments, team access, site transfers, migrations and automatic backups.^[14][15] These examples should not be interpreted as guarantees applying to every managed provider.

Questions to Ask Before Choosing a Hosting Platform

Website management

• How many WordPress installations are included?
• Can sites be labelled or grouped by client?
• Can each site be transferred independently?
• Can a client be given access to only their website?
• Is there an activity log?

Development workflow

• Is staging available for every site?
• Can files and database tables be deployed separately?
• Are backups created before deployment?
• Are SSH, SFTP and WP-CLI available?
• Is Git-based deployment supported?
• Can PHP versions be changed per site?

Backups

• How often are backups created?
• How long are they retained?
• Can they be downloaded?
• Can they be restored to staging?
• Are more frequent backups available?
• What happens after cancellation?

Security

• Is two-factor authentication available?
• Are client websites isolated?
• Is malware scanning included?
• Is malware removal included?
• Is a firewall provided?
• How are incidents handled?
• Which responsibilities remain with the agency?

Performance

• Which resources are limited?
• Are limits applied per site or per account?
• Are overage charges possible?
• What happens during traffic spikes?
• Is a CDN included?
• Is server-level caching included?

Support

• Is support WordPress-specific?
• Is it available outside business hours?
• Can contractors contact support?
• Are migrations included?
• What falls outside the support scope?
• Is emergency support available?

Commercial arrangements

• Can the agency rebill or resell hosting?
• Can billing be transferred to a client?
• Are there minimum contracts?
• What are the renewal prices?
• Are taxes included?
• Can individual sites be cancelled?
• Are agency discounts dependent on maintaining a minimum spend?

A Practical Hosting Setup for a Solo Freelancer

A solo freelancer managing a small portfolio might use:

• A reputable multi-site hosting plan
• Separate WordPress installations for each client
• Individual client and contractor accounts
• Daily provider-managed backups
• An independent backup for important websites
• Staging for significant changes
• A password manager
• Two-factor authentication
• A documented website-handover process
• A standard maintenance agreement

The freelancer should avoid building a complex infrastructure system before the workload requires it.

A Practical Hosting Setup for a Growing Agency

A growing agency may require:

• Centralised multi-site management
• Separate production and staging environments
• Role-based team access
• Standardised deployment procedures
• Automated backups with tested restoration
• Resource monitoring
• Git or controlled-code deployment
• Documented security procedures
• A client offboarding checklist
• Provider-independent backups
• Defined support escalation
• Clear hosting and maintenance contracts

The agency should regularly review whether one platform still suits every client. A high-traffic store and a five-page brochure site do not necessarily belong on the same type of plan.

Common Mistakes to Avoid

Choosing solely by the number of websites

A plan allowing 100 websites may provide insufficient resources or poor isolation for an agency’s actual workload.

Sharing one master login

Every team member should use an individual account where the platform supports it.

Hosting client email without a clear support agreement

Email problems can become urgent and time-consuming. Define who is responsible before offering the service.

Treating staging as a backup

Staging is for testing. It should not replace a proper, restorable backup system.

Relying exclusively on provider backups

Maintain an independent recovery option for commercially important websites.

Failing to plan client exits

A client should be able to receive a usable export or account transfer under the terms agreed at the start of the relationship.

Bundling unlimited support into a small hosting fee

State what is included, what is chargeable and how urgent requests are handled.

Placing every client on the same plan

Select hosting according to each website’s risk, workload and commercial importance.