Check what expires, confirm somebody receives the alerts, freeze changes, and make sure the site tells visitors when you will respond. Most holiday failures are expiries or an unread inbox.

The longest unattended period of the year

For a fortnight the site keeps taking enquiries, and nobody is looking at it.

Nothing is being posted, nobody notices a form failing, and an alert email arrives in an inbox that will not be opened until January.

Meanwhile visitors are researching, comparing, and occasionally buying, because the period is quiet for you and not for them.

Which makes an hour before you leave worth more than an hour at almost any other time, and the things to check are few and predictable.

The four things that break

Almost every holiday website failure is one of those four, and each is preventable in a few minutes.

Check what expires first

The one with a date attached, which makes it both the most predictable and the most damaging.

Look at your certificate expiry, your domain renewal, and any licence or subscription falling due between now and the middle of January.

A certificate expiring on the twenty-seventh produces a browser warning for every visitor, at a moment when nobody will notice for days.

Where anything falls in the window, renew it now rather than relying on automatic renewal, since a failed automatic renewal over a holiday has nobody to catch it.

Check the payment card too, because a card expiring in December takes several renewals down with it.

Test the form, properly

The failure that costs the most and produces no symptom.

Submit your own form, from a phone, on mobile data, and confirm the message arrives in the inbox somebody will actually read.

Not the inbox it was set up to reach three years ago. The one being monitored over the holiday.

Do the same for any booking or order confirmation, and check what the customer receives as well as what you receive.

A form that has been failing since November is a fortnight of enquiries lost, and the only way to find out is to send one.

Turn off automatic updates

For the period, deliberately.

Automatic updates are generally good and are wrong for a fortnight when nobody is available to notice a problem.

Pause them until the first working week of January, and apply anything outstanding now, in daylight, with time to test afterwards.

Security patches are the exception worth thinking about, and for most small sites the risk of an unattended breaking change over two weeks outweighs the risk of a fortnight's delay on a patch.

Whichever you choose, make it a decision rather than a default nobody examined.

A worked example

A business closed on the twenty-third and returned on the fourth.

Their certificate expired on the twenty-eighth. The renewal had failed because the card on file had been replaced in November.

For seven days every visitor saw a security warning, and the site was effectively unreachable for anybody cautious.

Nobody told them, because the alert emails went to an address checked by the person who was away.

The following year they added a ten-minute check before closing: expiry dates, a test submission, updates paused, and alerts redirected to a phone somebody carried.

Their observation was that the entire failure had been visible on a renewal date nobody had looked at.

Make sure somebody receives the alerts

The arrangement that turns an outage into a phone call.

Uptime monitoring is inexpensive or free and is worth nothing if the alert goes to an unread inbox.

Before you close, redirect alerts to whoever is contactable, ideally as a message to a phone rather than an email.

Agree who that is, and agree what they do if something arrives, which for most small businesses is telephoning one named person rather than attempting a fix.

Even where nobody can act immediately, knowing on the twenty-seventh rather than the fourth changes how long the problem lasts.

Tell visitors what to expect

The half that is about people rather than systems.

Say on the site when you close, when you return, and when somebody will respond to an enquiry.

Set the automatic reply to say the same, with a date rather than a vague shortly.

Update your listing hours for the period, including the days you are open, so nobody arrives at a closed door.

Somebody who enquires on the twenty-eighth and is told they will hear on the fourth will wait. Somebody who hears nothing assumes you did not want the work.

What to leave running

A short note, because the instinct is to switch things off.

Leave the site accepting enquiries, since the period produces research that turns into January work.

Leave any scheduled content publishing, which keeps the site looking active during a fortnight when everything else is quiet.

Consider leaving a small amount of advertising running, since costs fall after the peak and competition thins.

What to pause is the things that need attention: anything requiring a same-day response, and any offer that expires while nobody is watching.

The counter-case

This can be more preparation than a small site warrants.

A brochure site on managed hosting, with no forms beyond a contact address and nothing expiring, needs a five-minute look rather than a checklist.

There is also a risk in changing several things immediately before leaving, which is exactly the pattern that causes the problems this is meant to prevent.

Do the checks a week before you close rather than on the last afternoon, so anything found can be fixed calmly.

And accept that some risk is proportionate: a fortnight of a slightly stale site is not a business problem, while a fortnight of a browser warning is.

Before you close

  1. Check every expiry falling before mid-January.
  2. Renew anything close, rather than relying on automation.
  3. Submit your own form and confirm it arrives.
  4. Pause automatic updates until January.
  5. Redirect alerts to a phone somebody carries.
  6. Publish your closure and return dates.
  7. Do it a week early, not on the last afternoon.

Step one prevents the most damaging version of this, and it takes about two minutes to look.

What service commitments actually mean is covered in uptime percentages in hours.

Frequently asked questions

What usually breaks over the holidays?

Something expiring, a form silently failing, an automatic update breaking something, or an alert arriving in an inbox nobody will open until January.

Why check expiry dates specifically?

Because a certificate expiring on the twenty-seventh produces a browser warning for every visitor at a moment when nobody notices for days. Renew anything close rather than trusting automation.

How do I test the contact form?

Submit it yourself from a phone on mobile data and confirm it arrives in the inbox being monitored over the holiday, not the one it was set up to reach three years ago.

Should I pause automatic updates?

For the fortnight, yes. They are generally good and wrong when nobody is available to notice a problem. Apply anything outstanding now, with time to test.

What about monitoring alerts?

Redirect them to a phone somebody carries rather than an email nobody reads, and agree that the response is to telephone one named person rather than attempt a fix.

What should stay running?

Enquiries, scheduled content, and possibly a small amount of advertising since costs fall after the peak. Pause anything needing a same-day response.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Closing for two weeks?

Check what expires before mid-January, then submit your own contact form. Those two cover most of what goes wrong.

Start a Conversation