Redirect Configuration

A redirect sends a visitor or search engine from one URL to another. Redirects are commonly used after changing a page address, moving a domain, consolidating content or enabling HTTPS.

Choose the redirect type

301: use when the old address has moved permanently.
302 or 307: use for a genuinely temporary destination.
HTTP to HTTPS: send every insecure address to its secure equivalent.
Domain redirect: map old-domain pages to the most relevant new-domain pages.

Choose one configuration layer

Redirects may be configured in a hosting panel, web server, CDN or WordPress plugin. Use the layer that receives the request and can be maintained safely. Avoid creating the same rule in several places because overlapping rules can produce loops or unexpected destinations.

Plan and test the change

List each old URL and its intended final destination.
Keep the page path where possible rather than sending every old URL to the home page.
Create a backup of the current configuration.
Add the rule, then test it in a private browser window.
Confirm the redirect uses the intended status and reaches the final page without another unnecessary hop.

Changing the WordPress Address or Site Address is not the same as creating a redirect. See Change a WordPress URL when the site itself is moving to a different address.

Common questions

Frequently Asked Questions

Should I use a 301 or 302 redirect?

Use a 301 when the move is permanent. Use a temporary redirect only when you expect the original URL to return.

What is a redirect loop?

It happens when redirect rules send a visitor between addresses without reaching a final page, such as HTTP redirecting to HTTPS and another rule sending it back.

Should every old page redirect to the home page?

Usually not. Send each old URL to the closest relevant replacement. If no suitable page exists, a genuine not-found response may be clearer.

Why does an old redirect still appear after I removed it?

The browser, CDN, host or WordPress cache may still hold the earlier response. Check each configuration layer and test in a private window after clearing the relevant cache.