Bold geometric logo mark in deep indigo and near-black 2 Geeks Web Design

How to use redirects when moving a page to a new URL

Moving a page to a new URL can improve your site structure, refresh outdated content, or support a business rebrand. It can also create broken links, lost search rankings and confused visitors if the old address is simply deleted. A redirect tells browsers and search engines where the content now lives.

For an Australian small business, this matters whether you are changing a service page for customers in Parramatta, updating a tradie website in Geelong, or moving an online shop from an old domain to a new one. A properly planned redirect preserves useful traffic and helps people find the right information without needing to search again.

Redirect type Best use Search signal Typical example
301 permanent A page has moved for good Usually transfers most ranking signals /old-service to /services
302 temporary A short-term test or temporary change May keep the old URL indexed Promotional landing page
307 temporary Temporary move while preserving the request method Similar to a 302 Temporary system or campaign change
308 permanent Permanent move while preserving the request method Similar purpose to a 301 Technical API or form migration

Choose the right redirect status

A 301 redirect is usually the correct choice when a page has permanently moved. It works for common website changes such as replacing an outdated product URL, merging two similar articles, changing a domain name or switching from HTTP to HTTPS. Search engines can gradually transfer the old page’s authority and relevance to the new address.

Use a 302 or 307 when the original page will return. For example, a retailer might send visitors to a seasonal promotion while stock is unavailable, then restore the original product page later. Using a temporary redirect for a permanent move can leave search engines uncertain about which URL should be indexed.

A 308 redirect is a permanent alternative that preserves the request method, which can matter for technical applications and form submissions. Most standard content websites do not need to choose between 301 and 308 manually. For ordinary pages, a well-configured 301 is generally the practical option.

Map the old URL to the most relevant new page

Before changing anything, create a URL map. List each old address, its proposed destination, the redirect type and the reason for the move. Website crawling software, server logs, Google Search Console and your analytics reports can reveal URLs that still receive visits or backlinks.

Send visitors to the closest equivalent page rather than automatically directing every old address to the home page. An old page about emergency plumbing in Newcastle should lead to the replacement emergency plumbing page, not a generic homepage. Relevance makes the transition clearer for customers and provides a stronger signal to search engines.

If no comparable page exists, a carefully written category page may be suitable. Redirecting a discontinued article to an unrelated page can look misleading and may provide little value. In some cases, returning a 410 status for content that has genuinely been removed is more accurate than creating a weak replacement.

Avoid redirect chains and loops

A redirect chain occurs when the old URL points to a second URL, which then points to a third. For example, /about-us may redirect to /company, and /company may later redirect to /our-story. Each extra step adds delay and creates another point of failure. Update the original rule so it goes directly to the final URL.

A redirect loop is more serious because the browser is sent back and forth between addresses. This can happen when HTTP and HTTPS rules conflict, when trailing-slash settings are duplicated, or when a content management system applies a different canonical URL from the server configuration. Visitors may see an error before the page loads.

Test both the old and new addresses in a private browser window, then check the response path with a redirect checker or command-line tool. Review variations such as uppercase letters, a www prefix, non-www domains and URLs with tracking parameters. Australian businesses often run campaigns through email and social media, so old links may remain active in several places.

Configure redirects at the right level

Redirects can be managed through a web server, hosting control panel, content management system or specialist plugin. Apache sites commonly use .htaccess, while Nginx uses server block rules. Platforms such as WordPress, Shopify and other hosted systems may offer their own redirect manager.

Server-level rules are efficient because the redirect happens before the full page loads. A CMS plugin can be easier for a small business owner who needs to update redirects without editing configuration files. The safer choice depends on your hosting setup, technical access and ability to test changes before they reach the live site.

Keep rules readable and document why they exist. Broad regular expressions can accidentally redirect image files, admin paths or unrelated pages. If a web developer is handling the migration, ask for a copy of the redirect list and an explanation of where the rules are stored. That makes future website maintenance less dependent on one person.

Update links, canonicals and site signals

Redirects are a safety net, not a substitute for updating the website. Change internal links, navigation menus, XML sitemaps, canonical tags, hreflang references and structured data so they use the new URL directly. This reduces unnecessary redirects and helps search engines understand the preferred address.

Review external references that you control, including Google Business Profile, directory listings, social profiles, email templates and advertising campaigns. A local café in Hobart, for instance, should update its menu link across its profile, booking platform and printed QR codes. Australian customers commonly search on mobile while travelling between suburbs, so a slow or broken redirect can quickly become a lost booking.

Submit the updated sitemap in Google Search Console and use the URL Inspection tool to check important pages. Keep the old redirects in place for a substantial period, especially when the previous URL has backlinks, printed material or long-running marketing campaigns. Removing them too quickly can revive broken-link errors.

Check performance after the move

Monitor organic traffic, conversions, crawl errors and indexed URLs after the change. A small temporary fluctuation is possible while search engines process the new addresses, but a continuing fall in impressions or leads deserves investigation. Compare the performance of individual pages rather than relying only on total website traffic.

Look at server logs and analytics for repeated visits to old URLs, unexpected redirect destinations and spikes in 404 errors. Check whether query strings are being retained where they should be. Product filters, booking references and campaign tags can behave differently depending on the redirect rule, so test real links from newsletters and advertisements.

It is also worth checking page speed from Australian locations. A business serving customers in Perth may use a hosting arrangement or content delivery network that performs differently from one serving Melbourne or Brisbane. The redirect should be quick, but the destination page must load reliably on mobile networks and common devices.

Handle domain and site migrations carefully

A domain change involves more than moving one page. Prepare redirects from every important old URL to its matching new URL, confirm that the new site is crawlable, and retain the same content where possible during the transition. If the move also changes navigation, page names and design, it becomes harder to identify which change affected search performance.

Keep ownership of the old domain and hosting access active. Do not let an expired domain become available to someone else while its redirects are still needed. Verify HTTPS certificates, DNS records, email services and subdomains before launch, since a web migration can affect more than the public website.

Use a staged launch when the project is complex. Test a sample of pages first, check the redirect map, then monitor the live site after the full change. The hands-on approach used in a detailed build journal reflects a useful principle for website migrations: document the components, test each system and make changes in a controlled sequence.

Treat redirects as part of ongoing maintenance

A redirect list should be reviewed whenever a page is renamed, merged or removed. Record the date, old URL, new URL, status code and owner of the change. This simple record prevents future developers from creating duplicate rules or accidentally removing redirects that still protect valuable links.

Audit the site after redesigns, platform changes and URL structure updates. Tools can find broken internal links, redirect chains and pages linking to old addresses, while Search Console can reveal indexing problems that may not appear in a quick visual check. Pay special attention after major retail periods such as Boxing Day sales or end-of-financial-year promotions, when old campaign URLs may receive sudden traffic.

A redirect works best when it supports a clear content structure. Choose the most relevant destination, use a permanent status for a genuine permanent move, update internal references and monitor the results. With that process, changing a page address becomes a manageable part of website development rather than a source of avoidable search and usability problems.