How to set up redirects correctly when you change a post URL
Changing a WordPress post URL can look like a two-minute edit, but the old address may be bookmarked, shared in newsletters, indexed by Google, or linked from another site. A correct 301 redirect sends that traffic to the replacement while preserving the path visitors already know. Knowing how to set up redirects correctly when you change a post URL is therefore part of site maintenance, not cosmetic housekeeping.
Plan before pressing Update. Record the current address, decide the final destination, and find internal links that point to the post. Australian readers often discover content on a phone while commuting on public transport in Sydney or Melbourne, so a redirect loop, broken page, or slow detour is immediately visible. Keep the destination URL stable while you edit; repeated slug changes create avoidable chains and make troubleshooting harder.
Choose the right redirect
A permanent move to a new post address normally calls for an HTTP 301 redirect. It tells browsers and crawlers that the old URL has moved for good. Use a temporary response only when the move is genuinely temporary, such as during a short campaign test. Each old address should point directly to one final page.
| URL change | Recommended response | Reason |
|---|---|---|
| Permanent move with equivalent content | 301 redirect | Preserves the intended destination and search signals |
| Temporary test or seasonal version | 302 redirect | Signals that the original address may return later |
| Several old URLs for the same content | Separate 301 redirects | Keeps every old address relevant without long chains |
| No suitable replacement | 410 response | Clearly indicates that the resource is permanently unavailable |
Before applying a rule, decide which situation matches your change. Changing a post’s slug does not automatically create a redirect in WordPress. Also avoid sending the old address through several intermediate URLs. A visitor should reach the final page in one hop, and the final URL should return a normal 200 response.
Prepare the new URL and site links
Choose a descriptive, lowercase slug with words separated by hyphens. Keep it short enough to read aloud and avoid unnecessary dates, campaign names, or repeated category labels. If the content and purpose remain the same, a modest slug improvement is usually enough. Changing the title, categories, publication date, domain, and URL together makes the migration harder to isolate if something breaks.
WordPress may update some database links when you change a permalink, but it will not reliably update every reference. Search the site for the old slug in posts, pages, navigation menus, widgets, footers, image captions, and reusable blocks. If the post supports a broader topic cluster, update links from your supporting pillar page as well as from related articles. Also check attachment pages, PDFs, and embedded media that may reveal the old address.
Protect readers and search engines
A redirect should preserve the visitor’s original intent. Someone clicking an old link for a WordPress tutorial should arrive at the updated tutorial, not a general homepage or an unrelated promotion. Predictability reduces friction, rather like a consistent routine makes recurring actions easier in daily life. Keep the same subject, format, and level of usefulness wherever possible.
If the page has been substantially rewritten, consider whether it should retain the same URL. A new target can be appropriate when the article addresses a different search intent, but changing a slug merely for aesthetics can discard accumulated authority. When the replacement remains equivalent, update the page title, opening text, internal links, canonical tag, and structured data so that everything confirms the same destination. This consistency helps readers and search engines understand that the move was deliberate.
Configure redirects for your stack
The redirect must be installed in the environment that controls your web server. On Apache or LiteSpeed hosting, this may mean adding a rule to the .htaccess file. Nginx requires configuration in its server block, while managed hosts may provide a control panel or caching layer for URL rules. WordPress plugins can also create redirects, but use one clear method rather than combining a plugin rule with a manual server rule that produces duplicate responses.
Test the destination in a private browser window while logged out, since administrator tools and plugins sometimes affect what logged-in users see. Confirm that the old address returns a 301 response, the new address returns 200, and the browser lands directly on the final page. Clear the site and CDN caches, then repeat the test. Watch for redirect loops, HTTPS mismatches, dropped query parameters, and chains created by overlapping rules.
Update campaigns and business records
Begin with internal references. Replace the old URL in navigation, calls to action, related-post blocks, email signatures, and footer links. Update hard-coded links in custom HTML, CSS, JavaScript, PDFs, and media captions as well. These references may not appear in the normal WordPress editor, yet they can still direct visitors away from the new address or leave outdated links visible in the browser.
Review the commercial purpose of the post before changing a URL used in paid media. A revenue stream comparison can help confirm that the destination still matches the offer described in advertisements, affiliate emails, and social posts. Replace tracked links with direct new URLs where possible, then use a redirect for external references that cannot be edited immediately. Do not forget autoresponders, customer support materials, and links supplied to partners.
Australian small businesses often rely on WordPress and WooCommerce, so old post addresses can appear in Google Business Profile campaigns, local directories, invoices, and booking pages. Check that Australian-dollar pricing, GST information, and product destinations remain accurate after the move. If the page collected email addresses, preserve its privacy notice and consent records; the Privacy Act 1988 and Spam Act 2003 continue to apply when forms and electronic messages remain connected to the destination.
Verify the move and preserve a rollback
After publishing, test the old URL again and examine the server logs. Add the new address to your XML sitemap, confirm its canonical tag, and submit it through Google Search Console and Bing Webmaster Tools. Review analytics for referral traffic, search impressions, and unexpected 404 errors over the following days. If the post is time-sensitive, update social profiles and scheduling tools immediately rather than waiting for the next crawl.
Keep a record of the old URL, final destination, rule location, and test results. Back up the server configuration before editing it, and retain the old redirect until the new page has been indexed and any important backlinks have been checked. As your concrete next step, put the current and proposed URLs into a staging test, create one 301 rule between them, and confirm that the old address reaches the intended replacement in a single hop before changing the live site.