Security and maintenance

Website monitoring and management protocols

Systems and processes to keep the site under control: continuous monitoring, alerts for outages or critical crawl changes, and a workflow with staging and development environments.

It warns you
Before a client sees it
Reproducible
Nothing gets touched straight in production
Documented
The process does not live in one head

The problem

The expensive part is not the outage: it is finding out three weeks later

The most expensive disasters I have seen were not big incidents. They were small things nobody spotted: a noindex that went from staging to production, a robots.txt that blocked half the site, a certificate that expired on a Friday afternoon, a template that stopped printing canonicals after an update.

All of them are detectable in minutes with the right monitoring. Without it they are detected once traffic has already dropped and there is rebuilding to do.

What gets set up

What stays running

  • Uptime and status-code monitoring, with immediate alerts
  • Watching the things that decide crawling: robots.txt, meta robots, canonicals, sitemaps
  • Alerts for sharp changes in indexing or crawling in Search Console
  • Development and staging environments separated from production, with controlled deployment
  • Verified backups: a backup nobody has ever restored is not a backup
  • Documentation of the process, so it does not depend on one specific person being around

How it works

How it gets put in place

  1. Risk inventory

    What can break in your specific case, and what each thing would cost if it broke without warning.

  2. Monitoring

    The alerts that matter get set up. Lots of alerts nobody reads are worse than none.

  3. Environments and deploys

    Separating production, staging and development, with a clear path between them.

  4. Documentation and handover

    The process written down and the team knowing how to use it.

FAQ

What people ask before hiring

Is this website maintenance?

It is similar, but typical maintenance is updating plugins and not much else. What gets set up here is the system that warns you when something breaks and the process that stops changes reaching production without passing through staging.

Does it have to be a recurring contract?

Not necessarily. It can be set up as a project and left running with your team in charge. If you would rather I watched it, it goes inside the monthly service.

With which tools?

The ones you already have if they do the job, and if not, the ones that fit your size. There is no single answer, and setting up a disproportionate system is as bad as having none.

You might also need

Related services

Malware and hacked site recovery

Your site is hacked, swamped by bots or flagged by Google. I find the problem, remove it and close the way in.

Custom quote

Urgent

Monthly SEO and web development

Technical SEO, development and content strategy on your project, month after month. The same person decides what needs changing and then writes the code.

From €1,200 /month

Custom plugins and software

When the tool you need does not exist, it gets built: WordPress plugins, internal tools and automations.

Custom quote

Next step

Shall we talk about
your project?

Tell me what is going on and I will be straight with you about whether this service is what you need or whether something else fits better.