Blog / WordPress /

How to validate WordPress redirects after changing a permalink

The old slug was awkward, so you changed it. The new page loads. Job done.

Then a bookmark, a search result or a link in an old article sends someone to a not-found page. Changing the address is the easy step. Checking the route from every old reference is the part that actually protects visitors.

A redirect should take people from an obsolete URL to the closest relevant destination. Your review should also confirm that the site’s own links and canonical signals use the new address directly.

Record the old and new URLs

Before changing a permalink, copy the existing URL and note the intended new one. Record why the change is needed and whether the page has links, traffic or references worth preserving. If several pages are moving, keep a mapping rather than relying on memory.

Choose the destination based on what the old page offered. A revised article redirects to its new URL. Merged content redirects to the page that now answers the same need. Don’t send every removed URL to the homepage just to avoid a 404. That leaves visitors wondering whether the page still exists. I’d rather show an honest 404 than a homepage redirect that pretends to help.

WordPress may create or update a redirect for you, depending on the setup, but it varies with configuration and plugins. Check what your site actually does. Don’t assume the permalink change took care of it.

Test the redirect itself

After publishing, open the old URL and confirm it reaches the intended destination. Check the response code and the final URL with a browser or redirect checker. The visitor should not pass through unnecessary hops or a loop.

Test realistic variations: trailing slash, uppercase letters, URL-encoded characters and the preferred hostname. One format can work while another old version fails. Don’t test every imaginable pattern unless there’s evidence the site uses them. Focus on real references and the platform’s conventions.

Check that the final destination returns a successful page and contains the expected content. A redirect to a page that is itself missing, blocked or unrelated is not a successful migration.

Update internal signals

Search the site for links to the old permalink. Update navigation, related links, buttons, category listings and important article references so they point straight to the new URL. The redirect is there for external links. Your own links shouldn’t make visitors take a detour.

Inspect the canonical tag on the new page. It should identify the preferred address according to the site’s convention. Check the sitemap and any structured data or feeds that include the URL. If a plugin or theme generates those values, test the published output instead of trusting a setting label.

If the page appears in a WordPress archive or RSS feed, verify that the updated link is used there too. A page can be correct in the editor while a cached feed or plugin output still contains an old destination.

Check the redirect implementation

Find where the redirect lives: a WordPress plugin, hosting configuration, server rule or platform feature. Don’t add duplicate rules in several places without knowing how they interact. Keep a note of the owner and the reason, so a future editor doesn’t delete it as unexplained clutter. On the client sites I manage, I keep that note in the same log as the change itself.

Test for chains and loops. A changed URL that redirects through an earlier permalink before reaching the current page adds complexity and can make future changes harder. If a chain exists, update the rule so the old address reaches the current destination directly, after confirming this is safe for other routes.

Use a staging environment for broader rule changes when available. Back up relevant configuration and know how to reverse the change if a shared rule affects more pages than intended.

Monitor and document

After the change, check Search Console or crawl data for old URLs that still appear, remembering that reports lag. An old URL in a report doesn’t mean the redirect is broken. Test the URL and look at the actual response.

Record the date, old path, destination, test result and any follow-up. Keep the permalink map with the site’s migration or content records. If the page changes again, this history helps someone understand why the route exists.

The old address may be present in emails, social posts, partner sites, saved documents or search results. The redirect helps people who still use those references, even after internal links are updated. If a high-value external link points to the old URL, keep the destination relevant and stable rather than removing the redirect because the new page works.

Check whether a permalink change affects a feed, sitemap or published link preview. These sources may update at different times. If the page has a canonical that still uses the old address, correct the underlying source and inspect the live output. A redirect and canonical should not send conflicting signals about the preferred version.

Add the change to a shared URL log if the site has one. Include the original address, current destination and reason. That record is useful during a later redesign, when a team may otherwise remove a redirect without knowing what it protects.

A permalink change is finished when old visitors reach the right content and the site itself points to the new URL. Next time you change a slug, paste the old URL into a fresh browser tab before you close the editor. Which old WordPress link would you test first?