You pay an agency to build a website. The pages look right, the contact form works and you receive a login for editing the text. It is tempting to think the job is finished. But delivering a website and keeping its software in good condition are different jobs.
What has the agency actually delivered? Your browser, the program that displays websites, asks a computer over the internet for a page. That computer is the server. A website system can run programs there to prepare the requested page, read stored content and respond to submitted forms. Your browser receives the resulting page and displays it. Software means the programs and instructions that make this happen, rather than the physical computer itself. 25 26
WordPress is one such system for managing and publishing web content. It lets an authorized editor change an article through an administration screen instead of rewriting the website’s page instructions by hand. The saved content and the programs presenting it are different things: correcting a product description is an editorial change, while replacing a faulty form program is software maintenance. A site can therefore have accurate, recently edited text and still contain software that nobody has maintained. 3 18
Think of a building handed over with fitted equipment. Receiving the keys does not arrange servicing for everything inside it. In the same way, receiving a WordPress administrator account does not tell you who will update the site, protect access or restore it after a failure.
What is actually being maintained?
The main WordPress software is often called the core. A theme helps determine how the site looks and behaves. Plugins extend what it does. The site also includes uploaded files, settings and a database: the organized store holding posts and other information. Updating one part does not establish that every other part has been maintained. 3 18
Suppose an agency installed a form plugin when it built your site. Years later, the form still displays correctly. That visible success tells you the form appears to work; it does not answer whether someone is checking for updates or whether the component still has a maintainer.
WordPress’s own security guidance recommends keeping software updated and obtaining themes and plugins from trustworthy sources. It also discusses the hosting environment. Hosting means providing the computers and related services on which the website runs. A host and a website agency may therefore maintain different things. 3
A phrase such as “managed hosting” is not enough to tell you where that division falls. One supplier might cover the underlying environment while another handles WordPress and its plugins. Your arrangement may differ. The practical risk is a task falling between them because both assume the other is doing it.
Why updating is not just pressing a button
An update replaces software with a revised release. It can address problems, but a change also has to work with the other parts of the site. WordPress’s update guidance recommends keeping the software current and making a backup before an update. It describes automatic and manual ways of updating. 16
Take the form plugin as an example. Its program receives what a visitor enters and decides how to process it. A flaw in that processing can remain invisible during an ordinary friendly enquiry: it may appear only when input differs from what the developer expected. A maintenance release can replace the faulty instructions. If nobody installs that release, the existence of a repair at the developer’s website does not change the instructions running on yours. This is why “the form still works” and “the relevant repairs have been applied” answer different questions. 3 16
The other parts of the site matter during the change. The new plugin must still cooperate with the WordPress core and the site’s other components. For an important site, I recommend a test copy where the maintainer can try the change without interrupting customers. Using made-up enquiries instead of real customer messages helps avoid exposing those messages during that preparation. A backup and a way to recover provide a fallback if something goes wrong; they do not remove the need to check the changed function.
That does not mean the business owner should blindly click every available update. It means there should be a working way to apply relevant changes and notice when they fail. If your supplier says updates are automatic, the useful follow-up is whether that covers the core, themes and plugins on your actual site — and who handles failures or exclusions.
After a change, someone should check the functions customers rely on. For a small business, that might mean opening the contact page and sending a made-up enquiry to a designated test destination. If the site takes orders or provides signed-in services, those functions need appropriate checks too. Looking at the homepage alone is a weak substitute for checking the work the site is meant to do.
This is not an argument for indefinitely postponing updates because something might break. Preparation makes it easier to update responsibly. The desired outcome is a maintained site that still performs its job, not a choice between permanent delay and unexamined change.
A backup is useful only if it can bring the site back
A typical WordPress site needs both its files and its database for a complete restoration. The files include the software, themes, plugins and uploads. The database holds posts and other stored information. Copying only one side can leave you without what is needed to reconstruct the whole site. 18
The official guidance also recommends keeping backup copies in different locations and checking that automatic backup arrangements work. For a business, the natural extension is to ask whether a usable site has actually been restored from a backup in a safe test environment. 18
Consider a backup from before yesterday’s changes. Restoring it may recover the site but omit later work. Someone has to understand what would be lost and how to handle it. “We have backups” is therefore the start of a recovery explanation, not the whole explanation.
Keep the service clear as well. A backup of a public marketing website is not automatically a backup of customer invoices stored in another application. The same supplier name on two services does not make their contents identical.
The people with access are part of the picture
Maintenance also includes administrative access. WordPress’s security guidance discusses strong credentials, additional two-step verification — another check alongside the password — and the importance of the surrounding hosting environment. These protections matter alongside software updates; one does not replace the other. 3
When an agency changes or a colleague leaves, I recommend checking who can still administer the site. The person editing product descriptions need not automatically have every maintenance power. This is a conversation about necessary access, not a request to email passwords around.
Finally, discovering that a supplier uses WordPress is not a verdict on its whole business. WordPress may run its public pages while a separate application handles invoices. The public site still matters to customers, but its technology name does not establish the security of the other system.
A small, useful step is to finish this sentence with your supplier: “After the website is delivered, maintenance means…” The answer should make clear who looks after the software, who can administer it and who can bring it back. If those responsibilities were never agreed, the gap is worth closing before the next problem makes it urgent.
Sources
[3] WordPress: Hardening WordPress
[16] WordPress: Updating WordPress
[18] WordPress: Backups