WordPress Website Maintenance in Montreal: What We Actually Do Each Month

In short

  • Real WordPress maintenance goes well beyond clicking “Update”: it covers your PHP version, backups you know you can restore, security and uptime monitoring, and SEO follow-up.
  • 2026 has been a busy year: WordPress 7.0 in May, 7.1 in August, PHP 8.2 reaching end of life on December 31, 2026, and the PHP2Shell vulnerabilities in October.
  • In Quebec, a hacked website that holds contact forms or customer accounts can be a “confidentiality incident” under Law 25: it has to be logged in a register and, if there’s a risk of serious injury, reported to the Commission d’accès à l’information.

A physiotherapy clinic in Laval that books appointments online, a Longueuil renovation contractor whose quote requests come in through a web form, a West Island boutique running WooCommerce: their websites have one thing in common. They work just fine, as long as someone is looking after them.

Clients often ask us what website maintenance actually involves. Fair question: a site that works shows none of the effort that keeps it working. You only notice maintenance when it’s missing, usually on a Friday evening right before the weekend.

Here’s what we really do every month, why 2026 made it hard to put off, and what Law 25 expects from you if your site gets hacked.

What real WordPress maintenance covers

Serious maintenance comes down to six jobs, repeated every month:

  • Updates: WordPress installs its own minor core releases, but major versions, plugins and the theme need a human decision. Back up, update, then check the pages that bring in business: quote form, booking, cart, checkout.
  • PHP version: the language WordPress runs on has end-of-life dates published on php.net. PHP 8.1 has received no fixes since December 31, 2025, PHP 8.2 gets security fixes only until December 31, 2026, and PHP 8.3 is covered until December 31, 2027. WordPress recommends PHP 8.3 or newer. Always test before switching.
  • Backups: files and database, stored away from the site’s server (in separate cloud storage, for instance), going back far enough to find a clean version. And tested: a backup you’ve never restored is just a theory.
  • Monitoring: a firewall, daily malware scans and an alert as soon as the site stops responding, so problems get handled in minutes instead of days.
  • SSL certificate: since March 15, 2026, public certificates can’t be valid for more than 200 days; that drops to 100 days in March 2027 and 47 days in 2029. Renewal is usually automatic, but a DNS or hosting change can quietly break it.
  • Small edits and SEO: updating opening hours, adding a project, watching page speed and Google Search Console. This is where maintenance meets SEO.

2026: WordPress 7.0, PHP 8.2’s end of life and PHP2Shell

WordPress 7.0 shipped on May 20, 2026, a few weeks behind schedule, with a redesigned dashboard, a command palette, new blocks and an AI Client built into core that lets WordPress talk to generative AI models. Real-time collaboration, billed as the headline feature, was pulled on May 8 because it wasn’t considered stable enough. Version 7.0 also dropped PHP 7.2 and 7.3: the minimum is now PHP 7.4.

WordPress 7.1 followed on August 19, and 7.2 is scheduled for December 8. In July, 7.0.2 fixed two vulnerabilities, one of them critical, and WordPress.org forced automatic updates on affected sites.

Plugins: where nearly all the vulnerabilities live

According to Patchstack’s annual report, 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025, up 42% from 2024: 91% in plugins, 9% in themes, and just 6 low-priority issues in core. On top of that, 46% had no fix available when they were disclosed. Hence the monthly cleanup: remove plugins you don’t use, replace abandoned ones, and let the firewall block what a patch doesn’t cover yet.

PHP2Shell, in October

On October 21, 2026, the PHP team shipped emergency fixes for two critical flaws (CVE-2026-109618 and CVE-2026-109619, rated 9.2 under CVSS v4.0) that could allow unauthenticated remote code execution, with no complete mitigation other than updating. PHP 8.1 and older no longer get updates from the PHP project. We explained how we checked our clients’ sites one by one.

A hacked site: what it costs, and what Law 25 requires

No need to be alarmist: plenty of neglected sites run for months without trouble. But according to Statistics Canada, about 1 in 6 (16%) Canadian businesses were impacted by cyber security incidents in 2023, and recovery spending doubled from 2021 to $1.2 billion. For a website, that looks like injected spam pages, phishing emails sent from your hosting account, or a warning in Google’s search results that sends visitors elsewhere.

The confidentiality incident

Since September 22, 2022, Quebec’s Act respecting the protection of personal information in the private sector, as amended by Law 25, has covered what it calls a “confidentiality incident”: among other things, access to personal information not authorized by law, or any other breach of its protection. A hacker getting into a site that stores quote requests, bookings or customer accounts fits that definition.

  • Act: the business must take reasonable measures to reduce the risk of injury and prevent new incidents (s. 3.5).
  • Notify: if there’s a risk of serious injury, it must promptly notify the Commission d’accès à l’information and the people concerned (s. 3.5).
  • Record: every incident goes into the register, serious or not (s. 3.8), and the regulation requires keeping that information for at least five years.

Well-run maintenance helps on all three fronts: lower risk, faster detection and a clear record of what happened. The Commission also published a guide in January 2026 to help businesses prevent these incidents.

Hosting and backups: know where your data lives

Before entrusting a provider outside Quebec with keeping personal information, a business must conduct a privacy impact assessment and sign a written agreement (s. 17). A website’s database and backups are sometimes stored in another country. Ask where, and have the person in charge of personal information protection at your company sign off on the setup.

Do it yourself or hire an agency: questions to ask

You can maintain your own site: it takes time every month, a staging copy, offsite backups and discipline. For a simple brochure site, that’s doable; with an online store, it gets heavy fast. If you’re shopping for a provider, ask:

  • Which updates do you run, how often, and do you check the site afterward?
  • Where are the site and its backups hosted, and when did you last test a restore?
  • Which PHP version is my site on, and what’s the plan if it’s PHP 8.2?
  • If the site gets hacked, is cleanup included, and will you help me document the incident?
  • Who holds the domain and hosting credentials, and how do I get them back if I switch providers?

If your site is so old that every update feels like a gamble, starting over on a clean build often takes less effort than patching.

Our take

At HDKN, an agency with a presence in Montreal and Mulhouse, maintenance isn’t a side service to web design: it’s the core of what we do. A site that goes live in 1 to 2 weeks is just the starting point. Every client gets a dedicated webmaster who knows their site and handles everything from the PHP version to a new services page. During PHP2Shell, our clients had nothing to do: checking was our job.

We don’t publish prices, because a brochure site and an online store don’t need the same things: plans are quoted after a free assessment of your site. You’ll find what’s included on our website maintenance page, and to talk about yours, get in touch.

Sources

Abstract illustration of glowing gears next to a monitoring dashboard with completed checkmarks and an uptime curve

More News