How often should a small business audit its website?

Websites do not decay on a timetable. They break on the day somebody changes something — a plugin update, a theme switch, a page renamed, a developer finishing a job and forgetting one checkbox. That is why "audit quarterly" is roughly the right answer and the wrong instrument.

A calendar catches slow drift. Most damage is not drift.

Check after every change, not on a schedule

The highest-value check is the one immediately after an edit, because you still know what you changed. A problem found the same afternoon takes five minutes to trace. The identical problem found in March takes an hour of archaeology.

Five changes are worth a check every single time:

• A redesign or theme change. The single most destructive event for a site's technical health. Templates carry titles, headings, canonical tags and viewport declarations, and a new one can silently drop all of them.
• A platform migration or host move. Addresses change, redirects get missed, certificates lapse in the gap.
• Renaming or deleting pages. Creates broken links in volume, from places you will not think to look.
• Installing or removing an SEO plugin. These write canonical tags, titles and robots directives. Two of them at once will fight.
• A developer finishing work. Staging sites are built with search engines blocked. A noindex tag surviving the move to production is the most common serious fault there is.

A realistic schedule for a business without a web team

Alongside the event-driven checks, this is a schedule most small businesses can actually keep.

Monthly — ten minutes

Open Google Search Console and look at two things: the Pages report, for any jump in excluded pages, and the Performance graph, for a drop in impressions. You are not analysing. You are checking that the shape of the line has not changed.

Then load your own site on your own phone, on mobile data, cold. It is the most honest test you have and it takes ten seconds.

Quarterly — an hour

Run a full audit across the whole site rather than a sample, and compare it with the last one. The comparison is the point: three new broken links and a slower server tell you more than any individual score. Fix anything critical or high the same week; put the rest on a list.

Also check the boring things that expire — your certificate, and any third-party service your site depends on.

Annually — half a day

Read your own site as a stranger would. Are the prices current? Is the service list still what you sell? Is the phone number the one you answer? Technical audits cannot see any of this, and it is more likely to be wrong than your canonical tags.

This is also the moment to audit external links, since other people's sites move without telling you.

What "continuously" buys you, and when it is worth it

Everything above is manual, which means it depends on somebody remembering. Automated monitoring removes that dependency: the site is checked on a schedule and you hear from it only when something changes.

The honest version of when that is worth paying for: when more than one person can edit the site, when the site is a meaningful source of enquiries, or when you have already been caught once. A five-page brochure site that nobody touches does not need watching weekly. A site where a staff member updates products, or an agency pushes changes you do not review, is a different situation — the value is not the audit, it is finding out within days instead of within quarters.

If you are somewhere in between, the useful compromise is a good quarterly audit plus the monthly ten-minute Search Console glance. That catches most of what matters for the price of remembering.

The one thing to do today

If you have never audited the site, do not start with a schedule. Start by finding out whether something is wrong right now, because the answer changes how much attention the next twelve months deserve.

Run the free audit below. If it comes back clean, you have learned that quarterly is plenty. If it does not, you have learned something more useful.