Title: ViewMend Site Tracker
Author: Oleksandr
Published: <strong>August 21, 2026</strong>
Last modified: September 26, 2026

---

Search plugins

![](https://ps.w.org/viewmend-site-tracker/assets/banner-772x250.png?rev=3682291)

![](https://ps.w.org/viewmend-site-tracker/assets/icon-256x256.png?rev=3658534)

# ViewMend Site Tracker

 By [Oleksandr](https://profiles.wordpress.org/phpner/)

[Download](https://downloads.wordpress.org/plugin/viewmend-site-tracker.1.1.1.zip)

 * [Details](https://li.wordpress.org/plugins/viewmend-site-tracker/#description)
 * [Reviews](https://li.wordpress.org/plugins/viewmend-site-tracker/#reviews)
 *  [Installation](https://li.wordpress.org/plugins/viewmend-site-tracker/#installation)
 * [Development](https://li.wordpress.org/plugins/viewmend-site-tracker/#developers)

 [Support](https://wordpress.org/support/plugin/viewmend-site-tracker/)

## Description

ViewMend Site Tracker connects WordPress to [ViewMend website change monitoring](https://viewmend.com/site-tracker).
It records content updates, plugin and theme changes, core updates, and supported
cache purges, then sends them to ViewMend in the background.

ViewMend runs website checks, captures screenshots, compares pages, and stores reports
on its own servers. The plugin displays those findings and performance results in
WordPress administration.

Events include the affected public page URL when WordPress can identify it. ViewMend
can match that URL to a tracked page and queue a check, depending on your integration
settings, credits, and existing queued checks.

Use Timeline events alongside completed checks to investigate changes after a release
or content update. A ViewMend account and Site Tracker integration are required.

#### Supported WordPress changes

 * Public posts, pages, and products when they are published, meaningfully updated,
   or permanently deleted.
 * Plugin installation, activation, deactivation, update, and deletion.
 * Theme installation, activation, update, and deletion.
 * Completed WordPress core updates.
 * Confirmed full-domain and exact-URL WP Rocket cache purges.
 * An explicit administrator connection test.

Autosaves, revisions, drafts, trash moves, comments, users, orders, customer records,
media churn, and arbitrary option changes do not create events.

#### How WordPress website change monitoring works

 1. WordPress confirms an enabled content, plugin, theme, core, or supported cache 
    action.
 2. The plugin creates one stable event ID and stores the compact event in its local
    queue.
 3. A background worker delivers the event to ViewMend without delaying the originating
    WordPress request.
 4. ViewMend records the Timeline context and returns delivery, matched-page, and queue
    status.
 5. If automatic checks are enabled and the page is eligible, ViewMend queues a check.
    Results appear in ViewMend and the WordPress Overview.

#### Native WordPress controls and durable delivery

The plugin has four sections: Overview, Connection, Event rules, and Activity. Overview
displays findings, content changes, resources, and selected-page performance from
completed ViewMend checks. Resource details include the stored request URLs for 
the selected check.

Event rules let you choose which actions to report. For example, you can report 
plugin updates while leaving activation and deactivation events off.

Activity shows delivery status, retries, and the response received from ViewMend.
Website checks and page comparisons run in ViewMend.

### External service

The plugin connects to [ViewMend Site Tracker](https://viewmend.com/site-tracker)
after an administrator saves an Integration ID and API token. It sends queued events
for enabled WordPress actions and connection tests. It reads dashboard results when
an administrator opens or refreshes Overview, and resource details when a resource
type is selected.

Event requests contain an event ID, type, time, change title and description, public
site URL, environment, affected public page URLs, changed-field categories, and 
WordPress/plugin/theme versions or public object IDs. Public-content events may 
include an administrative edit URL. The API token is sent in the Authorization header.

ViewMend uses this data to record events, match tracked pages and, when eligible,
queue website checks. It returns delivery status and counts of matched pages and
queued checks. Dashboard responses contain health counts, findings, content changes,
page performance, and resource URLs, MIME types, status codes, sizes and durations
from completed checks. They exclude request/response headers, cookies, authorization
values and remote IP addresses. Dashboard responses are cached for up to five minutes.
An accepted event does not guarantee a completed check.

The plugin does not send post bodies, excerpts, protected content, usernames, email
addresses, customer or order data, cookies, IP addresses or arbitrary settings. 
Use of the service is subject to the [ViewMend Terms of Service](https://viewmend.com/terms-of-service)
and [Privacy Policy](https://viewmend.com/privacy-policy).

### Privacy

Only public change metadata is sent; the full field list and exclusions are in External
service.

The local queue stores event payloads, delivery state, attempts, redacted errors,
HTTP status and ViewMend response details. Completed and failed history is limited
to 250 entries. The token is stored separately with autoload disabled and is never
displayed, written to queue rows or sent to browser JavaScript. Dashboard results
expire from the cache after five minutes.

## Screenshots

[⌊Overview shows selected-page health, tracked pages, critical findings, searchable
issues, and issue trends.⌉⌊Overview shows selected-page health, tracked pages, critical
findings, searchable issues, and issue trends.⌉[

Overview shows selected-page health, tracked pages, critical findings, searchable
issues, and issue trends.

[⌊Connection verifies the ViewMend integration and keeps the saved API token hidden
while making settings easy to update.⌉⌊Connection verifies the ViewMend integration
and keeps the saved API token hidden while making settings easy to update.⌉[

Connection verifies the ViewMend integration and keeps the saved API token hidden
while making settings easy to update.

[⌊Event rules let administrators choose the exact WordPress actions to report, including
publication, meaningful updates, and permanent deletion.⌉⌊Event rules let administrators
choose the exact WordPress actions to report, including publication, meaningful 
updates, and permanent deletion.⌉[

Event rules let administrators choose the exact WordPress actions to report, including
publication, meaningful updates, and permanent deletion.

[⌊Activity shows confirmed deliveries with exact affected URLs, matched pages, and
the response returned by ViewMend.⌉⌊Activity shows confirmed deliveries with exact
affected URLs, matched pages, and the response returned by ViewMend.⌉[

Activity shows confirmed deliveries with exact affected URLs, matched pages, and
the response returned by ViewMend.

[⌊Page insights combine performance history, Core Web Vitals, transferred resources,
resource changes, and local event delivery health.⌉⌊Page insights combine performance
history, Core Web Vitals, transferred resources, resource changes, and local event
delivery health.⌉[

Page insights combine performance history, Core Web Vitals, transferred resources,
resource changes, and local event delivery health.

## Installation

 1. Upload and activate the plugin.
 2. Open ViewMend from the main WordPress administration menu.
 3. Follow the setup-guide link on the Connection screen and create WordPress credentials
    in the target ViewMend Tracker project.
 4. Copy the Integration ID and one-time API token into WordPress > ViewMend > Connection.
 5. Save and test the connection. The test creates a real ViewMend event.
 6. Open Event rules and choose the confirmed WordPress operations that should create
    events.
 7. Open Activity, confirm the local test row reaches Delivered, and inspect the queue
    state returned by ViewMend.

WordPress cron must run for background delivery. The plugin schedules near-term 
work and a recurring five-minute recovery event.

Multisite network activation is not supported. Activate and configure the plugin
separately for each required site.

## FAQ

### Is this a standalone WordPress website monitoring plugin?

No. It connects WordPress events to ViewMend and displays ViewMend results. A ViewMend
account and Site Tracker integration are required.

### Can it track WordPress page changes?

Yes, for public posts, pages and products. Events include the affected permalink.
ViewMend can check an already tracked page when your integration settings and available
credits permit it. Drafts, autosaves, revisions, trash moves and protected content
are excluded.

### Which site changes can it report?

Public content changes, plugin and theme operations, successful core updates, WP
Rocket purges and connection tests. Choose individual actions in Event rules.

### Do website checks run on my WordPress server?

No. ViewMend runs checks, captures screenshots, compares pages and stores reports
on its own servers.

WordPress records and delivers events and caches results. ViewMend checks request
your public pages and their resources.

### Does the plugin contact an external service?

Yes, after you configure the ViewMend connection. See External service for the request
triggers, data fields, terms and privacy policy.

### Which cache plugins are supported?

WP Rocket. Domain purges apply site-wide. URL-specific purges include only public
posts, pages, products and the home page that WordPress can verify locally. Private,
password-protected and unknown routes are excluded.

### What happens when ViewMend is unavailable?

Delivery retries network failures, HTTP 429 and server errors up to six times, with
increasing delays. Retry-After is respected up to six hours. Manual retries keep
the original event ID.

### What happens on deactivation or uninstall?

Deactivation removes cron schedules and preserves all data. Uninstall also preserves
data by default. You can enable deletion of ViewMend settings, the token, and local
delivery history in Connection settings. On multisite, this choice is respected 
separately for each site.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“ViewMend Site Tracker” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ Oleksandr ](https://profiles.wordpress.org/phpner/)

[Translate “ViewMend Site Tracker” into your language.](https://translate.wordpress.org/projects/wp-plugins/viewmend-site-tracker)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/viewmend-site-tracker/),
check out the [SVN repository](https://plugins.svn.wordpress.org/viewmend-site-tracker/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/viewmend-site-tracker/)
by [RSS](https://plugins.trac.wordpress.org/log/viewmend-site-tracker/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.1.1

 * Prevented private, password-protected and unknown page URLs from being included
   in WP Rocket cache events.
 * Preserved encoded URLs and separate content edits, and added events for permalink
   changes and removal of password protection.
 * Fixed queue, credential and event isolation when switching between multisite 
   sites, and respected each site’s uninstall preference.
 * Preserved retried events during history cleanup and fixed scheduling of earlier
   deliveries.
 * Prevented failed WordPress core updates from being reported as successful.
 * Fixed validation of collapsed settings, clarified connection status and selected-
   page health, and kept isolated chart values visible.

#### 1.1.0

 * Added the ViewMend dashboard, findings, page performance, resource details and
   activity search.
 * Updated connection setup, event rules and responsive layouts.
 * Improved credential handling, delivery acknowledgements, retries and recovery.

#### 1.0.0

 * Initial release with WordPress events, background delivery, WP-CLI diagnostics
   and privacy controls.

## Meta

 *  Version **1.1.1**
 *  Last updated **4 days ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.4 or higher **
 *  Tested up to **7.1.2**
 *  PHP version ** 7.4 or higher **
 *  Language
 * [English (US)](https://wordpress.org/plugins/viewmend-site-tracker/)
 * Tags
 * [change tracking](https://li.wordpress.org/plugins/tags/change-tracking/)[content updates](https://li.wordpress.org/plugins/tags/content-updates/)
   [deployment](https://li.wordpress.org/plugins/tags/deployment/)[website monitoring](https://li.wordpress.org/plugins/tags/website-monitoring/)
 *  [Advanced View](https://li.wordpress.org/plugins/viewmend-site-tracker/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/viewmend-site-tracker/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/viewmend-site-tracker/reviews/)

## Contributors

 *   [ Oleksandr ](https://profiles.wordpress.org/phpner/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/viewmend-site-tracker/)