What Is a Redirect and How to Set Up 301 Redirects Properly

A redirect is a server response that sends one web address to another. When a visitor opens an old URL, the server returns a status code and destination. A 301 Moved Permanently response is the permanent option, commonly used after a page moves, a domain changes or a clearer URL replaces an outdated path.

For Australian bloggers, publishers and online retailers, redirects can protect traffic during a website redesign or domain migration. They are especially important for WordPress sites, where changed permalink settings can create broken links. Australian domains often use .com.au or .au extensions, making accurate URL mapping essential when consolidating duplicate addresses.

Redirects and the 301 status code

A server-side redirect sends an HTTP response before the browser displays the destination page. The response includes a status code and a Location header containing the new address. JavaScript redirects and meta refresh tags may work in a browser, but they are less reliable because search crawlers and some social media preview tools may not process them correctly.

The status code determines the redirect’s purpose. A 301 means the move is permanent, a 302 means the change is temporary, and a 307 preserves the original request method. Use a 301 only when the old address will not return to its former purpose, because browsers and crawlers may cache the permanent response for an extended period.

A 301 should also lead to the closest relevant replacement. Redirecting every old article to the home page destroys the visitor’s path through the site and can leave search engines with hundreds of URLs that no longer serve useful content.

Why permanent redirects protect useful traffic

A properly configured 301 tells search engines that the old URL has moved to a specific new page. This consolidates signals such as backlinks, crawl history and indexed content around the destination. It does not guarantee identical rankings, but it avoids leaving important pages orphaned when their addresses change.

Redirects also improve the experience for people arriving from bookmarks, email campaigns, printed material or social media posts. Sydney and Melbourne commuters often encounter links while using mobile data on trains or trams, so a quick server response is more dependable than a slow script-based redirect. The destination should load quickly, retain the expected content and work on a small screen.

Legal and marketing obligations do not disappear when a page moves. A promotional email landing through a 301 must still comply with the Spam Act 2003, while personal information collected at the destination must continue to meet applicable Privacy Act 1988 duties. Redirects should not conceal material changes to a privacy notice or bypass required consumer information under Australian Consumer Law.

Plan a one-to-one URL migration

Begin with a redirect mapping sheet containing each old URL, its exact destination, the reason for the move and the date it was implemented. Include old campaign pages, product URLs, service pages, images and any address shared in backlinks. A detailed sheet makes mistakes easier to identify, particularly for small WooCommerce retailers managing hundreds of product combinations.

Each old URL should have one clear destination. If two pages have become similar, choose the strongest version and redirect the other to it. If they serve different purposes, keep both and link to them with descriptive internal links. Sending every expired page to a broad category page is less useful than preserving the original topic and intent.

Plan how the server will handle trailing slashes, uppercase letters and query parameters. A URL containing parameters such as ?utm_source=newsletter may still need to reach the same page with those parameters intact. Avoid redirect chains, loops and rules that depend on one temporary redirect leading to another permanent one.

Set up redirects on your website

The best location for a redirect is usually the web server or hosting control panel. It executes before WordPress, a theme or another application processes the request, reducing load and preventing plugin conflicts. Check whether your host provides a dedicated redirection tool before editing configuration files manually.

WordPress users can install a reputable redirection plugin or use a feature supplied by their host. If the site also uses Yoast to manage search metadata, this WordPress Yoast guide can help the team review titles and descriptions while preparing the destination pages. Redirect rules and on-page optimisation should be checked separately because one does not automatically configure the other.

On Apache servers, a simple rule in .htaccess might redirect /old-service/ to https://example.com.au/new-service/. Nginx requires an equivalent location block containing a return 301 instruction. Use absolute HTTPS destinations, confirm that the server supports the chosen rule and make a backup before changing configuration files.

Test the path from click to final page

Test each rule with a redirect checker, browser developer tools or a command such as curl -I. The first response should be a 301, and the Location header should contain the expected destination. Follow the entire path until it reaches a normal 200 response, while checking that query strings remain available and no login screen, error page or redirect loop appears.

Open the final page on a phone as well as a desktop. For a real-world check, visit Ziyo Music after following a redirect and confirm that the destination displays the expected content without further manual action. A working HTTP response is not enough if the landing page is slow, broken or unrelated to the original link.

After publishing the rules, submit affected addresses through Google Search Console’s URL Inspection tool and monitor crawl reports. Also check Bing Webmaster Tools, server logs and analytics for unexpected redirects. Record the tests in the mapping sheet so another person can reproduce them when maintaining the site.

Maintain the redirect map

Remove or correct rules that produce 404 errors, point to deleted pages or create unnecessary chains. A redirect loop can make a site inaccessible, while excessive hops slow down crawling and may dilute the relationship between the old and new URLs. Redirecting a page to itself is invalid and should be treated as an urgent configuration fault.

Update internal links, XML sitemaps, social profiles and canonical URLs to use the new addresses. Keep the old redirect active because backlinks and bookmarks can remain online for years. Review server logs regularly, especially after a plugin update, migration, redesign or change to the site’s URL structure.

Create the mapping sheet today, implement one verified 301 rule at a time and schedule recurring crawl checks. For a WordPress site, document the old and new URLs first, then use a trusted redirection tool and confirm every rule from a mobile connection before announcing the move.