ViewMend Site Tracker

ViewMend Site Tracker connects confirmed WordPress changes to the ViewMend website change monitoring workflow. It records events locally and delivers compact metadata through a durable background queue, so normal WordPress requests do not wait for the external service. ViewMend handles the resource-intensive work on its own infrastructure: running audits, capturing screenshots, comparing pages, and storing monitoring reports and evidence. The WordPress plugin sends compact change events and brings site health, performance statistics, and findings into your admin dashboard. This keeps heavy audit processing and report storage off your WordPress hosting. Use this WordPress connector to add publication, plugin, theme, WordPress core, and WP Rocket cache context to tracked website changes. When WordPress can identify the affected public page, the event includes its exact URL. ViewMend may match already tracked pages and queue a check when auto-check, page scope, credits, and queue state allow. Timeline events and completed ViewMend checks help administrators investigate what happened around a release or content update. This plugin is an event connector, not a standalone crawler, rank tracker, backup tool, or replacement for ViewMend's page comparison and website change monitoring service. 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. When the ViewMend integration permits it, selected tracked pages can be checked and the completed evidence reviewed in ViewMend.

For the wider release-verification workflow, see post-deployment website monitoring. Native WordPress controls and durable delivery The settings area separates Overview, Connection, Event rules, and Activity. Overview reads project health, findings, significant content changes, resource impact, and selected-page performance from ViewMend. It does not invent sample values when no completed check is available. Selecting a resource type loads the exact stored request URLs for that check without exposing the API token to browser JavaScript. Each event category explains what is reported, what is excluded, what happens when it is disabled, and which exact actions can be selected. For example, plugin events can be limited to completed updates only. ViewMend owns server-side event deduplication, tracked-page selection, queue ordering, credit checks, Tracker checks, Timeline markers, and before/after comparisons. This plugin does not reproduce those services inside WordPress. The API token is stored separately with autoload disabled and is never displayed after saving. The plugin does not send post bodies, customer/order data, usernames, emails, cookies, IP addresses, or arbitrary settings. ViewMend Site Tracker is a service connector. A ViewMend account and an existing Site Tracker integration are required before events can be delivered. See the External service section for exactly when the plugin contacts ViewMend and which data is sent.

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.

1.1.0

• Added a ViewMend website monitoring dashboard with project health, tracked pages, findings, issue trends, and selected-page insights.
• Added searchable findings, severity filters, grouped duplicate issues, interactive performance history, and stored resource request details.
• Refreshed Overview, Connection, Event rules, and Activity with full-width responsive layouts, ViewMend branding, and corrected button icons and checkbox alignment.
• Simplified connection setup with a guide and Integration ID/API token fields, while keeping the saved token hidden and showing current authentication errors clearly.
• Improved Activity with event and URL search, status filters, pagination, exact affected URLs, and clearer delivery outcomes.
• Improved unsaved-change feedback, repeat-submit protection, dashboard cache handling, and the display of unavailable or partial results.
• Validated and bounded API responses, protected cached data from reflected credentials, and prevented invalid acknowledgements from marking events as delivered.
• Recognized ViewMend's server event IDs while preserving the original WordPress event ID for retries and duplicate deliveries.
• Paused queued deliveries without consuming retries when credentials are removed, and excluded failed or skipped updates and unconfirmed deletions from automatic events.
• Added five updated screenshots covering the dashboard, connection, event rules, activity, performance, and resources.

1.0.0

• Initial production release with durable delivery, recovery, observability, security controls, lifecycle handling, documented event adapters, external-service disclosure, and WordPress Privacy Policy Guide content.