In short and in plain language
This article shows what is left to do once a website is built. A website ages quietly.
The software must stay up to date. A backup is a copy of your website. It must be possible to restore it. Someone must notice when the site is down. The legal texts need checking too.
You can usually change texts and photos yourself. The technical work is better handed over.
Before you sign, settle in writing who owns the domain, the content and the logins.
We look after your website after handover. Domain, content and logins stay with you.
A website project has a start, a deadline and an end. What comes afterwards rarely appears in the quote: who installs the updates, who checks whether a backup can actually be restored, who notices on a Sunday evening that the site has stopped responding, who updates the privacy policy when the legal situation moves, and who removes the fitter from the team page who left six months ago. A website does not decay like a roof, where the damage is visible from the street. In its third year it looks exactly as it did on day one and is nevertheless no longer the same. This article works through what genuinely falls due after handover, what a trade business can take on itself, what it is better off handing over — and which question should be settled before signing: who owns the domain, the content and the logins.
Key takeaways
- A website decays invisibly: it keeps showing old services, old prices and staff who left long ago, while in the background software parts age for which security notices already exist.
- Five things fall due continuously: updating the software parts, backups with a restore test, monitoring availability, renewing the domain and the certificate, and reviewing the legal texts.
- Content is something a business can usually maintain itself: a new service, a new photo, changed opening hours. Technical updates, backups and recovery after an outage belong in other hands.
- Before signing, settle who the domain is registered to, who owns the text and photos, and who receives the logins for hosting, the admin system and the business profile — in writing, not by word of mouth.
- Website maintenance starts at 49 euros per month, hosting at 15 euros per month, both cancellable monthly with no minimum term. A maintenance contract with an annual commitment and no list of services is a warning sign.
Why a website ages quietly
94 percent (Bitkom 2025) of trade businesses in Germany use a website of their own. That figure says nothing about the condition of those sites. A website is not a workpiece that stays as it was handed over: it runs on a server that gets updated, behind a domain that has to be renewed, with a certificate that expires, and with content describing a business in a state that may no longer exist. The owner notices none of this as long as the home page appears in the morning when he opens it on his phone.
That is the actual point: there is no feedback. With a leaking roof somebody eventually rings the bell. With an outdated website nobody calls to say that the services page still lists the range from two years ago, or that the contact form has sent nothing since the last server move. The prospect simply clicks on to the next business, and the failure shows up only as something that does not happen — an enquiry that never arrives and that nobody misses, because nobody knew about it.
On top of that comes habituation. Anyone who opens their own website twice a week stops seeing it. Outside eyes notice the year in the footer first, then the photo with the old company van and the reference to a promotion that ended two summers ago. If clicking through your own pages turns up more than a handful of such spots, the question is no longer maintenance but a relaunch that keeps the existing addresses.
Two kinds of decay that have nothing to do with each other
What falls due continuously, even when nobody changes anything
A website nobody works on for a year still creates work. The reason lies outside the site: software parts receive updates because weaknesses become known. Browsers change their requirements. Certificates expire after a few months and are renewed. Server environments receive new versions of the underlying language, and what ran on the old version does not necessarily keep running on the new one. None of this is dramatic as long as somebody follows it. All of it is unpleasant when it first becomes apparent because the page has gone blank.
The same split applies to responsibility. The ongoing technical work can be described, put into intervals and assigned to a fixed place — which is exactly what maintenance with a clear scope of services provides. What the business itself knows and only has to pass on is a different matter: a new service, a new colleague, a changed emergency rota. Separating these two strands cleanly is half the battle. Mix them and both end up neglected, because nobody feels unambiguously responsible.
Updates
The admin interface, extensions and templates receive new versions. They are not installed blindly, but after a backup and with a visual check of the most important pages afterwards.
Backups
Files and database are backed up separately and stored outside the server. A backup that sits on the same server as the website does not help in precisely the case it exists for.
Availability
An automatic request to the home page at short intervals reports an outage before the first customer notices it. Without that monitoring you learn about a blank page on the next working day at the earliest.
Domain and certificate
The domain expires annually, the encryption certificate at shorter intervals. Both renew themselves only if somebody set that up properly once and keeps an eye on the renewal.
Legal texts
The legal notice, the privacy policy and the consent wording in the form are not permanent documents. If the legal situation or the business details change, they have to follow — in case of doubt with professional review.
Content
Services, team, opening hours, emergency service, job adverts and photos describe a state of affairs. If the state changes, the content changes — otherwise the website describes a business that no longer exists in that form.
Updates: the work nobody sees
A website consists of several layers: the server environment, the admin system, its extensions and the design template. Every layer has its own publisher and its own rhythm. Security-related updates appear irregularly and often at short notice, functional updates at longer intervals. Install nothing and after twelve months you have a website whose components are listed as vulnerable in publicly available registers — and the address of that website is public on the internet.
The practical sequence is unspectacular, but the order matters. First back up, then install, then check. Reverse that order and, when something breaks, you restore a backup that already contains the fault. What gets checked is not the home page alone but the paths that carry money: submitting the contact form, tapping the phone number, opening a services page on a phone, using the search. That check takes a few minutes and finds exactly the cases that would otherwise stay unnoticed for weeks.
A second point concerns volume. Update once a year and you install twenty version jumps at once and, if something breaks, you do not know which one caused it. Update monthly and you have small steps and, in case of doubt, an unambiguous culprit. The total effort is no higher, it is only spread differently — and it avoids the situation where a business has to choose between risking everything at once or never touching anything again.
- A full backup of files and database before every update, stored outside the server
- Install updates, security-related ones first and promptly, functional ones bundled
- Open the home page, one services page and one location page on a phone and look at them
- Submit the contact form once for real and check that the message arrives in the right mailbox
- Tap the phone number and check that the call dialogue appears with the correct number
- Note the result briefly: date, versions installed, anything unusual — later this is the only trace
A backup only becomes a backup once it has been restored
Almost every provider advertises backups. The question is not whether backups are made, but what is backed up, where to, how long it is kept and whether anybody has ever practised the restore. Files and database belong together: the database holds text, form submissions and settings, the files hold images, documents and the design template. A backup of the database alone produces a website without images, a backup of the files alone a website without content.
The storage location is the second critical point. If the backup sits on the same server, a server failure takes it along with the website. A copy outside that environment costs little and is the only reason a backup is of any use when it matters. On retention there is a thought many people miss: if damage is only noticed after three weeks, a seven-day supply does not help. A sensible supply mixes daily states from recent weeks with a few older ones.
And finally the test. A backup that has never been restored is an assumption. Whether the file is complete, whether the database loads in the new environment, whether file permissions and links hold up only becomes clear when you try. That test belongs on a test address, not on the live website, and it belongs in a fixed rhythm — once a quarter is usually enough, and it is more than many maintenance contracts actually provide for.
The question that shows the difference
Availability: the outage on a Sunday evening
85 percent (Bitkom 2025) of trade businesses see a clear expectation among their customers of constant availability. For the website that simply means: it should answer when somebody opens it, and in the trades that is rarely during office hours. Enquiries arise in the evening on the sofa and at the weekend after the water damage. At exactly those times nobody is sitting in the office who could notice a blank page. An outage on Friday evening that is only spotted on Monday morning costs a whole weekend of visibility.
The remedy is undemanding: an automatic request to the home page at short intervals from outside the server, triggering a message when the answer fails to arrive or comes back faulty. What matters is that the request actually checks the content and not merely whether the server answers — a server can cheerfully serve an error page. Equally important is that the message reaches somebody who can act. A warning in the mailbox of a business that closes on Friday lunchtime is not monitoring, it is a log.
What an outage actually costs in the trades
Legal texts change without anybody telling you
The legal notice and the privacy policy are correct at the moment of handover and do not stay correct on their own. Two things change independently of each other: the legal situation and the business. If the legal form changes, a commercial register number is added, the address changes or new professional liability cover is taken out, those details have to follow. If a new form is built in, a map section embedded or an appointment function added, the data processing changes — and with it the text that describes it.
One legal context that has unsettled many businesses is the German Accessibility Strengthening Act. It defines a micro-enterprise as a business with fewer than ten employees (BFSG) and at most 2 million euros in annual turnover or annual balance sheet total; micro-enterprises that offer or provide services are exempt from the accessibility obligation (BFSG). That relieves many trade businesses of this one duty. It is not a free pass: obligations regarding the legal notice and data protection remain untouched, and a page that cannot be operated with a thumb loses enquiries regardless of any legal norm.
In practice that means legal texts belong in a fixed review, usually once a quarter, and additionally whenever something about the business or the website changes. Anyone who adopted the text years ago and has not looked at it since will most likely find a wrong contact person, an outdated legal basis or a reference to a tool that has long since been removed. Assessing the substance of an individual case is a matter for a lawyer, not for the agency.
Keep responsibilities separate
Content ages faster than technology
74 percent (Bitkom 2025) of businesses find that customers have become more critical. You notice it in the small things: somebody opening a website whose latest news item is three years old, listing a person in the team who is no longer mentioned on the phone, draws conclusions about the business — not about the website, but about the care taken in the work. That is unfair, but it is the reaction to expect.
The second reason is recruitment. 80 percent (Bitkom 2025) of trade businesses use digital channels to address young talent specifically. A job advert that has stood unchanged online for eighteen months looks either unfillable or unreal, and both do damage. Anyone who wants applications through their own site needs a current state there — what is being looked for, from when, for which trade. How such a page should be structured is set out in more detail under our services.
The third reason is mundane and expensive: services the business now offers do not appear on the website. An electrical contractor who has been installing charging points for two years but only lists electrical installation will not be found for charging points and will receive no enquiries for them. Every new service that has genuinely arrived in the business deserves its own page with its own text — not half a sentence in a bullet list.
- A new service in the range, or an old one that is no longer offered
- Staff changes: contacts, master craftspeople, apprentices, a new extension number
- New address, new opening hours, changed emergency service arrangements
- New vehicles, new workshop, new machines — the old pictures show the old business
- Completed reference projects with usable photos, provided the client agrees
- Price changes, where prices or starting prices are stated on the site
- New certificates, specialist declarations or guild memberships
- Seasonal work: winter service, heating maintenance, storm damage — visible before the season starts
What the business can take on itself — and what it cannot
The honest answer is: content yes, technology no. For content the business has the knowledge and nobody else does. Whether the new colleague is a journeyman or a master, how the weekend emergency service is arranged, which system was installed on the last project — none of that is in any agency file. If the website has a sensible admin system, swapping a paragraph or a photo takes a few minutes, and an hour of instruction is usually enough for somebody in the office to handle it confidently.
With technology it is the other way round. Not because it is particularly difficult, but because it needs regularity and a way out. An update that goes wrong has to be reversible within minutes, and that requires the backup, the server access and the calm to do it at eight in the evening. A business whose office consists of one and a half people can organise that in an emergency — but not reliably alongside daily work, with a customer waiting and the crew waiting for material.
| Task | Feasible inside the business | Belongs in maintenance |
|---|---|---|
| Change the text of a services page | Yes, after brief instruction | Only for a larger rebuild of the page structure |
| Swap a photo | Yes, if crop and size are specified | For new image sets and before-and-after views |
| Opening hours and emergency service | Yes, website and business profile together | Only where additional markup in the source is needed |
| Publish a job advert | Yes, with a template in the system | For a full careers page with an application form |
| Update software parts | No, there is no way to roll back | Yes, monthly with backup and visual check |
| Backup and restore test | No, needs access outside the website | Yes, with storage outside the server |
| Monitor availability | No, not feasible around the clock | Yes, with alerts to somebody who can act |
| Adjust legal texts | Business details yes, wording no | Implementation and technical side, assessment by a lawyer |
A business that can maintain its own content stays able to act. A business that has to maintain its own technology loses an evening as soon as something goes wrong.
The question before signing: who owns the domain, the content and the logins
This is the question rarely asked during the quotation meeting and the one that decides everything in a dispute. Three things are at stake. First the domain: it is registered with a registry under a holder, and that holder should be the business, not the service provider. Second the content: text, photos and design, to which usage rights attach. Third the logins: server, admin system, domain management, mailbox, business profile and everything else protected by a password.
If the domain is registered to the service provider, a change of supplier can become awkward — not impossible, but dependent on the goodwill of the other side and, in unfavourable cases, drawn out. The same applies to the business profile in map search, which carries the reviews. Reviews are trust built over years, and they cannot simply be moved. It is considerably easier to settle this before the project starts than to retrieve it later.
A second point concerns usage rights to text and images. Whoever paid for the photos does not automatically hold the rights for every use; whoever wrote the text has not automatically assigned every right. This is not a sign of distrust but a sentence in the contract: the business receives an unlimited right of use, in time and territory, to all content created for it, including after the collaboration ends. Anyone comparing what we offer should look for that sentence in every quote.
- Which holder is the domain registered to, and what does the registry record say?
- Do I receive an unrestricted right of use to text, photos and design in writing, including after the contract ends?
- Who has access to the server, admin system, domain management and business profile, and how do I obtain those logins?
- Where are the backups stored, how long are they kept, and will they be handed over on request?
- What happens on termination: is the website handed over, in what format, and with what notice period?
- Is the maintenance cancellable monthly, or does it tie me in for a year?
| Item | Should belong to the business | How to tell |
|---|---|---|
| Domain | Yes, business registered as holder | The registry record names the business, not the agency |
| Text and photos | Yes, unrestricted right of use | A sentence to that effect is in the contract, not just an email |
| Admin login | Yes, own account with full rights | Signing in works without asking the service provider |
| Business profile | Yes, business as owner | Own account, agency listed as a manager |
| Server access | Access on request | Credentials are handed over when asked for |
| Backups | Yes, handover possible | The storage location is named and retention is in the contract |
One sheet of paper in the folder
How maintenance works in practice
Maintenance is often sold as a flat fee without anybody saying what happens inside it. Yet the process is easy to describe and fits on a single page. Three details matter: at what rhythm something happens, what exactly happens, and what happens in the event of a fault. Anyone who finds those three points in a quote can compare services. Anyone who only reads the word „maintenance“ is comparing prices without content.
Equally important is the route for change requests. A business wanting to add a new service does not need a ticket workflow but a number and an address it knows. In practice a fixed contact and a short reply about effort and timing works better than any form. Anything beyond that — a new page, a new image set, a change to the structure — is commissioned separately so that the monthly maintenance stays predictable.
Daily: backup and availability
Files and database are backed up automatically and stored outside the server. In parallel an automatic request runs against the home page; if the answer fails to arrive or an error page comes back, a message goes out without anybody in the business having to notice anything.
Monthly: update and review
After a fresh backup the updates are installed, security-related ones first. Then the home page, one services page and the contact form are checked on a phone. The result is noted with the date and the versions installed.
Quarterly: restore test and legal texts
A backup is restored to a test address to see that it is complete. In the same pass the legal notice, the privacy policy and the consent wording in the form are read against the current state of the business.
On event: bring content up to date
New service, staff change, changed opening hours, new photos: the business reports the change informally, implementation follows with a short reply about timing. Small changes are included in the scope, larger ones are quantified as effort beforehand.
Annually: a review of the whole
Once a year the website is reviewed as a whole: dead links, old year references, loading behaviour on a phone, completeness of the services, condition of the business profile. The result is a short list of suggestions — with no obligation to act on them.
Files and database are backed up automatically and stored outside the server. In parallel an automatic request runs against the home page; if the answer fails to arrive or an error page comes back, a message goes out without anybody in the business having to notice anything.
After a fresh backup the updates are installed, security-related ones first. Then the home page, one services page and the contact form are checked on a phone. The result is noted with the date and the versions installed.
A backup is restored to a test address to see that it is complete. In the same pass the legal notice, the privacy policy and the consent wording in the form are read against the current state of the business.
New service, staff change, changed opening hours, new photos: the business reports the change informally, implementation follows with a short reply about timing. Small changes are included in the scope, larger ones are quantified as effort beforehand.
Once a year the website is reviewed as a whole: dead links, old year references, loading behaviour on a phone, completeness of the services, condition of the business profile. The result is a short list of suggestions — with no obligation to act on them.
What maintenance costs and how to recognise a fair contract
With us website maintenance starts at 49 euros per month and hosting at 15 euros per month — both cancellable monthly, with no minimum term. If you also want to work on visibility, local visibility starts at 290 euros per month and SEO support at 490 euros per month, likewise cancellable monthly with no minimum term. The website itself is built for a fixed price from 1,490 euros net, a relaunch of an existing site from 2,900 euros net. An overview is available under our services.
Monthly cancellation is not a detail here but the actual promise of quality. Anyone who has to convince their customers afresh every month has an incentive to do something in that month. An annual commitment reverses that incentive. Other things that should raise doubts: maintenance without named services, a notice period of several months, a contract with no statement about handing over data, and a refusal to hand over the login to the admin system.
It can be weighed against the effort the business otherwise carries itself. Two hours a month in which somebody in the office installs updates, checks afterwards and calls somebody in case of doubt cost more than the flat fee — and they fall due precisely when it does not suit. If you are unsure what makes sense for your business, a short conversation helps more than any list: get in touch.
Related Articles
Selling maintenance contracts: the service page for trades
How trade businesses offer maintenance contracts on a dedicated service page: scope, interval, price, term, cancellation and an enquiry with equipment details.
Website backups: what is saved and how it comes back
Files, database, configuration and mailboxes: what belongs in a backup of a trade website, how often it runs and how you can tell that it will really come back.
One website for several trades: structure and legal notice
Electrical, plumbing and painting firms on one site: a page per trade, requests routed to the right firm, the legal notice under § 5 DDG and GDPR roles.