Security · Guide
How to Log User Activity in WordPress
Short answer
WordPress core does not keep a full record of who changed what on your site, so you need an activity log plugin. Install WP Activity Log or Simple History, activate it, and it starts recording logins, content edits, plugin and theme changes, and settings changes, each with the user, time, and IP address. You can then search and filter that log from your dashboard whenever you need to find out what happened.
Key takeaways
- WordPress core has no built-in activity log, so a plugin is required to record user actions.
- WP Activity Log records the user, role, time to the millisecond, and IP address for each event.
- Simple History starts logging at once, needs no setup, and sends a weekly email summary each Monday.
- Failed logins in the log are often the first sign of a brute-force attack on your site.
- Limit who can view the log to administrators, since it can expose IP addresses and email changes.
What is a WordPress activity log?
A WordPress activity log is a dated record of who did what on your site, with the time, the user, and the IP address for each change.
Each entry answers four questions: who made the change, what changed, when it happened, and where the request came from. WP Activity Log records the date and time to the millisecond, plus the user, their role, and the source IP address (WP Activity Log).
Logs cover content edits, user changes, plugin and theme changes, settings changes, and file changes. That range makes the log useful for security checks and for sorting out who changed a setting. If a page suddenly looks different, the log shows the edit and the account behind it.
Does WordPress keep an activity log by itself?
No, WordPress core does not keep a full record of user actions, so you need a plugin to log activity.
WordPress does keep post revisions and a list of users, but neither shows who changed a setting or installed a plugin. WordPress defines six roles, from Subscriber to Super Admin, and each role can do different things (Roles and Capabilities).
WordPress does have a debug log for PHP errors, but it records code errors, not user actions. Setting WP_DEBUG_LOG to true writes errors to a debug.log file in your wp-content folder (Debugging in WordPress).
That gap matters on any site with more than one user. Without a log, you cannot tell whether a change came from an editor, a developer, or an attacker who gained access. A logging plugin fills that gap from the moment you activate it.
Which activity log plugin should you choose?
Choose WP Activity Log for the widest event coverage, or Simple History for a free log that needs no setup.
WP Activity Log holds a 4.7 out of 5 rating from 493 reviews on WordPress.org, and its page was updated on 5 November 2026 (WP Activity Log).
Simple History is trusted by more than 300,000 sites, holds a 4.9-star rating from over 450 five-star reviews, and has been free for more than 10 years (Simple History).
| Plugin | Free version | Standout strength |
|---|---|---|
| WP Activity Log | Yes | Widest event coverage, including WooCommerce and third-party plugins |
| Simple History | Yes | No setup, before-and-after diffs, weekly email reports |
| Activity Log | Yes | Lightweight log with CSV export and privacy tools |
Premium plans add alerts and reports. WP Activity Log Premium starts at $139 per year for one site, and Enterprise starts at $189 per year (WP Activity Log pricing).
Pick the plugin that matches your site. A single-author blog is fine with Simple History, while a membership site or store with many staff accounts gains more from WP Activity Log. Either way, install only one logging plugin, since two logs of the same events waste database space.
How do you install and set up WP Activity Log?
Install WP Activity Log from Plugins > Add New, activate it, and it starts logging right away.
- Go to “Plugins > Add New” in your WordPress dashboard.
- Search for “WP Activity Log” and click “Install Now”, then “Activate”.
- Allow or skip diagnostic tracking when asked.
- Open the “WP Activity Log” menu to view the log.
Next, set who can view the log and how long entries are kept. The plugin lets you limit log access by user or role, and it offers configurable retention policies (WP Activity Log).
Turn on only the events you need. The plugin can log hundreds of event types, from post edits to database table changes, so disabling noisy events keeps the log readable. Leave login, user, plugin, theme, and settings events on, since those matter most for security.
How do you install and set up Simple History?
Install Simple History, activate it, and it starts logging at once with no setup needed.
- Go to “Plugins > Add New”, search for “Simple History”, then install and activate it.
- Open “Dashboard > Simple History” to see the log.
- Open “Settings > Simple History” to pick where the log appears and turn on weekly email reports.
The plugin even imports recent activity, so your log is not empty on day one. Each event is written in plain language, such as “Updated page About us”, with before-and-after comparisons instead of raw data (Simple History).
Simple History masks IP addresses by default, removing the last part before storing them. It also sets no cookies and loads no external fonts, which helps with privacy rules (Simple History).
What should you log on a team site?
Log logins, role changes, plugin and theme changes, settings changes, and content publishes on any team site.
- Failed logins, with the IP address, so you can spot password-guessing attacks.
- User profile and role changes, since a new administrator account is a classic sign of a hacked site.
- Plugin and theme installs, updates, and deletions, with the version and author.
- Settings changes, such as the site URL, default role, and permalink structure.
- Content publishes and deletes, with before-and-after text where the plugin supports it.
Failed logins deserve a daily glance. WP Activity Log records failed login attempts so you can spot a possible breach early (WP Activity Log).
On a store or membership site, log order and member changes too. WP Activity Log covers WooCommerce orders and products, plus MemberPress memberships and payments, in its third-party plugin support (WP Activity Log).
The stakes are high. Patchstack counted 11,334 new vulnerabilities across WordPress in 2025, up 42% on 2024, with 91% in plugins and 9% in themes (Patchstack).
How do you read the log to find a problem?
Start from the time the problem appeared, then filter the log by user, event type, or IP address.
- Note when the problem first appeared, then open the log for that time window.
- Filter by the user or IP address involved, if you know it.
- Look for settings, plugin, or role changes just before the problem started.
- Open the event to see the before-and-after values.
A changed setting is the most common cause of a sudden problem. For example, if comments stop working, check for changes to the discussion settings or a deactivated plugin. If the log shows a role change you did not make, treat the site as hacked and start recovery at once.
If the log points to a hacked account, read how to tell if your WordPress site is hacked before you change passwords or restore a backup.
How long should you keep activity logs?
Keep logs long enough to investigate problems, then delete old entries so the database stays small.
Both plugins let you control retention. WP Activity Log offers configurable retention policies (WP Activity Log). Simple History Premium adds custom retention periods, including the choice to keep logs forever (Simple History).
Match retention to your needs. A small blog can keep a few months of entries, while a store that must answer payment disputes may need a year or more. Whatever you choose, export the log before you delete old entries, and store the export outside the site database.
Logs are not a backup, so keep your backup routine separate. See how often you should back up WordPress and keep copies off the server.
How do you limit who can see the log?
Give log access only to administrators, since the log can expose IP addresses, email changes, and user activity.
WP Activity Log lets you limit who can view the log by user or role, so editors and authors never see it (WP Activity Log).
Simple History works the same way. Administrators can view all logged events, while lower roles see only what their role allows (Simple History).
Check privacy rules before you log IP addresses. Activity logs count as personal data in many regions, so read our GDPR compliance guide for WordPress before you set a long retention period.
What mistakes should you avoid?
Do not install a logging plugin and never look at it, since an unread log cannot warn you about anything.
- Logging everything with no retention limit, which grows the database until the site slows down.
- Letting every user read the log, which leaks IP addresses and admin activity.
- Ignoring failed logins, which are often the first sign of an attack.
- Treating the log as a backup, since it records changes but cannot restore deleted content.
- Installing two logging plugins at once, which doubles the database writes for the same events.
Review the log on a schedule, not only after a problem. A five-minute check each week catches odd logins and role changes while they are still easy to fix. If you find an account you do not recognise, follow our guide to recover a hacked WordPress admin account.
Frequently asked questions
Can I see who changed a WordPress setting?
Yes. Install an activity log plugin such as WP Activity Log or Simple History, then open the log and filter by settings changes. Each entry shows the user, the time, and the old and new values, so you can see exactly what changed and who changed it.
Does an activity log slow down WordPress?
A logging plugin adds a small database write for each admin action, but it does not log front-end visits by default, so visitors see no slowdown. Simple History states that most logging happens in the admin area and nothing is logged on the front end by default. Keep retention limits set so the log table stays small.
Can I export the WordPress activity log?
Yes. Activity Log exports records to CSV, and WP Activity Log Premium can generate HTML and CSV reports or mirror the log to an external database. Simple History Premium adds CSV and JSON export of filtered search results. Export the log before you delete old entries so you keep a copy.
Can I get an alert when something changes on my site?
Yes, with a paid add-on. WP Activity Log Premium sends email, SMS, and Slack notifications for important changes, and Simple History Premium alerts you by email, Slack, Discord, or Telegram. Set alerts only for high-risk events, such as role changes and plugin installs, so you are not flooded with messages.
Is an activity log enough to prove what happened on my site?
It is strong evidence, but not proof on its own. A log shows the account, time, and IP address for each change, yet an attacker with admin access could edit or delete entries. For legal or compliance needs, mirror the log to an external database or file, and keep server logs and backups as separate records.
Sources
- WP Activity Log WordPress.org
- Simple History – Track, Log, and Audit WordPress Changes WordPress.org
- Roles and Capabilities WordPress.org
- Debugging – Theme Handbook WordPress Developer Resources
- WP Activity Log Pricing Melapress
- State of WordPress Security in 2026 Patchstack
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
