Install this update to see response time over the last 24 hours and every monitor watching this site, right on the WordPress screen.<\/p>","1.6.0":"
Install this update if your shop does not use pretty permalinks, the cart and checkout could not be added for monitoring at all. Pages you monitor also report their state on the WordPress screen now, instead of only on pingview.app.<\/p>","1.5.1":"
Install this update if monitoring selected pages failed because an older monitoring location was no longer active.<\/p>","1.5.0":"
The PingView screen is shorter and leads with what changed: technical cards fold away until they have something to report, one action is highlighted instead of nine, and the plan you are on is kept up to date so paid features stop being advertised to people who already have them.<\/p>","1.4.3":"
The checkout test now checks each of your payment methods by name, so one disappearing (for example after a currency switch) is caught and named instead of hiding behind a passing cart total.<\/p>","1.4.2":"
A failing checkout test now shows on every admin screen and in the admin bar, the checkout journey card is fully translated into Polish, and the shop addresses PingView tests are kept in sync automatically.<\/p>","1.4.0":"
WooCommerce shops now send PingView their cart, checkout and product addresses automatically, so a checkout journey test can be built without configuring one by hand.<\/p>","1.3.0":"
The panel now tells you which PingView account this site reports into, connecting with an existing API key no longer leaves it empty, your cart and checkout pages can be monitored in one click, and a stopped WP-Cron is now visible instead of silent.<\/p>","1.1.0":"
The security headers report is now free for every site, a site without HTTPS is reported as a problem instead of "not applicable", and the panel speaks Polish.<\/p>","1.0.11":"
The admin bar status dot is visible again, a changed site address repoints the monitor by itself, and the plugin is tested with WordPress 7.1.<\/p>","1.0.10":"
Security headers get their own card: the grade, the checks you fail, why each matters, and the exact header line to copy.<\/p>","1.0.9":"
The unstable speed score is replaced by a "Needs attention" summary. Site status in the admin bar, a faster route from activation to setup, the full location list, and accessibility fixes.<\/p>","1.0.8":"
Lighthouse and Mozilla Observatory results on the status screen, an alert channel overview, and a performance score that no longer jumps on every refresh.<\/p>","1.0.7":"
Per-location results, a 24 hour availability chart, a recent incidents list, and a rebuilt setup screen.<\/p>","1.0.6":"
The status screen now shows the installed plugin version.<\/p>","1.0.5":"
Redesigned status panel, plus fixes for the missing incident banner, an unstable performance score, and stuck "checking..." states.<\/p>","1.0.4":"
Dashboard layout improvements and safer handling of incomplete SSL certificate data.<\/p>","1.0.3":"
Security and WordPress.org review-readiness fixes.<\/p>","1.0.2":"
WordPress.org review compliance fixes for assets, translations, and external-service disclosure.<\/p>","1.0.1":"
Documentation improvements and metadata fixes for WordPress.org submission.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3613898,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-144x144.png":{"filename":"icon-144x144.png","revision":3613898,"resolution":"144x144","location":"assets","locale":"","width":144,"height":144},"icon-152x152.png":{"filename":"icon-152x152.png","revision":3613898,"resolution":"152x152","location":"assets","locale":"","width":152,"height":152},"icon-192x192.png":{"filename":"icon-192x192.png","revision":3613898,"resolution":"192x192","location":"assets","locale":"","width":192,"height":192},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3613898,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon-384x384.png":{"filename":"icon-384x384.png","revision":3613898,"resolution":"384x384","location":"assets","locale":"","width":384,"height":384},"icon-512x512.png":{"filename":"icon-512x512.png","revision":3613898,"resolution":"512x512","location":"assets","locale":"","width":512,"height":512}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3615604,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3615604,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{"blueprint.json":{"filename":"blueprint.json","revision":3709081,"resolution":false,"location":"assets","locale":"","contents":"{\"$schema\":\"https:\\\/\\\/playground.wordpress.net\\\/blueprint-schema.json\",\"landingPage\":\"\\\/wp-admin\\\/admin.php?page=pingview\",\"preferredVersions\":{\"php\":\"8.2\",\"wp\":\"latest\"},\"steps\":[{\"step\":\"login\",\"username\":\"admin\",\"password\":\"password\"},{\"step\":\"installPlugin\",\"pluginData\":{\"resource\":\"wordpress.org\\\/plugins\",\"slug\":\"pingview-external-uptime-monitoring\"},\"options\":{\"activate\":true}}]}"}},"all_blocks":[],"tagged_versions":["1.0.10","1.0.11","1.0.3","1.0.4","1.0.5","1.0.6","1.0.7","1.0.8","1.0.9","1.1.0","1.3.0","1.4.3","1.5.0","1.6.0","1.7.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3616553,"resolution":"1","location":"assets","locale":"","width":1364,"height":1276},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3616553,"resolution":"2","location":"assets","locale":"","width":1906,"height":886}},"screenshots":{"1":"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","2":"Status header and KPI strip: current status, uptime for 24 hours and 7 days, response time and what needs attention","3":"SSL certificate and domain registration expiry, with days remaining","4":"Recent incidents: what broke, when and how long it lasted, with per-location results","5":"Setup: one field, the address alerts should go to, and the monitor is created"}},"plugin_section":[],"plugin_tags":[49036,5603,1536,29148,286],"plugin_category":[54],"plugin_contributors":[272360],"plugin_business_model":[],"class_list":["post-341663","plugin","type-plugin","status-publish","hentry","plugin_tags-downtime","plugin_tags-monitoring","plugin_tags-ssl","plugin_tags-uptime","plugin_tags-woocommerce","plugin_category-security-and-spam-protection","plugin_contributors-marcinatpingview","plugin_committers-marcinatpingview"],"banners":{"banner":"https:\/\/ps.w.org\/pingview-external-uptime-monitoring\/assets\/banner-772x250.png?rev=3615604","banner_2x":"https:\/\/ps.w.org\/pingview-external-uptime-monitoring\/assets\/banner-1544x500.png?rev=3615604","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/pingview-external-uptime-monitoring\/assets\/icon-128x128.png?rev=3613898","icon_2x":"https:\/\/ps.w.org\/pingview-external-uptime-monitoring\/assets\/icon-256x256.png?rev=3613898","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/pingview-external-uptime-monitoring\/assets\/screenshot-1.png?rev=3616553","caption":"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"},{"src":"https:\/\/ps.w.org\/pingview-external-uptime-monitoring\/assets\/screenshot-2.png?rev=3616553","caption":"Status header and KPI strip: current status, uptime for 24 hours and 7 days, response time and what needs attention"}],"raw_content":"\n
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.<\/p>\n\n
What it checks<\/strong><\/p>\n\n 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.<\/p>\n\n For agencies<\/strong><\/p>\n\n 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.<\/p>\n\n How it works<\/strong><\/p>\n\n The monitoring runs on PingView's servers. Nothing is added to the site's frontend and nothing runs during a visitor's request.<\/p>\n\n 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.<\/p>\n\n What the service is and what it is used for:<\/strong>\nPingView 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.<\/p>\n\n What data is sent and when:<\/strong>\n- 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.\n- 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.\n- When a monitor is created: the site URL, generated monitor name, monitor type, check interval, response-time threshold, and selected monitoring locations.\n- When loading or refreshing the dashboard: the stored monitor identifier and API token, used to retrieve current monitoring status.\n- After setup, PingView's external servers request the monitored site URL at the configured interval to measure availability and related monitoring signals.<\/p>\n\n When data is transmitted:<\/strong>\n- When the administrator submits either setup form.\n- When the PingView admin dashboard is opened or manually refreshed.\n- Continuously after setup, when PingView performs external checks of the configured site according to the monitor's settings.<\/p>\n\n Service provider:<\/strong>\nPingView<\/p>\n\n Terms of Service:<\/strong>\nhttps:\/\/pingview.app\/en\/terms-of-service<\/p>\n\n Privacy Policy:<\/strong>\nhttps:\/\/pingview.app\/en\/privacy-policy<\/p>\n\n\n PingView checks the site from several locations outside your hosting, so the panel tells the two apart: every location failing is an outage, one location failing is a regional or network problem. A plugin that checks from inside the site cannot answer this at all, because when the server is gone, so is the plugin.<\/p><\/dd>\n Yes. The plugin sends PingView the shop's cart, checkout and product addresses, and PingView builds a synthetic checkout test from them: open a product, add it to the cart, reach payment, and confirm each enabled payment method by name, BLIK, card, bank transfer, whatever the shop offers. The result and the exact step that failed show on the checkout journey card, as a notice on every admin screen and in the admin bar. The test runs daily on the free plan and more often on paid plans.<\/p><\/dd>\n Yes. The certificate card shows the days remaining, the domain registration expiry next to it, and a warning is sent before the certificate runs out. A site still served over plain HTTP is reported as a problem, not as \"not applicable\".<\/p><\/dd>\n No. Every check runs on PingView's servers, outside the site. The plugin adds nothing to the frontend and no plugin code runs during a visitor's request; it only reads results when you open the PingView screen in wp-admin.<\/p><\/dd>\n Yes, that is what it is built for. Each site gets its own monitor, all of them report into one PingView panel, and the same plugin exists for PrestaShop and Magento 2, so a mixed portfolio is watched in one place. Alerts can go to your own channels, the client's, or both. Deactivating the plugin on a client site does not stop the monitoring.<\/p><\/dd>\n The plugin and the monitoring it sets up are free to start: external checks from several locations, downtime alerts by email, the SSL and domain expiry warnings, the WP-Cron diagnosis, the security headers grade, and the checkout test once a day. Paid plans add shorter check intervals, more locations, more alert channels, the daily Lighthouse and Core Web Vitals scan, the WP-Cron heartbeat, public status pages and more frequent checkout tests.<\/p><\/dd>\n No. Enter the address alerts should go to and the plugin creates the account and the monitor for you; a sign-in link is emailed to that address. If you already use PingView, choose \"Connect with an API key\" on the setup screen instead.<\/p><\/dd>\n Email works out of the box. Slack, Microsoft Teams, Discord, webhooks and SMS are configured in your PingView account and apply to this monitor too.<\/p><\/dd>\n Yes, on paid plans. PingView runs a daily Google Lighthouse scan from outside your hosting and shows the performance, accessibility, best practices and SEO scores, with the lab Core Web Vitals behind the performance score: LCP, CLS and TBT. It is a monitor, not an optimizer: it does not cache, minify or defer anything on the site.<\/p><\/dd>\n Yes, on every plan. PingView runs a Mozilla HTTP Observatory scan and shows the grade (A+ to F), the checks the site fails and the exact header line to paste. It is an external check of what the site sends over HTTP; it is not a firewall or a malware scanner.<\/p><\/dd>\n The plugin removes its local connection data when you disconnect, and all local plugin data when you uninstall it. The PingView monitor and account remain active. Sign in at https:\/\/pingview.app to pause or delete the monitor and manage the account.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
External Services<\/h3>\n\n
\n
\/wp-content\/plugins\/pingview-external-uptime-monitoring<\/code><\/li>\n\n
Is it down for everyone or just me?<\/h3><\/dt>\n
Does it check that the WooCommerce checkout actually works?<\/h3><\/dt>\n
Will I know before my SSL certificate expires?<\/h3><\/dt>\n
Does it slow my site down?<\/h3><\/dt>\n
Can I use it for client sites?<\/h3><\/dt>\n
What happens on the free plan?<\/h3><\/dt>\n
Do I need a PingView account?<\/h3><\/dt>\n
Where can alerts be sent?<\/h3><\/dt>\n
Does it monitor Core Web Vitals?<\/h3><\/dt>\n
Does it check my security headers?<\/h3><\/dt>\n
What happens after disconnecting or uninstalling the plugin?<\/h3><\/dt>\n
1.7.0<\/h4>\n\n
\n
1.6.0<\/h4>\n\n
\n
1.5.1<\/h4>\n\n
\n
1.5.0<\/h4>\n\n
\n
1.4.3<\/h4>\n\n
\n
1.4.2<\/h4>\n\n
\n
1.4.1<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.11<\/h4>\n\n
\n
1.0.10<\/h4>\n\n
\n
1.0.9<\/h4>\n\n
\n
1.0.8<\/h4>\n\n
\n
1.0.7<\/h4>\n\n
\n
1.0.6<\/h4>\n\n
\n
1.0.5<\/h4>\n\n
\n
1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n