Without monitoring
A customer reports the issue. It then has to be reproduced, traced and dated.
WordPress maintenance & monitoring · Switzerland
I install my own monitoring system on your website: internal functions are checked every minute and external services every five minutes. As soon as a problem appears, I have the information needed to understand it and respond quickly.
No long-term commitment. You speak directly with the person monitoring and maintaining your website.
Before a customer tells you
The homepage may still load while the cart, payment, email delivery or an external synchronisation is already down. Without monitoring, the issue is often discovered by a customer — sometimes hours or days later.
A customer reports the issue. It then has to be reproduced, traced and dated.
The failed check is identified automatically with the time, affected service and diagnostic context.
Many incidents that could last for days can be handled within hours — sometimes within minutes.
More than the homepage
The exact list is adapted to your website. For an online shop it may include:
Server response, essential pages, SSL certificate and critical errors.
Resources, data access, scheduled tasks and queues.
Products, add-to-cart, totals and checkout.
Stripe, Datatrans, TWINT, PayPal or the gateway used by your site.
Shipping, CRM, ERP, stock, maps, bookings and business tools.
Orders, forms, notifications and password resets.
Backup execution and availability checks.
WordPress, plugins, theme, unusual errors and required patches.
Monitoring tailored to your site
I developed this system from real problems encountered on brochure sites, online shops and custom platforms. Each check represents a real function: reading data, triggering an action or confirming that an external service responds correctly.
Internal checks run every minute. APIs and external services are checked every five minutes to detect outages quickly without generating unnecessary traffic.
Monitoring immediately shows where to look. Maintenance then fixes the cause and reduces the chance of the same incident happening again.
Public status & technical log
A status page can show the overall state of important services. During a known incident, customers can see that the issue has been identified and is being handled.
View a status page example →The private log records the affected service, date and time, incident description, actions performed and recovery time.
How it works
An automated check fails and the incident is recorded with its context.
I determine whether the issue is with the site, server or an external service and assess its impact.
I fix what belongs to the site or introduce a workaround when technically possible.
The issue, its cause and the actions taken are recorded in the technical log.
Ongoing support
A predictable cost
Monitoring of the catalogue, cart, checkout, payment, transactional emails and essential APIs.
Questions
The monitoring system runs 24/7. Intervention conditions and hours are agreed at the start. A specific response level can be arranged for a critical business.
Monitoring distinguishes a website failure from a provider incident. I assess the impact, inform you and implement a workaround when technically possible.
Yes, after an initial diagnostic covering code quality, hosting, backups, licences and monitoring points.
Corrections to existing functions are included within the agreed scope. A new feature or redesign is quoted separately.
Yes. The service is paid at the start of each month and has no long-term commitment.
Next step
Show me your website and the services it depends on: payment, shipping, bookings, CRM, emails or business tools. I will tell you which checks matter and whether the standard plan fits.
First call free and without commitment · reply within one business day