Everything the platform does
Every update, backup, restore, staging action, migration, policy change, permission change and one-click login, with actor and timestamp.
Activity log
Every change, on every site, with the evidence attached
Who did what, on which site, when, and what happened as a result. Updates, restores, logins, permission changes and policy edits, all recorded automatically and exportable whenever you need them.
Included on every plan. No add-on pricing.
ActivityLive
Events today
214
across 34 sites
Actors
9
6 team, 3 automated
Retention
12 mo
configurable
Exports
Any period
CSV, JSON, API
UPYoast SEO 24.0 to 24.1
SuccessRBElementor 3.31.2 rolled back
RollbackLGJonah T. opened wp-admin
SessionPMPermission changed
Policy The problem
The question you cannot answer under pressure
A client calls to say something broke over the weekend. You need to know what changed and when, and the honest answer is usually that nobody wrote it down. WordPress itself keeps almost no history: you can see current plugin versions but not when they changed or who changed them.
Without a record you are reconstructing events from memory and file timestamps, while a client waits and forms an opinion about your professionalism.
What this looks like without a platform
- No record of when a plugin was updated or by whom
- Disputes about whether a change was authorised
- Reconstructing a weekend incident from file modification dates
- Reports written from memory rather than from a log
How it works
WordPress activity monitoring: what gets recorded
Evidence, not just an entry
An update record includes the risk score it received, the checks that ran, the before and after screenshots, and the result. A restore record includes what was restored and how long it took.
Site changes detected outside WPCentrify
If somebody activates a plugin directly in wp-admin, that appears too, so the log reflects the site rather than only your actions.
Tamper-evident
Entries are append-only and cannot be edited or deleted from the interface, including by an account owner. A log you can quietly edit is not evidence.
In practice
Using the record
Filter across the whole portfolio
Search by site, client, person, action type or date range. Answer "what happened to this site last Friday" in seconds.
Export for any period
CSV or JSON export, and the same data through the API, for compliance requests, disputes or your own analysis.
Feeds client reports automatically
The monthly report is generated from the log, which is why it is accurate rather than remembered.
Retention that matches your obligations
Retention is configurable per plan, with long-horizon retention available where a client contract or regulator requires it.
At scale
Built for a portfolio, not a single site
- Unified timeline across every connected site
- Filter by site, client, actor, action type or date
- Change evidence including screenshots attached to update records
- Append-only and tamper-evident
- CSV, JSON and API export
- Configurable retention windows
Answers
Questions about activity log
What people ask before they turn this on.
No. Entries are append-only and cannot be modified or deleted from the interface by anyone, including the account owner. That is what makes it usable as evidence.
Yes, for the significant ones: plugin and theme activation, deactivation, updates, user role changes and core updates. The log reflects the state of the site, not only actions taken through WPCentrify.
Twelve months by default, configurable to longer horizons where a client contract or regulatory obligation requires it.
Early access open
Try activity log on your own sites
Connect a site in under two minutes and see this working against something real. Free during early access.
Free during early access. Keep your data, export any time.