Easy ContentPush lets you safely and easily migrate content — including ACF fields, media files, featured images, taxonomy terms, and SEO metadata — directly from your staging/dev site to your production site.

A Push content button appears in the editor sidebar for all supported post types. When you click the button, the plugin instantly transfers the post, including all custom fields and media references, to your configured target site using a signed REST API request.

This plugin must be installed on every site that sends or receives content. Configure Settings Easy ContentPush on each site: target URL and push key for sending, sender site URLs and receive key for receiving. Requests are authenticated with HMAC-SHA256 signed REST requests.

Important: Your production site should have the same post types, taxonomies, and ACF field groups as your staging/dev site. This plugin does not register or sync post type or field definitions—it only pushes content and metadata.

Features

Manual Push content button for posts, pages, and custom post types (CPTs)
One-click transfer of all post content, including ACF Flexible Content, Relationships, Repeaters, and Groups
Seamless handling of featured images and other media (no duplication)
Taxonomy and term synchronization (including custom taxonomies)
Yoast SEO metadata transfer
Respects page templates and parent/child hierarchies
Supports scheduled posts, files, SVGs, and more
Customizable settings panel for site URLs, sync keys, and allowed post types
HMAC-signed REST API and connection test from the settings screen

Usage

Install and activate Easy ContentPush on each WordPress site in your workflow.
On a site that receives content: open Settings Easy ContentPush, add Sender site URLs, click Generate new key, and copy the Receive key.
On a site that sends content: enter the Target site URL, paste the target’s Receive key as your Push key, choose post types, and use Test connection.
Edit a post and click Push content in the editor sidebar.
Content, ACF data, media references, taxonomies, and SEO metadata are transferred while preserving status (draft, scheduled, published, etc.).

For chains (site A B C), configure push and receive sections independently on each middle site. Multiple senders may use the same receive key on the receiver.

Note: Make sure all ACF field groups, post types, and taxonomies exist on both sites for proper mapping.

Support

For support, questions, or feature requests, contact [email protected] / [email protected]
Contributions are welcome on GitHub.

License

This plugin is licensed under GPLv2 or later. You are free to use, modify, and distribute this plugin under the terms of the license.