The website works until a renewal is missed, or its former developer is the only person who can deploy a change. Hosting should have a clear owner and a useful recovery arrangement before that becomes an urgent problem.
We are based in Perth and offer remote website support across Australia. The right hosting arrangement depends on the site, CMS and services behind it.
Find the services behind the public address
A site may depend on a host, CMS, database, media store and email sender. The domain may be managed somewhere else. Identify those services and who owns each account.
An existing provider’s access can be reviewed before a move is considered. The business needs control of renewals and recovery details, not only a password for editing text.
Choose hosting for the actual website
A static site, WordPress installation and application with a database need different environments. We review the code or platform, traffic requirements and connected services before suggesting a destination.
Available plans, storage and usage charges need to be checked against that design. Hosting location and data requirements belong in the brief rather than being inferred from the business address.
Separate domain changes from an email move
Website records and business email can share the same domain while using different services. Record the current configuration and known senders before adjusting it.
The migration plan should say which records change and what stays. Website form delivery deserves a check after the move even if ordinary mailbox access remains unaffected.
Use a checked deployment before the switch
A preview or test environment can help verify a change before it reaches the public site where the platform supports that approach. We check the content and important behaviour against an agreed acceptance brief.
URLs and redirects need attention during a rebuild or move. A working home page does not establish that service pages or enquiry paths survived.
Establish how the site could be recovered
Identify the files, content and data required to restore the site. Recovery should cover the parts behind the screen as well as the deployed code. Agree on a relevant restore test where that is in scope.
Keep previous deployment and configuration details available. A successful update should still have a documented response if a later issue appears.
Agree on support after the site is live
The handover should name account owners, renewal responsibilities and the process for requesting an update. Record known limitations and the checks performed.
Ongoing maintenance, incident response and new development need explicit coverage and availability. Hosting support does not imply round the clock monitoring or unlimited changes. Fees and subscriptions are identified before you commit.
