Skip to main content
web60

Infrastructure

WordPress Activity Log: Who Changed Your Website, and When

Ian O'Reilly··13 min read
Flat illustration of a row of overlapping sage and teal circles linked by teal lines, with a trail of deep navy dots winding across them on an off-white background

If more than one person can log in to your website, you need a record of who changed what. WordPress does not keep one for you. Most business sites run for years without it, and owners only notice the gap on the morning something has changed and nobody in the building can say how.

This is not a niche security concern. It is basic housekeeping, in the same category as knowing who holds a key to the shop. An activity log costs nothing, takes about fifteen minutes to set up, and turns a morning of guesswork into a two-minute lookup. I would want one on any business site with more than one login, and the case for it is stronger than most owners realise.

What WordPress Remembers, and What It Forgets

WordPress does keep one kind of history. Its revisions system, in the words of the WordPress.org documentation, "stores a record of each saved draft or published update" [1]. You can drag a slider, compare two versions and restore an older one. Each saved revision appears against the account that saved it.

That covers the words on your pages. It does not cover most of what actually breaks a business website:

  • a plugin switched off, such as the one that sends booking confirmations
  • a new user account created, or an existing one promoted to administrator
  • a setting changed, such as the site address or who is allowed to register
  • a menu rearranged so a page quietly drops out of the navigation
  • a login at an hour when nobody on your team is awake

Core WordPress records none of those as a history you can read. The change takes effect in production, and the evidence of who made it simply does not exist.

The consequence is practical. When your contact form stops delivering enquiries, the first operational question is always "what changed, and who changed it?" Without a log, the honest answer is a shrug. You then spend the morning testing theories instead of reading a single line that would have told you.

A Composite Case: The Delivery Price Nobody Changed

Consider a composite scenario, assembled from a pattern that appears whenever a small team shares one website. A garden centre in Roscommon takes Christmas tree delivery orders through its WordPress site from mid-November. Four people can log in: the owner, a son who handles social media, a part-time staff member who updates opening hours, and the freelancer who built the site years ago and still holds an administrator account.

One Saturday morning in late November, the phone starts ringing. Customers want to know why the delivery charge on the website is lower than the one on their confirmation. Somebody has edited the delivery page. Orders have already been taken at the wrong figure.

The owner opens the page revisions. The change was saved by an account called "admin". Three of the four people use that account. Not one of them remembers editing the page. Nobody can rule out the freelancer, or a stranger who somehow had the password. The weekend goes on apologies and corrections, and on a question that never gets answered: was this a slip, or were we hacked? What would have settled it in two minutes was not a stronger password. It was a record of which person, from which account, at what time.

Shared Logins Make Every Record Useless

This is the uncomfortable part. Any log records accounts, not people. If three staff share one login, the best activity log available will tell you that "admin" did it, which you already knew.

So the first fix is free and has nothing to do with plugins: one person, one account. WordPress lets you give each person their own login with a role that matches their job, so the person updating opening hours does not need the power to install plugins or create new users. Our guide to choosing WordPress user roles for each person on your team walks through which role suits which job.

Separate accounts also make departures clean. When a staff member moves on, you remove one account. You do not have to change a password that three other people rely on and then chase them all with the new one. Ireland's National Cyber Security Centre makes the same two points in its Cyber Vitals Checklist: confirm that old accounts have been disabled, and that external contractors hold only the minimum access they need [2].

Flat illustration of four overlapping circles in teal, deep navy and grey joined by a single teal line on a warm off-white background
One person, one account: the log can only name what it can tell apart.

The Log Is Also Your Early Warning

Accountability is half the value. The other half is spotting trouble while it is still small. Intruders who get into a WordPress site rarely announce themselves. A common pattern is to create a new administrator account, or quietly deactivate a security plugin, and return later. Without a log, the owner tends to find out when a customer complains or the site starts showing up in search results for things it never sold. With a log, the new account sits in the list with a time, a username and an IP address, the morning after it appeared.

Not every unexplained change comes from outside, either. Verizon's 2025 Data Breach Investigations Report found that roughly three in ten breaches in Europe, the Middle East and Africa originated within the organisation [3]. That figure includes honest mistakes as well as bad intent, and it shifts considerably by sector, so treat it as a direction rather than a forecast. For a small team, the inside case is usually the mundane one. Someone clicked the wrong thing and never realised. A log turns that into a short, calm conversation instead of a weekend of quiet suspicion.

The NCSC checklist puts the standard in one line: review your logging and monitoring tools and ensure the coverage and retention is sufficient [2]. Applied to a website, coverage means the log captures plugins, users, settings and logins, not just page edits. Retention means last month's entries are still there when you finally go looking. Logging is one layer of several, and our complete guide to WordPress security and backups shows where it sits alongside scanning, restore points and recovery planning.

Where an Activity Log Falls Short

I would rather you know the limits now than discover them during an incident. There are three.

It lives inside the thing it is watching

The widely used free plugins store their records in your WordPress database, and Simple History's listing says so plainly [4]. Anyone who gains administrator access can, in principle, delete the log along with everything else. Keeping a copy somewhere the site cannot touch is generally a paid feature: WP Activity Log places external log storage and mirroring in its paid editions [5].

It forgets on a schedule

Simple History keeps 30 days of history by default [4]. WP Activity Log defaults to three months [5]. If you notice a problem six weeks after it happened, a 30-day log has already discarded the evidence. Set retention to match how quickly you realistically spot things, not whatever the installer picked.

It is not a backup

A log can tell you that a page was changed at 09:12 by a named account. It cannot rebuild a deleted product, a broken layout or a plugin's lost settings. You still need a restore point.

It holds personal data of its own

One compliance note belongs here too. A log records usernames and IP addresses, which can count as personal data. That does not make logging a problem, but it does mean you should keep retention proportionate, mention the logging in your privacy policy, and check with your solicitor or data protection adviser if your site handles anything sensitive.

Flat illustration of a stack of teal and beige horizontal bars like ledger pages, with a deep navy circle ringed in teal at the top right, on a warm grey background
A log is a ledger, not a safety net. It tells you what happened; a backup puts it right.

The Fifteen-Minute Version

None of this needs a consultant. A sensible setup for a small team looks like this:

  • Give everyone their own account. Once each person has a named login, delete or downgrade the shared "admin" account.
  • Install one log plugin, not two. Simple History and WP Activity Log each report more than 300,000 active installations on WordPress.org [4] [5], and both record logins, plugin changes, user changes and settings in their free versions. Pick one. If your host gives you a staging environment, deploy it there first and verify nothing conflicts before pushing to production.
  • Set retention deliberately. For a team that checks the site occasionally, around three months is a reasonable starting point.
  • Verify it is recording. Change something harmless, such as a draft page title, and confirm the entry appears under your own name.
  • Read it weekly. Five minutes, looking for three things: new accounts, deactivated plugins and logins at strange hours.

That routine would have closed the garden centre's weekend mystery before the first customer rang back.

Where Your Hosting Fits In

A log tells you what happened. The infrastructure underneath decides how quickly you can put it right. A sound standard for any business site has five parts:

  • a restore point from last night that you can roll back to without raising a ticket and waiting
  • an automatic snapshot before updates and restores, so the rollback itself is never a gamble
  • a separate environment to test changes before they touch the production site
  • security scanning at the server level, which an intruder cannot switch off from inside the dashboard
  • real people you can reach when the log shows something you do not understand

Without the first of those, the fix for a page someone broke is retyping it from memory while orders keep arriving at the wrong price.

Web60 was built to meet that standard. Every site gets automatic nightly backups with one-click restore, on-demand manual backups, and safety snapshots taken automatically before updates and restores. One-click staging is included. Security hardening, fail2ban intrusion prevention and automatic malware scanning run at the server level rather than as plugins inside your dashboard, and the data stays on sovereign Irish infrastructure. All of that comes as part of Web60's managed WordPress hosting, with server-level protection built in, for €60 a year with nothing added on top.

Because it is full WordPress, the same platform that runs close to two in five of all websites according to W3Techs [6], you can install whichever activity log suits you rather than waiting for a closed builder to offer one. When the log shows something odd, the person you talk to is on an Irish-based support team, not an outsourced queue. If you are starting from scratch, the AI website builder will have a WordPress site in front of you in under a minute, with the backups and scanning already running.

When a plugin log is not enough

To be fair about scale: some businesses need more than a plugin log can give. A regulated firm whose auditors want tamper-evident records kept off the server for years is better served by enterprise managed hosts that ship every log line to a separate, centralised logging service with its own access controls. That is a genuine requirement, and those platforms handle it well. It is also a small minority of local firms. For the owner-operator with four logins and a busy Christmas, a free plugin, separate accounts and a host that keeps restore points will cover the realistic risks.

Knowing Beats Guessing

Every website with more than one login will eventually change in a way nobody expected. That part is normal. What decides whether it costs you two minutes or a weekend is whether a record exists. Give each person their own account, install one log, set the retention you actually need and glance at it once a week. The next time something on your site looks different, you will be reading an answer instead of guessing at one.

Frequently Asked Questions

Does WordPress have a built-in activity log?

Not a full one. WordPress keeps revisions of posts and pages, so you can compare and restore earlier versions of your content and see which account saved each one. It does not record plugin changes, new user accounts, role changes, settings changes or logins. For those you need an activity log plugin.

Can I see who deleted a page in WordPress?

Not reliably without an activity log. WordPress keeps deleted pages in the Trash for 30 days by default, so you can usually restore the page itself, but core WordPress does not show which account moved it there. With an activity log installed, the deletion appears with the account name and the time.

Which activity log plugin should a small business use?

Simple History and WP Activity Log are both free on WordPress.org, both have more than 300,000 active installations, and both record logins, plugin changes, user changes and settings changes in their free versions. Simple History is the lighter of the two. WP Activity Log offers more detail and paid options such as notifications and storing logs outside the site. Install one, not both.

How long should I keep website activity logs?

Long enough to cover the gap between something happening and you noticing it. Simple History keeps 30 days by default and WP Activity Log keeps three months. For a small team that only reviews the site occasionally, around three months is a sensible starting point. Keep it proportionate, because the log holds usernames and IP addresses.

Will an activity log slow down my website?

For most small sites, not noticeably. The log mostly records actions taken in the dashboard, such as edits, logins and plugin changes, so ordinary visitors browsing your pages trigger very little of it. A very long retention period on a busy site can make the log large, which is another reason to set retention deliberately rather than keeping everything forever.

Does an activity log help with GDPR?

It can support your security obligations, because it helps you spot and investigate unauthorised access. It also creates new personal data of its own, since it records usernames and IP addresses. Keep the retention period proportionate, mention the logging in your privacy policy, and check with your solicitor or data protection adviser if your site handles sensitive information.

Sources

IO
Ian O'ReillyOperations Director, Web60

Ian oversees Web60's hosting infrastructure and operations. Responsible for the uptime, security, and performance of every site on the platform, he writes about the operational reality of keeping Irish business websites fast, secure, and online around the clock.

More by Ian O'Reilly →

Ready to get your business online?

Describe your business. AI builds your website in 60 seconds.

Build My Website Free →
Buy NowTry Free
WordPress Activity Log: Who Changed Your Website? | Web60