How to use this checklist
A website doesn't need constant attention. It needs a little, regularly, from someone who knows what to look for. This checklist splits the work into four rhythms:
- Weekly checks catch the failures that cost leads right away: forms, phones, reviews.
- Monthly checks keep the facts right: hours, contact details, your Google profile.
- Quarterly checks catch the slow problems: speed, search errors, backups, broken links.
- Yearly checks protect the things that take the whole site down: the domain and the certificate.
Pick one person to own it, put the four rhythms in their calendar, and keep a simple log of what was checked and what was found. If something on the list doesn't apply to your platform, the notes near the end say what to skip. If you'd rather someone else did the technical half, that's what a care plan is for.
Weekly checks
These are short on purpose. If you only ever do one section of this guide, do this one.
Weekly: about ten minutes
- Send a test through every form. Why: a broken form still looks fine, so it's the most expensive failure a site can have. How: fill in the contact and quote forms as a customer, with a real email address, and confirm the message arrives where your team reads it. Note the time it took.
- Check the spam folder for real enquiries. Why: form emails often get filtered as spam, especially after an email setting changes. How: search spam for your form's subject line or "website".
- Open the home page on your phone. Why: most local customers see you on a phone first. How: load it on mobile data, not office wifi. Does it load, look right, and does tapping the phone number start a call?
- Reply to new Google reviews. Why: Google names responding to reviews as a way to improve your local presence. How: open your Business Profile and answer every new review, good or bad, briefly and by name of the job if you can.
- WordPress only: look for security updates. Why: outdated plugins are one of the most common ways small sites get broken into. How: check the Updates screen in the dashboard and apply security releases promptly, after a backup.
The form test is the one people skip, and it's the one that matters most. A form that silently stops sending looks perfect from the outside. If your site gets a lot of enquiries, test weekly. If it gets a few a month, monthly is enough, but don't skip it.

Monthly checks
Once a month, set aside half an hour to make sure what the site says is still true.
Monthly: about half an hour
- Contact details match everywhere. Why: a wrong number or old address costs calls and confuses Google. How: compare the phone, email and address in your header, footer and contact page against your Google Business Profile.
- Hours, including the next holiday. Why: wrong hours send customers to a locked door. How: check the hours on the site and set special hours on your Google profile before each holiday.
- Click through the main menu and key buttons. Why: a page that's been renamed or removed leaves dead links behind. How: click every menu item, every "get a quote" button and every link in the footer.
- Google Business Profile. Why: Google lists complete, accurate info and photos among the things that help local results. How: confirm the category, services and hours, and add a few recent job photos.
- Refresh the reviews on your site. Why: a testimonial from years ago reads like a business that stopped. How: swap in two or three recent reviews, with permission.
- Glance at your analytics. Why: a sudden drop in visits or form submissions is often the first sign something broke. How: compare this month's visits and enquiries against last month and the same month last year.
- Search Console email and overview. Why: Google tells you when it finds problems, if you look. How: read any Search Console emails, then check the overview for new issues.
- WordPress only: full updates and a backup check. Why: themes and plugins update on their own schedules. How: update core, theme and plugins (on a staging copy first if you have one), remove plugins you no longer use, and confirm last night's backup actually ran.
Hours and contact details are worth checking against your Google profile at the same time, because Google compares what it finds in different places. Our guide to Google Business Profile for service businesses covers the profile side properly. For analytics, you don't need to read every report. Two numbers (visits and enquiries) and a comparison against last month will catch most problems.
Quarterly checks
Four times a year, take a longer look. These are the problems that build up slowly, where nobody notices the day they start.
Quarterly: an hour or two
- Restore a backup. Why: a backup that has never been restored is a guess. How: restore a recent backup to a test copy of the site (never over the live one) and click around. If you're on a plan, ask your provider when they last did this.
- Speed test your key pages on mobile. Why: sites get slower as photos and widgets pile up. How: test the home page and your top service page. Write down the scores so you can compare next quarter.
- Search Console reports. Why: pages dropping out of Google, or failing Core Web Vitals, rarely announce themselves. How: open the Pages report under Indexing, the Core Web Vitals report, and Security and Manual Actions. Anything new since last quarter gets a look.
- Broken link sweep. Why: links to other sites (suppliers, associations, maps) break as those sites change. How: click through every page, or use a link checker, and fix or remove anything that errors.
- Accessibility spot check. Why: customers with low vision or who can't use a mouse should be able to call you too. How: tab through the home page and your main form with the keyboard only, check that new images have alt text, and that text is readable against its background.
- Content refresh on your top pages. Why: services, prices, staff and towns change faster than anyone updates the site. How: reread your home page and top three service pages as a customer. Is everything still true?
- Remove old logins. Why: a former employee or contractor with access is a risk you don't need. How: review users on the website, the domain registrar, your Google profile and analytics, and remove anyone who has left.
For the speed test, our free Website Speed Test gives you a quick read, and Google's PageSpeed Insights shows both lab scores and, for busier sites, real visitor data. Our guide to page speed and Core Web Vitals explains what the numbers mean and which fixes pay off first. For accessibility, the spot check isn't a full audit, but it catches the obvious barriers. Our accessibility page explains the standards we build to.
Yearly checks
Once a year, protect the foundations and step back to see whether the site is still doing its job.
Yearly: half a day
- Domain renewal and auto-renew. Why: an expired domain takes your site, and often your email, down the same day. How: log in to your registrar, check the expiry date, confirm auto-renew is on, the card on file is current, the contact email is one you read, and the account has two-factor sign-in.
- SSL certificate. Why: a lapsed certificate puts a full-page security warning in front of every visitor. How: click the icon left of the address in your browser, view the certificate and note the expiry date. Most hosts renew automatically; confirm yours does.
- Every page, read through. Why: the pages nobody visits often hold the oldest mistakes. How: once a year, read every page. Fix dates, the copyright year, old photos, retired services and staff who've moved on.
- Privacy policy and legal pages. Why: if you've added analytics, ads, a booking tool or a newsletter, your policy should say so. How: compare what the site collects today against what the policy says.
- Renewal prices. Why: hosting, plugins and builder plans often renew higher than their first-year price. How: list every website bill and what it renews at.
- A full accessibility review. Why: the quarterly spot check only covers a few pages. How: go through every template (home, service, contact, blog) the same way, or have someone do it for you.
- Year-over-year results. Why: one bad month is noise; a whole year down is a signal. How: compare visits, enquiries and calls from the site against last year, and decide what to change.
On renewal prices, here's a real example of the pattern. WordPress.com's Business plan shows $25 a month for the first year and renews at $28 a month, billed yearly (wordpress.com/pricing, checked November 2026). That's honest and clearly shown, but it's exactly the kind of change that slips past if nobody reads the renewal notice. Plugins, themes and hosting work the same way.
The domain check deserves the most care. Make sure the domain is registered in your business's name, not a former web designer's, and that the account has two-factor sign-in. Our security basics guide explains why the registrar account is the one to protect above all.
What changes by platform
The checklist above covers every kind of site. Depending on what yours is built on, some items are yours, some are the platform's, and some don't exist.
| WordPress | Wix or Squarespace | Custom-coded static site | |
|---|---|---|---|
| Software updates | Yours, weekly to monthly: core, theme, plugins | The platform does it | None: no CMS or plugins |
| Backups | Yours to set up, store off-site and test | The platform keeps the site; keep your own copy of text and photos | Off-site file backups (included on our plans) |
| SSL / HTTPS | Usually your host. Confirm it auto-renews | The platform does it | Automatic on our Cloudflare hosting |
| Forms | A plugin. Test after every update | Built in. Test monthly | Test monthly (on a care plan we keep them working) |
| Domain | Yours, at the registrar | Yours if bought elsewhere; check renewal if bought through the builder | Registered in your name; check the renewal yearly |
| Content edits | You, in the dashboard | You, in the editor | Made for you on a care plan |
| Logins to review | Site admins, host, registrar | Builder account, registrar | Registrar and DNS accounts (there's no site login) |
On any platform the content, hours, Google profile, reviews and analytics checks are yours, or your provider's if your plan includes them.
WordPress
WordPress has the longest list, because the site is software you're responsible for. The weekly update check and the monthly backup check are not optional. Keep the plugin count down: every plugin you remove is one less thing to update and one less way in. If you have a staging copy, update there first. If an update breaks something and you have no staging copy, a tested backup is what saves you.
Wix, Squarespace and other builders
The platform handles the software, the hosting and the certificate, so your list is shorter: forms, content, the Google profile, reviews, analytics and the domain. Watch the apps and add-ons you've installed, since each one can break or start billing on its own. Keep your own copy of your text and photos, because a builder site can't be moved to another host as-is.
Custom-coded static sites
There's no software to update and no login on the site, so the technical half of the list mostly disappears. What's left is content, forms, monitoring, backups and the domain and DNS accounts. On our care plans we handle the technical checks and make the changes they turn up; you keep an eye on the facts only you know, like hours and services.
A monthly check, worked through
Worked example
Say an HVAC company in Maple Grove runs the monthly check on the first Monday. Here's what thirty minutes turns up:
- The test form submission arrives, but in the inbox of an office manager who left in the spring. Every enquiry since then has gone to an account nobody reads. They change the recipient to a shared office address.
- The footer still lists last year's emergency number. The Google profile has the new one. They update the site so both match.
- The holiday hours for Thanksgiving aren't set on the Google profile. They add them.
- Analytics shows visits steady but enquiries down by about half since spring. That matches the form problem in step one, so it isn't a search problem at all.
- The newest review on the site is from two years ago. They swap in three recent ones from their Google profile.
Nothing here needed a developer. Every item was found by following the list, and the first one was costing them leads every week.
This is a made-up example, but every item in it is common. The pattern to notice is step four: a drop in enquiries is often a broken form or a wrong phone number, not a ranking problem. Check the plumbing before you pay anyone for marketing.
Starting from a new site
If your site is new, or about to be, start the log on launch day. Run our free Website Launch Checklist once before launch, then use this guide as the routine after. The launch checklist catches setup mistakes; this one catches drift.
Set up the things that make maintenance easier while it's fresh:
- A shared inbox (office@ or info@) for form submissions, so a staff change doesn't break them.
- Auto-renew on the domain, with a card that won't expire soon and a contact email you read.
- Search Console and analytics, with at least two people who have access.
- A list of every account the site depends on: registrar, DNS, hosting, forms, booking, analytics. Who owns each one, and where the login lives.
That last list is the most valuable document a small business can have about its website. When something breaks, it turns a week of searching into a five-minute fix.
Whether you keep the list yourself or hand it to us, the work is the same. Businesses from Plymouth to St. Cloud have us run it on a care plan. Prices are on our pricing page, and you can ask us what your site would need.
Want a straight answer for your business?
Every Stonekept build is custom-coded, hosted on Cloudflare and kept on a monthly plan. Prices are public: builds from $2,200 with care from $199/mo. See pricing or tell us about your project and we'll give you an honest read, even if that's not us.
