Redirects Explained: Permanent, Temporary and Chains

What a redirect does

A redirect is an instruction from your server that says, in effect, “the page you asked for is somewhere else”. When a browser or crawler requests the old address, the server answers with a status code and the new location, and the visitor ends up on the new page.

Redirects are how you keep old links, bookmarks and search listings working after a page moves. Used well, they are invisible. Used badly, they slow pages down and confuse crawlers.

Permanent and temporary

The two main families differ in what they say about the future.

Permanent redirects (301, and also 308). The move is lasting. Search engines generally treat the new address as the one to keep, and over time replace the old address with it. Use this when:

• A page has a new address for good.
• You are changing your domain or moving from http to https.
• You are merging two pages and want the old one to point to the combined one.
• You are choosing between versions of the address, such as with or without www.

Temporary redirects (302, and also 307). The move is short-term, and the original address is expected to come back. Search engines may keep the old address in their index. Use this when:

• A page is briefly unavailable and you send visitors to an alternative.
• You are running a short test or a time-limited promotion.
• Content depends on something like the visitor’s region, and the original address stays valid.

The common mistake is using a temporary redirect for something permanent, often because it was the default setting in a plugin or platform. Search engines have become fairly good at recognizing a temporary redirect that has stayed in place for a long time, but being explicit is safer.

Other kinds exist. Redirects done through a meta refresh tag or a script work, but they are slower and less clear than a server-level redirect, so they are generally a last resort.

Redirect chains

A chain happens when one redirect leads to another, which leads to another. For example:

1. http://example.com/old-page redirects to
2. https://example.com/old-page, which redirects to
3. https://www.example.com/old-page, which redirects to
4. https://www.example.com/new-page.

Each step is an extra request. For visitors, that adds delay, particularly on slow mobile connections. For crawlers, it means extra fetches, and very long chains may be abandoned before reaching the end. Chains tend to build up over years of changes: a protocol switch, then a rename, then a redesign, each adding a layer on top of the last.

The fix is to point every old address straight to the final destination in a single step.

Redirect loops

A loop happens when redirects send a request in a circle, such as page A to page B and back to A. The browser eventually gives up and shows an error saying the page redirected too many times. Loops often come from conflicting rules, for example one rule that adds a trailing slash and another that removes it, or an https rule fighting with a setting at a content delivery layer.

Loops are always errors. Visitors cannot reach the page, and crawlers cannot either.

How to find them

• Crawl the site with a desktop crawler and look at its redirect reports. Most can show chains, the number of hops, and loops.
• Check specific addresses with a tool that shows the full sequence of status codes for a URL.
• Test the usual variants. Request the http and https versions, with and without www, with and without a trailing slash. Each should reach the final page in at most one hop.
• Review internal links. Links in your navigation or content that point to redirecting addresses create unnecessary hops for every visitor.
• Check your sitemap. It should list final addresses only, not ones that redirect.

Cleaning up

1. List the redirects you have, including those in server settings, plugins and the platform.
2. Flatten chains so each old address goes directly to the final page.
3. Fix loops by finding the conflicting rules and removing one of them.
4. Update internal links to point directly to the final address, so redirects serve only outside visitors.
5. Match the content. Redirect an old page to the closest relevant replacement. Sending unrelated pages to the home page tends to frustrate visitors and may be treated as a soft error.
6. Keep long-lived redirects in place. Search engines and other sites may take a long time to catch up, and people may keep old bookmarks for years. As a general habit, keep permanent redirects for a long time rather than removing them after a few weeks.
7. Recheck after changes with a new crawl.

Planning for big changes

During a site migration, a spreadsheet mapping every old address to its new equivalent is the backbone of the work. Prepare it before launch, test a sample, and check again after launch for errors and chains. Meanwhile, fixing broken links so they do not need a redirect at all is cleaner than adding redirects on top of them.

A final habit worth building: every time you rename or move a page, ask what already points at the old address, and update those links as part of the change.