Short answer
Website maintenance is a set of small checks repeated after launch: backups and a restore test, updates, SSL and domain dates, a hand test of the form and orders, broken links, Search Console messages, an access list and a change log. Split them into a weekly, monthly, quarterly and yearly rhythm.
Picture this: a small shop’s contact form quietly stops working after a plugin update. The site opens, the pages are in place, nobody notices anything. Weeks later a customer says, “I wrote three times and you never replied.” This is an illustration, but it shows why the question of how to maintain a website is really a checklist question: seeing a site open does not mean knowing that it works.
Maintenance is the small, repeated work that keeps a site healthy after it goes live. This guide lists that work by rhythm: weekly, monthly, quarterly and yearly. It gives a frame that fits any kind of site; where a rule depends on the platform we say so, and we use WordPress’s own documentation as the example. We have covered choosing a platform and its upkeep burden in what a CMS is and how to choose one, and choosing a domain name and hosting in how to choose a domain name and hosting. We do not repeat them here.
Step 1: Make a maintenance inventory
The first job of maintenance is to write down what needs maintaining. The table below shows the minimum inventory for a site; put a name and a date against every row.
| Item | Question to ask | Where it should sit, and with whom |
|---|---|---|
| Domain registration | Who is the registrant, and when does it renew? | In the company’s name, on a shared company address |
| DNS and hosting | Who can sign in to the panel, and where is the backup? | In a company account, with at least two people authorised |
| Certificate | Who renews it, and who gets the warning? | In the hosting or your own account, with a shared address |
| Site software and plugins | Which version, and who does the updating? | A named person responsible |
| Form and payment | Where do messages and order notices land? | In a mailbox someone actually reads |
| Analytics and Search Console | Which account, and who is authorised? | In a company account |
Step 2: Take backups and try a restore
WordPress’s developer documentation says to back up the database regularly and always before an upgrade. The same page says that fully restoring a typical WordPress site takes both the files and the database; downloading the file folder usually does not back up the database, because the database lives in a separate system outside that folder. As a general suggestion it says a weekly backup for smaller sites with few posts and a daily one for high-activity sites. It advises keeping at least 3 to 5 recent backups in different places, for example on the hosting server, in cloud storage and on your own computer. The page also recommends checking automatic backups against a manual backup now and then, and notes that most hosts back up the whole server, but that requesting a copy takes time while a quick recovery matters.
These are sentences from one platform’s documentation. On a hosted site builder the provider may take the backup; read that in your own provider’s documentation. On a static site the backup is the repository that holds the source code. Our advice is platform-neutral: never let a backup exist as a single copy on the same server, and every three months restore a backup to a test environment and confirm the site opens. Check weekly, too, that a backup was really taken. A backup that has never been restored is a backup that has not been shown to work.
Step 3: Update after the backup
The WordPress documentation says to always update to the latest version, and that you will see a notice in the admin screens when a new version is out. According to the same page, it is a good idea to back up before updating, you need to check that plugins and themes are compatible, and no single update order suits every site. After updating, it says, you should look for remaining plugin and theme updates and visit the site to confirm everything works. The page also says that from WordPress 3.7 onwards most sites can apply minor and security updates automatically in the background, while major feature releases need you to click “Update Now”.
With our advice added, that order becomes a rhythm: one update round a month, backup first, then the update, then open the site and the form by hand. The part that depends on the platform is this: on a CMS you host yourself, you or someone under a management agreement does it. On a hosted site builder the provider updates the software but you still need to review plugins and apps. On a static site, what gets updated is the dependencies. Detmore’s maintenance and performance service covers updates, security patches and Core Web Vitals tracking, and its scope is written in a separate proposal. You can read more on our web and software service page.
Step 4: Put SSL and domain dates in a calendar
An expired certificate shows visitors a warning page; when a domain expires, the site and the email go down with it. Both run on dates, so write the dates in a calendar. For an SSL/TLS certificate, Let’s Encrypt’s FAQ, as it reads today, says its default certificates are valid for 90 days and recommends renewing 90-day certificates every 60 days. That is what that organisation says about its own certificates; another certificate provider or host may use a different period. Either way, find out two things: is renewal automatic, and who is warned if it fails?
For the domain, ICANN’s page says that if a domain has expired you should contact the registrar (or reseller) at once. It also notes that a domain which is not renewed or restored in time after expiry may be made available for registration on a first-come, first-served basis. If you do not know your registrar, the page suggests a WHOIS search on ICANN’s site. Our advice: set a reminder two months before the renewal date and check then that the card is still valid.
Step 5: Test the form and the payment by hand
No monitoring tool will notice for you that a notification email is sitting in the spam folder. Once a week, send the contact form from your own address and confirm that the message reaches the right mailbox in a reasonable time. If there is a shop or a booking system, run one order from start to finish once a month: add the product to the basket, go as far as the payment step, and check that the confirmation email arrives. If your payment provider offers a test mode, use it so no real payment is taken; if it does not, ask the provider how to run the test. These are our own suggestions and do not rest on a source.
Step 6: Review broken links, Search Console messages and speed
Broken links. Once a month, click the links in the menu, on the home page and on the pages that get the most traffic; if you have a link-checking tool, crawl the whole site. Set up a redirect for pages that were deleted or renamed.
Search Console. Google’s Manual actions report page says that if your site is affected by a manual action, Google will tell you both in the Manual actions report and in the Search Console message centre. The same page, describing a mobile redirect problem, also suggests checking the Security Issues report to see whether Google thinks the site has been hacked. None of this helps if nobody reads the message, so look at the message centre once a week and make sure notifications go to more than one person. For how to use the tool, see what Google Search Console is and how to use it. We set out step by step what to do in the first hour of a suspected hack in our website security checklist.
Speed. Once a month, measure the home page and the two or three most important pages, and compare with the previous month. The Core Web Vitals checker gives a quick first look; for the fixes, see how to speed up a website.
Step 7: Keep the access list and a change log
This step does not rest on a source; it is our own advice. Every three months, list who has access to the panel, hosting, domain, analytics and Search Console accounts. Close the access of anyone who has left or finished their work on the same day, and change the password wherever a shared one is in use. Tie access to a company account rather than a person’s own, so that the site is not locked when the person goes.
A change log can be as simple as a table or a shared note: date, what changed, who did it, why, and how to undo it. A year from now, it holds the answer to “why was this plugin installed?”
Step 8: Tie it all to a rhythm
You do not need to do all of the above every day. Three weekly checks are enough: test the form, look at the Search Console messages and see that the backup was taken. There are five monthly jobs: the update round, the order test, broken links, the speed measurement and a look at the SSL date. Three jobs come every three months: the restore test, the access list and a review of the change log. Three are left for the year: domain renewal, hosting and licence renewals, and updating the handover file.
What to hand over when someone else takes over
If you are handing the site to an agency or a new person, give these items in writing: the inventory table (with its names and dates) and the access list. Add where the backup sits and the date of the last restore test, the change log and the rhythm table. What to receive at handover when a site is built is covered separately in how to commission a website. Detmore says that if you do not continue after the support period, it hands over the domain, the source code and the accounts. It adds that thanks to the technical documentation another team can carry on the work from where it stopped.
Common mistakes
- Never restoring a backup. The first restore attempt should not fall on the day you need the backup most.
- Trusting automatic renewal and sending the warning to nobody. When the card expires or a renewal fails silently, nobody knows.
- Updating without a backup. If something breaks, there is nowhere to go back to.
- Testing the form only at setup. An update or a new plugin can break the form later.
- Tying access to a person. When the person leaves, the account goes with them.
Common questions
How often should a website be maintained?
Small checks can be weekly, update and test rounds monthly, the restore test and access review quarterly, and domain and hosting renewals yearly. This rhythm is our suggestion; on a very active site, backups and tests become more frequent.
Do I need WordPress for this?
No. The frame in this guide fits any site; only the backup and update details change with the platform. We used WordPress’s documentation only as an example of how one platform describes them.
Should I do the maintenance myself or hand it to someone?
You need to know the inventory and the rhythm in either case. You can do the work yourself, or give updates, backups and monitoring to a team; whichever you choose, write down who does what.
One thing you can do today
Open a calendar and enter three dates: the domain’s renewal day, the certificate’s expiry day and the day this week when you will test the form. Then send the contact form once from your own address and see whether the message arrives.
Sources
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 14 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.