Website down? Small-business response plan

Confirm the outage before you change anything

Start by checking whether the issue is real, widespread and current. Open the website on another device, try a different browser, and check again using mobile data instead of your office Wi-Fi. Ask one trusted person outside the business to test the same web address and tell you exactly what they see. Your aim is to work out whether customers are likely affected, not to diagnose the server yourself.

Be specific about the scope. Is the whole site offline, or only one page? Is the home page working but the booking link, contact form, checkout, menu or image gallery failing? Are people seeing a blank screen, a security warning, a slow-loading page, a 404 not found message, or a 500-type server error? Avoid editing DNS records, deleting files, disabling services or restoring backups unless a qualified provider has asked you to and you understand the impact.

Sources: [1] [4]

Record symptoms so support can act faster

Before you call or lodge a ticket, collect clean evidence. Write down the time you noticed the problem, the exact page address, the error message, the device and browser used, and whether you recently changed content, plugins, themes, payment settings, booking settings or domain details. Take screenshots that include the error and the web address. This helps your provider separate a website fault from a local device, internet, domain, payment or third-party platform issue.

A simple incident log can be enough. Use columns for time, person checking, page or function tested, what happened, screenshot saved, provider contacted, advice received and next action. This is not bureaucracy; it stops repeated guessing when you are stressed. It also gives you a record if you later need to review the outage, check supplier responsibilities, or explain the situation to staff.

Sources: [4]

Contact the right provider with facts, not guesses

Work out who is most likely responsible for the affected part of the system. If you have a managed website provider, contact them first because they may already know whether hosting, SSL, backups, software updates or recent website changes are involved. If you run the site yourself, you may need your hosting provider, website platform, domain registrar, ecommerce platform, booking provider, payment provider or internal IT support, depending on the symptom.

Send a short factual message: what is down, when it started, what you tested, screenshots, recent changes and the business impact. Do not send passwords through email, text or social media messages. If access is needed, use the secure method your provider recommends. If the issue involves payments, bookings or customer records, mention that clearly so the right people are involved. Taking bookings online requires a compatible booking integration; a chatbot or website message alone cannot confirm live availability unless it is properly connected to that booking system.

Sources: [1] [3]

Decide if it is routine downtime or a possible security incident

Many website outages are routine technical incidents: hosting problems, expired services, broken updates, plugin conflicts, platform outages, SSL issues or a single damaged page. They still matter because they can block enquiries, bookings or sales, but the response is usually to preserve evidence, contact the responsible provider and wait for a safe fix rather than changing several things at once.

Treat the situation more seriously if you see unexpected content, suspicious redirects, malware warnings, admin lockout, strange account activity, customer data concerns, unfamiliar users, unauthorised payments, or emails claiming your site has been compromised. In that case, stop non-essential changes and get qualified IT or cyber help. Australian Government guidance recommends planning for cyber incidents, protecting customer information, backing up information, using multi-factor authentication and knowing where to get cyber security advice, including the Australian Cyber Security Hotline for cyber incidents.

Sources: [3] [4]

Use an existing customer channel while the site is unavailable

If customers may be trying to contact you, buy, book or check details, use a channel you already control. That might be your Google Business Profile updates, social media page, email list, phone greeting, front-window signage, SMS list or an industry booking portal. Do not create a new channel during the incident unless you have to; customers are more likely to trust a place where they already recognise you.

Keep the message plain and short. Say that the website is temporarily unavailable, give the best alternative contact or purchase path, and say when you will update them if you know. Avoid blaming a supplier or promising a fix time you cannot control. For example: “Our website is temporarily unavailable. For appointments today, please call our main number during business hours. We’ll update this page once the site is back.” When the site returns, update the same channel so customers are not left wondering.

Sources: [4]

Verify recovery before you call it fixed

When the provider says the site is back, test the parts customers actually use. Check the home page, key service pages, contact page, contact form, phone links on mobile, booking links, checkout or payment handoffs if relevant, and any pages mentioned in ads or social profiles. Look for security warnings, broken layout, missing images, old content, error messages and unusually slow loading. If you receive enquiry notifications, confirm they are arriving where expected.

This is a basic owner recovery check, not a forensic security review. If there were signs of compromise, customer data exposure, payment issues or suspicious admin activity, ask a qualified professional what further checks are needed before treating the incident as closed. Measure the essentials after recovery: how long the outage lasted, which functions were affected, how many customer contacts came through alternative channels, what the provider identified as the cause, and what needs to change so the next outage is easier to manage.

Sources: [3] [4]

Website outage response checklist

Use this checklist during an active outage, and keep a copy with your website support contacts. The goal is calm action in the right order: confirm, record, contact, communicate, verify and learn.

• Confirm the issue on another device, another browser and mobile data before changing anything.
• Ask one trusted person outside the business to test the same page and report what they see.
• Record the time, page address, error message, device, browser and recent website or account changes.
• Take screenshots that show the web address and the problem.
• Identify whether the issue affects the whole site, one page, forms, bookings, checkout, payments or customer logins.
• Contact the responsible website, hosting, platform, domain, booking, payment or IT provider with facts and screenshots.
• Use secure access-sharing methods only; do not send passwords through insecure messages.
• Escalate to qualified IT or cyber help if there are redirects, malware warnings, admin lockout, suspicious account activity or customer data concerns.
• Post a short customer update through an existing alternative channel if customers are likely affected.
• After recovery, test key pages, forms, booking links, checkout or payment handoffs, mobile display and security warnings.
• Update customers through the same alternative channel once the site is working again.
• Write down the cause, downtime, customer impact and one improvement for next time.

Sources: [3] [4]

Fictional example: a clinic website fails before opening

Fictional example: a suburban allied health clinic opens at 8:30 am and finds its website showing a server error at 8:10 am. The owner checks on a laptop, then on a phone using mobile data, and asks a receptionist at home to test the site. All three see the same error on every page, but business email still works. The owner takes screenshots, notes that no website changes were made overnight, and logs the time the issue was first seen.

The owner contacts the managed website provider with the screenshots and incident log instead of trying random fixes. Because online bookings are handled through a connected booking platform, the owner also checks whether the booking platform itself is available. While support investigates, the clinic posts a short update on its existing social page asking patients to call for bookings that morning. Once the site returns, the owner tests the home page, service pages, phone link, contact form and booking handoff before removing the temporary notice.

Prepare one contact sheet before the next outage

Your best next action is to prepare an outage contact sheet before anything breaks. List your website manager, hosting provider, domain registrar, booking platform, payment provider, email provider, internal admin owner and approved customer communication channels. Add account names, support links or phone numbers where appropriate, but store passwords in a proper password manager rather than on the sheet.

This is where a managed website arrangement can make life easier: it gives you clearer ownership for hosting, care, backups, routine maintenance and minor website fixes within an agreed scope. Business Growth Clinic’s small-business website design and ongoing care service is built around that kind of clarity for focused brochure sites, with hosting and ongoing care included for hosted services. If your current setup leaves you unsure who to call when your site is down, that is a practical reason to explore the website service and agree responsibilities before the next incident.

Sources: [6]