To check a 301 redirect after changing a WordPress URL, request the old address and inspect its HTTP response. Confirm that it forwards to the intended replacement, that the destination loads successfully, and that your own links now point directly to the new page. A browser landing on the right page is a useful first check, but it does not reveal the status code or every redirect along the way.
This guide covers one changed blog or service-page address. It uses a browser Network panel and, where needed, Rank Math’s redirect manager. A sitewide domain migration needs a full URL map and a broader launch plan.
1. Write down the old and new URLs before changing anything
Copy the complete old address from a known link or your records. Then open the replacement directly and confirm it contains the expected content. Do not create a redirect to a draft, password-protected page or unrelated destination just because that URL exists.
Keep a small redirect record. For a business site, it should be clear who changed the URL and why. This also prevents another editor from creating a second rule for the same source a week later.
| Field | Illustrative entry |
|---|---|
| Old URL | https://example.com/blog/old-checklist/ |
| Replacement URL | https://example.com/blog/new-checklist/ |
| Reason | The article was renamed and updated |
| Expected behavior | Permanent redirect to the replacement |
| Owner and test date | Named editor; date the live rule was checked |
Google’s redirect documentation treats 301 and 308 as permanent server-side redirects. A temporary move has different semantics. For a permanent article rename, choose a permanent redirect rather than treating the code as an arbitrary setting.
2. Check the HTTP response in Chrome
Open Chrome Developer Tools, choose Network, and enable Preserve log. Turn on Disable cache while DevTools is open, then enter the old URL in the address bar. Google’s Network-panel guide explains how to inspect requests and response details.
Look for the main document requests, rather than a stylesheet, image or analytics request. Select the request for the old page and inspect its response status and Location header. Then inspect the request for the destination. For a straightforward move, the useful result is a permanent response from the source followed by a successful response from the intended page.
If the old request is missing, clear the Network log and enter the full old URL again. Test with DevTools already open. A previously cached redirect can otherwise make it harder to see what the server is currently doing.
| Observed result | What to investigate |
|---|---|
| 301 followed by 200 at the intended page | The basic redirect works; continue with links and canonical checks |
| 302 for a permanent move | Whether the rule was accidentally configured as temporary |
| 404 at the old address | Whether a redirect exists and matches this exact request |
| Several redirect responses | Whether rules can point directly to the final address |
| Requests return to an earlier URL | A possible loop or conflicting rule |
| 200 at both addresses | Whether the old page still exists as a separate copy |
An online redirect checker can provide a second view, but you do not need to buy a tool to test one URL. Inspect the response chain rather than relying only on a tool’s green success badge.
3. If the redirect is missing, inspect the existing rules
First identify where redirects are managed. A WordPress plugin, hosting dashboard, CDN and web-server configuration can each be involved. Inspect the existing setup before adding another rule in a different place. Two correct-looking rules can conflict when they operate together.
For a site already using Rank Math, its official redirections guide explains the Redirections module. In Advanced mode, enable that module if needed, then go to Rank Math SEO → Redirections → Add New. For one page, use a narrowly matched source, the complete replacement URL, the appropriate permanent type and an active status.
After saving, request the old URL again and inspect the response. A saved rule is not the same as a verified working redirect. If nothing changes, check whether the actual request differs from the configured source, or whether an upstream rule handles it first.
Avoid a broad contains or regular-expression rule for a single renamed article. Write the smallest rule that solves the known problem. Leave an existing working redirect alone unless you have identified a reason to change it.
4. Test the variants that people actually use
Check the old links you can find in menus, article text, email campaigns or external references. Pay attention to HTTPS, hostname, trailing slash and relevant query parameters. You do not need to invent every possible variation, but the versions present in real links deserve a test.
For a tagged campaign link, inspect whether the required parameters survive the redirect and whether the destination still works. Do not assume every parameter must be kept: search, filter and campaign parameters have different purposes. Test the behavior your site needs.
Record the actual chain for each meaningful variant. If an old HTTP address first upgrades to HTTPS and then changes the page path, note both steps. A developer can decide whether the configuration can send that request to its final destination more directly.
5. Update internal links, canonical and sitemap
Use your internal-linking review to replace old addresses in navigation, related articles, buttons and other links you control. A redirect remains useful for visitors following old references, while your own navigation should use the intended destination.
Check the replacement page’s canonical URL. It should identify the appropriate preferred page, rather than accidentally naming the retired address. Confirm the new URL appears in the relevant sitemap and that a retired redirecting URL is not being presented as a current indexable page.
Google’s URL-move guidance recommends aligning redirects and other signals, and keeping redirects in place for at least a year for site moves. Do not remove an old rule simply because the latest internal links have been corrected; visitors and external sites may still use it.
6. Choose the right action when there is no replacement
A genuinely removed page does not always need a redirect. If there is no relevant successor, returning an appropriate not-found or gone response can be more useful than sending everyone to a generic homepage. Choose based on what the visitor was trying to reach.
For example, an outdated service page may have a close successor covering the same service. A discontinued announcement with no continuing purpose may not. The decision should come before the redirect rule, not after it.
A worked example: rename one checklist
Illustrative case: a business renames an old checklist and changes its slug. The new article loads correctly, but a previous newsletter still points at the old address.
The editor tests that newsletter URL and finds a 404. They confirm the intended replacement, add one exact redirect in the site’s existing manager, and retest. Next they update the links inside the site and check the replacement canonical. They keep the newsletter address in the test log because readers may continue to open it.
The project is complete when the evidence matches the planned behavior. No ranking increase is assumed. Search engines still need to revisit the URLs and process the change.
A compact sign-off checklist
| Check | Evidence to retain |
|---|---|
| Source response | The old address returns the intended permanent status |
| Destination | The correct replacement loads successfully |
| Chain | No loop; unnecessary extra hops identified |
| Internal links | Known links you control use the new address |
| Page signals | Canonical and sitemap identify the intended URL |
| Ownership | A dated record of the rule and who maintains it |
Frequently asked questions
Does changing the page title require a redirect?
Only changing a title does not necessarily change the URL. Check the permalink. A redirect is relevant when an address changes, not merely because an editor rewrote a heading.
Can I check a redirect without coding?
Yes. A browser Network panel or an online checker can show the HTTP status and destination. A redirect manager can also handle a simple rule without editing server files.
Why does the old URL work for me but fail for someone else?
Compare the exact addresses and cached behavior. Different hostnames, paths or parameters can encounter different rules. Reproduce the visitor’s request and inspect its chain.
Will a redirect immediately update Google?
No. A working redirect is one part of the change. Search engines must recrawl and process the URLs; a sitemap or successful browser test does not confirm the updated search listing.
Featured image: Carlos Muza / Unsplash. Documentation checked 15 October 2026.