[mirrorpress_documentation_nav]
SirSync allows you to deploy content from wherever you’re editing it, so you don’t need to navigate to a separate deployment screen.
Where you’ll find the deployment controls depends on the content editor you’re using:
For supported content types, you’ll see two deployment options:
Deployments can be started immediately or scheduled for a future date and time.
When you start a deployment, SirSync packages the selected content and securely transfers it to the connected website.
SirSync automatically determines whether the content already exists on the destination website. If it has previously been synchronized, the existing content is updated. If no connected item exists, SirSync attempts to locate an existing item with the same URL path or slug before creating a new one.
During the deployment, SirSync also synchronizes any supported related data associated with the content, including media, SEO metadata, custom fields, taxonomies, page builder data, and other supported integrations.
Once the deployment completes successfully, the relationship between the two pieces of content is stored so future pushes and pulls update the same content rather than creating duplicates.
SirSync gives you control over what information is synchronized between your websites. Each setting can be configured independently for Push and Pull operations, allowing each direction to behave differently.
For example, you may want content pushed from your Stage site to update publication status on Production, while preventing pulls from Production from changing the status on Stage.
Deployment settings are available under Tools > SirSync.
Every supported content type includes an Enable Sync option.
When enabled, SirSync will allow synchronization of that content type between paired websites.
When disabled, deployment controls for that content type are hidden and SirSync will ignore those items during deployments.
This allows you to decide exactly which content types should be managed through SirSync.
Several synchronization options can be configured independently for pushes and pulls.
| Setting | Description |
|---|---|
| Update Post Status | Synchronizes the publication status (Draft, Pending, Private, Published, etc.). |
| Update Post Slug | Updates the destination URL slug to match the source. |
| Update Visibility | Synchronizes the post visibility (Public, Private, Password Protected). |
| Update Published / Scheduled Date | Updates the publish date and scheduled publication time on the destination site. |
| Sync SEO Meta | Synchronizes supported SEO metadata, including Yoast SEO and All in One SEO. |
| Sync Custom Fields (Post Meta) | Synchronizes WordPress custom fields and supported plugin metadata, including Advanced Custom Fields and other integrations. |
Each option has separate Push and Pull controls, allowing you to decide exactly what information is synchronized in each direction.
SirSync automatically synchronizes WordPress core fields and includes built-in support for many popular plugins, including Advanced Custom Fields (ACF), WooCommerce, Yoast SEO, and All in One SEO.
However, many themes, custom plugins, and third-party integrations store their own metadata. Since SirSync can’t predict every custom meta key that may exist, Scan Keys on This Site searches the selected post type for additional metadata keys that are currently being used.
After the scan completes, any newly discovered keys become available in the synchronization settings, allowing you to choose whether they should be included in Push and Pull deployments.
You may want to run a scan after:
For example, if a WooCommerce extension stores its own product settings as custom post meta, running a scan will discover those keys so you can choose whether to synchronize them.
Now that you understand how deployments work and how to configure synchronization settings for Push and Pull operations, you’re ready to automate your content releases. Continue to Scheduled Deployments to learn how to schedule deployments for a future date and time, queue multiple deployments in advance.
