See local WordPress signals centrally
Health status, update posture, and malware scan results can be stored and reviewed in FirePhage.
WordPress Plugin
The FirePhage WordPress plugin connects local WordPress health and malware scan visibility with the hosted FirePhage dashboard. Paid sites can also pull live firewall and performance telemetry back into the WordPress admin.
Health checks
Connected
Malware results
Reported
Paid telemetry
Synced
Connected signal flow
See local WordPress signals centrally
Health status, update posture, and malware scan results can be stored and reviewed in FirePhage.
Unlock live plugin telemetry for paid sites
Covered paid sites can view live firewall and performance context directly in the plugin.
Connect without messy setup
The plugin uses a scoped connection flow so dashboard sync is explicit and site-aware.
Problem this solves
WordPress teams often split visibility across local plugins, separate dashboards, and unreadable edge tools. They need one clearer flow.
Example: one site, two visibility layers
A WordPress operator sees local scan findings and health checks in the plugin while the SaaS dashboard stores the same security context and adds edge-side firewall visibility for paid coverage.
Health summaries
WordPress posture, checksum state, and update exposure can be reported into the SaaS dashboard.
Malware scan visibility
Latest findings and suspicious-file counts are stored as part of the connected site view.
Paid firewall visibility
When a site is covered by a paid plan, the plugin can load real firewall activity and performance summaries from FirePhage.
Agency-friendly workflow
Teams can manage the site in WordPress while still using FirePhage as the main edge-control dashboard.
How it fits FirePhage
Every FirePhage service page is meant to explain one capability clearly, then connect that capability back to pricing, onboarding, the dashboard, and the real website problems teams are trying to solve.