We install and configure an activity log — recording who did what and when across your WordPress site (logins, content changes, plugin activity) — with a sensible retention period, giving you a genuine audit trail for troubleshooting or accountability rather than no record at all of what’s actually happened on your site.
Activity log installation & retention config
An activity log installed with sensible retention — a real record, not no record at all.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Admin access to install and configure the activity log
- Confirmation of your desired retention period
- Confirmation of which activity types matter most to you, if you want to prioritise certain events
This or something else?
| You want an activity log installed, recording user actions with an appropriate retention period | This fix covers it |
| You want security-specific event alerting, not a general activity record | Security event logging & alerting, a more focused, alert-driven version |
| You want to investigate something that already happened, without a log currently in place | Worth confirming what other records might exist, since a log installed now won’t retroactively cover past activity |
| You want error logging, not user activity logging | Error log configuration & rotation, a different kind of log entirely |
What we do
- Confirm which activity types should be logged and your desired retention
- Install and configure an appropriate activity logging solution
- Verify it correctly captures logins, content changes, and other specified activity
- Set the retention period to your specification
- Test that the log is genuinely reviewable and useful, not just accumulating unreadable data
- Document how to review the log when needed
What is included
- An activity log installed and configured for your specified activity types
- Set retention period as specified
- Verified genuine, reviewable logging of real activity
- Documentation on how to review the log
Not included
- Retroactively capturing activity that happened before this log was installed
- Security-specific alerting on logged events — a separate, related fix if you want active alerting rather than passive record-keeping
- Investigating a specific past incident, if that’s your actual underlying need — worth discussing directly what records might already exist
- Ongoing review of log content as a standing service
Questions about this fix
Will this show me what happened on my site before it was installed?
No, an activity log only records activity from the point it's installed forward — if you're trying to investigate something that already happened, we'd need to look at whatever other records (backups, existing logs) might already exist instead.
Is this the same as the security event alerting fix?
Related but distinct — this is a passive, ongoing record of activity for review when needed; the security alerting fix actively notifies someone in near-real-time when a specific, concerning event occurs, which is a different kind of monitoring.
How long should I retain activity log data?
This depends on how far back you'd realistically want to look if investigating something — a longer retention gives more history but takes more storage, which we'd balance based on your specific needs.
Who should have access to review this log?
Typically whoever has administrative responsibility for the site — we'd configure access appropriately based on who you specify should be able to review this potentially sensitive activity record.
Will this slow down my site by logging every action?
A well-configured activity log has a modest, generally unnoticeable performance impact — it's a lightweight recording process rather than something that meaningfully affects site speed.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.