Craig Campbell SEO Training & Consultancy

Tutorials

Redirects for SEO: choose the right response and protect useful journeys

By Craig Campbell · 16 Nov 2026

7 min read

A redirect is useful when an address really needs to change. The important decisions are whether to move it, where visitors should land and how to check that the replacement works—not just which status code to select.

This guide covers those decisions from planning to maintenance. It complements the existing redirect chains article rather than replacing it. The UK shop example is fictional and illustrative only; no client results are invented.

1. Decide whether the URL needs to move

A redirect sends a request for one address to another. Use one when a page genuinely moves, you consolidate equivalent content or you standardise a website address. It is not a reason to rename established pages just to add a keyword.

  • Keep a useful page at its existing address when only its content needs improving.
  • Redirect a moved page to its real replacement.
  • Investigate overlapping pages before deciding to merge them.
  • Keep a product page useful if an item is temporarily unavailable and will return.

Write down the reason for the change, the old URL and the intended destination before touching any rules. The content refresh guide covers improvements that do not need a new address.

2. Choose permanent or temporary

Choose the response that reflects the real situation, not the one you think will produce an instant ranking gain.

  • 301 or 308: permanent server-side redirects for a move you do not expect to reverse. Google uses these as a signal that the target should be canonical.
  • 302 or 307: temporary redirects when the original address is expected to return. Google follows them, but its indexing pipeline does not use the redirect itself as that canonical signal; other signals can still influence indexing.
  • No redirect: keep the page when the address has not changed and it still provides the intended answer.

301 and 308 serve the same permanent-move purpose for Google Search, but HTTP request-method handling differs. Likewise, 302 and 307 are not interchangeable for every application request. Have the person managing the website check forms, payments or other non-GET requests before changing their behaviour.

Do not use a temporary redirect for a permanent move simply because it is easier to configure. Nor should a temporary promotion become an unreviewed permanent replacement.

3. Map to a genuine replacement

Open both pages and compare the audience task. A successful response at the end is not enough: the destination must still make sense to someone arriving through an old bookmark or link.

Fictional UK example — illustrative only

Lochside Cycle Works is a fictional Glasgow cycling shop. These paths describe an invented shop, not pages on Craig’s website or observed client results.

  • /bike-servicing → /cycle-servicing: a 301 is appropriate if the new page really replaces the same servicing information.
  • /summer-opening-hours: keep and update it if visitors still need that seasonal information; a wording change alone does not require a new URL.
  • /closed-workshop-event: keep a useful archive, or return a genuine missing-page response if the content is removed and has no replacement. Do not send everyone to the bike catalogue.
  • Temporary closure notice: first consider keeping the original page with accurate information. If a temporary redirect is necessary, record when it should be reviewed and removed.

None of these decisions implies a measured traffic or ranking outcome.

For removed content with no suitable equivalent, a proper 404 or 410 can be the right result. Google warns against redirecting many unrelated old pages to one irrelevant destination because that can be treated as a soft 404. The migration checklist covers reviewing the wider URL map.

For a platform change, use the website migration SEO guide to preserve articles, images and downloads alongside the reviewed redirect map. A working redirect alone does not prove the wider migration is complete.

4. Implement reviewed rules

Google recommends server-side redirects where possible. Configure them through the website, host or delivery service that actually handles the request. There is no universal plugin or configuration snippet that works safely for every platform.

  • Use explicit old-to-new mappings for individual moves.
  • Review broad pattern rules against real examples and exceptions.
  • Confirm the destination host is correct and controlled by the business.
  • Decide deliberately which query parameters should be kept or removed.
  • Keep a copy of the previous rules and an agreed rollback plan.

A rule that works for one page can misdirect many others if its pattern is too broad. Avoid letting untrusted visitor input choose an arbitrary external redirect destination.

JavaScript redirects depend on rendering and are a fallback, not the first choice for a normal site move. A canonical tag is also not a redirect: it suggests a preferred URL without taking the visitor there.

Keep useful old-address redirects, but change links under your control to the final intended destination. That includes menus, article links and collection pages. Use the internal linking guide to check context as well as the address.

  • Update internal links to avoid unnecessary hops.
  • List preferred canonical, indexable destinations in sitemaps.
  • Review canonical tags and, where applicable, hreflang references.
  • Check that new redirects do not collide with older rules.

If several historic addresses need to reach the same equivalent page, keep each useful source mapping. The existing redirect chains guide explains shortening the route without breaking old incoming links.

When a move affects country or language versions, use the international SEO guide to review the audience, equivalent destinations and visitor access alongside your redirect plan.

6. Test the entire reader journey

Test before release and again on the public website. Check the response path and read the final page; a redirect checker alone cannot judge whether the answer is relevant.

  • Request each important old URL and record its first response.
  • Follow the full path and check for loops or unexpected hosts.
  • Confirm the final page loads normally and answers the original task.
  • For pages intended for search, check noindex, robots access and canonical signals.
  • Test relevant HTTP/HTTPS, hostname, slash and query-string variants.
  • Open representative old links on a phone and check navigation works.

Use a reviewed sample for large patterns, plus every important exception. Record what was checked and what remains unverified. The technical SEO audit guide places these checks alongside crawl and indexing evidence.

7. Maintain and monitor the move

For site moves, Google recommends keeping redirects for at least a year. Useful bookmarks and external links can justify retaining them much longer. Do not delete a working historical mapping simply because the new page has appeared in search.

Use Search Console to inspect representative old and new URLs and review indexing evidence. Keep dates for the release, later changes and any problems. A visitor reaching the right page does not mean Google has already processed the move.

Review clicks and genuine business outcomes over comparable periods, allowing for seasonality and other changes. Do not assign a fixed percentage of lost link value to each hop or promise that a redirect will preserve every ranking. A before-and-after traffic change alone does not prove causation.

Checklist and next step

  • Is moving the address genuinely necessary?
  • Does the response match a permanent or temporary move?
  • Is the destination a useful equivalent rather than a convenient homepage?
  • Have you tested exceptions, loops and the final content?
  • Are current links and search signals consistent?
  • Is there an owner for monitoring and long-term maintenance?

Start with one reviewed page group and a clear URL map. Redirects protect useful journeys during change; they do not guarantee crawling, indexing, rankings or enquiries.

Sources and review notes

Google’s redirect guidance was checked on that date. The site-move source below is reused with its original check date. The workflow and fictional shop are teaching recommendations, not a claim that Craig personally tested them.

Let's work together.

Whether you need an SEO partner, a consultant, a speaker for your event or training for your team — get in touch and let's chat.

Get in touch
Get in touch