301 vs 302 Redirects: How to Plan Them Before You Change a URL

A 301 redirect is permanent and tells Google the old URL has moved for good, so use it when you change a URL, merge pages or move a site. A 302 is temporary, for short-term moves such as a test or maintenance page. Map every old URL to its closest new page and avoid redirect chains.

A redirect sends visitors and search engines from one URL to another. It is a small technical detail that decides whether a page change keeps its search visibility or loses it. This guide explains the difference between 301 and 302, when each one fits, how to plan redirects before changing URLs and which mistakes cause the most damage.

Key takeaways - Use 301 for permanent moves and 302 for temporary ones. - Redirect each old URL to the most relevant new page, not to the homepage. - Plan the redirect map before you change anything, then test it. - Avoid chains and loops. One hop from old to new is the target. - Update internal links, sitemaps and canonical tags to the new URLs.

What is a redirect?

A redirect is an instruction from the server saying that a URL now lives somewhere else. Anyone who requests the old address is sent to the new one automatically, and search engines learn the change.

What is the difference between 301 and 302?

Google can treat a long-lasting 302 as a permanent move, but you should not rely on that. Choose the code that matches your intention.

When should you use a 301 redirect?

• You change a page's URL or slug.
• You move from HTTP to HTTPS.
• You choose one version of the site, such as www or non-www.
• You merge two similar pages into one.
• You move to a new domain.
• You delete a page that has a close replacement.

When should you use a 302 redirect?

• A product is out of stock for a short time and you send visitors to a related page.
• A page is under temporary maintenance.
• You run a short test or campaign and will bring the original URL back.

If the old URL will not return, use a 301.

How do you plan redirects before changing URLs?

1. Ask if you need to change the URL at all. Every change carries some risk. Change URLs only when there is a good reason.
2. List all current URLs. Use a site crawl, your sitemap, Search Console and analytics so you do not miss pages that get traffic.
3. Decide the new URL for each page. Keep URLs short, readable and consistent.
4. Build a redirect map in a spreadsheet, such as the table below.
5. Match by meaning, not by title. Send each old page to the page that answers the same question.
6. Implement the redirects on the server or through your CMS. Your developer will know which method suits your hosting.
7. Test a sample of old URLs and confirm they reach the right page in one step.
8. Update internal links, the XML sitemap and canonical tags to the new URLs.
9. Monitor Search Console for new errors and watch traffic on the changed pages.

An example of a permanent redirect on an Apache server (your hosting may use a different method):

apache Redirect 301 /old-service-page/ https://www.example.com/new-service-page/

What are redirect chains and loops?

A chain happens when one URL redirects to another that redirects again, such as A to B to C. Chains slow visitors down and waste crawling. Fix them so A goes straight to C. A loop happens when redirects send visitors in a circle, such as A to B to A, and the page never loads. Google follows only a limited number of hops, so aim for one.

Chains often appear after several redesigns, when each new set of redirects is added on top of the previous one. Review old redirects whenever you add new ones.

What mistakes do the most damage?

• Redirecting everything to the homepage. Google may treat irrelevant redirects as errors, and visitors lose the page they wanted.
• Using 302 for a permanent change.
• Leaving internal links pointing at old URLs, so every click passes through a redirect.
• Blocking old URLs in robots.txt, so Google cannot see the redirect.
• Forgetting parameters or trailing-slash versions of the old URL.
• Removing redirects too soon. Google recommends keeping redirects in place for at least a year, and longer is fine.
• Changing URLs without a reason.

What about WordPress sites and migrations?

WordPress can handle redirects through plugins or server settings, and your developer can set them at server level. When upgrading or moving a site, redirects are part of the plan, not an afterthought. See how to upgrade WordPress safely without losing SEO and why website migration matters, when to do it and what to expect.

How does DAB handle this?

DAB provides technical SEO and website migration support in Thailand and has 18+ years of experience in web design and SEO in Bangkok. Our technical SEO services include planning redirects so URL changes do not cost you search visibility.

Planning a URL change or a site move?

If you are changing URLs, merging pages or moving a site, contact DAB through LINE or our contact page before you start. Learn more about our technical SEO services in Thailand.

FAQ