Quick answer
Use a 301 redirect when a page has moved permanently, because it passes ranking signals to the new URL. Use a 302 only for genuinely temporary moves. Redirect each old URL to the most relevant new page in one step, avoid chains and loops, update internal links, and test everything after changes.
Last updated: November 2026
Redirects are the quiet workhorses of website maintenance. Every time you change a URL, retire a page, merge content or move to a new domain, a redirect decides whether visitors and search engines end up in the right place or hit a dead end.
Used well, redirects preserve rankings and links through major changes. Used badly, they create slow chains, lost authority and confusing signals that can cost months of progress.
This guide explains the difference between the main redirect types, when each is appropriate, how to implement them in WordPress and on the server, and the mistakes to avoid during redesigns and migrations.
In this guide
- What a redirect does
- 301 redirects: permanent moves
- 302 and 307 redirects: temporary moves
- Meta refresh and JavaScript redirects
- Redirect chains and loops
- Choose the right destination
- How to set up redirects in WordPress
- Redirects during a redesign or migration
- Redirects and internal links
- A simple example
- Checklist before you redirect
- FAQs
What a redirect does
A redirect is an instruction sent by the server telling browsers and crawlers that a requested URL is now somewhere else. The visitor lands on the new page automatically, and search engines learn where the content lives.
Each redirect has a status code. The codes you will meet most are 301 (moved permanently), 302 (found, temporary), 307 and 308 (the stricter modern equivalents of temporary and permanent). Choosing the right one tells Google how to treat the old and new URLs.
301 redirects: permanent moves
A 301 says the old URL is gone for good and the new URL replaces it. Google generally passes the ranking signals of the old page to the new one and, over time, replaces the old URL in the index.
Use 301s when you change a URL structure, merge duplicate pages, move to HTTPS, switch domain, or delete a page that has a close replacement. Google has confirmed that 301 redirects do not lose PageRank in the way people once feared, as long as the redirect points to a relevant page.
302 and 307 redirects: temporary moves
A 302 or 307 says the move is temporary and the original URL should be kept in the index. Use them for short-term situations such as redirecting to a holding page during maintenance, running a time-limited promotion or A/B testing a landing page.
Problems arise when a 302 is left in place for months. Google may eventually treat a long-lived 302 like a 301, but you cannot rely on it, and you risk the wrong URL being indexed in the meantime.
Meta refresh and JavaScript redirects
A redirect can also be done in HTML with a meta refresh tag or in JavaScript. These are slower, less reliable and less clear to search engines than server-side redirects, so avoid them for SEO-critical moves. Use 301 redirects at the server, in your .htaccess file, in Nginx configuration or through a redirect plugin.
Redirect chains and loops
A chain occurs when A redirects to B, which redirects to C. Each hop adds delay for users, uses crawl, and risks Google not following all the way. A loop, where A redirects to B and B back to A, makes the page unreachable altogether.
Fix chains by pointing the first URL straight to the final destination. After site changes, run a crawl to detect chains and loops, and update old rules so they point to final URLs. Aim for a single hop in every case.
Choose the right destination
Redirect each old URL to the most relevant new URL, not automatically to the homepage. Mass-redirecting deleted pages to the homepage is treated by Google as a soft 404 in many cases and wastes the old page’s equity.
If a page has no equivalent, it is acceptable to return a 404 or 410 status. Use these to signal that content has been removed intentionally. For consolidated content, redirect to the single best replacement, and make sure the new page actually covers the old topic.
How to set up redirects in WordPress
- Use a plugin such as Redirection, Rank Math or Yoast Premium to manage 301 rules without editing server files.
- For large migrations, use server-level rules in .htaccess or Nginx, or a CSV import for hundreds of URLs.
- Always test a sample of old URLs after saving rules.
- Keep a log of redirects in a spreadsheet, including date and reason.
- Remember that plugin-based redirects stop working if the plugin is deactivated.
Redirects during a redesign or migration
Before launch, crawl the old site and list every URL, then map each to its new equivalent. Include images, PDFs and old blog posts that earn traffic or links. After launch, crawl the old URLs again to confirm each returns a 301 to the correct page and not an error.
Keep redirects in place for at least a year, ideally permanently for pages with backlinks. Our technical SEO service includes migration planning and redirect mapping, which is one of the most valuable ways to protect your rankings through a rebuild.
Redirects and internal links
Redirects should be a safety net, not a navigation method. Update internal links, menus, sitemaps and canonical tags to point directly to final URLs, so visitors and crawlers do not rely on redirects. This reduces crawl waste and speeds up the site.
A useful habit is to review your site’s internal links after any URL change using a crawl tool, and fix every link that triggers a redirect. It is a small job that prevents chains from building up over the years.
A simple example
A Cardiff solicitor merges three similar blog posts about wills into one comprehensive guide. The old URLs each have a few backlinks. The firm sets three 301 redirects from the old posts to the new guide, updates internal links to point to the guide, and removes the old URLs from the sitemap.
Within weeks, Search Console shows the guide absorbing the impressions of the old posts, and the combined page ranks higher than any of the originals did. Had the firm deleted the posts or redirected them all to the homepage, the links and rankings would have been wasted.
Checklist before you redirect
- Is the move permanent? Use a 301.
- Is the destination the closest relevant page?
- Will the redirect land in one step, with no chain?
- Have internal links, sitemaps and canonicals been updated?
- Have you tested the old URL in a browser and in a crawler?
- Have you recorded the change?
Technical SEO Services
Crawling, indexing, speed and schema fixed properly.
Frequently asked questions
Does a 301 redirect pass link equity?
Yes. Google has said that 301 redirects pass ranking signals to the destination, so links to the old URL continue to help the new one, provided the pages are relevant.
How long should I keep 301 redirects?
Keep them for at least a year, and permanently for URLs with valuable backlinks or steady traffic.
Is it bad to redirect everything to the homepage?
Usually yes. Google may treat it as a soft 404 and ignore the signals. Redirect to the closest relevant page where possible.
What is the difference between 301 and 308?
Both are permanent. The 308 keeps the HTTP method unchanged, while 301 may change POST requests to GET. For ordinary page moves, 301 is fine.