Redirects That Keep Old Links Working
A website can accumulate hundreds or thousands of links over time. Some point to pages that have moved, others lead to renamed articles, and a few may still be printed on flyers, saved in browser bookmarks or shared in old community newsletters. When those addresses stop working, visitors encounter a 404 page and search engines lose confidence in the site’s structure.
Redirects provide a practical way to guide an old address to the most relevant current location. Used carefully, they preserve access to historical material, protect search visibility and make a domain easier to manage as its content changes. Used carelessly, they can create loops, chains, irrelevant journeys and confusing signals for both people and search crawlers.
This matters particularly for an archive-focused website. A preserved news story may have been linked by a local organisation in Perth, a school group in Brisbane or a community publication in regional New South Wales. Those references can remain valuable long after the original site design has changed.
The aim is not to redirect every old address to the home page. Good URL redirection preserves the purpose of the original link, keeps useful history discoverable and gives visitors a clear path forward. That requires an audit, a suitable redirect type and regular checks after implementation.
Why Old Links Still Matter
Old URLs often have value that is invisible from the current navigation menu. They may have backlinks from newspapers, councils, sporting clubs, universities or community groups. They might also appear in PDFs, email campaigns, social posts and printed material that cannot be updated easily. Removing the original page without a replacement breaks those pathways.
A useful first step is to identify the pages that people still request. Server logs, Google Search Console, analytics reports and backlink tools can reveal visits to outdated addresses. A page with modest traffic may still deserve protection if it has strong links or represents an important part of the site’s history.
For a resource hub, the context behind a link matters. An old article about a local event should usually lead to a preserved article, an archive category or a related record, rather than a generic landing page. Someone searching for historical news on a Saturday arvo wants evidence and detail, not a dead end.
A carefully maintained news archive can therefore serve as both a destination and a reference point for redirected URLs. It gives older material a stable home while allowing the wider website to change its menus, templates and sections.
Audit Addresses Before Making Changes
Begin with a complete list of current and historical URLs. Export addresses from the sitemap, content management system, analytics platform and web server logs. Add URLs found in old newsletters, downloadable documents and incoming links. For a long-running Australian site, also check references from .au directories, local media and community organisations.
Group the addresses by subject, format and condition. A renamed article, a changed folder, a deleted attachment and a duplicated page need different treatment. Record the old URL, its status code, its likely replacement, traffic, backlinks and any notes about editorial importance.
Do not rely on a simple search-and-replace exercise. URL differences may include capital letters, trailing slashes, file extensions, query strings and old tracking parameters. For example, /news/story.html, /News/story and /news/story/ may be treated differently by a server even though a person sees them as variations of the same address.
The audit should also identify redirect chains. If an old page goes to a second old page before reaching the final destination, the journey is slower and less reliable. Map the full route and point the original address directly to the final, relevant page wherever possible.
Choose The Right Redirect For The Job
A permanent 301 redirect is generally appropriate when a page has moved for good. It tells browsers and search engines that the old address should be replaced by the new one. A 308 redirect also indicates a permanent move, though hosting environments and content management systems vary in how they handle it.
A temporary 302 or 307 redirect is better when the original address may return, such as during a short campaign, a maintenance period or a controlled experiment. It signals that the move is not necessarily permanent. Choosing a temporary code for a permanent migration can delay the transfer of search signals and create uncertainty.
| Situation | Preferred response | Reason |
|---|---|---|
| Article moved to a new permanent URL | 301 or 308 | Transfers visitors and communicates a lasting change |
| Page temporarily unavailable | 302 or 307 | Keeps the original address available for restoration |
| Similar page no longer exists | Relevant 301 or helpful 410 | Sends users to a close replacement or clearly marks removal |
| Several old URLs share one destination | Individual mapped redirects | Preserves context and avoids broad, irrelevant routing |
| HTTP changed to HTTPS | Server-level 301 | Creates a secure, consistent version of each page |
| Old query parameters create duplicates | Parameter-specific rules | Prevents unnecessary copies and redirect loops |
A 404 response is not always a failure. If no suitable replacement exists, a useful 404 page may be more honest than sending visitors to an unrelated article. A 410 response can indicate that content was intentionally removed, though it should be used with care when old links may still have public value.
Avoid sending every discontinued URL to the home page. Search engines may treat that as a soft 404, and visitors are unlikely to understand why they arrived there. A redirect should preserve intent as closely as possible: a former event page can lead to its archive record, while an obsolete staff profile might lead to an organisation page.
Implement Redirect Rules Carefully
The best place for a redirect depends on the platform. Apache commonly uses .htaccess, Nginx uses server configuration, and many content management systems provide redirect managers. Server-level rules are often efficient for large migrations, while a CMS tool may be easier for editors handling a small number of content changes.
Write specific rules before broad rules. A precise redirect for /community/annual-report-2018 should be evaluated before a general rule covering the entire /community/ directory. Keep a dated record of every change, including the reason, date and destination, so another administrator can understand the decisions later.
A typical Apache rule might look like this:
Redirect 301 /old-news-item https://example.com/archive/news-item
The exact syntax depends on the server, so configuration should be tested in a staging environment where possible. A small punctuation error can affect many pages. If the site uses a CDN, reverse proxy or managed host, check whether redirects are being processed before or after those services.
Redirects should point directly to the final HTTPS address. Avoid sending a visitor from an old HTTP page to an intermediate HTTPS URL, then from an old folder to a renamed page. Each extra step adds delay and creates another place for the migration to fail.
Test The Visitor Journey
After publishing redirect rules, test representative URLs from every category. Open old HTTP addresses, former folder paths, uppercase variations, URLs with trailing slashes and links containing query parameters. Check the response code, the final destination and the page content.
Use command-line tools such as curl -I, browser developer tools or a reliable crawler to inspect the full redirect path. A healthy response should normally contain a single redirect followed by a 200 status at the final page. Check that the destination loads over HTTPS, uses the preferred hostname and does not redirect back to the original address.
Test on mobile connections as well as desktop networks. Australian users may access a site through variable NBN connections, mobile data in regional areas or public Wi-Fi at a library or council facility. A chain that feels merely inconvenient on a fast office connection can become frustrating on a slower one.
Review analytics and server logs after launch. Look for continuing visits to old addresses, spikes in 404 errors, repeated requests from crawlers and unexpected destinations. Search Console can help identify indexing issues, while a scheduled crawl can uncover internal links that still point to outdated URLs.
Internal links should be updated even when redirects work. Redirects are a safety net, not a substitute for maintaining current navigation. Change menus, related-article links, XML sitemaps, canonical tags and structured data so they reference the final URLs directly.
Protect Archives And Community Context
Historical content often needs a different redirect policy from commercial product pages. An old product may have a clear successor, but a report about a 2009 neighbourhood project may have no equivalent replacement. Preserve the original page where its facts, names and dates remain useful, and redirect only when the material has a stable new location.
When a page must be retired, consider creating a short archive record explaining what happened and where related material can be found. This approach respects readers who arrive through an old citation. It also helps maintain the story of a domain, especially when content relates to local initiatives, public events or community publishing such as community project work.
Be cautious with redirects between unrelated subjects. A former article about a community garden should not be routed to a general services page simply because both use the same directory. Relevance helps people make sense of the move and gives search engines a clearer understanding of the relationship.
Long-term stewardship also means reviewing redirects when the site changes ownership, platform or structure. A rule created during a 2021 migration may become unnecessary after a later redesign. Keep a redirect register, remove obsolete chains and retain important historical mappings in a controlled backup.
Practical Redirect Checks To Follow
- Create a complete inventory of old URLs before changing the site structure.
- Match each address with the closest relevant current page, not automatically with the home page.
- Use 301 or 308 for permanent moves and 302 or 307 for genuinely temporary changes.
- Point every redirect directly to the final HTTPS destination.
- Test status codes, mobile loading, query strings and unusual URL variations.
- Update internal links, sitemaps and canonical tags after the redirect work.
- Review logs, analytics and search reports regularly for broken or looping paths.
A redirect policy should be simple enough for editors to follow and detailed enough for technical administrators to apply consistently. Define who approves a destination, how changes are recorded and when old rules are reviewed. This avoids improvised fixes that solve one broken link while creating several new ones.
For Australian organisations, include regional and community references in the review process. A link used by a council in Victoria, a historical society in Tasmania or a local paper in Queensland may carry more significance than traffic figures suggest. Contact details, archived files and event records deserve careful handling before a URL is retired.
Well-managed redirects make a website feel dependable. Visitors can follow an old bookmark, a search result or a decade-old article reference and still reach information that makes sense. Search engines can understand the site’s changes, while administrators gain a cleaner, more sustainable domain.
Review your old links, map the strongest destinations and implement redirects in small, testable batches. With a clear register and regular monitoring, a changing website can preserve its history without trapping visitors in broken paths.