When should a small business request a redirect?

The strongest reason is simple: people may still use an old URL, and there is a clear new destination for the same or substantially equivalent information.

A page is renamed or moved. Perhaps a business changes /home-renovations to /renovation-services. The new page serves the same purpose, so the old address should normally guide visitors to it.

Two overlapping pages become one. A business combines separate pages about related services into a more useful, consolidated page. Old addresses can lead to that combined page when it genuinely covers what visitors came to find.

An existing website changes structure. A designer reorganises service or blog addresses during a website update. The owner should ask for an old-to-new URL list and a redirect plan before the old links stop working.

A redirect can also be appropriate when a page's address changes without any visual redesign. No redesign is required.

Permanent and temporary redirects: the useful difference

You may hear a website specialist mention 301 and 302 redirects. These are common HTTP response codes, but the decision behind them is easy to understand.

A 301 redirect generally communicates a permanent move. It suits a page that has been replaced at a new address and is not expected to return to its old address. Another permanent option is 308, although owners rarely need to choose between these codes themselves.

A 302 redirect generally communicates a temporary move. It can make sense when an original address is expected to be used again after a short-term change. Other temporary codes exist too.

Google treats permanent redirects as a stronger signal that the new URL should be considered the preferred destination. Temporary redirects communicate a different intention. Neither code is a promise that Google will immediately display a particular URL, or that traffic and rankings will remain unchanged.

Tell your website provider whether the move is genuinely permanent or temporary. Let them choose the appropriate implementation for your platform.

The new destination must answer the visitor's original question

A redirect is useful only if the landing page makes sense to someone who followed the old link.

Suppose a hypothetical plumbing business previously had a page about geyser repairs. It now has a revised geyser-repair service page. Redirecting the old address to the replacement would be logical.

Sending the same visitor to the homepage instead is much less helpful. The person may have to search the site all over again. Sending them to a page about bathroom tiling would be more confusing still.

Before approving a redirect, ask yourself: If I clicked the old link expecting its original information, would this new page satisfy that expectation? If the answer is no, reconsider the destination.

A sensible one-to-one match is often better than sending every retired address to the homepage. If several older pages have genuinely been merged into one relevant page, a many-to-one redirect can be appropriate. The deciding factor is whether that combined destination answers the original needs.

What if the page has been retired with no replacement?

Not every removed page needs a redirect.

Imagine a once-off event page for an event that will never happen again. If the business has no relevant replacement, directing visitors to a loosely related service page may mislead them.

In such cases, allowing the old address to return a proper 404 (not found) or 410 (gone) response can be the appropriate outcome. A helpful missing-page screen can still offer navigation and a way to contact the business.

The important distinction is between content that moved and content that genuinely ended. Do not create a redirect merely to avoid seeing a 404. The decision should reflect what happened to the information and what visitors would reasonably expect.

A small change to a website address can create an unexpected problem. You rename a service page, shorten a long blog URL or remove an outdated offer. The updated page looks fine when you open it from your website menu, but someone following an older link may reach an error instead.

That person might be using a bookmark, an old Facebook post or a link from another site. A website redirect can help guide them to the correct new location.

You need to know what moved, where visitors should arrive and how to test the change.

What does a website redirect actually do?

Every webpage has a URL: its individual web address. A redirect tells a browser that the resource requested at one address should be reached at another address instead.

Imagine a hypothetical Cape Town-based cleaning company with a page at example.com/office-cleaning-old. The business replaces it with an updated page at example.com/office-cleaning. If the old address redirects properly, someone opening the original link is taken to the updated office-cleaning page.

The visitor does not need to search again or work out which menu item to choose. Their browser follows the direction to the new address. It preserves a useful route to moved information.

A redirect does not automatically improve the new page's content, make it relevant or guarantee a particular search ranking. It simply directs requests from one URL to another.

Changing the page title is not always changing the URL

A webpage's visible heading, menu label and address are related, but they are not the same thing. You could change a heading from “Our Services” to “Business Cleaning Services” without changing the URL at all.

Conversely, editing the part of an address after the domain name—sometimes called the URL slug—may create a new address. Your website builder may or may not change the URL automatically.

Before requesting a redirect, ask: Has the actual address changed, or only the words people see on the page? If the URL remains unchanged and the page still works, a redirect may be unnecessary.

Make an old-to-new address list before changes go live

For a single page, you may only need to record two addresses. For a larger set of edits, a basic spreadsheet or written list helps prevent mistakes.

Record the old URL exactly as it was used, the intended new URL, what changed, whether the move is permanent or temporary and whether the new page is already live.

For example, a hypothetical company might record:

· Old address: example.com/our-team-2024

· New address: example.com/our-team

· Reason: team page address simplified

· Decision: permanent move, provided the replacement covers the same information

· Check: old link reaches the updated team page

These are hypothetical addresses. Sharing the list with your website provider clarifies the request and gives you a test plan.

Why redirect chains should be avoided

A redirect chain happens when one old address sends a visitor to a second address, which then sends them to a third before reaching the final page.

For example: an old services URL redirects to last year's services URL, which then redirects again to the current services page.

The visitor might still arrive, but each extra step can add delay. Long chains can also be harder to manage, and a faulty rule may send the visitor in a circle instead of to a working page. That is called a redirect loop.

A clearer arrangement is to point the original URL directly to the current destination where possible. When a page moves again, revisit earlier redirects rather than automatically adding another link to the chain.

As the owner, you do not need to inspect server rules. Ask your provider to confirm that important old addresses reach the final page directly.

How to check a redirect without being a developer

After the change is made, test the result from a customer's point of view.

1. Open the exact old URL. Type or paste the original address rather than clicking only the new menu item.

2. Look at where you arrive. Check that the final page is the intended replacement, not a generic homepage or unrelated service.

3. Read the destination. Confirm that the new page still answers the question someone following the older link would have had.

4. Check the address bar. The final address should be the current URL you approved.

5. Try a private browser window and a phone. This can help reveal differences caused by an existing browser session, saved data or device-specific behaviour, although it does not replace a technical check.

6. Ask about redirect hops. A technical provider or suitable inspection tool can confirm the redirect response and whether the route goes directly to the destination.

If the old address produces an error, opens the wrong page or keeps bouncing between addresses, report the exact old URL and the page you expected to see. Include the two addresses when reporting the issue.

A browser test confirms the visible experience. It does not necessarily confirm the HTTP status code behind the redirect. Ask your provider to verify the permanent or temporary status when that distinction matters.

Update the links you control as well

A working redirect does not mean your business should keep using outdated addresses forever.

After the new page is live, update links you control in your website navigation, other relevant pages, social-media profiles, scheduled posts and active advertising, where applicable. If an important external website links to the older URL, you can ask its owner to update that link too.

Direct links to the final page are simpler for visitors and avoid an unnecessary extra step. The redirect remains useful for bookmarks, older posts and links you cannot immediately change.

For permanent page moves, Google recommends keeping redirects in place for generally at least a year, and considering longer retention for people using older links. This is a planning guideline, not an expiry date that automatically applies to every website.

Questions worth asking your website provider

You can keep the conversation practical:

· Which existing URLs will change, and what are their replacement addresses?

· Which moves are permanent and which, if any, are temporary?

· Does each old URL lead to the closest relevant page?

· Have older redirects been updated to avoid unnecessary chains?

· Can you confirm the redirects work and use the intended status codes?

· Which links we control should we update after the change?

If your platform does not support the requested redirect in its usual editor, ask what options are available before deleting the old page. Different website builders and hosting systems offer different controls.

A good redirect keeps the journey clear

Website addresses sometimes need to change as a small business grows. The important thing is not to make every URL permanent at all costs. It is to protect the route visitors already know when useful information moves.

For a genuine move, choose a relevant destination, agree on whether the change is permanent or temporary, test the original link and avoid sending visitors through a series of unnecessary redirects. For content that has ended without a suitable replacement, an honest missing-page response may be better.

If you are planning website changes and are unsure what should happen to existing links, WebWise Management can help review the page changes and discuss a practical plan that keeps the customer journey understandable.

Contact

Reach out anytime for personalized support.

Email:

Phone:

info@webwisemanagement.co.za

+27 72 709 7557

© 2026. All rights reserved.

Services

Home

Portfolio

Contact