Does Republishing Old Blog Posts Hurt SEO? What WordPress and Google Do With the Old URL
Republishing old blog posts does not hurt SEO by itself: outside Google News, no Google text we read forbids it, and a post republished at its own address keeps the links pointing to it. What puts rankings at risk is what happens to the post's address: a URL moved without a 301 redirect, a post taken offline to rewrite it, or a new copy beside the original or in its place.
The short answer
Whether republishing an old blog post hurts SEO depends on what happens to its address, not on the word.
Keep the URL and nothing needs redirecting; change a published post's slug and WordPress redirects the old one itself. A post switched back to draft answers 404. Of two copies, Google shows one; a replacement without a redirect usually takes longer to be seen as relevant.
On the text, Google's advice, dated December 10, 2025, for a small drop in position is to avoid "making radical changes if your page is already performing well". What a rewrite does to rankings: AI rewriting and rankings. Whether to move the date too: the publish date question.
Five things republishing can mean, and which ones move the URL
"Republishing" covers at least five gestures, and only one gives a post a new address by default.
| What you do | The address | What WordPress does | What Google does |
|---|---|---|---|
| Update the post in place | Stays, unless it carries a date that moves | Keeps the slug; redirects a moved dated address if still published | Nothing to move |
| Switch it to draft, edit, publish again | Stays, but answers 404 meanwhile | 404 for everyone but you, logged in | Deindexes it if crawled meanwhile |
| Edit a copy, then replace the live post | Stays, never down | Keeps the live post online meanwhile | Nothing to move |
| Publish it again as a new post | A new URL by default | No redirect unless you add one, or its 404 guess finds the new post | No redirect: usually slower to see the new URL as relevant; a 301: shows the new URL instead; both online: shows one |
| Republish it on another site | Yours stays | Nothing | May rank the copy above yours (FAQ) |
Of the ten pages we read from Google's results for this question on September 21, 2026, seven use the word, for five different things, including a social media share, which leaves the address alone; three never use it.
What WordPress redirects on its own, and what it forgets
WordPress already redirects the old address of a published post whose slug you change; the traps are where it keeps no memory.
Since WordPress 2.1, and still in 7.1, it keeps the old slug and sends requests that would 404 on it to the current address, with a 301 and no expiry date. Since version 4.9.3, dated permalinks get the same memory: change the date of a post that stays published, and its old dated address redirects too, matched on year, month and day.
It forgets in five cases:
- a page: pages get no such memory;
- a slug or date changed while the post is a draft, or in the save that unpublishes it;
- a new post: the memory stays with the old one;
- a date pushed into the future: the post turns scheduled, and the old dated address never redirects;
- an old slug taken by another post, which the address then serves.
On a 404, WordPress also guesses, redirecting to a published post whose slug starts with the one requested: redirects nobody set, not always to the right post.
None of the ten pages we read on September 21, 2026 says WordPress redirects by itself; one, on dated permalinks, tells you to create the redirect yourself. Before adding one, open the old address: if one 301 already lands on the right post, add nothing.
What Google does with a URL that moved
Behind a permanent redirect, a moved URL loses no PageRank, Google's site-move documentation says, and the redirect should generally stay at least a year.
To change a page's URL in search results, Redirects and Google Search, dated April 14, 2026, says: "we recommend that you use a permanent server-side redirect whenever possible." The PageRank line is in How to move a site, dated August 20, 2026, where a move takes place "on a per-URL basis":
"301 and other permanent redirects don't cause a loss in PageRank."
The same page: "Keep the redirects for as long as possible, generally at least 1 year." For readers, it adds, consider keeping them indefinitely. Rankings can still move: when the URLs of existing pages change, "you may experience ranking fluctuations while Google recrawls and reindexes your site", warns Debugging drops in Google Search traffic, dated December 10, 2025: on a medium-sized site, Google generally notices after a few weeks. No Google text we read on September 21, 2026 says how long fluctuations last for a single URL.
Your part, as the site-move guide asks: point internal links at the new URL, and redirect straight to the final URL; a chain should ideally stay within three hops.
None of the ten pages we read on September 21, 2026 quotes or links what Google wrote about redirects or moved URLs. The rule stays in our guide to updating old blog posts in WordPress: leave a ranking post's URL alone unless you must.
Republishing as a new post: what the old URL takes with it
Republishing as a new post is the one gesture that gives an old post a new address by default, and Google News guidelines forbid one way of doing it.
Delete the old post without a redirect and its address answers 404, unless WordPress's guess catches it, then leaves the index while its links still point there. Without redirects, search engines usually take a bit more time to see the new URL as more relevant, John Mueller said in the April 2024 office hours, about a social media page's new URL.
Leave the old post online and you have duplicate content. Some is normal, says What is canonicalization, dated August 20, 2026, and "it's not a violation of Google's spam policies"; but "Google uses the canonical page as the main source to evaluate content and quality," and its pick may not be yours.
Google News has the written rule: Google's Publisher Center help, undated and without a Creative Commons license, rules out publishing a lightly edited copy of a story, then deleting and redirecting the original to it. On September 21, 2026 we found no Google text outside Google News on reposting your own post on your own site; Google's spam policies, dated August 28, 2026, use "republishing" only for other sites' content.
The rule: same need, same post, updated in place. A genuinely new post redirects the old one it replaces, or leaves both if they differ: by Google's definition, a canonical is for duplicates. Removing a post for good is another decision: prune or refresh.
Taking a post offline to rewrite it
The careful-sounding method (unpublish, rewrite, publish again) takes the page off your site: a WordPress draft answers 404 to visitors and to Google, while you, logged in, still see it.
So do pending and private posts. How HTTP status codes affect Google's crawlers, dated February 4, 2026, says URLs that are "already indexed and return a 4xx status code are removed from the index". No current Google text we read says how fast a returning address regains its place. A future date is no way around it: the post turns scheduled and answers 404 until then.
The safe way keeps the post published: work on a copy, or use a tool that keeps it online until approval. None of the ten pages we read on September 21, 2026 warns that a post taken offline answers 404; two recommend or offer a step that takes it offline.
What a republishing tool should put in writing
A republishing tool should state in writing what it changes and what it leaves alone. Our main guide's test, extended to six questions; Unstale's answers:
- Same post, same slug? It publishes into the same post and never writes the slug; only a year in the title can change, from Balanced up.
- Online during the work? It refuses to start on a post that is not published, and a refresh never changes the post's status.
- Review before publishing? Nothing goes live before you approve the diff, unless automatic publishing, off by default, is on; a consolidation always waits.
- The version from before? A WordPress revision in the block and classic editors and on Divi, with revisions on; on Elementor and SeedProd, whose layout WordPress does not version, Unstale's own copy for Restore. A WordPress revision never holds the URL or the date.
- Links in the post? They rest on an instruction to the model, at Maximal to keep those still relevant, and on your review; no code compares them before and after. The diff compares text, not link targets, so a changed target alone shows as identical content. On a post that ranks, check its links before approving, or crawl it after publication.
- What does it not do? No canonical, no noindex, no sitemap entry, no reindexing request. Its one redirect follows a Pro consolidation, when you retire the absorbed post: it goes to draft, and its address gets a 301 to the post that absorbed it, on a 404 only, in one hop, while that post stays published and the free plugin is active. Other posts' links to it are not rewritten: update them as for any moved URL.
Whether and when it moves the date is the date question; the mechanism: rewrite old posts with AI.
Questions people ask about republishing old posts
Can I republish my posts on another site without hurting mine?
Yes, if you accept that another site or a publishing platform may rank above you: John Mueller, asked about a platform's copy in the June 2024 office hours, called it "a business decision on your end." If only yours should rank, the other site should block indexing of its copy: since May 2023, Google's documentation prefers that to a canonical.
My old URL still shows in Google after the redirect. Is something wrong?
No. Google tracks both addresses, and the old one, usually an alternate name of the new, can still show in results for a while, says Redirects and Google Search, whose example is a domain move. Keep the redirect.
Is a 302 redirect enough when a post moves for good?
No. With a temporary redirect, Google tends to keep showing the old address and does not read it as a canonical signal. Redirects and Google Search: "Use permanent redirects when you're sure that the redirect won't be reverted."
Does changing a post's title change its URL in WordPress?
No. Updating a published post keeps its slug unless you edit it; WordPress builds one from the title only when the field is empty, as at first publication. What a new title does to rankings is another question.
Should I change a post's slug to add my keyword?
Rarely. Google's SEO Starter Guide says keywords in the URL path alone have "hardly any effect beyond appearing in breadcrumbs", and a moved URL must be recrawled. If you do it, WordPress redirects a published post's old slug; on a page, add the 301 yourself.
Do I need to ask Google to reindex the old URL and the new one?
Not the old one: Googlebot follows a permanent redirect, and Google reads it as a signal that the target should be canonical. For the new one, a request is optional, has a quota and "does not guarantee that inclusion in search results will happen instantly", or at all; hosted WordPress usually submits new content itself, Google notes.
Refresh in place, and keep the address
Run a refresh on a post that ranks: it stays published, keeps its slug and, on default settings, waits for your review with its diff. Check its links before you approve. The free plugin is in the WordPress plugin directory; Pro is on the pricing page.
Quoted material from Google Search Central and Google Crawling Infrastructure is used under the Creative Commons Attribution 4.0 License. Sources: "Redirects and Google Search", "How to move a site", "Debugging drops in Google Search traffic", "What is canonicalization", "Ask Google to recrawl your URLs" and "Search Engine Optimization (SEO) Starter Guide", Google Search Central documentation; "How HTTP status codes affect Google's crawlers", Google Crawling Infrastructure documentation; "June 2024 Google SEO Office Hours Transcript", Google Search Central.