What is website maintenance?
Website maintenance is the ongoing work that keeps a website available, accurate and usable after launch. It includes software updates, backup checks, fixing broken features, reviewing content and monitoring the pages that customers rely on. Hosting supplies the infrastructure; maintenance checks that the business website actually works.
For a small business, start with what would interrupt revenue: an unavailable site, a failed booking, a missed enquiry or an order that never reaches your team. A maintenance routine should detect these failures and give someone responsibility for resolving them.
Your website maintenance schedule at a glance
Daily or automated: monitor availability, certificate warnings, backup failures and important security alerts. For a busy store or booking site, also monitor failed transactions and integration errors.
Weekly: submit an enquiry, verify delivery, check bookings or checkout, review software updates and inspect priority pages on a phone.
Monthly: check broken links, indexing, page performance, business information and analytics. Record what changed and what still needs attention.
Quarterly: test a backup restoration, review account access and check important journeys with a keyboard and across browsers.
Annually: review domain and hosting renewals, licences, recovery contacts, platform support and the maintenance budget. These intervals are a starting point; incidents and critical security fixes cannot wait for a calendar reminder.
Daily checklist: availability, alerts and backups
1. Monitor the pages that matter. Check the homepage plus a contact, booking or product page. A homepage can remain online while a form endpoint fails. Send alerts to a monitored address and name a backup contact for absences.
2. Verify backup completion. Include the database, uploads and configuration needed to recover the site, with protected copies separate from the production server. Choose the frequency based on how much recent data you could afford to lose; a store receiving orders all day may need more frequent protection than a brochure site.
3. Review urgent alerts. Investigate expired certificates, unexpected administrator accounts, malware warnings, failed payments and repeated server errors. Mark this check complete only when failures have an owner and a recorded next action.
Weekly checklist: forms, mobile journeys and updates
4. Send a real test enquiry. Use a clearly labelled test message, confirm the success screen, check delivery to the correct inbox or CRM and verify any customer confirmation. Test validation and spam controls too. A button click alone does not prove that a lead arrived.
5. Walk through the customer journey on a phone. Follow phone and email links, open navigation, request a booking and check important downloads. For stores, use an appropriate test transaction to verify checkout, payment status, order records and confirmations without creating unintended charges.
6. Review updates and supported versions. Check the CMS, plugins, themes, application dependencies and hosting runtime. Back up before changes, test risky updates in staging and keep a rollback plan. Prioritize security fixes based on severity and exposure rather than delaying every update until the next weekly session.
7. Check after deployment. Re-test forms, login and checkout after an update, even if the page layout looks unchanged. Record the version changed, test result and person responsible. Remove unused extensions after checking that they are not required.
Monthly checklist: content, technical SEO and performance
8. Check broken links and redirects. Review important navigation, service pages, images and downloads. Repair incorrect links; redirect retired pages only to a relevant replacement. Keep a useful not-found page for URLs that have no replacement.
9. Review Google Search Console. Inspect important URLs for indexing issues, check the selected canonical and investigate accidental noindex directives or crawling restrictions. Keep the sitemap limited to intended, canonical, indexable URLs. A sitemap helps discovery but does not guarantee indexing.
10. Measure mobile performance. Review PageSpeed Insights and available Search Console field data. Google defines good Core Web Vitals as LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, assessed at the 75th percentile. These are experience targets, not a guarantee of rankings. Low-traffic pages may lack field data; use lab tests to diagnose issues without treating a lab score as real-user evidence.
11. Keep business information accurate. Check opening hours, service areas, contact details, product availability, team information and expired offers. Review titles and descriptions when the underlying content changes, and make the next action clear on every important page.
12. Verify measurement. Confirm that enquiry, booking and purchase events reflect successful actions rather than button clicks. Compare recorded conversions with actual enquiries or orders. Investigate sudden changes by device and landing page before assuming the website or marketing caused them.
Quarterly checklist: recovery, access and accessibility
13. Restore a backup in an isolated environment. Check pages, uploaded files and database records, and prevent test systems from sending real customer messages or taking payments. Record the recovery duration and missing dependencies. A successful backup job is not proof of a successful restore.
14. Review account ownership. Confirm that the business controls its domain, hosting, CMS and analytics accounts. Remove access that is no longer needed, use individual accounts and enable multi-factor authentication where available. Keep recovery instructions in a secure location accessible to authorized staff.
15. Test accessibility and browser behavior. Use a keyboard to navigate menus and forms, check visible focus, review labels and error messages, and test zoom and mobile layouts. Automated checks help find some issues but do not replace testing important tasks manually.
16. Review external services. Check booking tools, maps, payment providers, email delivery and CRM integrations. Record who handles an outage or an API change, and confirm that the business has a workable fallback.
Annual checklist: renewals, ownership and the support plan
17. Confirm renewals before they become emergencies. Review domain registration, hosting, certificates, paid extensions and software licences. Check billing contacts and payment methods even when automatic renewal is enabled.
18. Reassess the platform and maintenance scope. Identify unsupported software, recurring defects and integrations that are difficult to operate. Decide whether targeted fixes are enough or a larger rebuild is justified by specific limitations.
19. Review responsibilities and response expectations. Confirm support hours, emergency contacts, backup retention, recovery responsibilities and what counts as separately quoted development. Ask for a sample maintenance report that records completed work and unresolved risks.
Adapt the checklist to WordPress, hosted stores or custom websites
For WordPress, include core, plugin and theme updates, compatibility checks, database backups and a review of unused extensions. Verify the specific features that depend on each plugin after changes.
For a hosted store or website builder, confirm what the platform manages and what remains your responsibility. Content, domain ownership, third-party apps, account access, exports and customer journeys still need attention. Do not assume the provider can restore every type of deleted content.
For a custom website, assign dependency updates, runtime support, deployment checks, application monitoring and database recovery to a developer. If the site takes orders, test stock, payment, refund and fulfilment states as part of maintenance.
How much does small business website maintenance cost?
The useful comparison is the scope of work, not a universal monthly price. A small informational website with occasional edits needs a different service from a store with payments, inventory and urgent out-of-hours support. Ask providers to separate routine care, content allowances, emergency work and new development.
Build a monthly budget from hosting and domain costs, software licences, backup and monitoring services, and the agreed support time. List annual charges separately or divide them by twelve when comparing plans. Confirm the currency, taxes, exclusions and fees for exceeding included hours.
A business owner can usually review content, submit test enquiries and log issues. Technical updates, recovery failures and persistent integration problems need someone who can diagnose and reverse changes. Outsource when the site is business-critical or no one internally can own those responsibilities.
A reusable website maintenance log
Copy this format into a spreadsheet: task | page or system | frequency | owner | last checked | result or evidence | next due | issue and follow-up. Avoid recording passwords or customer information in the log.
Example: Contact form | /contact | weekly | office manager | date checked | test enquiry reached inbox and CRM | next scheduled date | no issue. For a failed test, add a named person and a deadline instead of simply marking the task done.
Use three priorities: urgent for outages, security incidents and broken transactions; scheduled for defects that still have a workable alternative; improvement for lower-risk changes. Close a task after checking the result, and keep evidence such as a test reference or deployment record.
What to do if your website is not appearing on Google
First separate indexing from ranking. Use Search Console URL Inspection to see whether Google has indexed the page, which canonical it selected and whether the live URL is accessible. A search for the title or a site: query cannot reliably establish the full indexing state.
If the page is blocked, returns an error or points to an unintended canonical, resolve that cause. If it is indexed but gets few impressions, review whether it answers the search intent, has useful original detail and is linked from relevant pages on your website.
After a substantial update, request indexing through URL Inspection and monitor query impressions, clicks and enquiries over time. Google says crawling can take days to weeks and that requesting a crawl does not guarantee inclusion. Maintenance supports a healthy website, but repeating keywords or changing dates alone will not secure first-page placement.
Start with the checks that protect your next customer
If you have no routine today, assign an owner, verify a backup, send a test enquiry and check the mobile customer journey first. Then schedule the remaining tasks and keep the log somewhere the responsible team can find it.
Nixoware can review your website and agree a maintenance scope covering updates, backups, performance, technical SEO and ongoing support. Share your platform, important customer journeys and current problems so the support plan reflects how your business operates.