---
title: "Same Slug on Both Sites: What Content Sync Does and How to Free the URL"
url: "https://wpimportexport.com/sync-slug-conflicts-same-slug-wordpress-sites/"
description: "A post pushed to a site that already has the same slug gets -2. See how to give it the clean URL with a 301 redirect for the old post, step by step."
type: post
published: 2026-11-18T13:00:00+00:00
modified: 2026-11-18T13:11:42+00:00
categories: ["Content Sync", "Tutorials"]
tags: ["Content Sync", "Import Export by RockStarLab", "sync WordPress sites"]
docs_topics: ["Sync and migration"]
---

# Same Slug on Both Sites: What Content Sync Does and How to Free the URL

Seasonal pages come back every year with the same address: “holiday-menu”, “summer-sale”, “christmas-opening-hours”. When this year’s version is written on staging and last year’s post with the same slug is still on the live site, the push has to put the new post somewhere. Below: what [Import Export by RockStarLab](https://wordpress.org/plugins/import-export-by-rockstarlab/) Content Sync does in that case, and how to give the new post the clean address while last year’s link keeps working.

**Free:** Content Sync for posts and pages. **PRO:** the same for custom post types and WooCommerce products.

## Short Answer

- With **Create New Post**, the pushed post is added next to the existing one. The existing post is not changed, and WordPress gives the new post a free slug such as `holiday-menu-2`.
- To give the new post the original slug, change the slug of the old post on live first, then push the new post again as an update. It gets the slug it has on staging.
- WordPress redirects both old addresses (301), so links to last year’s post and to the temporary `-2` address keep working.

## The situation

The live site of a coffee roastery had last year’s post “Holiday Menu” with the slug `holiday-menu`, published on 20 November 2025. On staging, the team wrote “Holiday Menu 2026” and gave it the same slug, `holiday-menu`. The titles differ, so **Auto-match by Title** doesn’t pair them, and the mapping shows **Create New Post**:

![Map Posts for Sync: Holiday Menu 2026 from staging set to Create New Post](https://wpimportexport.com/wp-content/uploads/2026/11/01-mapping-create-new.webp)

_The titles differ, so the post is pushed as a new post._

## What the push does

We selected the post in **Posts** on staging, clicked **Sync Content**, chose the live site and **Push to Site**, and confirmed with Create New Post. On live:

- “Holiday Menu” kept its title, text and slug `holiday-menu`;
- “Holiday Menu 2026” was added as a second post with the slug `holiday-menu-2`, the next free slug WordPress chose.

Nothing was lost, but the new post has an address with `-2`, which isn’t what you want to share in a newsletter.

## Give the new post the original slug

1. On live, open last year’s post and change its slug in the post settings, for example to `holiday-menu-2025`, and update it.
2. On staging, push “Holiday Menu 2026” again. In **Remote Site Action**, choose its live copy (**Update: Holiday Menu 2026**), not Create New Post.

After the update, the new post had the slug `holiday-menu` from staging, because it was free now:

![Tables of slugs on the live site: after Create New the new post has holiday-menu-2; after renaming the old slug and updating, it has holiday-menu; old addresses redirect with 301](https://wpimportexport.com/wp-content/uploads/2026/11/02-live-slugs.webp)

_Free the slug on live, push again as an update, and both old addresses redirect._

WordPress remembers old slugs of a post. Opening last year’s old address led to `/holiday-menu-2025/`, and the temporary `/holiday-menu-2/` address led to the new post, both with a 301 redirect. To check many addresses after a move, see [building a 301 redirect map](https://wpimportexport.com/build-301-redirect-map-wordpress-url-export/).

If you want this year’s text to replace last year’s post instead, so the post keeps its address, map the staging post to “Holiday Menu” (Update) when you push. Then the old post’s content is replaced.

## Before you push

An update replaces the content of the live post you choose. Check the mapping before you confirm, and [back up the live site](https://wpimportexport.com/how-to-create-a-wordpress-website-backup-and-restore-it/) before you push many posts.

## With an AI agent

An AI agent connected to staging through the WordPress MCP Adapter (see [connecting Claude Code to WordPress](https://wpimportexport.com/connect-claude-code-to-wordpress-mcp/)) can do the second push once you’ve changed the old slug:

```
Push "Holiday Menu 2026" to the live site again as an update of its live copy.
```

In our run, the agent called `rsl-ie/sync-push` with the staging post ID and a mapping to the live post ID. The result was 1 updated, 0 created, 0 failed, and the post in the result had the slug `holiday-menu`, the same as on live afterwards.

## FAQ

### Can a push overwrite a different post just because the slug is the same?

No. With Create New Post a new post is added, and the existing one is left as it is. A post on live is only updated when you map to it.

### Why did the new post get “-2” at the end?

Slugs of posts must be unique, so WordPress added the next free number when the slug was taken.

### Does an update change the slug on live?

Yes, to the slug the post has on staging, if that slug is free on live. That is how “Holiday Menu 2026” moved from `holiday-menu-2` to `holiday-menu`.

### Do links to the old address break?

In our test both old addresses redirected with a 301 to the post’s new address.

### What if I push the same post with Create New Post twice?

The second push updates the copy made the first time, so there is still one copy on live.

## Related Guides

- [How Auto-Match by Title Works and When to Map Posts Manually](https://wpimportexport.com/auto-match-by-title-map-posts-between-sites/)
- [How to Copy Only New Posts from Staging to Production (Without Touching Orders and Users)](https://wpimportexport.com/how-to-copy-only-new-posts-from-staging-to-production/)
- [Sync Custom Fields and Yoast SEO Data Between WordPress Sites](https://wpimportexport.com/sync-custom-fields-yoast-seo-between-wordpress-sites/)
- [Build a 301 Redirect Map from Before and After URL Exports](https://wpimportexport.com/build-301-redirect-map-wordpress-url-export/)

Get the free plugin on [WordPress.org](https://wordpress.org/plugins/import-export-by-rockstarlab/).
