The InspectWP WordPress Connector lets your project receive a daily health snapshot from inside your WP install — data that is impossible to detect from outside via crawl. The connector doesn't analyse anything itself; it only sends InspectWP a strict allow-list of technical health metrics. This guide walks you through download, installation, pairing, the data we collect, and how to disconnect.
1. Download and install the plugin
The InspectWP WordPress Connector is not in the public WordPress.org directory — you download it directly from InspectWP and upload it to your site.
- Open the connector download page and click Download connector plugin (ZIP). You don't need to unzip the file.
- In WordPress, go to Plugins → Add New → Upload Plugin.
- Select the downloaded ZIP, click Install Now, then Activate Plugin.
- You'll find the new menu under Tools → InspectWP Connector.
2. Generate a pairing code in InspectWP
- Open the project you want to connect in your InspectWP dashboard.
- Click Connect plugin on the project card.
- Click Generate code. The code is single-use and expires in 10 minutes.
3. Pair on the WordPress side
- In WordPress, open Tools → InspectWP Connector and stay on the Connection tab.
- Paste the pairing code and click Connect.
- You're done. The plugin schedules a daily snapshot and a 6-hour heartbeat.
4. What data is sent
InspectWP only collects a strict allow-list of technical health metrics. The full list is shown in the plugin under Tools → InspectWP Connector → Data, plus a live JSON preview of the exact payload. We never send:
- Post content, comments, customer data, mail bodies
- Passwords, password hashes, session tokens
- wp-config values (only boolean flags like WP_DEBUG)
- User emails or names (only counts)
What we do send: WP core version & integrity, plugin & theme versions and update status, PHP/MySQL config, debug flags, DB health metrics (size, autoloaded options, transients/revisions/spam counts), config flags (default DB prefix, default salts, FS_METHOD), cron health (overdue jobs).
5. Schedule and reliability
The plugin uses WP-Cron. On low-traffic sites WP-Cron can fire late or not at all. If a daily snapshot doesn't arrive in time, the InspectWP backend marks the connection as stale. You can check the next scheduled snapshot and heartbeat any time under Tools → InspectWP Connector → Schedule. The recommended fix on production sites is a real Linux cron hitting wp-cron.php.
6. Manual sync
You can push a snapshot on demand via the Sync now button on the Connection tab (also available on the Schedule tab). Useful right after pairing to verify everything works, or after an update to push a fresh state to InspectWP.
7. Disconnect
Two ways:
- From WordPress: open Tools → InspectWP Connector → Connection and click Disconnect. The plugin tells the InspectWP backend to revoke this connection, clears the local credentials, and stops the cron jobs.
- From InspectWP: in the project card, click Disconnect. The connection token becomes invalid; the plugin will see a 401 on its next sync attempt.
Either way, snapshots already delivered remain visible in InspectWP. If you reconnect later, the historical snapshots reappear.
8. Frequently asked questions
Does the plugin slow down my site? No. It only runs on the daily cron and on the explicit „Sync now“ click — no frontend overhead, no admin-page overhead beyond the settings tab.
Can I use one InspectWP account for multiple sites? Yes. Each WP site pairs against a specific InspectWP project. One InspectWP account can have many projects and therefore many connected sites.
What if I lose the pairing code? Generate a new one. The previous one expires automatically after 10 minutes anyway.
How do I update the plugin? When a new version is available, download the latest ZIP from the connector download page and re-upload it in WordPress. Your connection stays intact across updates.