| 开发者 | Mike.Miler |
|---|---|
| 更新时间 | 2026年6月19日 17:18 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
api.webchangedetector.com only after you have entered your API token, and only in these circumstances: when you connect or verify your account, when you enable a child site or sync its page URLs (the public URLs and page titles of that site are transmitted), when you start a visual check (screenshots are taken of the selected public URLs), and when you review or update results. Your API token is sent with each request to authenticate your account. No data about your WordPress users or any non-selected content is transmitted.
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.