Reviews Inquire

Redirects and revamps: a practical guide for Australian sites

An old link can still matter long after a website changes. A reader may have bookmarked a news article, a community organisation may mention the site in a newsletter, or a search result may point to a page that no longer sits at its former address. The immediate question is practical: should the old address send people somewhere useful, or should the wider site be rebuilt? Choosing the wrong route can create broken paths, dilute the value of archived material, or make a sound resource harder to navigate.

A redirect is a route from one address to another. A revamp is a broader rebuilding of how a site presents, organises and delivers its content. Both may be undertaken at once, but they solve different problems. Redirects preserve continuity when a particular URL has moved; a revamp improves the structure and experience around many pages. Treating these as interchangeable either creates unnecessary complexity or leaves important legacy links stranded.

For a resource hub such as papajohnphillips.com, the aim is not simply to make the front page look current. Historical news, community-focused articles and background material each have a different role. A responsible refresh should keep that material identifiable, make the domain's purpose clear and provide stable paths for people arriving from outside the site. The approach should serve both a first-time visitor with a specific question and a returning reader looking for an older piece.

Australian context sharpens those choices. Many people travel between Sydney, Melbourne, Brisbane and Perth while checking reference material on a phone, so a useful page must load quickly and make its next step obvious. The .com.au namespace remains familiar in the local market, while community groups, small publishers and not-for-profits often rely on shared web resources. Any redesign that adds forms, mailing lists, comments or user accounts should also be checked against the Privacy Act 1988, the Spam Act 2003 and the Online Safety Act 2021.

Why clarity prevents costly rework

The first step is to identify the actual problem. A page that has moved, changed its address or been replaced by a newer resource usually needs a redirect. Difficulty finding related articles, weak navigation, inconsistent labels or an outdated presentation points toward a revamp. A failure to find one archived item can be solved without redesigning every page.

The scale of the disruption matters. Moving twelve related articles may justify a well-planned redirect map, while a library of hundreds of pages may need new navigation and templates. A redirect is precise and comparatively contained. A revamp touches content, design, metadata, internal links, accessibility and often the underlying publishing system.

Clear decisions also protect search visibility and shared references. Search engines and other sites may have recorded the old addresses, and readers will not understand why familiar paths suddenly fail. Whichever route is chosen, the goal is the same: keep people connected to relevant material while making the site easier to use.

How redirects preserve access

A redirect works when a browser requests an old URL and receives an instruction to continue at a new one. A permanent response is usually appropriate when the old page has genuinely moved and will not return. A temporary response can be used during a planned change, although leaving it in place indefinitely can weaken signals about which address should be treated as canonical.

The destination should be specific. Sending every old URL to the home page is easy to implement, but it gives visitors no useful answer and can create a frustrating series of redirects. A former community article should lead to that article or its nearest equivalent, while a deleted event notice might lead to a relevant archive index. Redirect chains and loops should also be removed because they slow delivery and can prevent crawlers from reaching the final page.

Preservation does not have to mean freezing a site in amber. Further background on community stewardship can be found in community preservation guidance, which offers a useful reference point for maintaining continuity. In practical terms, maintain a record of every changed URL, its destination and the reason for the change, then review that record whenever content is reorganised.

What a revamp changes

A revamp begins with content rather than a new colour palette. Editors need to decide what the resource hub should cover, how historical material differs from current information, and which pages deserve prominent navigation. Categories, tags, page templates and search functions should then support those decisions instead of forcing existing content into an awkward shape.

Readers looking for older material should not be forced into a generic landing page. The archived news pages can remain a deliberate destination within the revamped information architecture, with context that distinguishes a historical report from current guidance. A revamp can also introduce clearer introductory copy, contextual links between subjects and pathways into related sections without erasing the original archive.

Design and technical work follow the content plan. Australian public-sector experience makes WCAG 2.1 AA a familiar accessibility benchmark, which is also a sound reference for community organisations. Smaller text, uncertain contrast and complicated navigation can exclude readers who browse with older devices or assistive technology. Before republishing archived words or images, the Copyright Act 1968 should also be considered, particularly where ownership or permission details are uncertain.

Choosing the right response

Redirect when the content remains available and the main fault is its address. This is common after a section is renamed or an older site is consolidated into a resource hub. Redirect when a specific URL has moved, when two versions have been merged or when a temporary landing page must direct visitors to a stable resource.

Revamp when visitors can find the page but cannot understand what it contains, navigate between related subjects or trust that they are looking at the right material. A visual refresh may be appropriate if the underlying information architecture works. A full rebuild becomes necessary when the publishing system cannot support accessible pages, reliable search or the intended range of archived material.

A combined approach often serves a historical resource best. Individual legacy URLs can be redirected into a newly designed structure, with an archive index for material that has no precise successor. Australian readers increasingly use local search results, mobile pages and quick link taps, so every destination should be tested on a small screen and through a slow mobile connection rather than only on a office desktop.

Comparing the two approaches

The practical choices align across several decision points. The appropriate method depends less on preference than on the condition of the content, the number of affected addresses and the amount of change visitors need to absorb.

Decision point Redirect Revamp
Primary purpose Send a known address to a relevant destination Improve the overall content and user experience
Best fit Moved, renamed or consolidated pages Obsolete navigation, structure, design or publishing system
URL treatment Preserves continuity through redirects May retain, reorganise or rewrite addresses
Content work Usually limited to destination selection and context Requires auditing, rewriting, templates and navigation
Continuity Strongest for a specific incoming link Depends on how carefully legacy material is integrated
Main risk Redirect loops, chains or irrelevant destinations Scope growth, broken legacy paths and disrupted search visibility
Relative effort Narrow and usually quicker Broader, requiring editorial and technical coordination
Best measurement Check status codes, destination relevance and traffic Test discovery, accessibility, engagement and search performance

Neither option should be treated as a cure-all. A polished revamp cannot compensate for sending visitors to irrelevant destinations, while a redirect cannot make confusing content easy to understand. The strongest results come from making the redirect map and content architecture agree with each other.

Steward the change and keep the archive useful

A controlled transition begins with an inventory. Record each important URL, its current status, relevant incoming links and the intended destination. Then define what “preserved” means for this domain: stable access, clear provenance, searchable metadata or simply an honest notice explaining that a page has changed. These decisions give future maintainers a defensible basis for their work.

The following actions provide a practical foundation for either approach:

Ownership and review are essential after launch. Redirects should be monitored for errors, and content owners should periodically confirm that destinations remain relevant. A link can work technically while leading somewhere less useful several years later. For papajohnphillips.com, regular stewardship helps the domain remain a dependable archive as technologies, community interests and reading habits change.

Explore the preserved material, use the site's inquiry option when ownership or access needs clarification, and coordinate structural changes before another trusted path is broken.