usdigitalmarketingindex.com SEO
What SEO risks arise when an unchanged article is republished at a new URL?
Updated November 15, 2026
Three risks: the old and new URLs exist together as duplicates and Google chooses between them, links and history that belong to the old URL are not carried to the new one, and internal links and the sitemap go on pointing at the address you meant to retire. All three come from the same cause, which is publishing the copy without deciding what happens to the original. If the old URL is redirected to the new one in the same release, the move is routine. If both stay live, the outcome is left to Google’s canonical selection, which the publisher can influence and cannot dictate.
Old versus new URL status
After republishing, the two URLs can be in one of four states. Only the first is a clean outcome.
Old URL New URL Result
----------------- --------------- ---------------------------------------------
301 redirect --> 200, live Preferred: one page; the old address forwards
200, live 200, live Duplicate: Google clusters them and picks one
200, canonical --> 200, live Hint given; both still load for visitors
404 or 410 200, live Old links and bookmarks break; history is dropped
Decision points:
Is there any reason for the old URL to keep loading?
no -> redirect it (first row)
yes -> Is the reason temporary, such as a campaign still pointing at it?
yes -> canonical to the new URL now, redirect on a set date
no -> the page was not moved; reconsider republishing
On the second row, Google’s documentation describes what happens: where it “finds multiple pages that seem to be the same or the primary content very similar, it clusters them together”, and then chooses one as canonical (Google’s explanation of canonicalization). The page chosen may be the old one, in which case the new URL you wanted found is the one left out of results.
Canonical and redirect choices
Google lists the ways to indicate a preference “in order of how strongly they can influence canonicalization”, with redirects first, as “A strong signal that the target of the redirect should become canonical”, then rel=”canonical” annotations, also a strong signal, then sitemap inclusion, a weak one (Google’s guidance on consolidating duplicate URLs).
| Method | What visitors experience | When to use it |
|---|---|---|
| Permanent redirect from old to new | Sent to the new URL | The default for a moved article |
| Canonical on the old page pointing to the new | Both pages load | Only when the old URL must stay reachable for a time |
| Removing the old page with no redirect | An error page | Not for a moved article; it discards links pointing at the old address |
| Leaving both with no signal | Both pages load | Never deliberately |
Whatever is chosen is a preference. The canonicalization documentation states that “indicating a canonical preference is a hint, not a rule”, and that Google “may choose a different page as canonical than you do”.
Two things to avoid. Do not add noindex to the old copy as a way of choosing between the two. The same documentation advises against using noindex to prevent canonical selection within a site. And do not send conflicting signals, such as a canonical pointing one way while the sitemap lists the other URL.
These choices apply to two URLs on one site. When the second copy sits on someone else’s site, the available controls differ, and they are covered in the guide to managing articles syndicated to third-party websites.
Internal link and sitemap updates
A redirect handles visitors. The site’s own references still need correcting.
- Update internal links to point at the new URL directly.
- Replace the old URL with the new one in the XML sitemap.
- Make the new page’s canonical tag point to itself.
- Update any structured data, social tags, and feeds that carry the old URL.
- Check navigation, related-article modules, and email templates.
Leaving internal links on the old address means the site itself keeps declaring the retired URL, which works against the preference you set.
How to verify chosen index URL
Check the result in Search Console once the pages have been recrawled.
- Inspect the new URL. Look at the canonical Google selected. It should be the new URL.
- Inspect the old URL. It should be reported as a redirect, with the new URL as its target.
- In the performance report, watch the two URLs over the following weeks. Impressions should move from the old to the new.
- Search for a distinctive sentence from the article and note which URL is shown.
If Google has selected the old URL as canonical while you want the new one, look for the cause among your own signals: a missing redirect, internal links still pointing to the old address, the old URL in the sitemap, or a canonical tag carried over unchanged from the old page.
Before republishing at all, ask whether the new URL is needed. An article that is unchanged gains nothing from a new address. The reasons that justify a move are concrete: the old URL states something false, the site’s structure has changed, or the article is being merged into a different section. A new date in the address or a preference for a different path does not justify one.
There is also the question of dates. Republishing an unchanged article with a fresh publication date presents old content as new. If nothing was revised, the original date stays.
This guide covers one article moving within a site. Moving a whole site to a new domain involves the same principles at scale, with additional steps, described in the guide to preserving organic value from backlinks during a domain migration.
The preferred outcome, documented: one live URL, the old address redirecting to it, every internal reference updated, and Search Console confirming the new URL as the canonical.
Add your comment to this answer