Who Changed It/Guides

WordPress Built-In Logs: What debug.log, Access Logs and Revisions Tell You

WordPress has no activity log, but it leaves traces in a dozen places. Here is where each one is, how to read it, and the questions it can answer. Just as usefully: the questions none of them can.

The short version
  • debug.log records PHP errors, not what users did.
  • The server access log shows every request and its IP address, but not which WordPress user made it or what a form submission contained.
  • Revisions are the only built-in record that names who changed something, and they cover post content only.
  • Nothing built in records who changed a setting, a plugin, a theme or a user role.

debug.log: errors, not actions

Switch it on in wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );      // writes to wp-content/debug.log
define( 'WP_DEBUG_DISPLAY', false ); // keep errors off the page

It records PHP errors, warnings, notices and deprecations, with the file and line that raised them. That makes it the right tool for "the site shows a white screen" or "this plugin stopped working after the update".

It records nothing about people. No sign-ins, no edits, no settings changes. It can still help with a "who changed it" question indirectly: the moment a new error first appears is often the moment something was updated or reconfigured.

Two cautions. The default location is inside the web root, where it may be downloadable by anyone who guesses the address; give WP_DEBUG_LOG a path outside the web root instead of true. And turn debugging off again on a production site, because the file grows without limit.

The server access log: every request, no names

Your web server writes one line per request. It is in your hosting panel, or on your own server under a path such as /var/log/nginx/ or /var/log/apache2/.

203.0.113.7 - - [20/Nov/2026:03:12:44 +0000] "POST /wp-admin/options.php HTTP/1.1" 302 0 "https://example.com/wp-admin/options-general.php" "Mozilla/5.0 ..."

That line says an address sent a form to the general settings page at 03:12 and was redirected, which is what a successful save looks like. It does not say which user, or which setting, or what the old value was. Form contents are not logged.

Useful patterns to search for:

The limit is retention. Many shared hosts keep a few days, some only 24 hours. If you think you will need the logs, download them now.

The PHP and server error logs

Separate from debug.log, and present even when WordPress debugging is off. They catch fatal errors, memory exhaustion and timeouts, and on some hosts the output of security modules that blocked a request. Read them for crashes and for requests that were denied.

Revisions: the one place WordPress names a person

For posts, pages and any post type with revision support, WordPress stores each saved version with its author and time. Open the editor and choose Revisions to compare two versions side by side.

The limits matter. Revisions cover title, content and excerpt. They do not cover the featured image, categories, custom fields, SEO settings, the slug or the publish status. Page builders that keep their layout in custom fields may show a revision in which nothing visible changed. Revisions can be capped or disabled with WP_POST_REVISIONS, and optimisation plugins often delete them.

The quieter traces in the database

Email as an accidental log

WordPress emails the site's admin address when automatic updates run, when the admin email address is changed, when a user resets their password, when a new user registers, and when a fatal error triggers recovery mode. If those go to a mailbox someone keeps, they are a dated record. If they go to a former developer's address, fix that today; it is also where password reset links are sent.

Plugin-specific logs worth knowing

What each source can answer

QuestionBuilt-in answer
Why is the site throwing an error?debug.log and the PHP error log.
Who edited this post?Revisions, for title, content and excerpt.
Was there a login attack?Access log, for as long as the host keeps it.
Who is logged in right now?Session tokens.
Who logged in last month?Nothing. Access logs show addresses, not accounts, and have usually rotated.
Who deactivated that plugin?Nothing.
Who changed that setting, and from what?Nothing.
Who made that account an administrator?Nothing.

Filling the gap

The bottom half of that table is the reason activity log plugins exist. They hook into WordPress and write down administrative changes as they happen, with the account, the address and usually the old and new values. There are several good ones, and they are compared here. This site's own, Who Changed It, is free and additionally grades each event and chains its records so deletions are detectable.

Whichever you choose, the one rule is that it has to be installed before the thing you want to know about happens. None of them can reconstruct the past.