Agency-side content health management: one crawler API key, multiple client sites, per-site monthly scan quotas, and a full audit log — without exposing credentials to any client.
What it does
Health Monitor Hub is the agency-side component of ToggleWP’s Content Health Monitor system. It sits on the agency’s own WordPress site and acts as a secure proxy between connected client sites and an external web crawler service.
Rather than giving each client site direct access to the crawler API, the agency manages a single API key in the Hub. Client sites submit page-check requests to the Hub, which forwards them to the crawler and enforces per-site monthly scan quotas. The crawler API key never leaves the Hub site.
Key features
Crawler Proxy
- Accepts page-check requests from registered client sites via REST API
- Forwards requests to an external crawler service using the Hub’s stored API key
- Returns crawler response to the client – clients never communicate with the crawler directly
- Enforces monthly scan quotas per client; over-quota requests are rejected with HTTP 429
Client Registry
- Register client sites and generate WordPress App Password credentials for authentication
- Each client gets a unique base64-encoded config string for fast import on the client side
- Regenerate credentials at any time without re-creating the client record
- Revoke or delete clients individually
- Update per-client monthly scan quota on the fly
Site Sync Integration
- When a new child site is registered via Site Sync, health monitoring is automatically enabled for that site
- When a SiteSync child site is deleted, its health monitoring access is automatically revoked
- Hub merges SiteSync child sites and standalone Health Monitor clients into a single unified managed-sites list
Scan Log
- Hub-wide log of all scan submissions across all registered clients
- Filter by client site, paginate through results
- Status indicators: pending, completed, failed
- Issue counts per scan
- Clear log button for housekeeping
Email Notifications
- Choose who receives scan result emails: the content publisher or a fixed service admin email
- Override the recipient at the Hub level — client sites pick up the setting automatically
Who It’s For
Agencies and freelancers who manage multiple client WordPress sites and want to offer content health monitoring as a service without giving clients direct access to crawler API credentials.
Settings & Configuration
| Setting | Description |
|---|---|
| Crawler URL | Base URL of the external crawler service |
| API Token | Credential for the crawler API — stored on Hub only, never sent to clients |
| Default Monthly Scans | Scan quota applied to new clients (default: 100) |
| Results Email Recipient | content_publisher (the user who published the post) or service_admin (fixed email below) |
| Service Admin Email | Fixed recipient when “service admin” mode is selected |
Dependencies / Compatibility
- No required sibling modules
- Integrates with Site Sync: child sites auto-register and auto-revoke health monitoring access
- Health Monitor Client on client sites connects to this Hub