Drupal audit checklist before development
š§ Listen to every article back to back
A Drupal audit is most useful before a major decision: changing providers, planning migration, preparing procurement or building new functionality on an old system.
What to check
A useful audit is more than looking at the front page. A Drupal site must be reviewed from technical, editorial and business perspectives. The Drupal update documentation (opens in a new tab) gives a baseline, but the real state appears in code and configuration.
The checklist should include:
- Drupal core and module versions;
- security update and PHP version status;
- custom modules, theme and integrations;
- content types, fields, views and unused configuration;
- forms, permissions, logs and backups;
- automated tests or a manual release test plan.
When to order an audit
An audit is especially important when someone gives a price without seeing the system. That quote may be quick, but the risk stays with the client.
WebPro audit and testing shows what should be fixed immediately and what belongs in a larger work plan. The public Drupal scanner is useful as a first pre-check, but a real decision needs access to code and administration.
Need Drupal help?
Send the website URL and a short context. We will tell you whether the sensible next step is an audit, maintenance, an upgrade or a migration.