
Your Drupal site works: pages load, editors publish. Yet a site that “works” can be poorly maintained, and it often only shows at the worst moment: an exploited vulnerability, an update that can’t be applied, a site that goes down during a traffic peak.
Good news: most warning signs can be checked in a few minutes, from the administration interface, without being a developer. All you need is an administrator account.
1. Pending security updates
Where to look: Reports → Available updates (/admin/reports/updates).
Drupal compares the installed versions with the latest releases. Lines in red flag security updates: known, public vulnerabilities that bots often exploit within days of the announcement.
- ✅ Good sign: no red lines, or updates released only a few days ago.
- 🚩 Warning sign: security fixes pending for weeks or months.
If this page is empty or says the data was never fetched, that is already a signal: the update status module is disabled, or cron is not running (see point 4).
On the technical side, the same check is done with drush pm:security or composer audit.
2. An end-of-life Drupal or PHP version
Where to look: Reports → Status report (/admin/reports/status), at the top of the page.
The status report shows the Drupal and PHP versions. An end-of-life version no longer receives security fixes, however serious the rest of the maintenance is.
-
Drupal 7 has been unsupported since 5 January 2025, Drupal 9 since November 2023.
-
Drupal 10 will in turn reach end of support after Drupal 12 is released: now is the time to plan ahead.
-
On the PHP side, each version is only supported for a few years: Drupal 11 requires at least PHP 8.3.
-
🚩 Warning sign: an unsupported Drupal or PHP version, with no migration plan.
3. Errors in the status report
Same page: Reports → Status report.
Drupal lists its own problems there, as errors (red) and warnings (yellow). The most common ones on a poorly maintained site:
-
pending database updates: code was updated, but not the database;
-
missing security settings, such as trusted host patterns;
-
file system permission problems;
-
missing or incompatible modules.
-
🚩 Warning sign: red errors that have been there for a long time, apparently unnoticed.
4. Cron is not running
Same page: the Cron line shows when it last ran.
Cron runs Drupal’s background tasks: checking for updates, indexing search, processing queues, cleaning up temporary data. If it doesn’t run, these tasks pile up silently.
- ✅ Good sign: a run less than an hour ago (or at the planned frequency).
- 🚩 Warning sign: the last run was several days ago.
5. Logs full of errors
Where to look: Reports → Recent log messages (/admin/reports/dblog).
Filter on the php type and the Error or Critical severity. A few isolated messages are normal. Hundreds of identical errors, repeating every day, show that a problem is known… and ignored.
- 🚩 Warning sign: PHP errors in a loop, or thousands of “page not found” (404) hits that were never redirected.
On some sites, logs are sent to an external tool (syslog, New Relic, Sentry…) and this page is empty. In that case, ask your provider where to look: if they don’t know, that is a signal in itself.
6. Development settings in production
Where to look:
-
Configuration → Development → Logging and errors (
/admin/config/development/logging): “Error messages to display” must be set to None in production. Otherwise, visitors may see technical messages that reveal information about the server. -
Configuration → Development → Performance (
/admin/config/development/performance): CSS and JavaScript aggregation must be enabled, and the cache lifetime must not be set to “no caching”. -
Extend (
/admin/modules): development modules such as Devel or Webprofiler should never be enabled in production. -
🚩 Warning sign: a production site configured like a development environment. It is both a performance and a security problem.
7. Too many administrators, or shared accounts
Where to look: People (/admin/people), filtered on the Administrator role.
- 🚩 Warning signs:
- generic administrator accounts (“admin”, “agency”, “webmaster”) used by several people;
- accounts of former providers or former employees still active;
- far more administrators than needed.
Every administrator account is a way in. Named accounts and a limited number of administrators are the baseline.
The checklist at a glance
| # | Check | Where | Warning sign |
|---|---|---|---|
| 1 | Security updates | /admin/reports/updates |
Old red lines |
| 2 | Drupal and PHP versions | /admin/reports/status |
End-of-life version |
| 3 | Status report | /admin/reports/status |
Persistent red errors |
| 4 | Cron | /admin/reports/status |
Last run several days ago |
| 5 | Logs | /admin/reports/dblog |
PHP errors in a loop |
| 6 | Production settings | /admin/config/development/… |
Errors displayed, caching off, Devel enabled |
| 7 | Administrator accounts | /admin/people |
Shared or stale accounts |
What next?
If you ticked one or two warning signs, don’t panic: they are often quick fixes. From three or four, the problem usually runs deeper. Maintenance is reactive rather than preventive, and it is time to talk to your provider, or to consider an audit.
These checks don’t replace a full audit (code quality, performance, architecture, backups), but they give a reliable picture of your site’s health in a quarter of an hour.
Want a full diagnosis of your Drupal site? I offer performance and security audits, and maintenance contracts. And if you are thinking of switching providers, here is the checklist for taking over a Drupal site.
