How to Change WordPress URLs Without Losing Traffic

Changing a WordPress URL is straightforward, but changing it without a redirect can leave visitors facing a 404 error and search engines pointing to the wrong address.

The safe approach is to record the existing URL, create the replacement, add a permanent redirect from the old address to the new one, update your internal links and test the result. If you plan to change the permalink structure across an established website, treat it as a small migration rather than a routine settings change.

What part of the WordPress URL are you changing?

Before making any changes, establish their likely reach. Three jobs that may appear similar can carry very different levels of risk.

WordPress provides its main URL options under Settings > Permalinks. Its permalink documentation explains the standard structures and custom options. An individual page or post slug can usually be edited in the block editor’s page or post settings.

Should you change an existing URL?

A shorter or neater URL is not automatically worth the disruption. Leave an established URL alone if the proposed change offers no clear benefit, particularly when the page already attracts traffic or has links pointing to it.

A change may be worthwhile when:

• the URL contains an old product, service or company name;
• the original slug is misleading, misspelt or unnecessarily long;
• your site uses an awkward structure inherited from an earlier build;
• you are consolidating several overlapping pages into one stronger resource;
• the URL no longer reflects the purpose of the page.

Google recommends using simple, descriptive words in URLs and separating words with hyphens. However, this guidance is best applied when creating new pages. It is not a reason to rename every existing URL purely for cosmetic purposes. You can review the principles in Google’s URL structure guidance.

How to change a single WordPress page or post URL safely

1. Record the old and new addresses

Copy the complete existing URL before editing anything. Then decide on the exact new slug.

Keep the new version concise, meaningful and easy to read. Use lowercase words separated by hyphens, and avoid adding dates unless the date is genuinely important to the content.

For example:

• Old: example.co.uk/our-range-of-wordpress-help-services/
• New: example.co.uk/wordpress-support/

2. Back up the website

A slug edit is normally a small change, but backups matter whenever redirects, plugins or server settings are involved. Confirm that you have a recent backup and know how it would be restored. If you are not certain that your backup works, follow our guide to testing a WordPress backup.

For important landing pages, online shops or larger URL changes, use a WordPress staging site to rehearse the process first.

3. Prepare a permanent redirect

A redirect automatically sends anyone requesting the old address to the new one. For a page that has moved permanently, use a server-side 301 or 308 redirect. Google recommends permanent server-side redirects when a URL shown in search results has changed.

You may be able to create the redirect through your hosting control panel, an SEO or redirection plugin, or your website support provider. Server rules can also be used, but do not edit files such as .htaccess unless you understand the server configuration and have a recovery route.

The redirect should lead straight to the closest relevant replacement:

Old URL → New URL

Do not send every changed or removed page to the home page. That is unhelpful for visitors and can be interpreted by search engines as a soft 404. Google’s redirect guidance provides more detail on permanent and temporary redirects.

4. Change the WordPress slug

Open the page or post in the WordPress editor. In the settings panel, find the URL or slug field, enter the new slug and save or update the page.

The exact label can vary slightly between WordPress versions and editor configurations. Be careful not to alter the page title, content or publication status unintentionally.

5. Activate and test the redirect immediately

Open a private or incognito browser window and enter the old URL. It should take you directly to the new page without displaying an error or passing through several addresses.

Then test the new URL independently. Check that:

• the page returns normally and displays the expected content;
• images, downloads, forms and buttons still work;
• the old URL reaches the new one in a single redirect;
• there is no redirect loop;
• the page is not accidentally set to noindex.

6. Update your internal links

A redirect protects old links, but your own website should link directly to the new address. Update navigation menus, buttons, blog links, image links, related-post sections and reusable templates.

Also check email templates, social profiles, advertising campaigns, downloadable PDFs and third-party listings that you control. Updating these links reduces unnecessary redirects and gives visitors the cleanest route to the page.

7. Check the canonical URL and sitemap

Your SEO plugin or website setup may automatically update the page’s canonical URL and XML sitemap, but do not simply assume this has happened. View the page’s SEO settings and confirm that its canonical points to the new address.

Check the XML sitemap as well. It should list the new URL rather than the old one. If the page is important, you can inspect the new address in Google Search Console and request indexing.

Changing the permalink structure across the whole website

Changing Settings > Permalinks can alter every post URL in one action. Clicking Save Changes is easy; dealing with hundreds of old addresses is the difficult part.

Before changing a site-wide structure:

1. Export or crawl the current URLs.
2. Create an old-to-new URL map.
3. Take and test a full backup.
4. Rehearse the change on staging.
5. Prepare direct permanent redirects.
6. Check for duplicate slugs or unexpected category paths.
7. Update internal links, canonicals and the sitemap.
8. Test representative pages, posts, categories and pagination.

A predictable change, such as removing dates from every post URL, may allow a carefully constructed redirect rule. Exceptions still need to be checked individually. Google’s URL migration guidance recommends mapping old URLs, updating internal links, testing redirects and submitting the new sitemap.

Some movement in search visibility can occur while changed URLs are recrawled and processed. A correct migration helps search engines understand the move, but nobody can guarantee that rankings will remain completely unchanged.

Common URL-change mistakes

• Changing the slug without a redirect: Existing bookmarks, search results and external links lead to a 404 page.
• Using a temporary 302 redirect for a permanent move: This sends the wrong long-term signal about the old URL.
• Creating redirect chains: An old URL redirects to another old URL before reaching the current page.
• Redirecting unrelated pages to the home page: Visitors do not reach the information they expected.
• Forgetting menus and buttons: Your website continues sending visitors through avoidable redirects.
• Changing every URL for appearance alone: The work and risk may outweigh the limited benefit.

How long should you keep the redirect?

Google advises retaining migration redirects for at least a year. For useful old URLs that have backlinks, appear in printed material or may still be bookmarked, keeping the redirect indefinitely is often the more practical choice.

Review your redirects periodically rather than deleting them automatically. Remove one only when you are confident that the old address is no longer needed and will not leave visitors stranded.

Need help changing WordPress URLs?

A single page change can be manageable, but permalink migrations and large redirect maps deserve careful preparation. ThriveWP can help investigate the safest approach, implement redirects and check the website after the change. Talk To Us about your WordPress support needs or explore our WordPress SEO and maintenance service.

For more practical WordPress guidance, subscribe to the ThriveWP newsletter and get the free site-care guide.