Content Revalidation Tracker – WordPress Plugin
Content Revalidation Tracker (version 2.1.0) is a WordPress plugin developed by Dropndot Solutions that connects content changes in WordPress with page revalidation on a headless frontend. It helps developers, agencies, and content teams keep their frontend content current through automatic requests to a configured revalidation endpoint.
The plugin supports Next.js on-demand ISR, Nuxt, Astro, Gatsby, and other frontends with a compatible endpoint. Its tabbed dashboard brings connection settings, URL mapping, activity monitoring, and system information together, giving teams a practical way to configure and monitor revalidation from WordPress.
WordPress Plugin Link: https://wordpress.org/plugins/content-revalidation-tracker/
INSTALLATION PROCESS
Installation
- In your WordPress dashboard, go to Plugins → Add New, search for Content Revalidation Tracker, and click Install Now → Activate. For manual installation, upload the extracted content-revalidation-tracker folder to /wp-content/plugins/ and activate it from the Plugins list.
- Open Settings → Content Revalidation.
- On the Connection tab, enter your Frontend Domain, such as https://example.com, and a Secret Key. Use Generate to create a strong secret, store the same value on your frontend as the server-only environment variable REVALIDATE_SECRET, and click Save Settings.
- Add an /api/revalidate endpoint to your frontend. It must accept POST requests, validate the X-Revalidate-Secret header, and refresh the route supplied in the path query parameter. A Next.js App Router example is available in the plugin’s WordPress.org description.
- If your frontend uses different routes from WordPress, open URL Mapping, configure the appropriate prefixes, and save each relevant section.
- Return to Connection, enter a valid frontend path in the test field, and click Test Path to confirm that your endpoint accepts the request.
Configuration
Overview – Check Revalidation Status at a Glance

Open Settings → Content Revalidation → Overview to review the connection status, last revalidation, success rate across recent logged requests, and pending retries.
The setup checklist shows whether you’ve configured a frontend domain, shared secret, and successful request. A How it works panel explains the request flow, while Recent activity highlights the latest paths and their results. Use Open connection settings to adjust the connection or View all to inspect the activity log.
Connection – Configure and Test Your Frontend Endpoint

In the Connection tab, set the frontend domain and shared secret used by your revalidation endpoint. The secret is masked, with controls to show, generate, or copy it. Keep the frontend value in a server-only environment variable such as REVALIDATE_SECRET; do not use a NEXT_PUBLIC_ variable.
Choose Header only, the recommended authentication method, to send the secret in the X-Revalidate-Secret header. Header + legacy query parameter is available for older integrations and is marked as deprecated. Keep SSL Verification enabled for production and click Save Settings after making changes.
Under Test connection, enter a path and click Test Path to send a real request. The Example API Calls panel shows the request format with the secret masked.
URL Mapping – Match WordPress Content to Frontend Routes

Use URL Mapping when your frontend routes differ from WordPress permalinks. Configure prefixes for posts, pages, and public custom post types, then review the resulting path preview before clicking Update Prefixes.
For example, a WordPress portfolio item at /portfolios/acme-redesign/ can target /portfolio/acme-redesign/ on the frontend by setting its prefix to /portfolio/.
The Taxonomy Prefixes section provides separate mappings for categories, tags, and custom taxonomies. A category prefix of /blog/category/ produces a route such as /blog/category/announcement/. Save these changes with Update Taxonomy Prefixes.
Use Author Archive Prefix for a different frontend author route. Leaving it empty preserves /author/[slug]/. Click Update Author Prefix to save.
Activity – Inspect Requests and Troubleshoot Failures

Open Activity to see when requests were made, which content triggered them, the requested paths, and the results returned by the frontend. Each entry includes a timestamp and response details to help investigate errors.
Switch between All, Success, Failed, and Retrying, or search by path, content type, or message. This helps teams locate a specific request and distinguish successful updates from requests that need attention.
Choose how many entries to retain using Number of entries to store, then click Update Limit. Use Clear log when you want to remove the recorded activity.
System – Review the Active Configuration

The System tab displays the installed plugin version, configured endpoint, request mode, and security status. It also lists the public post types and taxonomies currently being tracked.
Developers can use the content_revalidation_tracker_allowed_post_types and content_revalidation_tracker_allowed_taxonomies filters to limit tracking. Reviewing this screen helps confirm which content types are included and whether header authentication and SSL verification are enabled.
Automatic Revalidation – Handle Content Changes and Bulk Updates
The plugin covers publishing, updates, unpublishing, and supported deletion events. When a slug changes, it targets both the previous and new URLs. Requests run after the editor response finishes, and eligible temporary failures are retried through WP-Cron.
Bulk edits, imports, and WP-CLI changes use parallel processing, with 10 requests at a time by default and a retry queue holding up to 5,000 paths. Developers can adjust timeouts, concurrency, and queue limits through filters. Background retries require working WP-Cron scheduling.
The stack behind the build.
A pragmatic set of tools chosen for speed, maintainability and long-term reliability.
WordPress PLUGIN STRATEGY
Content Revalidation Tracker gives teams a way to connect editorial changes with frontend updates and inspect the outcome from WordPress. A publishing team can map its articles and category archives to blog routes, while an agency can configure separate prefixes for portfolio items, careers, and team profiles.
The workflow combines automatic requests with visible results. Editors can continue managing content in WordPress, and developers can use connection tests, activity details, and system information to investigate integration issues. This makes revalidation easier to manage across headless projects with different content structures and frontend routes.
Have a project in mind?
Tell us about your goals and we'll come back within one business day with a plan, a team, and a realistic timeline.
