301 vs 302 vs 307 vs 308 Redirects: Which One to Use When You Change Your Website

You've just launched your new website. It looks better, loads faster and finally works on mobile. Two weeks later, enquiries drop. Old pages that used to rank now show errors, or Google keeps showing your old URLs.

Very often, the cause is a small technical choice made during launch: which redirect was used, or whether one was used at all.

Google's Search Central team released a video on 4 November 2026 titled "301, 302, 307, 308: Which redirect is the chosen one?", a sign that this is still one of the most common mistakes site owners make.

This guide explains the four redirect codes in plain language, how Google treats each one, and a simple checklist to follow whenever you redesign, rename pages or move domains.

Quick answer: Use a 301 (or 308) when a page has moved for good. It tells Google the new URL should replace the old one in search results. Use a 302 (or 307) only when the move is temporary and you want Google to keep the original URL. For Google Search, 308 is treated like 301 and 307 like 302. The difference is that 307 and 308 also keep the browser's request method, which matters for forms and APIs, not for normal pages.

What a redirect does

A redirect sends visitors and search engines from one URL to another. Google's guide to redirects and Google Search lists the common reasons:

1. You moved your site to a new domain
2. People reach the same page through several URLs (with and without www, http and https)
3. You merged two websites
4. You removed a page and want to send users to a new one

Visitors usually can't tell the difference between redirect types. Google can. It uses the type of redirect as a signal for which URL to show in search results.

The four redirect codes, explained

301: Moved permanently

The most common redirect. Google's documentation says it follows a 301 and uses it as a strong signal that the target should be processed. In its redirect guide, Google says permanent redirects tell the indexing pipeline that the new URL should be canonical, so the new URL shows in search results.

302: Found (temporary)

Google follows a 302 too, but its indexing pipeline doesn't use it as a signal that the target should be canonical. The original URL usually stays in search results. That is exactly what you want for a short-term move, and exactly what you don't want for a permanent one.

307: Temporary redirect

Google's HTTP status code documentation says a 307 is "equivalent to 302" for Google.

308: Permanent redirect

Similarly, Google treats a 308 as "equivalent to 301".

So why do 307 and 308 exist?

They come from the HTTP standard. Under RFC 9110, a browser following a 301 or 302 may change a POST request (such as a form submission) into a GET request. With 307 and 308, the method must stay the same. This matters for forms, payment steps and APIs. For an ordinary service page or blog post, 301 and 308 behave the same in Google Search.

Google also notes that although it treats these pairs the same way, they are semantically different, so use the code that fits the situation, because other clients and search engines may rely on it.

1. 301. Type: Permanent. Google treats it as: Strong signal: show the new URL. Use it when: A page, section or domain has moved for good.
2. 308. Type: Permanent. Google treats it as: Same as 301. Use it when: A permanent move where the request method must be kept (forms, APIs).
3. 302. Type: Temporary. Google treats it as: Keep the original URL in results. Use it when: A short-term move, such as a page under maintenance or an A/B test.
4. 307. Type: Temporary. Google treats it as: Same as 302. Use it when: A temporary move where the request method must be kept.

Key takeaways

1. Permanent move: 301 or 308. Temporary move: 302 or 307.
2. Google treats 308 like 301 and 307 like 302; the pairs differ only in keeping the request method.
3. A 302 on a permanent move can keep your old URL in Google instead of the new one.

Where websites go wrong

Using a 302 for a permanent change

Many CMS plugins, hosting panels and frameworks default to 302. If your redesign moved every page and the redirects are 302s, Google may keep showing old URLs, because a temporary redirect isn't a canonical signal.

Sending every old page to the home page

Google's site move guide warns against redirecting many old URLs to one irrelevant destination, such as the home page. This confuses users and might be treated as a soft 404. Redirect each old URL to its closest new equivalent. If you merged several pages into one, redirecting them to that merged page is fine.

Building redirect chains

Old page to page B to page C to the final page. Google says Googlebot can follow up to 10 hops, but it advises redirecting straight to the final destination, or keeping chains ideally to no more than 3 and fewer than 5. Chains also slow pages down for users.

Relying on JavaScript or delayed redirects

Google recommends server-side redirects. It treats an instant meta refresh as permanent and a delayed one as temporary, and suggests JavaScript redirects only when the other options aren't possible, because rendering can fail.

Removing redirects too early

Google's site move guide says to keep redirects for as long as possible, generally at least one year, so Google can transfer signals and recrawl links from other websites. From a user's point of view, keeping them indefinitely is even better.

When a temporary redirect is the right choice

302 and 307 aren't bad. They're simply for temporary situations:

1. A/B tests: Google's testing guidance says to use a 302, not a 301, when a test redirects users from the original URL to a variation.
2. Short maintenance: a service page that is briefly unavailable can point to an explanation page while keeping its own URL in search.
3. Seasonal or campaign pages: a page that will return to its original URL after a short period.

If you're not sure the change is temporary, it probably isn't. Use a 301.

A redirect checklist for your next redesign or URL change

1. List every old URL. Use your sitemap, Search Console and analytics to find pages with traffic, links or enquiries.
2. Map each old URL to its best new match. One to one wherever possible. Don't send everything to the home page.
3. Use server-side 301 redirects for permanent changes (308 where forms or APIs need the method kept).
4. Redirect all versions: http and https, www and non-www, and old domains you still own.
5. Update internal links so they point directly to the new URLs instead of passing through redirects.
6. Check canonical tags on new pages so they point to the new URLs, not the old ones.
7. Submit an updated sitemap and monitor the Page indexing report in Search Console.
8. Test before and after launch that each old URL returns a 301 and lands on the right page in one hop.
9. Keep the redirects for at least a year, and ideally longer.

If pages drop out of Google after a launch, our guide to why web pages aren't getting indexed will help, and our SEO best practices for web developers covers what to build in from the start.

Examples of redirect setups

Here is how a permanent redirect looks in common setups. Your developer or hosting provider will know which applies to your server.

1. Apache (.htaccess) 301. For a permanent page move on Apache, add this line to .htaccess: Redirect 301 /old-services/cardiology /services/cardiology.
2. NGINX 301 or 308. For a permanent move, put return 301 https://www.example.com/services/cardiology; inside location = /old-services/cardiology { ... }. Use return 308 instead when the original request method must stay the same, such as a form or API.
3. WordPress plugin redirects. In a redirect plugin such as Redirection or Rank Math, add the old URL and the new URL and set the type to 301 for a permanent change. Do not add a plugin redirect on top of a server rule for the same URL, or you may create a chain.
4. 302 or 307 (temporary). Use a 302 for a short-term move such as an A/B test or a seasonal page, so Google keeps the original URL in search results. Use a 307 when that temporary move must also preserve the request method, such as a form or API endpoint.

These patterns follow the examples in Google's redirect documentation. Test every rule on a staging site first.

A note for hospitals and clinics

Healthcare websites change often: new departments, renamed specialities, doctors who join or move, and new branches. Each change can break URLs that patients bookmarked or that other websites link to.

1. When a doctor profile moves, redirect the old URL to the new profile.
2. When a speciality page is renamed, redirect the old URL to the new speciality page, not the home page.
3. When a department closes, redirect to the most relevant related page.

Small details like these protect the search visibility you've built over years. They also help patients find the right page when they need it.

Key takeaways

1. Map old URLs one to one and use server-side 301s for permanent changes.
2. Avoid home page dumps, redirect chains and JavaScript-only redirects.
3. Update internal links, canonicals and sitemaps, and keep redirects for at least a year.

How Pengwin Solutions helps

Pengwin Solutions designs and develops websites with SEO built in from the first sprint, with design, development and marketing in one team. For redesigns, URL changes and domain moves, we:

1. Audit your existing URLs, rankings, backlinks and enquiry pages before anything changes
2. Build a full redirect map and implement server-side 301s on your stack
3. Test every redirect, canonical tag and sitemap on staging and after launch
4. Monitor Search Console and fix crawl or indexing problems in the weeks after go-live

Explore our website development services, our SEO services and our healthcare digital services. If you're comparing platforms, see our guide to static vs dynamic websites.

Frequently asked questions

What is the difference between a 301 and a 302 redirect?

A 301 is a permanent redirect, and Google uses it as a signal that the new URL should be shown in search results. A 302 is temporary, so Google doesn't use it as a canonical signal and usually keeps the original URL in its results.

Is a 308 redirect better than a 301 for SEO?

No. Google treats a 308 the same as a 301. The difference is technical: a 308 requires the browser to keep the original request method, such as POST, which matters for forms and APIs but not for normal pages.

When should I use a 307 redirect?

Use a 307 for a temporary redirect where the request method must stay the same, such as a form or API endpoint that is temporarily handled elsewhere. Google treats a 307 the same as a 302.

Do 301 redirects lose PageRank or rankings?

Google's site move guide says 301 and other permanent redirects don't cause a loss in PageRank. Rankings can still change during a move if pages, content or internal links change, so map URLs carefully and monitor Search Console.

How long should I keep redirects after a website redesign?

Google recommends keeping redirects for as long as possible, generally at least one year, so it can transfer signals and recrawl links. Keeping them indefinitely is better for visitors using old bookmarks and links.

Can I redirect all old pages to my home page?

It's not recommended. Google warns that redirecting many old URLs to one irrelevant page, such as the home page, can confuse users and may be treated as a soft 404. Redirect each old URL to its closest matching new page.

Planning a redesign or URL change?

Call +91 90326 18332, email hello@pengwinsolutions.com, or contact Pengwin Solutions to plan a website launch with a complete redirect map, so your new site keeps the rankings and enquiries your old one earned.