A business website is never quite finished. Service details change, forms connect to other tools, staff access shifts, and platform providers release updates. A short maintenance routine helps catch obvious problems before they frustrate customers or turn into a confusing handover.
There is no single schedule that fits every site. A simple brochure site, an online store, and a booking platform have different risks. Use the checklist below as a starting point, then adjust it to the platform, integrations, update frequency, and support agreement you actually have.
Before you begin: assign an owner
Choose one person to keep the checklist moving, even if a developer or provider performs the technical work. Record where the domain, hosting, site platform, analytics, forms, and key integrations are managed. Note who can approve a change, too. Store access securely; do not put passwords in the checklist itself.
For each item, note the date, what you checked, anything that needs attention, and who owns the follow-up. The aim is not to create paperwork. It is to make the next action easy to find when the person responsible changes.
Monthly website maintenance checklist
Start with the actions closest to a customer enquiry, booking, or purchase. A quick manual check often reveals issues that a dashboard will not explain.
- Test your main customer path. Open the homepage and one important service or product page on a phone. Follow the link to contact, booking, or checkout. Confirm that the next step is clear and the page does not have an obvious layout problem.
- Send a test through key forms. Check that a contact, quote, or booking request reaches the right inbox and that the on-screen confirmation makes sense. Use a test mode where one exists; otherwise, tell the receiving team before sending a test so it is not mistaken for a real enquiry.
- Confirm important details. Review services, prices or starting rates, hours, locations, staff names, and contact details on the pages customers use most. Update facts that have changed and identify pages that need a larger rewrite.
- Look for broken links and missing media. Check important buttons, navigation links, downloadable files, and recently changed pages. Pay attention to seasonal offers and old references that may still be visible.
- Review backup status and recovery ownership. Find out when the last backup ran, where it is stored, and who knows how to restore it. A backup status label is not the same as a tested recovery plan; ask the platform provider or technical owner what verification is appropriate for your setup.
- Review platform and security notices. Check the update and security notifications for your CMS, host, or website platform. Follow the provider’s guidance and use the agreed update process; avoid making a high-risk production change without knowing how to recover if it fails.
- Look at trends, not just a single number. If you have analytics and Search Console, review key landing pages, enquiries, search queries, and indexing or security notices. Google describes Search Console as a way to monitor search performance and site issues; its reports are useful signals, not an explanation of every change. See Google’s Search Console overview.
Quarterly website maintenance checklist
Use a longer review to check the parts of the site that are easy to forget when everything appears to work.
- Review domain and service renewals. Confirm who receives notices for the domain, hosting, SSL certificate, email, plugins, and other paid services. Check that billing and account ownership will not depend on a former employee or contractor.
- Check access and account owners. Remove access that is no longer needed through the normal account process, confirm the right people can reach essential systems, and make sure recovery contacts are current. Ask your provider about multi-factor authentication and account recovery where applicable.
- Review usability and accessibility basics. Use the site with a keyboard, make sure focus is visible, and check that form fields have clear labels and useful instructions. This is a practical spot-check, not a formal accessibility audit. The W3C forms tutorial explains accessible form labels and instructions.
- Check your important search pages. Confirm that priority services and locations are still described accurately, internally linked, and reachable. If you use Google Search Console, review whether important URLs have indexing issues and compare search trends over time. A sitemap can help search engines discover URLs, but it does not guarantee that a page will be indexed. Google’s sitemap guidance explains its role.
- Decide on one improvement. Use customer questions, support requests, search data, and form behaviour to pick a clear next improvement. Write down the expected benefit and who will make or approve the change.
After a redesign, update, or integration change
Do a focused check whenever an important page, domain, platform, form, payment step, or third-party connection changes. Before a larger release, agree who is responsible for testing and who can reverse the change if something breaks.
If the change includes a full redesign or new URL structure, use the website redesign SEO checklist to plan redirects, staging checks, launch tests, and follow-up.
- Open the changed pages at desktop and mobile widths and follow the main calls to action.
- Test forms and connected tools, including the confirmation and the destination where each submission should arrive.
- Check internal links and any URLs that moved. Confirm that planned redirects and analytics events work as expected.
- Verify that the right version of the page is public and that important search settings were not unintentionally changed.
- Record what changed, when it went live, who approved it, and where to find the recovery instructions.
When to ask for technical help
Bring in the person responsible for the site if a key form stops working, the website or checkout becomes unavailable, you receive a credible security warning, a platform update fails, or nobody can confirm that the site can be restored. Avoid repeatedly changing settings while the cause is unclear; note what happened and when, then follow your host’s or provider’s incident process.
If small changes repeatedly require workarounds, or the current platform cannot support an important customer task, the issue may be larger than routine maintenance. The managed website services guide explains how to assess ongoing ownership and provider scope. Neon Media’s managed website service describes the support we offer; confirm the exact responsibilities and response expectations in any proposed agreement.
Keep the checklist useful
A maintenance routine should fit the way your business works. Keep a short record, review the customer journeys that matter, and make ownership clear when a check uncovers an issue. Some updates are routine; others deserve a specialist, a backup plan, or a separate scope.
If you are not sure who owns your site or what should be checked first, talk with Neon Media about your current website. We can help identify a sensible starting point and clarify which work belongs in ongoing care.