Outcome
A master/source site can push a shared template, component, global style, or content release to a group of WordPress sites without manually repeating the same operation for every target.
Multisite Rollout
Push a shared release to many sites using groups and batch-aware workflows.
Video walkthrough
▶
Video walkthrough coming soon.
The YouTube embed will appear here.Risk level
High. High blast radius. Use groups, batches, dry runs, and per-site verification.
Before you start
- Each target is configured as a remote.
- Targets are organized into groups.
- You know which sites should receive the release.
- Batch settings are ready for larger groups.
Steps
- Add remotes
Register every target site with tested credentials. - Create groups
Group targets by client tier, environment, region, or product line. - Create a group push workflow
Use the Push to All Sites template or a custom group workflow. - Run a group dry run
Check per-site failures before the actual push. - Execute in batches
Use batch processing for large groups or heavier payloads. - Review network activity
Check failed jobs, retries, and per-site results.
Screenshots
wp wpchangesync workflow run group-push --mode=dry_runnwp wpchangesync workflow run group-pushDo not treat all sites as identical
Per-site overrides, local media, and client-specific settings can make overwrite strategies risky. Keep the scope narrow unless a full rollout is intentional.Verify and recover
After completing this guide, verify the result in Activity and on the target site. Keep the pre-change export or backup until the release has been accepted. If anything looks wrong, stop further syncs, restore the affected item or integration from backup, and re-run with a narrower scope or safer conflict strategy.
How to find the workflow ID
Open Workflows in the admin UI and inspect the workflow details, or run wp wpchangesync workflow list. Use the ID from that list in workflow show and workflow run commands.