Title: PingView — Uptime, SSL & Checkout Monitoring for WordPress and WooCommerce Author: marcinatpingview Published: 19. Juli 2026 Last modified: 23. September 2026 --- Search plugins ![](https://ps.w.org/pingview-external-uptime-monitoring/assets/banner-772x250.png? rev=3615604) ![](https://ps.w.org/pingview-external-uptime-monitoring/assets/icon-256x256.png? rev=3613898) # PingView — Uptime, SSL & Checkout Monitoring for WordPress and WooCommerce By [marcinatpingview](https://profiles.wordpress.org/marcinatpingview/) [Download](https://downloads.wordpress.org/plugin/pingview-external-uptime-monitoring.1.7.0.zip) * [Details](https://de-ch.wordpress.org/plugins/pingview-external-uptime-monitoring/#description) * [Reviews](https://de-ch.wordpress.org/plugins/pingview-external-uptime-monitoring/#reviews) * [Installation](https://de-ch.wordpress.org/plugins/pingview-external-uptime-monitoring/#installation) * [Development](https://de-ch.wordpress.org/plugins/pingview-external-uptime-monitoring/#developers) [Support](https://wordpress.org/support/plugin/pingview-external-uptime-monitoring/) ## Description 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 ## Screenshots [⌊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⌉[ 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 [⌊Status header and KPI strip: current status, uptime for 24 hours and 7 days, response time and what needs attention⌉⌊Status header and KPI strip: current status, uptime for 24 hours and 7 days, response time and what needs attention⌉[ Status header and KPI strip: current status, uptime for 24 hours and 7 days, response time and what needs attention ## Installation 1. Upload the plugin files to `/wp-content/plugins/pingview-external-uptime-monitoring` 2. Activate the plugin through the ‚Plugins‘ screen in WordPress 3. Navigate to PingView in the admin menu 4. Enter your email and click «Start Monitoring» 5. Review the newly created monitor in PingView ## FAQ ### Is it down for everyone or just me? 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. ### Does it check that the WooCommerce checkout actually works? 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. ### Will I know before my SSL certificate expires? 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». ### Does it slow my site down? 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. ### Can I use it for client sites? 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. ### What happens on the free plan? 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. ### Do I need a PingView account? 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. ### Where can alerts be sent? 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. ### Does it monitor Core Web Vitals? 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. ### Does it check my security headers? 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. ### What happens after disconnecting or uninstalling the plugin? 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. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “PingView — Uptime, SSL & Checkout Monitoring for WordPress and WooCommerce” is open source software. The following people have contributed to this plugin. Contributors * [ marcinatpingview ](https://profiles.wordpress.org/marcinatpingview/) [Translate “PingView — Uptime, SSL & Checkout Monitoring for WordPress and WooCommerce” into your language.](https://translate.wordpress.org/projects/wp-plugins/pingview-external-uptime-monitoring) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/pingview-external-uptime-monitoring/), check out the [SVN repository](https://plugins.svn.wordpress.org/pingview-external-uptime-monitoring/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/pingview-external-uptime-monitoring/) by [RSS](https://plugins.trac.wordpress.org/log/pingview-external-uptime-monitoring/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.7.0 * Added: A response time chart for the last 24 hours under the uptime figures, with a dashed line at the threshold above which a check counts as slow. * Added: Other monitors running against this site, for example ones created in the PingView app or for a campaign page, are now listed on this screen. Only monitors for this site’s own address are shown, never other sites on the same account. * Improved: A location that is not simply operational now says why: answering but slow, not answering in time, or not answering at all. * Improved: The link offering to change the slow threshold now opens the monitor’s settings instead of its overview. * Fixed: The card header counted a retired monitoring location, so it said «checked from 5 locations» next to a median taken from 4. * Improved: New plugin name and description, and the remaining status panel texts are translated into Polish. #### 1.6.0 * Added: Pages you asked PingView to monitor now report back on this screen. Each one shows its current state, when it was last checked, and links straight to that monitor in PingView. Until now the only thing the card said was that the page had been added, and everything else had to be read on pingview.app. * Fixed: On shops that do not use pretty permalinks, the cart and the checkout were listed as already monitored the moment the home page was, and their checkboxes were hidden. They could not be added at all. They are now offered like every other page. * Fixed: A monitor still pointed at http while the site had moved to https made the card offer to monitor the home page a second time. * Fixed: Monitors created from this card were named after the page address, so on shops without pretty permalinks several of them ended up with the same name. They now carry the name of the page you ticked, for example «Your shop – Cart». * Fixed: When your plan ran out of monitors part way through, the screen said the plan was full without mentioning the pages that had just been added, and left the old ticks in place, so clicking again could add the same page twice. It now says how many were added and refreshes the list. * Fixed: Pages that failed to be added for any other reason were silently dropped from the confirmation, which reported only the successes. * Fixed: When PingView could not be reached, the screen said monitoring was still being set up and waiting for its first check, on sites monitored for months. It now says only that the latest status could not be loaded. * Improved: The warning colour used by the degraded and partial states was below the accessibility contrast minimum and is now darker. Disconnect is a button rather than a link, so it answers the space bar and is announced as an action. * Improved: Confirmation and error messages are now announced by screen readers, and the one message that stayed in English on Polish installs is translated. #### 1.5.1 * Fixed: Monitoring selected pages could fail when the main site monitor still contained a retired monitoring location. New page monitors now use PingView’s current default location instead of copying historical locations. * Improved: Monitor creation requests identify the WordPress plugin and its version, so rejected requests are visible in the PingView team audit trail. #### 1.5.0 * Improved: The PingView screen led with five screens of diagnostics before anything you could act on. The technical cards, locations, certificate, security headers, scheduled tasks, alert channels and account, are now folded shut and open themselves when they actually have something to report, a certificate about to expire, a probe reporting trouble, an overdue scheduler. Nothing was removed. * Improved: Nine buttons on the screen were styled as the main action, so none of them read as one. There is now a single highlighted action, and it stands down entirely while an incident is open or the monitor is still pointed at your old address. * Improved: The screen now knows which plan you are on and why, refreshed daily instead of only at the moment the site was connected. Paid features no longer carry a «Premium» badge for people who already pay for them, and the account card says where the plan comes from, a subscription, an invoice, a trial or a grant. * Fixed: «Public status page» in the footer opened the monitor page instead of your status pages. * Fixed: When PingView could not start monitoring the pages you picked, the same sentence was printed twice, once as a summary and once in the list below it, making the problem look bigger than it was. * Improved: The plugin menu entry now carries the PingView mark instead of a generic WordPress eye icon. * Improved: Removed 42 KB of stylesheet left over from three earlier versions of this screen, which every page view was downloading and none of it was used. #### 1.4.3 * Added: PingView’s checkout test now checks each of your shop’s enabled payment methods by name, BLIK, card, bank transfer, whatever you offer, instead of only confirming the cart total changed. A payment method that quietly disappears ( for example after a currency switch) now fails the test by name instead of going unnoticed. * Added: The checkout journey card now lists exactly which payment methods are being monitored, so nothing is checked without your knowledge. #### 1.4.2 * Fixed: A failing checkout test was only visible if you remembered to open Settings, PingView and look. It now also shows as a dismissible notice on every wp-admin screen, and as a line under the admin bar status when the site itself is otherwise fine, so a broken checkout cannot go unnoticed for weeks. * Fixed: Several labels on the checkout journey card, «Checkout test», «Passing»,« Not passing», «Checking now», «Resend shop configuration», and the paragraphs explaining what the card does, were missing from the Polish translation and always showed in English regardless of site language. * Added: The cart, checkout and product addresses sent to PingView are now kept in sync automatically. Once a day, PingView re-checks them and resends only if something actually changed, a new checkout URL, a theme change, a first product finally published, instead of requiring «Resend shop configuration» to be clicked by hand. #### 1.4.1 * Fixed: The checkout journey card only ever showed when the shop’s addresses were last sent, never whether the test built from them actually worked. A checkout test that silently failed its first run left downtime alerts off for that path with nothing in WordPress to say so. The card now shows the real state, checking, passing, or not passing with the exact step that failed, and says plainly that alerts stay off until it passes. * Improved: The «Premium» label on the checkout journey card now says what it means, a paid PingView plan, instead of leaving you to guess whether opening it lands on a paywall. #### 1.4.0 * Improved: WooCommerce shops now send PingView their cart, checkout and latest product addresses automatically, so PingView can build a checkout journey test itself instead of asking you to configure one by hand. The checkout journey card shows exactly what was sent, with a button to resend it after your pages change. #### 1.3.0 * Added: The panel now shows which PingView account this site reports into, the team and its plan, with a way in to manage them. Until now it only said «connected», which is no help at all when a site changes hands and you need to know whose account holds the data. * Improved: Links into PingView now carry your account address, so signing in is one click instead of remembering which address the account uses. Sign-in stays passwordless: the link is emailed to that address and nothing signs you in from inside WordPress. * Improved: The setup screen now says plainly that an account is created for the address you enter and that a sign-in link is emailed to it, so nothing about the account happens silently. * Fixed: Errors coming back from PingView said only «Validation failed», naming neither the field nor the reason. They now say what was rejected and why, in your language. * Fixed: Connecting with an existing PingView API key, on a site that had no monitor yet, created the monitor but never finished connecting. The panel stayed empty and the only way out was to disconnect and start again. * Improved: A new card lists the pages this site actually has, the cart, the checkout, a product and a category, and shows which ones are already watched. The ones that are not can be added with one click. A monitor pointed at the home page alone cannot tell you that your checkout is down. * Improved: A new card watches WP-Cron. The diagnosis is free on every plan: whether the scheduler is switched off in wp-config.php, how many jobs are queued, and whether the next one is overdue. A dead WP-Cron stops your abandoned cart emails, order notifications and backups while the site keeps answering normally, so nothing checking from outside would ever notice. * Improved: A new card gives you the copy and paste code for your public status page badge, with a live preview, when your team has a public status page. #### 1.1.0 * Improved: The security headers report is now included for every site, on every plan. It used to appear only with deep scans enabled, so most sites saw three greyed out placeholder rows. You now get the Mozilla HTTP Observatory grade, the checks your site fails, and the exact header line to paste, with a copy button. * Fixed: A site served over plain HTTP had its certificate reported as «not applicable», which read as though nothing was wrong. It now says the site is served over plain HTTP with no certificate, and that browsers mark such pages as not secure. This also appears in the list of items needing attention. * Improved: A new card explains what a synthetic checkout journey watches, product page, add to cart and reaching payment, and where to set one up. An uptime check cannot see a broken checkout while the homepage still answers. * Improved: The panel now states plainly that monitoring runs on PingView servers, that no plugin code runs on visitor requests, and that deactivating the plugin does not stop monitoring. * Improved: Polish translation of the whole panel. #### 1.0.11 * Fixed: The coloured status dot in the admin bar was never drawn, so the item showed the label with no indicator next to it. It is now visible on every screen, including the post and site editors where WordPress 7.1 keeps the toolbar in view. * Improved: Moving the site to a different address, for example from http to https, now repoints the monitor instead of asking you to reconnect it by hand. There is also a button to move it straight away. * Tested: WordPress 7.1. #### 1.0.10 * Added: Security headers now have their own card. It shows the Mozilla HTTP Observatory grade and score, the checks your site fails, what each one protects against, and how many points fixing it wins back. * Added: A copy button next to every failed check, with the exact header line to paste into your server configuration. * Improved: The failed checks are ordered by how much they are worth, so the fix with the biggest effect is first. Smaller ones stay collapsed. * Improved: The alerts card now points at the weekly summary, for the weeks when nothing breaks. #### 1.0.9 * Fixed: The speed score changed on every refresh even when nothing about the site had. It restated the response time shown next to it and could not be acted on, so it is replaced by «Needs attention», which counts the certificate, domain and uptime issues waiting for you. * Added: A status indicator in the admin bar, so you can see whether the site is up without opening the PingView screen. * Added: A link to PingView on the Plugins screen, and the setup screen now opens right after activation. * Fixed: The location list only showed locations that had already reported, so a monitor covering several locations could claim it was checked from one, or show no locations at all until the first results arrived. * Fixed: Cancelling the «Connect with an API key» form left the key sitting in the field. * Improved: Status and error messages are now announced by screen readers, and the API key form reports whether it is open. #### 1.0.8 * Added: A quality report card with the daily Google Lighthouse scores for performance, accessibility, best practices and SEO, plus Core Web Vitals. * Added: The Mozilla Observatory security grade for your site, next to the SSL and domain checks. * Added: An overview of where alerts are delivered, covering email, Slack, Microsoft Teams, Discord, webhooks and SMS. * Fixed: The performance score changed on every refresh, because it was based on a single check. It is now based on the 95th percentile response time over 24 hours and is labelled «Speed score, 24h». #### 1.0.7 * Added: The status screen now lists every monitoring location your plan checks from, with its own status and response time. * Added: A 24 hour availability chart, one block per time bucket, so a short outage is visible at a glance instead of hidden in an average. * Added: A recent incidents list showing what broke, when, and how long it lasted. * Fixed: The «Where should we send alerts?» text on the setup screen was not a real form label, so clicking it did not focus the field and screen readers did not announce it. * Fixed: The refresh button icon sat off the text baseline. * Fixed: Refreshing only cleared part of the cached data, so some panels could keep showing older values. * Improved: Rebuilt the setup screen around a single card, so the connection form is no longer competing with a marketing panel for attention. * Improved: The panel is centred and uses more of the available width on wide screens. #### 1.0.6 * Improved: The status screen now shows which version of the plugin is installed. #### 1.0.5 * Fixed: The incident banner never appeared, because open incidents were read from a field that does not exist. Active incidents are now shown with their reason and start time. * Fixed: The performance score changed on every refresh even when the underlying data had not. The same response time now always produces the same score. * Fixed: Sites monitored over plain HTTP no longer sit on «Checking certificate…» forever. They now state that no certificate applies. * Fixed: A domain without registration data no longer shows an endless «Checking domain registration…». * Fixed: The refresh button was rendered several times with the same HTML id, so only the first one worked. * Improved: Redesigned the status panel around a header card, a four-tile metric strip, and a two-column layout. * Improved: Response times, uptime percentages, and scores are set in a monospaced face so values line up and stay comparable. * Improved: Every status is now conveyed by colour, icon, and text label together, never colour alone. * Improved: The setup screen no longer promises a first check «in ~5 minutes» when the backend has not scheduled one yet. * Improved: Honoured reduced-motion preferences and tightened the layout on small screens. #### 1.0.4 * Fixed: Prevent an undefined SSL expiration warning when certificate data is incomplete. * Improved: Redesign the monitoring dashboard for clearer desktop and mobile layouts. * Improved: Remove horizontal overflow and improve visual consistency. #### 1.0.3 * Security: Escape all API messages rendered in the admin dashboard. * Security: Store new API tokens using authenticated encryption and fail safely when encryption is unavailable. * Fixed: Render canonical PingView monitor statuses without reducing them to UP or DOWN (BR-STATUS-01 / CT-STATUS). * Improved: Require an explicit, unchecked consent before sending setup data to PingView. * Improved: Align feature descriptions with plan-dependent intervals and locations. #### 1.0.2 * Fixed: Load all admin CSS through the WordPress enqueue API. * Fixed: Match the translation text domain to the WordPress.org plugin slug. * Improved: Fully document the PingView external service and transmitted data. * Tested: WordPress 7.0 with WP_DEBUG enabled. #### 1.0.1 * Fixed: Plugin URI updated to working URL * Improved: Documentation for external service usage * Updated: Contributors metadata #### 1.0.0 * Initial release ## Meta * Version **1.7.0** * Last updated **3 Wochen ago** * Active installations **Fewer than 10** * WordPress version ** 5.8 or higher ** * Tested up to **7.1.3** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/pingview-external-uptime-monitoring/) * Tags * [downtime](https://de-ch.wordpress.org/plugins/tags/downtime/)[monitoring](https://de-ch.wordpress.org/plugins/tags/monitoring/) [ssl](https://de-ch.wordpress.org/plugins/tags/ssl/)[uptime](https://de-ch.wordpress.org/plugins/tags/uptime/) [woocommerce](https://de-ch.wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://de-ch.wordpress.org/plugins/pingview-external-uptime-monitoring/advanced/) ## Ratings Es wurden noch keine Rezensionen eingereicht. [Your review](https://wordpress.org/support/plugin/pingview-external-uptime-monitoring/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/pingview-external-uptime-monitoring/reviews/) ## Contributors * [ marcinatpingview ](https://profiles.wordpress.org/marcinatpingview/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/pingview-external-uptime-monitoring/)