PingView — Uptime, SSL & Checkout Monitoring for WordPress and WooCommerce
PingView — Uptime, SSL & Checkout Monitoring for WordPress and WooCommerce

PingView — Uptime, SSL & Checkout Monitoring for WordPress and WooCommerce

0/5 (0 ratings) — active installs Updated Sep 23, 2026
Checkout journey card: the synthetic cart to payment test built from the shop's own pages, with the payment methods it confirms and the step that failed

Checkout journey card: the synthetic cart to payment test built from the shop's own pages, with the payment methods it confirms and the step that failed

PingView is for agencies and freelancers who look after WordPress sites and WooCommerce shops for other people. A management plugin looks at the shop from the inside; PingView checks from outside, from several locations, whether a customer can open the site and buy today, and emails you before the client notices.

What it checks

  • Site availability from several external locations, with per-location status and response time, so “the site is down” and “slow from one region” are told apart
  • The WooCommerce checkout journey: a synthetic test built from your shop’s own cart, checkout and product pages that adds a product, reaches payment and confirms each enabled payment method by name. Daily on the free plan, more often on paid plans
  • SSL certificate expiry, domain registration expiry and a site still served over plain HTTP, with days remaining
  • Uptime for the last 24 hours and 7 days, a 24 hour availability chart, one block per bucket, and a list of recent incidents with what broke, when and for how long
  • WP-Cron: whether the scheduler is switched off, how many jobs are queued and whether the next one is overdue, plus an external heartbeat that notices when it stops
  • Lighthouse scores and the Core Web Vitals behind them (LCP, CLS, TBT), from a daily scan on paid plans
  • Security headers: the Mozilla HTTP Observatory grade, the checks you fail and the exact header line to paste
  • Your cart, checkout, product and category pages, each with its own monitor, added in one click
  • A status indicator in the admin bar, a status page badge you can embed, and the account and team the site reports into

Alerts go to email out of the box; Slack, Microsoft Teams, Discord, webhooks and SMS are set up once in your PingView account and apply to every site.

For agencies

One plugin family, three platforms: PingView has the same plugin for WordPress, PrestaShop and Magento 2, and every client site reports into the same panel. Add a site with one field, the address alerts should go to, and PingView creates the account and the monitor. No API key to copy, no code on your visitors’ page loads. Deactivating the plugin does not stop monitoring, and disconnecting removes only the local credentials.

How it works

  1. Install and activate the plugin
  2. Enter the address alerts should go to
  3. PingView creates an external monitor and starts checking the site; WooCommerce shops also send their cart, checkout and product addresses so the checkout test builds itself

The monitoring runs on PingView’s servers. Nothing is added to the site’s frontend and nothing runs during a visitor’s request.

External Services

This plugin depends on the PingView external monitoring service (https://pingview.app). The service creates or connects a monitor, checks the configured website from external locations, sends downtime alerts, and returns monitoring information for the WordPress admin dashboard. The plugin cannot provide monitoring functionality without this service.

What the service is and what it is used for:
PingView is an external website monitoring service provided by PingView. It checks website availability, performance, certificates, and incidents from external locations and provides the results shown by this plugin.

What data is sent and when:
– During new account setup: the administrator’s email address, WordPress site URL, site name, plugin version, and a source identifier stating that the request came from the WordPress plugin.
– When connecting an existing account: the API token entered by the administrator. The token is sent in an authorization header so PingView can validate the account and list or create its monitors.
– When a monitor is created: the site URL, generated monitor name, monitor type, check interval, response-time threshold, and selected monitoring locations.
– When loading or refreshing the dashboard: the stored monitor identifier and API token, used to retrieve current monitoring status.
– After setup, PingView’s external servers request the monitored site URL at the configured interval to measure availability and related monitoring signals.

When data is transmitted:
– When the administrator submits either setup form.
– When the PingView admin dashboard is opened or manually refreshed.
– Continuously after setup, when PingView performs external checks of the configured site according to the monitor’s settings.

Service provider:
PingView

Terms of Service:
https://pingview.app/en/terms-of-service

Privacy Policy:
https://pingview.app/en/privacy-policy