Originally published: January 24, 2021 · Last updated: August 17, 2026
On a one-person WordPress site, you usually know who changed a post. On a multi-author, agency or client site, that becomes much harder. The useful goal is not to receive an email for every save. It is to create enough accountability that important changes can be reviewed and unexpected edits can be traced.
Start with WordPress revisions
WordPress revisions record saved versions of posts and pages. They let you compare changes and restore earlier content when necessary.
Revisions are the first place to look when the question is “what changed in this page?” They are not, however, a complete activity log for everything that happens across the site.
Decide which changes actually need alerts
Emailing an administrator every time an author fixes punctuation creates noise quickly. Define the events that matter to your workflow, such as:
- a published page being edited;
- a post changing status;
- a high-value landing page being modified;
- a new administrator or editor being created;
- SEO metadata or redirects changing;
- plugins or themes being installed or activated.
The more selective the rules are, the more likely someone will pay attention to the alerts.
Use an activity log when you need site-wide accountability
An activity-log plugin can record events beyond post content, including user sessions, settings, plugin changes and sometimes ecommerce or custom post type activity.
This is useful for teams and client sites because it creates a chronological record instead of sending every event into an inbox.
Choose a tool that clearly documents which events it records, how long logs are retained and who can access them. Avoid keeping sensitive logs indefinitely without a reason.
Use email for exceptions, not the full audit trail
If your monitoring tool supports notifications, configure email for high-priority conditions. A practical setup might notify you when a published homepage or sales page changes, while ordinary draft edits remain only in the log.
This separation makes the log useful for investigation and email useful for action.
Protect important pages with permissions
Monitoring is not a substitute for access control. Give users the lowest role that still lets them do their work. If someone only writes drafts, they may not need permission to edit published pages or install plugins.
For complex teams, document who owns key pages and who approves changes before publication.
Keep a backup before major editorial or structural work
Revisions can restore post content, but they are not a replacement for a full backup. A plugin update, theme change or database-level mistake can affect much more than one post.
Use revisions for editorial rollback and backups for site recovery.
A simple monitoring workflow
- Keep WordPress revisions enabled.
- Define which site events are genuinely important.
- Use an activity log if multiple people administer the site.
- Send email only for high-priority changes.
- Review user roles periodically.
- Keep independent backups for broader recovery.
The practical rule
Good change monitoring answers three questions: what changed, who changed it and whether someone needs to act. If every minor edit produces an alert, the system will eventually be ignored.
Official reference: WordPress revisions documentation.