Small sites don't get redesigned. They get abandoned.

A handful of things quietly expire behind every website: the domain, the certificate, the form nobody has tested since launch. A short calendar of checks keeps yours running, and this guide sets out what to check monthly, quarterly and annually, plus what to do if one of them has already lapsed.

The five ways small sites die

Small sites rarely fail because a competitor outdoes them. They fail because something quiet stops working and nobody was watching for it. There are five recurring causes, and each one gives a warning if you know where to look.

The domain lapses

A domain name is a lease. It runs out on a fixed renewal date, and if the card on file has expired or the reminder email went to a spam folder, the registrar (the company holding your domain name on your behalf) will let it lapse. After that, the domain usually enters a grace period, then a redemption period with a much higher fee to get it back, then it becomes available for anyone else to register. A site can look untouched for years and still vanish inside a fortnight this way.

The certificate expires

Every site using HTTPS (the padlock that shows a connection is encrypted) runs on a certificate with its own expiry date, often as short as ninety days. When it lapses, browsers stop showing the padlock and start showing a warning page instead, which turns visitors away before they ever see the content. Many hosts renew this automatically, but not all do, and a site moved between hosts sometimes loses that automation without anyone noticing.

A plugin or add-on stops being maintained

If the site runs on a content management system, or CMS (software that lets you edit pages without writing code), it likely depends on plugins for things like contact forms or image galleries. When the plugin's author stops updating it, it can quietly break when the CMS itself updates, or become the way an attacker gets in. Nobody chooses to stop maintaining a plugin on purpose; it just falls off someone's list, and the site inherits the consequence.

The enquiry form breaks and nobody notices

A form can fail silently: the page still loads, the button still submits, but the emails stop arriving because of a change on the host's mail server, a filter marking them as spam, or an update that quietly altered the form's settings. Since nobody sees a form fail from the outside, a broken one can sit there for months collecting enquiries that never reach anyone. This is the failure mode most worth checking for deliberately, because it costs business without ever showing an error.

The host closes or changes hands

Small hosting providers get bought, merge, or shut down, sometimes with a few weeks' notice and sometimes with less. If the site's files and backups live only with that host, and nobody downloaded a copy elsewhere, the site can disappear along with the company that was running it. The plumber, choir or campaign group affected does not get a say in the timing, which is why an independent backup matters more than the reputation of any one host.

The calendar and checks that catch each of these before they cause damage are set out in the maintenance section of this guide, and the recovery section covers what to do once one of them has already happened.

Through the year

The maintenance calendar: monthly, quarterly, annual checks

Work down each column in order: the monthly checks take a few minutes, the annual ones are the point where a forgotten renewal actually costs you the site.

  1. Monthly

    The things that fail quietly and cost you enquiries before anyone notices.

    Send a test enquiry through every form on the site and check it arrives, because a broken form usually gives no error to the visitor or to you. Load the site and confirm it still shows a padlock and no security warning, which means the certificate behind HTTPS is still valid. Glance over the homepage for anything visibly wrong, such as a broken image or a link that goes nowhere.

  2. Every three months

    The parts of the site nobody looks at unless something has already gone wrong.

    Confirm a recent backup actually exists somewhere you can get to it. Check who still has admin access to the site and the hosting account, and remove anyone who no longer needs it. Read the main pages for anything out of date: a price, an opening time, a phone number that changed months ago and was never updated.

  3. Once a year

    The renewals that expire quietly and the review that keeps the site telling the truth.

    Check the domain's renewal date directly with the registrar, the company that holds the domain name on your behalf, because an expired domain can be registered by someone else within days. Read the site against what the business actually does now. If anything has changed, such as taking online payments or collecting email addresses, check the legal essentials again.

This is a starting calendar: a site handling online payments or personal data needs some of these checks more often, and a host or platform that runs automatic backups and renewals removes some of them entirely, so check what your own setup already does for you.

When something has already gone wrong

A small site rarely fails all at once. Something specific breaks, usually quietly, and the fix is usually smaller than it feels from the outside.

An expired domain

A domain that is not renewed does not vanish immediately. Most registrars (the company holding your domain name on your behalf) run a grace period of a few weeks where you can renew it yourself at the normal price, followed by a longer redemption period where the registrar can usually recover it for a higher fee. After that it is released and anyone can register it, including someone who buys it specifically because your old site still ranks for your name. Check who your registrar is first, since it is not always the same company as your host, and act inside the grace period if you can. For a .uk domain, Domains, DNS and Hosting, Explained Once covers how registrar, host and domain fit together, and Nominet's own lookup will tell you the exact status of a .uk name.

A lapsed certificate

An HTTPS certificate encrypts the connection between a visitor's browser and your site, and it has an expiry date like a passport. Once it lapses, browsers show a warning that stops most visitors going further, even though nothing on the site itself has changed. Many hosts renew certificates automatically now, so the fix is often a setting to switch on, but it is worth checking that renewal is actually happening.

A form that stopped sending

A form can look fine and still be failing, because the page loads and the button works, but the message never arrives. Causes worth checking in order: the address it sends to has changed, the messages are landing in a spam folder, or a plugin or third-party service behind the form has been updated or has quietly stopped working. Test it yourself every few months. Enquiry Forms and Visitor Data, Done Properly covers what a form needs to do beyond simply sending.

A host that has closed

A host holds your website's files; when it closes, those files need moving to a new host and your domain's DNS records (the settings that tell the internet where to send visitors) need repointing. If you still have access to the old host's control panel, take a copy of the files and any database first. If you do not, the domain itself usually still works as your way back in, since it is held separately by the registrar, and a new host can rebuild from there once the DNS points at it.

Keeping a small site alive is a matter of habit, not effort.

Domains expire, certificates lapse and forms break quietly. None of it shows on the site itself until a visitor hits the problem.