# Redirect Old URLs in WordPress: 7 Essential, Safe Checks

Source: https://hostreta.com/2026/10/redirect-old-urls-wordpress/

To redirect old URLs in WordPress after a domain change, map each old address to its matching new page and use a permanent server-side redirect where possible. You moved your WordPress site to a new domain. The site looks perfect, but every link pointing to your old address — from Google, social media, other websites, and bookmarks — now needs to send people to the right place. If it doesn’t, you lose traffic, rankings, and sales.

This guide shows how to redirect old URLs in WordPress after a domain change: why forwarding rules matter, server-level and plugin methods, how to fix redirect chains, and how to monitor 404 errors.

Table of Contents

[Toggle](#)

- [Why forwarding rules protect traffic](#Why_forwarding_rules_protect_traffic)
- [Server-level forwarding rules with .htaccess](#Server-level_forwarding_rules_with_htaccess)
- [Redirect old URLs in WordPress with a plugin](#Redirect_old_URLs_in_WordPress_with_a_plugin)
- [Finding and fixing redirect chains](#Finding_and_fixing_redirect_chains)
- [Testing and monitoring 404s](#Testing_and_monitoring_404s)
- [Tools and hosting that help](#Tools_and_hosting_that_help)
- [Key takeaways](#Key_takeaways)
- [Before you redirect old URLs in WordPress: 7 checks](#Before_you_redirect_old_URLs_in_WordPress_7_checks)
- [Build a redirect map before writing a wildcard rule](#Build_a_redirect_map_before_writing_a_wildcard_rule)
- [Troubleshoot when you redirect old URLs in WordPress](#Troubleshoot_when_you_redirect_old_URLs_in_WordPress)
- [The old domain shows a certificate warning](#The_old_domain_shows_a_certificate_warning)
- [The browser reports too many forwarding rules](#The_browser_reports_too_many_forwarding_rules)
- [The redirect reaches the wrong page](#The_redirect_reaches_the_wrong_page)

- [Verify results after you redirect old URLs in WordPress](#Verify_results_after_you_redirect_old_URLs_in_WordPress)
- [Frequently asked questions](#Frequently_asked_questions)
- [Do I need a redirect plugin if I already have server rules?](#Do_I_need_a_redirect_plugin_if_I_already_have_server_rules)
- [Can DNS alone redirect old URLs in WordPress?](#Can_DNS_alone_redirect_old_URLs_in_WordPress)
- [Will forwarding rules guarantee that rankings stay unchanged?](#Will_forwarding_rules_guarantee_that_rankings_stay_unchanged)

- [Choose the redirect layer your team can maintain](#Choose_the_redirect_layer_your_team_can_maintain)
- [A practical redirect test matrix](#A_practical_redirect_test_matrix)
- [Inspect a redirect without relying on browser memory](#Inspect_a_redirect_without_relying_on_browser_memory)
- [Handle query strings, files and changed structures carefully](#Handle_query_strings_files_and_changed_structures_carefully)
- [Plan rollback before launch day](#Plan_rollback_before_launch_day)
- [Maintain the redirect after the move](#Maintain_the_redirect_after_the_move)
- [Define acceptance criteria for the redirect project](#Define_acceptance_criteria_for_the_redirect_project)

## Why forwarding rules protect traffic

- Search rankings: 301 or 308 forwarding rules signal a permanent move. Correct forwarding rules help Google understand the new URL, but do not guarantee unchanged rankings during a migration.

- Backlinks: links from other sites keep their value instead of hitting 404 pages.

- Visitors: people using old bookmarks or links in emails still reach the right page.

Planning the move? Start with [Domain Migration SEO: Keep Rankings After a Rebrand](https://hostreta.com/2026/10/domain-migration-seo/).

## Server-level forwarding rules with .htaccess

If the URL paths are the same on both domains, one rule on the old domain can redirect everything. On Apache or LiteSpeed hosting, add this to the old domain’s .htaccess file:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?olddomain\.com$ [NC]
RewriteRule ^(.*)$ https://newdomain.com/$1 [R=301,L]
This sends olddomain.com/any-page/ to newdomain.com/any-page/ with a single 301 redirect. Server-level rules are fast because WordPress doesn’t need to load.

On Nginx servers, the equivalent goes in the server configuration — ask your host if you don’t manage the server yourself. Always back up .htaccess before editing it.

## Redirect old URLs in WordPress with a plugin

When page paths changed, or you want a dashboard instead of code, use a plugin on the site that receives the old traffic:

- Redirection: free, popular, and logs 404 errors so you can add forwarding rules for them.

- SEO plugin redirect managers: check whether your installed edition includes this feature before adding another plugin.

Best practice: redirect page to page. An old pricing page should go to the new pricing page, not to the homepage. Sending everything to the homepage confuses visitors and is often treated like a missing page by Google.

Don’t forget to update links inside your own content too, using a search-replace tool — see [How to Change Your WordPress Site Address Without Breaking It](https://hostreta.com/2026/10/wordpress-site-address/).

## Finding and fixing redirect chains

A redirect chain happens when one redirect leads to another, for example: http://olddomain.com → https://olddomain.com → https://newdomain.com → https://www.newdomain.com. Extra hops add latency and make troubleshooting harder. Google recommends directing old URLs to their final destinations.

- Test URLs with an online redirect checker or the Network tab in Chrome DevTools.

- Update rules so every old URL goes to its final destination in one hop.

- Decide on www or non-www and https once, and redirect straight to that version.

## Testing and monitoring 404s

- Test your most important old URLs by hand: homepage, top posts, product pages, and contact page.

- Crawl the old URL list with a tool like Screaming Frog to confirm each returns a 301 to the right page.

- Check the Pages report in Google Search Console for “Not found (404)” errors.

- Review the Redirection plugin’s 404 log weekly for the first month and add missing forwarding rules.

New to Search Console? Read [Google Search Console: A Beginner’s Walkthrough](https://hostreta.com/2026/10/search-console-guide/).

## Tools and hosting that help

A fast, well-supported host makes every WordPress task smoother. [Kawedma WordPress hosting](https://kawedma.com/wordpress-hosting.php) and [managed WordPress hosting powered by Rocket.net](https://my.hosting.com/aff/08a016e41d3100e5460ff6ebee1b5e0a91e643d6) include staging sites for safe testing, while [shared hosting from Hosting.com](https://my.hosting.com/aff/279b8376451ad79ddf8c565d9a897e29387ab1eb) or [Kawedma shared hosting](https://kawedma.com/shared-hosting.php) suit smaller sites. Protect the site with an [SSL certificate](https://kawedma.com/ssl-certificates.php) and automatic backups from [CodeGuard](https://kawedma.com/codeguard.php).

## Key takeaways

- Use 301 forwarding rules, at server level or with a plugin.

- Redirect page to page, not everything to the homepage.

- Remove redirect chains so each URL takes one hop.

- Monitor 404 errors for weeks after the move.

## Before you redirect old URLs in WordPress: 7 checks

- Export an old URL list. Include important pages, images, downloads and URLs with external links, not just pages in the main menu.

- Map destinations. Match each old page to a relevant new equivalent and record pages that have no replacement.

- Check the new site. Confirm destination pages load successfully and are not unintentionally blocked from indexing.

- Retain the old domain. Its DNS and server or redirect service must continue accepting requests for forwarding rules to work.

- Keep HTTPS working. Old HTTPS URLs need a valid certificate before the browser can receive an HTTP redirect.

- Back up configuration. Save the current server rules and database before applying changes.

- Test a small set first. Include nested paths and both preferred and alternate hostname versions.

Google’s [site migration guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) recommends permanent server-side forwarding rules where possible. Its [redirect documentation](https://developers.google.com/search/docs/crawling-indexing/301-redirects) explains how permanent and temporary status codes are interpreted. Use the method supported by your actual hosting setup.

## Build a redirect map before writing a wildcard rule

Old URL
New destination
Expected result

/about/
The equivalent new about page
Permanent redirect to a working page

/old-service/
The relevant replacement service
Permanent redirect only when the content is equivalent

/guide.pdf
The new location of the same guide
A working downloadable file

A removed page without a replacement
No unrelated destination
An appropriate 404 or 410 response

A wildcard rule is suitable only when preserving the old path produces a relevant new URL. If the structure changed, create explicit mappings before a catch-all rule. Otherwise, a technically valid redirect may simply lead to a new 404 page. Check the destination, not just the presence of a redirect response.

## Troubleshoot when you redirect old URLs in WordPress

### The old domain shows a certificate warning

Confirm that the old hostname has valid HTTPS coverage. The redirect happens after the secure connection is established, so a redirect rule cannot repair an expired certificate. Ask the hosting provider how the old domain’s certificate will be renewed after the move.

### The browser reports too many forwarding rules

Check for conflicting rules at the CDN, hosting server and WordPress plugin. A rule sending to www can conflict with another sending back to the non-www address. Restore the last working configuration if needed, then keep one documented policy for the final hostname and HTTPS.

### The redirect reaches the wrong page

Inspect rule order, exact path matching and query-string behaviour. More specific mappings generally need to be considered before broader catch-all rules. Test a normal browser request as well as a crawler or HTTP status checker; cached forwarding rules can make an old mistake appear to persist.

## Verify results after you redirect old URLs in WordPress

For each important URL, record the initial status, destination address, number of hops and final response. The final page should load normally and display the intended content. Check that forms, navigation, downloads and canonical URLs refer to the new site, rather than relying on forwarding rules for every internal link.

Submit the new sitemap and review indexing and crawl errors in Search Console. If you use the Change of Address tool, follow Google’s eligibility and setup instructions; it does not replace forwarding rules. Monitor the old domain and forwarding rules over time rather than removing them as soon as the new homepage appears in search.

## Frequently asked questions

### Do I need a redirect plugin if I already have server rules?

Not necessarily. Use a method you can maintain and test. Multiple systems handling the same forwarding rules can create conflicts. Document which layer handles whole-domain moves and which, if any, handles individual page changes.

### Can DNS alone redirect old URLs in WordPress?

DNS routes a hostname to infrastructure; it does not send an HTTP page-to-page redirect by itself. A registrar forwarding feature may provide a separate redirect service, but you still need to verify its HTTPS and path-handling behaviour.

### Will forwarding rules guarantee that rankings stay unchanged?

No. A migration can involve recrawling and changes in search visibility. Correct permanent forwarding rules, relevant destinations and updated internal links support the move, but no plugin can guarantee a particular ranking outcome.

## Choose the redirect layer your team can maintain

Start by identifying where a request to the old address actually arrives. A CDN can receive it before the origin server; a hosting control panel can have its own forwarding setting; WordPress plugins operate after the request reaches WordPress. Write those layers down before changing rules. A redirect configured on a server that no longer receives traffic cannot help, even when the rule itself is correct.

For a whole-domain move, discuss the redirect plan with your hosting provider before switching DNS. Ask whether the old domain can remain attached, how certificates renew, where rules are stored and how exceptions are added. If you are comparing domain and WordPress hosting services, [KAWEDMA](https://kawedma.com/) offers options worth reviewing. Confirm the redirect features, migration scope and ongoing costs for the specific plan before ordering.

For a few renamed posts on the same site, a plugin may be easier to maintain. Assign one owner to the redirect list and record the reason for every entry. Avoid stacking several plugins that each attempt automatic redirect. A simpler configuration makes it easier for the next administrator to understand what happens when a visitor follows an old link.

## A practical redirect test matrix

Testing only the homepage leaves important gaps. Build a small sample that represents the site’s actual traffic: a top article, a nested category path, a product, a document download and a page with a meaningful query parameter. Include a genuinely missing address so you can verify that unknown pages still return an appropriate error instead of being sent to an unrelated sales page.

Request to test
What to inspect
Failure to investigate

Old HTTP and HTTPS homepage
Final hostname and secure connection
Certificate warning or extra hops

Old nested article path
Relevant replacement content
Homepage fallback or new 404

Known PDF download
File opens and has the right content
An HTML error page returning 200

URL with a useful parameter
Required parameter survives correctly
Broken search, filter or referral flow

Unknown old path
Honest missing-page response
Catch-all redirect to irrelevant content

Record the date, the exact old URL, the redirect status and final URL in a spreadsheet. Add a result column and a short note describing any exception. This becomes a repeatable acceptance test after configuration changes, rather than a collection of screenshots nobody can reproduce. Use public page URLs in shared reports and remove private tokens or customer details from query strings.

## Inspect a redirect without relying on browser memory

A browser can remember a permanent redirect. After correcting a rule, a normal window may therefore appear to show an old result. Compare the response with a fresh HTTP inspection and the browser’s network panel. Distinguish a cached response from a currently incorrect origin configuration before changing several settings at once.

For administrators comfortable with a terminal, an initial header inspection can look like the following. Replace the example address with a public URL from your own test list:

curl -I https://old.example.com/example-page/
Read the status line and Location header. This command uses a HEAD request; some applications handle HEAD differently from GET. If the result seems inconsistent, inspect a normal page request too. A successful first response is only half the check: open the destination and confirm it actually presents the intended content.

Keep a redirect inspection separate from an application transaction. Do not use a checkout submission, password reset link or signed download token as a casual test URL. Public articles and ordinary landing pages are safer examples. Where a business workflow needs testing, use a controlled test account and the site’s normal testing process.

## Handle query strings, files and changed structures carefully

A path-preserving redirect rule is convenient when the new site has the same structure. It does not know that an old product was merged into a different category or that a download moved into a media folder. Treat those changes as explicit exceptions. Review high-value paths individually before enabling a broad rule for the remainder of the site.

Query strings also deserve a deliberate policy. Some parameters are tracking labels; others control language, search terms or a product variation. Decide which are needed at the destination and verify the actual behaviour of the chosen redirect system. Do not assume a registrar’s forwarding feature handles them exactly like a server rule.

Check encoded characters and trailing slashes using examples that really exist on your site. A URL containing an accented character or a space in an old file name can expose an incorrect match. Avoid creating several near-identical rules without understanding which one runs first; overlapping patterns make later maintenance harder.

## Plan rollback before launch day

Save a dated copy of the working configuration, the URL map and the intended final hostname. Identify who can restore the old rule set if a redirect loop makes the site inaccessible. Keep hosting access available independently of the WordPress dashboard, because a broken server rule can prevent that dashboard from loading.

Apply changes during a period when someone can immediately test the important routes. Begin with a limited example where the system supports staged changes, then check the broader configuration. If the result fails, restore the last known working rule instead of adding another speculative redirect on top of the mistake.

After recovery, describe the cause in plain language: a destination pointed back to the old domain, a wildcard captured the wrong path, or two layers disagreed about the hostname. Add that case to the test list. A short incident note is more useful than leaving unexplained exceptions scattered across several control panels.

## Maintain the redirect after the move

The old address remains part of your site’s maintenance responsibilities while links still point to it. Keep its registration, DNS, certificate and redirect service under review. A correctly configured rule stops helping if the domain expires or HTTPS becomes invalid. Put these dependencies in the same renewal checklist used for the primary domain.

Google recommends retaining migration redirects for at least a year, and longer where practical. Treat that as a minimum planning reference rather than a date on which every old link becomes irrelevant. Bookmarks, printed materials and links from other websites can remain in use for much longer. Review actual traffic and business needs before retiring infrastructure.

Update internal navigation and prominent external profiles to the final addresses so visitors do not need an avoidable redirect. Where a valuable backlink remains outdated, you can ask the site owner to update it. Keep monitoring missing pages, but prioritise real broken journeys over random bot requests for files your website never had.

## Define acceptance criteria for the redirect project

A migration is ready for handover when the important old addresses reach relevant working destinations, the final hostname is consistent and the team knows where rules live. Include a named owner, a renewal reminder and instructions for adding future mappings. This makes maintenance possible even if the person who performed the move leaves the project.

Separate technical acceptance from search performance. You can verify a redirect status immediately; search engines need time to process changed URLs. Compare useful measures such as successful page visits and working forms alongside indexing reports. Investigate a meaningful traffic drop, but avoid repeatedly changing stable URLs simply because a report has not updated yet.

Finally, retain the test list as a living document. When a destination is renamed again, update the original mapping to the latest relevant page rather than building a chain of historical stops. This small maintenance habit keeps old links useful and gives future administrators a clear, testable redirect policy.
