Settings → DeploySeal. Site key and Enabled are the only required fields; the page shows the origins to register, the declared environment label, the build marker and the exact tag that will be rendered.
Test releases on your real site, and prove what was tested.
DeploySeal lets your team and stakeholders review a WordPress or WooCommerce site before it goes live: testers follow a checklist on the actual pages, pin issues where they see them (screenshot, session replay and browser details captured automatically), developers fix and send them back for verification, and the people who sign off do so on a record that cannot be quietly changed afterwards.
This plugin is the WordPress install path for that widget. It does what a pasted script tag cannot:
- A build marker that is true on every deployment. The plugin derives it from your WordPress version and active theme version and, when available, the git commit of the deploy (a SHA file or a
DEPLOYSEAL_BUILDconstant in wp-config.php), so the readiness report can confirm that the build testers used is the build you shipped. No theme file to remember to edit. - One install per site, multisite included. Every site keeps its own environment key and label, with the exact origins to register shown next to the field. Network activation is supported; settings stay per site.
- Platform inventory as evidence (optional). With a DeploySeal API key the plugin reports which plugins and themes, at which versions, were installed when a release was tested — WooCommerce included — and the report shows what changed since the last signed release. Useful for plugin updates and WooCommerce upgrade projects.
- Survives theme updates. The tag is enqueued by the plugin, not written into a theme, and never appears in wp-admin unless you choose that, and never on the login page.
Setup takes two fields. Create an environment for the site in DeploySeal, paste its public key into Settings DeploySeal, tick Enabled, save. The page then shows exactly what the site will send (origins to register, declared environment label, the build marker, the rendered tag) so you can confirm it matches. Everything else (environment label, build marker source, git SHA file, inventory) lives under Advanced and Platform inventory with sensible defaults.
What it sends. Only the widget tag and, if you enable it, the platform inventory. Visitor and customer data is never touched; the widget loads for everyone but only activates for invited testers on registered origins.
Requires a DeploySeal account. DeploySeal is currently in private pilot: request access at deployseal.com. The plugin is open source under MIT; issues and pull requests are welcome on GitHub. Documentation: deployseal.com/docs/wordpress.
External services
This plugin connects to DeploySeal, a hosted go-live sign-off service operated at deployseal.com.
- The widget loader. When the plugin is enabled with a site key, every public page includes
<script src="https://cdn.deployseal.com/ds-widget.js" async>with the site key, the declared environment label, the build marker and the plugin version asdata-ds-*attributes. The visitor’s browser downloads the widget from cdn.deployseal.com and sends a heartbeat (site key, page URL with sensitive query parameters removed, page title, environment label, build marker, widget version, installer) to api.deployseal.com on each page load. For invited testers only, the widget also sends the issues, screenshots and session replays they capture. - The platform inventory (optional, off until you add an API key). From your server, never from the browser, the plugin posts the list of installed plugins and themes (name, version, active or not), the WordPress and PHP versions and the build marker to
https://api.deployseal.com/api/v1/sites/{site key}/inventory, when you press “Send inventory now” and, if you turn on “Send inventory on a schedule”, every 6 hours.
DeploySeal terms of service and privacy policy.