Back to blog
6 min read Content Sync

Syndicate Blog Posts from One WordPress Site to Several Sites

If you run several WordPress sites, such as regional shops, a company site and its blog, or sites for different brands, the same announcement often has to appear on all of them. Copying it by hand means uploading the images again and fixing every link. With Content Sync in Import Export by RockStarLab, one site becomes the main site: you write the post there and push it to the other sites, and later push the corrections the same way. Below are the setup and the routine, tested with one main site and two connected sites.

Free: pushing posts and pages to any number of connected sites. PRO: the same for custom post types and WooCommerce products.

Short Answer

  • Install the plugin on every site. On the main site, add each other site under Content Sync → Add New Site with its URL and API key.
  • Write the post on the main site, then push it to each site: Sync Content → choose the site → Push to Site.
  • To correct the post later, push again; Auto-match by Title finds the existing copy on each site, so it is updated, not duplicated.
  • Images and categories are copied, and links to the main site’s pages point to the same pages on each site.

Step 1: Connect the sites to the main site

The connections live on the main site only. For each site that should receive posts:

  1. On that site, open Import Export → Content Sync → This Site Configuration → Show Details and copy its API key.
  2. On the main site, click Add New Site, enter a name you’ll recognize (for example “Germany shop”), the site’s URL and the key, and click Save Connection.

The main site then lists all connected sites. Last Sync shows when each one last received or sent content, so a site that was skipped is easy to spot.

Connected Sites table on the main site with two sites, Sister site and Live, both Active, with their Last Sync times
All receiving sites are connected on the main site; Last Sync shows the last push to each.

How the key works and what a connection allows is explained in How Content Sync works.

Step 2: Push a new post to each site

  1. On the main site, publish the post as usual.
  2. On Posts, tick it (or several posts), click Sync Content, choose the first site and click Push to Site. In the block editor, Sync This Post in the sidebar does the same.
  3. In Map Posts for Sync, a new post shows Create New Post. Click Confirm & Sync.
  4. Repeat for the next site.
Sync Content window with 1 selected post and Sister site chosen in Select Site, with Push to Site and Pull from Site buttons
Choose the site, push, then choose the next site.

We pushed the post “Autumn Workshop Dates” from the main site to two sites. On both, it arrived with:

  • the same title, text, slug and publish status;
  • the category “Events”, created on each site because it didn’t exist there yet;
  • the featured image, uploaded to each site’s Media Library;
  • the link to the main site’s contact page changed to each site’s own contact page.

Each copy gets the ID that its site assigns; the IDs don’t have to match.

Step 3: Push corrections

We then added a third workshop date to the post on the main site and pushed it to both sites again. Auto-match by Title found the copy on each site (Update: Autumn Workshop Dates), and both copies showed the new date after the push. A correction made directly on one of the sites would be replaced by the main site’s version, so make all changes on the main site.

A push changes content on the receiving sites. Before the first push of many posts to a site, create a backup of it.

Things to decide before you syndicate

  • Duplicate content. Each copy is a normal post on its site with its own URL. Content Sync changes links to the main site into links to the receiving site, and this also applies to a canonical URL saved by an SEO plugin: in our test, the canonical URL on each copy pointed to the copy itself. If search engines should treat the main site’s post as the original, set the canonical URL on the copies in your SEO plugin after the last push, or write a shorter or translated version for each site. A later push replaces that setting with the main site’s value.
  • Titles. Auto-match pairs posts by title. Keep the title the same on all sites, or choose the post manually when you change it; see how Auto-match by Title works.
  • Site-specific details. A post with prices, addresses or opening hours that differ per site is better kept separate, or pushed once and then edited on each site and not pushed again.
  • Same text on many pages. For legal pages like a privacy policy with per-site details, see updating the same page on multiple sites.

With an AI agent

With several sites, an AI agent saves the repeated clicks. Connected to the main site through the WordPress MCP Adapter (see connecting Claude Code to WordPress), it can push to all connected sites in one request:

Push "Autumn Workshop Dates" to every connected site. Update the existing
copy where there is one, create it where there isn't, and give me a short
report per site.

In our run, the agent read the two connections with rsl-ie/connection-list, called rsl-ie/sync-auto-map for each site (it found the existing copy on both), started one rsl-ie/sync-push-start job per site and checked them with rsl-ie/sync-job-status. Report: both sites updated, 1 post each, and Last Sync on the main site showed the time of each push.

FAQ

Can I push one post to several sites at once?

From the screen, you push to one site at a time: choose the next site and push again. An AI agent can push to all connected sites in one request.

Do I need to add connections on every site?

No. Add all sites on the main site only, using each site’s URL and API key.

Will the images be uploaded to every site?

Yes. The featured image and images in the text are uploaded to each receiving site. Pushing the post again reuses the files that are already there.

What happens to links in the post?

Links to pages of the main site are changed to the same addresses on each receiving site. Links to other websites stay as they are.

Can the receiving sites change the post?

They can, but the next push from the main site replaces the post with the main site’s version.

Get the free plugin on WordPress.org.

Dmitriy
About author

Dmitriy

WordPress Developer with 15+ years of commercial experience. Elite Author on ThemeForest and creator of custom WordPress plugins. Passionate about clean code, performance optimization, and building useful tools for the WordPress community.

JOIN THE CONVERSATION

Comments 0

Have a question or a tip to share? Leave it below.

Leave a comment

Your email address will not be published. Required fields are marked *

We store your name, email and comment to show and moderate it; your email is never published. Spam protection is provided by Cloudflare Turnstile and profile pictures by Gravatar. See our Privacy Policy.


Try the plugin with no risks!

New users get 1 month with access to all premium features. Experience the most powerful WordPress data engine today.

Download Now
Get PRO for FREE