A public site receives requests every day from visitors that are just looking for something. Most of them ask for files that do not exist and end in a 404. Without a habit of reading the log, though, the one line that deserves attention is easy to miss among them. This article describes how to look at a WordPress access log in a read-only way, centered on separating routine probing from what to confirm. Reading logs does not make a site safe. It gives you more clues to notice things.
What an access log records
A web server records each request as a line. In the common "combined" format, a line looks roughly like this:
client - - [time] "METHOD path protocol" status bytes "referrer" "user-agent"
Enter fullscreen mode
Exit fullscreen mode
Note: The status is the HTTP response code. 200 means the server returned the content; 404 means nothing was found. See the HTTP status code article for more.
Where logs live and how you download them depends on your hosting provider, so check its documentation first.…