by
Mike Miler
1 (0 reviews)
WebChange Detector for MainWP
Visual checks for your MainWP updates: before/after screenshots of all child sites in one run, compared automatically.
WebChange Detector for MainWP ranks #23,882 among WordPress.org plugins with 1+ active installations, is #2,391 of 4,499 in the Security category, a 1/5 rating from 0 reviews, and was last updated Jun 19, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 7 (Current: 7.1)
v1.0.2
Current Version v1.0.2
Updated 2 months ago
Last Update on 19 Jun, 2026
Refreshed 9 hours ago
Last Refreshed on
#2,391 of 4,499 in Security
Rank
#23,882
—
No change
Active Installs
1+
—
No change
KW Avg Position
20.5
—
No change
Downloads
267
+8 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
23,170
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 3 more installs to reach 10+
Rank Changes
Current
#23,882
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.2
- Last Updated
- Jun 19, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7
- PHP Version
- 7.4 or higher
- Author
- Mike Miler
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,751
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,006
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#8
Wordfence Security - Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#17
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#33
WP Super Cache
1M+ installs
#38
Frequently Asked Questions
Common questions about WebChange Detector for MainWP
An on-demand check is a visual diff you run around a change you make yourself. WebChange Detector takes a screenshot of each selected page before the change, you apply the change, it takes another screenshot after, and the two are compared automatically on desktop and mobile. In MainWP this is wrapped around the updates you run: the plugin captures the pre-update screenshots, installs the updates, captures the post-update screenshots, and shows you every page that changed, with an AI summary. The AI ignores moving parts like sliders, carousels and ads, so you only get flagged on real changes.
No. The plugin runs entirely on your MainWP Dashboard and talks to the WebChange Detector service. Child sites are captured through their public URLs.
Yes. The screenshots are captured and compared by the WebChange Detector service, so you need an account and API token. A free plan is available.
You choose. After enabling a child site, its published pages and posts are synced and you select which URLs are checked, separately for desktop and mobile. Every selected URL and device counts as one check per capture.
Before it can check a site, the plugin needs the list of public URLs on that site. Syncing fetches the published pages and posts from the child and makes them available for selection. It runs automatically when you enable a site and again after MainWP syncs the child. Until a site is synced, there are no pages to select and no checks can run.
The run tolerates it: the offline site is skipped for updates and the other sites continue. The post-update screenshots still run for the sites that were updated.
No, the plugin does that for you. It clears each child site's cache before the pre-update screenshots and again after the updates, using the cache clearing built into the MainWP Child plugin (supports 20+ caching plugins, detected automatically). This makes sure the comparison shows the actual state of the site after the updates instead of a cached old version. If no supported caching plugin is active, this step is simply skipped.
Updates you start outside the plugin's own flow still trigger post-update screenshots as a safety net, so you can compare against the last baseline. For the full pre/post comparison, start the run from the "Run visual checks & updates" button.
