301 Redirects Explained: When and How to Use Them

What is a 301 redirect?

A 301 redirect is a server response that says a page has moved permanently to another URL. Its full HTTP status is 301 Moved Permanently.

When someone requests the old address, the server returns the 301 response and the new location. The browser then loads the destination automatically:

Old URL
https://www.example.com/old-service/

301 Moved Permanently
↓

New URL
https://www.example.com/services/new-service/

The old URL remains useful as a route for people, bookmarks and external links, but the new URL becomes the intended permanent destination.

Google treats a permanent server-side redirect as a strong signal that the target URL should be canonical. That means the new page is normally the version intended to appear in search once the move has been processed.

What does a 301 redirect do for SEO?

A well-planned 301 redirect helps preserve continuity when URLs change.

• Visitors reach the right content: old bookmarks, adverts and links continue to work.
• Crawlers receive a clear move signal: the response states that the new location is permanent.
• Canonical signals can consolidate: Google can treat the destination as the representative version of the moved page.
• External links retain a useful route: links pointing to the old address lead to the relevant replacement.
• Duplicate URL versions can be unified: protocol, hostname or path variations can resolve to one preferred format.

A redirect does not guarantee that two unrelated pages will share rankings or that the destination will perform exactly like the source. Content relevance still matters. If an old guide redirects to a generic homepage, the homepage does not suddenly become an equivalent guide.

Search engines also need time to recrawl the old URL, follow the redirect and process the destination. It is normal for old addresses to remain visible in reports or occasionally appear in search during the transition.

When should you use a 301 redirect?

A page has moved permanently

Use a 301 when you change a useful page’s URL and the content now lives at a new stable address. This applies to renamed articles, reorganised services and products moved into a better URL structure.

Two pages have been consolidated

If overlapping pages are merged into one stronger resource, redirect the retired URLs to the combined page. Make sure the destination covers the substance that made each old page useful.

A deleted page has a close replacement

A discontinued product may have a direct successor, or an expired event may have a new edition serving the same visitor need. A permanent redirect can be appropriate when the replacement is genuinely relevant.

The website has moved to a new domain

Map each old URL to its matching new-domain URL. Page-to-page redirects preserve the structure and user journey more effectively than sending the entire old site to the new homepage.

URL variations need one preferred version

Permanent redirects commonly consolidate:

• HTTP to HTTPS.
• Non-www to www, or the reverse.
• Trailing-slash and non-trailing-slash versions.
• Mixed-case paths to the preferred lowercase format.
• Old filename or extension formats.

Choose one convention and apply it consistently across redirects, canonical tags, internal links and XML sitemaps.

When should you not use a 301 redirect?

The move is temporary

If the original URL will return, use a temporary response such as 302 or 307. This tells search engines that the source should generally remain the primary URL.

The old page has no relevant replacement

Return a proper 404 Not Found or 410 Gone response when content has been permanently removed and no suitable alternative exists. Redirecting unrelated URLs to the homepage can confuse visitors and may be treated as a soft 404.

You only want to choose between duplicate pages

If both duplicate URLs need to remain accessible, a canonical tag may be more appropriate. A redirect removes the source page from the visitor’s journey by sending everyone to the target.

You want to hide private or unwanted content

A redirect is not an access-control method. Use authentication for private material and an appropriate noindex rule for an accessible page that should stay out of search.

The new page is not ready

Do not redirect an important page to an incomplete placeholder simply to publish the new URL. Keep the existing page working or use an intentional temporary arrangement until the replacement is ready.

What is the difference between a 301 and 302 redirect?

Both responses send visitors to another URL. The difference is the expected duration and the canonical signal.

Choose based on what will happen to the source URL. If the old page is never coming back, use a permanent redirect. If visitors are being sent elsewhere only for a defined period, use a temporary one.

Google can sometimes interpret a long-standing temporary redirect as permanent, but relying on that interpretation makes the signal less clear. Send the status that matches your intent.

Check redirects in Clearcrawl

Clearcrawl shows the path between the requested URL and its final destination. This helps reveal redirects that appear to work in a browser but pass through unnecessary steps, return to themselves or finish on an error page.

Use the affected-page lists to find where your own site still links to old URLs. A redirect protects historic routes, but current internal links should point directly to the final destination.

Common 301 redirect examples

Changing an article URL

/blog/old-technical-seo-guide/
→ 301 →
/academy/technical-seo-guide/

The content has moved permanently, and the old article route sends visitors to its new home.

Consolidating overlapping pages

/services/seo-audits/
/services/technical-audits/
→ 301 →
/services/technical-seo-audits/

This works when the destination genuinely combines the useful information and purpose of the retired pages.

Moving from HTTP to HTTPS

http://www.example.com/about/
→ 301 →
https://www.example.com/about/

Apply the rule across equivalent pages and make internal links, canonicals and sitemaps use HTTPS.

Retiring a product with a direct successor

/products/model-100/
→ 301 →
/products/model-200/

Use this only when the new model is a meaningful replacement. If there is no equivalent, retain a useful retired-product page or return 404 or 410 according to the content plan. After choosing a destination, update the links that still point to the old URL and use the 404 guide when there is no relevant replacement.

How to implement a 301 redirect

The exact control depends on your CMS, ecommerce platform, hosting service or web server. Many platforms provide a redirect manager. Custom sites may use server configuration or application routing.

Whatever system you use, follow the same planning process.

1. 01
   List the source and target URLs.

   Create an explicit one-to-one map. Record the complete old URL and its best permanent destination. During a migration, keep this mapping separate from assumptions based only on matching filenames.

2. 02
   Check that the destination is suitable.

   Open the target and confirm that it answers the same or a closely related need. It should return 200 OK, load its intended content and be eligible for indexing when appropriate.

3. 03
   Add a server-side permanent redirect.

   Use your platform’s permanent option or configure a 301 response on the server. Server-side redirects are the clearest and most reliable approach for users and search engines.

   Avoid JavaScript redirects when a server response is available. JavaScript needs rendering before the move can be detected and may fail when scripts or resources do not load.

4. 04
   Update internal references.

   Change internal links, navigation, canonical tags, hreflang annotations, structured data and XML sitemaps to use the target URL directly. Do not leave the old address in the sitemap simply because it redirects correctly.

5. 05
   Test the whole route.

   Request the source URL and confirm that it returns 301 with the intended Location header. Follow the redirect and verify that it reaches one final working page without a chain or loop.

How to fix redirect problems

Redirect chains

URL A → URL B → URL C

Change A so that it redirects directly to C, then update internal links to C. This shortens the journey and reduces the chance that one step will later fail.

Redirect loops

URL A → URL B → URL A

Browsers eventually stop and show an error. Review overlapping server, CMS and CDN rules, then keep one clear direction towards the final destination.

Redirects to 404 or 5xx pages

A valid 301 can still lead to a broken destination. Restore the target, select a better replacement or remove the redirect when the source should return a genuine 404 instead.

Irrelevant bulk redirects

Rules that send every discontinued product or deleted article to one category or homepage may create poor journeys and soft 404 signals. Map only URLs with a meaningful replacement.

Redirected URLs in internal links or sitemaps

The redirect may remain useful for external links, but your current site should reference the final URL. Update the system that generates the old links so the problem does not return after the next deployment.

How to verify a 301 redirect

Check the implementation from both ends:

• Confirm that the old URL returns 301 Moved Permanently.
• Confirm that the Location points to the intended complete URL.
• Follow the route and make sure the destination returns 200 OK.
• Check that no intermediate redirect, loop or error occurs.
• Run another Clearcrawl crawl and remove internal links to redirecting URLs.
• Remove old URLs from XML sitemaps and other page signals.
• Inspect important migrated URLs in Google Search Console after recrawling.

Search Console can continue to show old URLs while Google processes the move. Monitor the indexed destination and the crawl dates instead of repeatedly changing a redirect that is technically correct.

For a domain or large-site migration, retain redirects for as long as visitors and search engines may still use the old addresses. Do not remove them immediately after the new pages begin appearing in search.

Common mistakes

Frequently asked questions