Safe updates
Automatic WordPress updates, verified before they go live.
Verploy tests every update on a private copy of your site, checks what changed, and only then updates the live site. If something still goes wrong, it rolls back.
Safe updates
Updates are proven on a copy before they touch your live site.
Verploy builds a temporary test copy on your own server. What passes there has been tested in the real environment, not in a lookalike.
01
A private test copy
Built on your own server, with the same PHP version and limits. Invisible to visitors and search engines, and it never sends email.
02
The update runs there first
Plugins, themes or WordPress core are updated on the copy, never straight on your live site.
03
Verploy checks the result
Every page is compared with the same copy just before the update, on desktop and mobile.
04
Only safe updates go live
If anything new breaks, the update is stopped. Your live site is never touched.
05
The live site is checked again
Right after going live, Verploy compares the site with how it looked seconds before.
06
Problem? Automatic rollback
Files and database are restored from a snapshot taken just before, even if the update crashed the whole site.
Test copy created same server
Baseline measured desktop + mobile
Update applied on the test copy
No new problems found layout within threshold
Going live short maintenance window
Live site verified compared with just before
During go-live the site is in maintenance mode for a few minutes, so a rollback can never erase new orders or form entries.
See it work
A real update run, replayed.
Two runs from 24 September 2026, step by step. One update was stopped on the test copy before it could reach the live site. The other was tested, put live and verified.
5 updates, including WooCommerce 11.0.1 → 11.1.2
- 19:258 pages chosen to testHome, news, about, contact, shop, cart, checkout, plus the login page
- 19:26Baseline on the live site17 of 17 measurements OK
- 19:26Test copy created on the same server31,252 files, 99 database tables
- 19:28Updates installed on the test copyPremium plugin fetched with the site’s own licence
- 19:29Test failed: news page, desktop4.2% visual difference, 2% allowed
- 19:29Go-live skipped, test copy removed
The live site was never touched. Verploy explained why and suggested the next step: check the difference image, then mask the changing element or keep the current versions.
| Page on the test copy | Desktop | Mobile |
|---|---|---|
| Home | 0.0% | 0.0% |
| News | 4.2% | 0.0% |
| About | 0.0% | 0.0% |
| Contact | 0.0% | 0.0% |
| Shop | 0.0% | 0.0% |
| Cart · Checkout | 0.0% | 0.0% |
1 update: WPCode Lite 2.3.6 → 2.3.9
- 19:38Baseline on the live site17 of 17 measurements OK
- 19:39Test copy created on the same server20,429 files, 62 database tables
- 19:40Update installed on the test copy
- 19:42All tests on the test copy passed8 pages, desktop and mobile, plus the login page
- 19:44Maintenance mode on, backup of files and database
- 19:44Update put live
- 19:46Live site checked right afterCompared with seconds before: passed
Nothing for the agency to do. Every step is in the run’s timeline, with before, after and difference screenshots per page.
| Page | Desktop | Mobile |
|---|---|---|
| Home (test copy) | 1.4% | 1.4% |
| 6 content pages (test copy) | 0.0% | 0.0% |
| Floor plan (test copy) | 0.0% | 0.0% |
| Home (live, after go-live) | 2.0% | 0.5% |
| Other pages (live) | 0.0% | 0.0% |
| Login page | OK | — |
Small differences, such as a rotating image, stay within the allowed threshold, which you set per site (2% by default).
Replays of two real Verploy runs on 24 September 2026. Site names are anonymised and screenshots blurred; times, steps and percentages are unchanged.
Verification
More than a screenshot comparison.
Verploy measures each page before and after an update, on desktop and mobile. Only new problems count: issues your site already had won't block an update.
Pages still load
Reachability, HTTP status, and PHP or WordPress error pages.
No new JavaScript errors
Console errors that weren't there before the update.
Scripts and styles load
Your site's own CSS and JavaScript files still load.
Layout stays intact
Pixel comparison per page, with a threshold you choose and masks for sliders or dates.
Structure is still there
Header, navigation, main content and footer haven't disappeared or halved.
Login still works
The WordPress login form still appears as it should.
Coming soon
Forms and checkout: checking that contact forms submit, and that WooCommerce carts and checkouts open.
When something goes wrong
A failed update is a notification, not an emergency.
Verploy is built for the moment an update breaks something. That moment should cost you a minute, not an evening.
Stopped on the copy
If a check fails on the test copy, nothing happens to your live site. You get a notification with the diagnosis.
Rolled back on live
If a problem only appears after going live, Verploy restores files and database from the snapshot. Even when the site crashed completely.
Explained in plain language
Every stopped or rolled-back update comes with an explanation: which plugin, what went wrong and what you can do.
You stay in control
Every run is transparent.
Choose which updates to run, per site or in bulk. Each run has a timeline with every step, and before, after and difference screenshots per page.
- Test settings per site: pages, threshold and masks
- Timeline for every update run
- Before, after and difference screenshots
- Notifications by email in your team's language
Spend less time checking WordPress.
Let Verploy do the maintenance work.
Launching soon. Founding spots: 40% off, for life.