A simple guide to setting up redirects properly

Redirects send visitors and crawlers from one web address to another. They are essential when a business reorganises its site, retires a campaign page, moves a resource, or replaces an offer. A good redirect is almost invisible: the visitor reaches the correct page, while search engines understand that the old address has moved. This guide explains how to set up redirects properly across web platforms while protecting performance, data, and customer trust.

Poor redirects create loops, chains, irrelevant pages, broken forms, and slow requests. These faults matter across Australia, where customers may connect from Perth, Adelaide, Brisbane, Sydney, or Melbourne using NBN, fixed-line, and mobile services. A regional user can feel every extra server round trip. A confusing redirect can undo the intent of a customer who followed a product, support, or booking link on a phone.

Build a reliable redirect map

Start with an inventory of URLs that receive traffic, backlinks, bookmarks, or messages. Include campaign pages, product and category addresses, PDFs, contact pages, and links published in emails. Analytics, server logs, referrer reports, and crawl tools reveal which paths deserve attention. A visual scan is insufficient because orphaned pages can remain invisible to visitors while still attracting crawlers and shared links.

Create a redirect map with the old path, destination, reason, status code, owner, and test status. The destination should be the closest genuine equivalent, not simply the homepage. One old page should normally lead to one relevant new page. Record permanent changes separately from temporary tests to prevent an experiment becoming permanent. A clear naming convention helps teams interpret the map without guesswork.

Remove duplicate pages and decide which URL remains canonical. Consolidate equivalent content instead of building a chain of forwards, which confuses crawlers and reporting. For Australian businesses, protect valuable .com.au and .au domains when consolidation is necessary, and retain country-specific paths where the content or audience is genuinely Australian.

Match each redirect to its purpose

A 301 Moved Permanently tells browsers and crawlers that the old URL has a new home. Use it for a lasting migration, renamed product, or section move. The signal can consolidate link equity and indexing, but it should reflect an editorial decision. Do not use 301 for an uncertain destination or seasonal campaign, because the permanence is difficult to undo in search results and browser caches.

A 302 Found is temporary. It suits a short campaign, maintenance page, landing-page test, or content returning to its original location. Search engines may keep crawling the old URL. Label each 302 with an expiry date and owner so it does not linger. A 307 Temporary Redirect or 308 Permanent Redirect preserves the original HTTP method and request body, which can help with forms.

A 303 See Other sends the request to another URL using GET, commonly after a form submission and before a receipt page. A meta refresh can be a basic fallback, but JavaScript redirects are a last resort because some crawlers and assistive technologies may not execute them. Whenever possible, issue the redirect from the web server or CDN so the response begins before any page loads.

Implement redirects at the edge

Add permanent rules at the web server, edge platform, or CDN whenever possible. Apache, Nginx, and managed tools can return the correct status before HTML is delivered. On WordPress or another CMS, use a reputable plugin or application feature rather than template code, which often fires too late and can conflict with caching. Document the implementation layer because a cache purge may not affect server rules as expected.

Check hostnames and path formats. Decide whether www and non-www addresses should resolve to one canonical host, and whether trailing slashes, uppercase letters, or encoded characters should be normalised. Preserve useful query parameters deliberately, and stop at the final destination. A rule for an old article must not also capture product filters, payment return URLs, or support identifiers.

Performance is part of correctness. A redirect should normally resolve in one hop, with DNS, TLS, caching, and the destination server configured efficiently. A useful explanation of the critical rendering path shows why late redirects can delay visible content. Keep the response small, avoid unnecessary scripts on intermediate pages, and confirm that mobile connections do not reveal a white screen while the forward request is processed.

Protect trust during the journey

Protect context as well as the destination. A campaign email linking to a relocated resource should still reach that resource, with approved tracking parameters carried across when appropriate. Never dump every visitor on the homepage or a loosely related category. Payment gateways, account areas, and checkout sessions need care because a misplaced redirect can abandon an order. Australian shoppers should retain clear AUD pricing and GST information instead of landing on an overseas default.

External destinations deserve review. For example, an instruction pointing to an external Viber download listing should be checked against the current official app route before the old page is retired. Users should not be sent to a lookalike host without warning. Label external links clearly, check the destination on mobile, and avoid intermediary pages that create another click. The same applies to software downloads, banking services, government forms, and transport bookings.

Do not create an open redirect by accepting an arbitrary destination from a query parameter. Allow only approved relative paths or trusted hosts, and reject malformed values. Never place passwords, session tokens, email addresses, or personal information in a redirect URL because browsers and servers may store or log it. Under the Privacy Act 1988 and Australian Privacy Principles, keep data handling secure. If a redirect feeds a mailing list, the Spam Act 2003 makes consent and working unsubscribe mechanisms essential.

Test redirects like a customer

Test with command-line tools as well as a browser. Confirm the status code, destination, headers, query handling, HTTPS, and caching. A browser’s address bar can hide intermediate hops, so inspect the network panel or redirect checker for the full chain. Test in a private window after clearing cached data, then repeat with JavaScript disabled to confirm the server response is sufficient. Include mobile viewport tests for sites that redirect by device type.

Check edge cases: a trailing slash and no trailing slash, a lowercase version, an encoded character, a query string, and a missing parameter. Try the destination directly as well. It should return a normal 200 response rather than another redirect, and its title, language, currency, and navigation should match the original promise. Forms should retain entered data where lawful and practical, while expired coupons or sold-out products should lead to useful alternatives rather than empty categories.

Compare analytics before and after release. Record visits, goal completions, search impressions, crawl patterns, server errors, and referral sources attached to redirected URLs. Campaign parameters can be lost if a rule replaces the query string, although original tracking data may remain in server logs. Use first-party analytics and annotate the launch date. For an Australian audience, split results by state or connection quality where privacy rules allow, looking for problems a Sydney-based test might miss.

Track performance and keep ownership

Keep redirect logs under regular review. Alert on unexpected 3xx responses, loops, rising latency, or a surge in requests to a removed path. Event alerts can reveal a broken link soon after deployment. Compare the live map with internal links and the XML sitemap. Remove rules when their purpose ends, especially temporary forwards, and archive the decision so another team does not reinstate an obsolete route.

Provide a clear route for reporting mistakes. Visitors should be able to tell support what they clicked and where they expected to land without seeing a raw status code. Teams using SpeedTao can use the SpeedTao support channel to confirm ownership of a published rule or escalate an inconsistent path. For customer-facing messages, plain Australian language works well: “No worries, we’ve moved that page; here is the new route” is clearer than technical wording about a 301 response.

Assign an owner and review date to every material rule. Useful Australian-market signals include branded searches, traffic to .com.au addresses, and enquiries after a migration, not merely a global traffic total. When content owners change their mind, they can update the map without creating another layer of forwarding. A documented owner, an expiry date for temporary rules, and routine verification make redirect management a dependable operational process rather than a one-off chore.