A monthly website health check is twelve concrete checks — a backup restore test, updates, speed, a real form submission, broken links, Search Console coverage, certificate expiry, analytics anomalies, content freshness, an accessibility spot check, hosting and disk space, and legal pages — done in one focused hour, scored out of 24, and written down. Sites rarely fail all at once; they drift, one skipped check at a time, and this hour is how an owner catches the drift while it is still cheap to fix.
Ask owners when their website was last checked and most will say “it seems fine” — which means the homepage loaded for them recently. Meanwhile the backup has been failing quietly for two months, the contact form’s messages are landing in a spam folder nobody opens, and a certificate warning is greeting the small share of visitors whose browsers check strictly. None of these faults announces itself. Each one is found either by a routine check or by a customer, and the customer route costs more in every currency: money, time and trust. This guide turns the vague intention to “keep an eye on the site” into a defined hour: twelve named checks, a minute-by-minute timetable that adds up to exactly sixty, a simple scoring system that makes month-to-month drift visible, and a record-keeping habit light enough to survive contact with a busy diary. It builds on the routines in our guides to backing up your website and updating your website safely, and assumes a small-business site; larger or heavily regulated sites will add checks of their own.
The 60-Minute Timetable
| Minutes | Time | Check |
|---|---|---|
| 0–8 | 8 min | 1. Backups — confirm the latest backup exists and test a restore |
| 8–13 | 5 min | 2. Updates — apply or schedule platform, theme and extension updates safely |
| 13–18 | 5 min | 3. Speed — load the homepage and one key page on a phone connection |
| 18–23 | 5 min | 4. Forms — submit the contact or booking form and confirm arrival |
| 23–28 | 5 min | 5. Broken links — run or review a link check on key pages |
| 28–35 | 7 min | 6. Search Console — coverage errors, exclusions and security warnings |
| 35–38 | 3 min | 7. Security — certificate expiry date and admin access review |
| 38–43 | 5 min | 8. Analytics — traffic and conversion anomalies versus last month |
| 43–49 | 6 min | 9. Content freshness — dates, prices, offers and opening hours |
| 49–53 | 4 min | 10. Accessibility — one page by keyboard and zoom |
| 53–57 | 4 min | 11. Hosting — disk space, resource warnings, domain and plan renewals |
| 57–60 | 3 min | 12. Legal pages — privacy, terms and contact details current; score and file the record |
How the 60 minutes are allocated across the health check (minutes) — hover or tap each bar for details.
The allocation is deliberate, not arbitrary. Backups and Search Console get the largest slices because they are the two checks that reveal problems invisible from the front of the site — a failed restore test and a coverage error both hide behind a homepage that looks perfectly healthy. The front-of-site checks, speed and forms, are quick because they are binary: the page loads acceptably or it does not, the form message arrives or it does not. Legal pages sit at the end with the scoring because both are quick reviews against last month’s record rather than fresh investigations — until the month something has changed, when they earn their minutes back.
The Twelve Checks, One by One
1. Backups: Prove the Restore Works
Confirm a recent full backup exists, stored somewhere other than the hosting account alone, then test the restore path — a full restore to a staging copy if you have one, or at minimum a walkthrough of the restore steps with the backup file opened and verified. A backup’s value is entirely in its restore, and restore faults — incomplete files, wrong formats, missing database — only appear when the restore is attempted. Do the attempt in a calm monthly hour, not during an incident.
2. Updates: Small, Ordered and Checked
Review available updates for the platform, theme and extensions, read any notes touching payments, forms or the page builder, and apply them in the safe order — backup first, minor items before major ones, money paths checked afterwards. The full routine is set out in our guide to updating your website safely; in the health-check hour, the goal is simply that no update is more than a month old and no security release is waiting at all.
3. Speed: Load the Pages That Earn Money, on a Phone
Open the homepage and your most important landing or product page on a phone using a normal mobile connection, and time them honestly. You are looking for change, not laboratory scores: a page that used to feel instant and now hesitates has gained something — an oversized image, a new script, a plugin doing more than it should. Note anything noticeably slower for investigation rather than trying to fix it inside the hour.
4. Forms: Submit One for Real, and Chase It to Arrival
Fill in the contact, booking or quote form exactly as a customer would, marking it clearly as a test, and then confirm the message arrived in the right inbox, any automatic confirmation reached the sender address, and the enquiry was stored wherever your process expects it. Forms fail silently more often than any other money path — a changed email address, a full mailbox, an over-eager spam filter — and the failure is invisible until this test performs it.
5. Broken Links: The Slow Rot of a Growing Site
Run a link checker over the site, or review the one your platform provides, and fix or remove internal links that lead nowhere. Prioritise links on high-traffic pages and links pointing outward to resources that may have moved. Broken links rarely cost a fortune individually; collectively they tell visitors and search engines that nobody is minding the shop.
6. Search Console: Coverage, Exclusions and Warnings
Open the coverage and pages reports and compare them with last month’s record. New errors, a rising count of excluded pages, or an important page newly dropped are the findings that matter; manual actions and security warnings, if any ever appear, outrank everything else on this list and should be acted on the same day. A short monthly look here is the cheapest ranking insurance available — our guide to reading Google Search Console walks through each report for owners new to it.
7. Security: Certificate Expiry and Who Holds the Keys
Check the security certificate’s expiry date and confirm renewal is automatic or diarised with weeks to spare — an expired certificate greets every visitor with a warning and is the most preventable embarrassment on this list. Then glance at the admin user list: remove accounts for people who have left, and confirm your own login still uses a strong, unique password with any available extra verification enabled.
8. Analytics: Anomalies, Not Vanity Figures
Compare this month’s traffic, top pages and conversions with last month’s, looking for anomalies rather than applause: a top page down sharply, conversions falling while traffic holds, a referral source appearing from nowhere. Each anomaly gets a line in the record and, if unexplained, a place on the investigation list. Small drifts caught here are the same figures that, unnoticed for six months, become a redesign brief or a panic.
9. Content Freshness: The Facts Customers Act On
Read the pages customers act on — prices, opening hours, service lists, delivery information, team and contact details — and correct anything the real business has outgrown. Check dated content for anything now misleading, and look at the blog or news section with a customer’s eyes: a site whose latest post is fourteen months old is telling a story about itself, whether it means to or not.
10. Accessibility: One Page, Keyboard Only, Zoomed In
Pick one important page, put the mouse aside, and work through it with the keyboard alone: can you reach every link and button, and can you see where you are? Then zoom the browser to a large size and confirm the page stays readable and usable. Four minutes of this finds the common faults — unreachable menus, invisible focus, text that breaks when enlarged — that shut real customers out.
11. Hosting and Disk: Headroom and Renewal Dates
Check disk usage and any resource warnings in the hosting panel, and confirm the domain name, hosting plan and any paid extensions have renewal dates safely in the future, with a working payment method behind them. Sites go offline every week because a card expired, not because anything broke; this four-minute check is the entire defence.
12. Legal Pages: Still True, Still Reachable
Open the privacy policy, terms and any cookie or returns pages, and read them against reality: do they still name the tools you actually use, the address you actually trade from, and the rights you actually offer? Confirm each is linked from the footer and loads correctly. Legal pages drift out of truth quietly as tools and practices change; a quarterly deep review can sit outside this hour, but the monthly glance keeps the drift visible.
Score the Hour: A Simple Table That Shows Drift
Score each check 2, 1 or 0 as you finish it: 2 means checked and healthy, 1 means checked with an issue found and scheduled, 0 means the check failed or could not be completed. Twelve checks give a total out of 24, and the total — tracked month over month in the record — is the point. A site scoring 23, 22, 19, 16 across four months is telling you something a single month’s score cannot: maintenance is slipping, usually because the hour is being squeezed, and the falling individual scores name exactly where.
| Total score | Reading | Response |
|---|---|---|
| 22–24 | Healthy | Keep the rhythm; clear any scheduled items before next month |
| 18–21 | Drifting | Book the fixes the low scores name; do not let them roll twice |
| Below 18 | At risk | The site needs a dedicated repair session, or outside help, this month |
| Any single 0 | Urgent regardless of total | A failed restore, dead form or expired certificate is fixed this week |
Keep the Record: One Row a Month
The record is a single document or spreadsheet that lives where you will actually open it. Each month adds one row: the date, the twelve scores, the total, a line of notes naming anything found, and the actions taken or scheduled with their dates. Add two standing fields at the top that never change shape — next certificate expiry and next domain renewal — so the dates with real deadlines are visible at every opening. That is the whole template. Its power is cumulative: after six months you hold a maintenance history that shows patterns, proves care if a dispute or an insurer ever asks, and hands a developer or a new team member the site’s recent story in five minutes. Owners who keep the record also stop re-checking settled questions, because last month’s row already answered them.
Five Myths That Keep Sites Unchecked
- “The site looks fine, so it is fine.” The failures this hour catches — failed backups, dead forms, coverage errors, expiry dates — are precisely the ones that leave the homepage looking fine. Appearance is a check of one page, not of the system behind it.
- “My host handles all of that.” Hosts handle servers. They do not test your form’s arrival in your inbox, notice your prices are a season old, read your Search Console coverage, or know that a former employee still holds an admin login.
- “Checking takes a whole day.” It takes a day the first time neglect is repaid. As a monthly routine with a timetable and a record, it takes the hour on the clock above — and the record is what keeps it at an hour.
- “Nothing has changed, so nothing can have broken.” The web around your site changes constantly: browsers tighten rules, linked sites move, certificates age, inboxes fill, a plugin’s update alters a form. Standing still is not the same as staying the same.
- “Maintenance is a cost with no return.” The return is the enquiries that arrived because the form worked, the ranking kept because a coverage error was fixed in week one, the outage that never happened because a renewal was caught. Our website maintenance cost guide sets the paid alternative beside this hour honestly; either way, the checks themselves are not optional.
Conclusion: One Hour, Twelve Checks, No Surprises
A website does not need constant attention; it needs regular attention, of a defined kind, at a defined interval. Put one hour a month in the diary, work the twelve checks in the timetable’s order, score them out of 24, and write the row in the record before you close the laptop. The first run sets up the system; every run after it is faster, calmer and more valuable than the last, because the record turns each check from a fresh investigation into a comparison. The sites that stay healthy for years are rarely the most sophisticated ones — they are the ones somebody checks, briefly and on purpose, every single month.
No hour to spare, or has this checklist surfaced a backlog you would rather hand over? Book a free consultation with Asad Webs — we will run the twelve checks on your site, score them honestly, fix what is urgent, and either hand the monthly routine back to you in a form you can keep, or run it for you.
Frequently Asked Questions
How long should a monthly website health check take?
About one hour for a typical small-business site, following the timetable in this guide. The first run takes longer — you are setting up the record sheet and finding where everything lives — and later runs get faster because the previous month’s notes tell you exactly where to look.
What is the single most important check?
The backup restore test. Backups that have never been restored fail in surprising ways, and every other problem on the list — a bad update, a hacked page, a broken form — becomes far less serious when a working restore is an hour away instead of a hope.
How do I test a contact form properly?
Submit it exactly as a customer would, from the live site, with a note saying it is a test — then confirm the message arrived in the right inbox, that any confirmation email reached the test address, and that the entry appears wherever enquiries are stored. Submitting is only half the test; arrival is the other half.
What should I look for in Search Console each month?
Coverage errors that were not there last month, pages unexpectedly excluded, and any manual action or security warning. Then compare clicks and impressions with the previous month for your most important pages, so a quiet slide is caught while it is still small.
My site is on a website builder. Do these checks still apply?
Most of them, in adapted form. The platform handles updates and much of the security, but backups and exports, form tests, broken links, certificate and domain expiry, analytics anomalies, content freshness and legal pages remain yours to check.
How do I keep records without it becoming paperwork?
One running document or spreadsheet, one row per month, twelve scores plus a line of notes and the actions taken. Five minutes to fill in during the check itself. Its value appears the first time a problem repeats and the record shows when it started.
What score should worry me?
Any individual check scoring zero — a failed restore test, a dead form, an expired certificate — needs action that week regardless of the total. Of the totals, below 18 out of 24 means the site is drifting and the weak areas should be scheduled, not just noted.
Be the first to share a useful question or thought.