Small Business Website Continuity Plan: Keep the Site, Email and Enquiries Working

Some links in my articles are affiliate links. I may earn a commission when you buy through them.

Desk with laptop and notebook used to plan website continuity and account access

A website continuity plan answers a short business question: if the person who built your site became unavailable tomorrow, could your team keep the domain, email and customer enquiries working? For a Formby service business, the answer depends less on the design than on account control, clear responsibilities and a tested recovery route.

Start with a one-page record of the services behind the site and one named person for each decision. Then test the route a customer actually uses: finding the right page, submitting an enquiry, receiving a response and, if you sell online, completing an order. A backup and an update schedule matter because they protect that route; neither proves it works on its own.

Map the six things your business depends on

Keep this record somewhere your business can retrieve without relying on the website or one employee’s personal inbox. Do not put passwords in the document. Record the account owner, provider, renewal or billing contact, authorised administrator and recovery route.

Dependency What it does Question to settle
Domain registration Keeps the business name registered Which organisation controls the registrar account and renewal?
DNS Directs web and email traffic Who can view and change the authoritative records?
Website hosting Runs the website files and database What is included, and who can request support or a restore?
Business email Receives enquiries and recovery messages Who administers mailboxes and protects the mail records?
WordPress and connected services Controls pages, plugins, forms, analytics and licences Who has administrator access and approves changes?
Backups and recovery Returns the site to a working state What is copied, where is it stored, and has a restore been tested?

The domain deserves special attention. The UK’s National Cyber Security Centre advises small organisations to keep the public domain under organisational control and protect its management account. A domain account held only in a former employee’s personal email is a continuity problem even if the website looks fine today. NCSC domain guidance explains the risk.

Check the journey that produces business

A site can be online while the enquiry path is broken. Choose two or three journeys that matter to your business and make them the acceptance test after meaningful changes. A service company might test a phone link, quote form and receiving inbox. A shop adds product, basket, checkout, order notification and fulfilment handoff.

Write down the test date, page, device, labelled test submission, result on screen and result at the receiving end. Use harmless test data agreed by the owner, never a customer’s details. A form’s success message is not proof that the business received the message. Our form enquiry diagnostic follows that evidence trail when a test fails.

A decorative layout defect may wait for a planned release; a broken quote form on a busy service page should have a named response owner and an alternative contact route while it is fixed.

Decide which work the host does and which remains yours

Hosting, application maintenance and business operation are separate layers. A managed WordPress host may handle server infrastructure, platform controls, backups or staging. It does not automatically own your service descriptions, staff mailboxes, third-party plugin behaviour or the quality of enquiries arriving in your inbox.

Compare any hosting plan against your responsibility record. Krystal’s managed WordPress plans currently describe backups and staging; email mailboxes are offered separately. Check the exact plan and terms before ordering. If that arrangement fits your requirements, compare Krystal’s managed WordPress hosting. If you already have suitable hosting, the next improvement may instead be a clearer maintenance agreement or a working recovery test. Our hosting comparison deals with the purchase decision; the maintenance-plan guide deals with paid support scope.

Make changes recoverable

Before an update or redesign, the person making it should know the last known-good state, rollback route and customer tasks that must pass afterwards. WordPress recommends backups and distinguishes the database from site files. A green “backup completed” notice is less useful than evidence that a copy can be retrieved and restored.

Use a separate test environment when a change could affect enquiries or orders. Our staging guide explains what a rehearsal can reveal and what still needs checking live. Our restore-test guide gives an acceptance record without telling an owner to overwrite a live site.

Do not turn “we have backups” into a promise that the business will be back online in a fixed number of minutes. Recovery depends on what failed, what the backup contains, account access and whether newer orders or enquiries would be lost by restoring an older copy.

Put renewals and handover on the calendar

Record renewal dates for the domain, hosting, email, premium themes, plugins and any service licence the site needs. Note who sees the notices and can authorise payment. A reminder sent to an abandoned inbox is not a control.

When a designer or maintainer completes a project, ask for the account map, working administrator access, licensed assets, backup and restore explanation, DNS and email dependencies, and a dated acceptance test. A website can look finished while the owner still cannot update a service page or recover the domain.

If a domain, host or DNS setting is changing, schedule a separate change record. The hosting move guide explains why website and email moves must be distinguished.

Rehearse the first hour of a failure

Write down who notices a problem, who decides its severity, who contacts the host or developer, and how customers can reach you while the site is unavailable. Keep the plan outside WordPress. For a suspected compromise, preserve evidence and seek qualified help rather than repeatedly changing settings or restoring over the site before understanding what happened. The NCSC’s small-business response and recovery guidance separates preparation, identification, resolution and learning.

For a local business, a practical interim action may be to confirm that the phone number and business profile still show the right details, then direct customers to that established contact route while the website issue is investigated. Do not promise that a public notice or temporary redirect will preserve search traffic or every enquiry.

A 30-minute owner review

  1. Account control: can the business recover the domain, DNS, host, email and WordPress accounts without one individual’s personal mailbox?
  2. Customer path: when was a complete labelled enquiry or order last received and checked?
  3. Change owner: who approves updates and checks the site afterwards?
  4. Recovery: who can retrieve a complete backup and show a successful isolated restore?
  5. Fallback: who answers customers if the site or email fails today?

Any blank answer is a useful work item. It does not automatically mean buying another service. If you need help mapping the site or planning a handover for a Formby or Freshfield business, describe the problem through our web design service or contact page. Bring the current provider list and the business path that matters most.

Use the four companion checklists

Start with the website ownership audit to locate the controlling accounts. Use the website handover checklist when a build or redesign is ready for sign-off. Keep the first-hour website outage plan with your contact details outside WordPress, and use the domain renewal and DNS change checklist before changing routing or renewing the name.