301 and 302 redirects: what is the difference?
A redirect tells a browser to request a different address. A 301 response describes a permanent move; a 302 describes a temporary one. The choice should reflect what has actually changed, not a guess about which number is better for SEO. Redirects are separate from DNS connection records.
Useful context
- List the old address and its intended replacement.
- Decide whether the move is permanent or a genuinely temporary arrangement.
How it works
Use a relevant replacement
If /old-menu has been replaced by /menu, the newer menu is a useful destination. Sending a retired menu to an unrelated homepage makes customers start again. If no equivalent page exists, a helpful missing-page response may be more honest than an irrelevant redirect.
Match the status to the intention
A permanent address change usually calls for a permanent redirect. A temporary alternative should not silently become the new long-term location. Tell the developer what the business intends so the implementation and future review date make sense.
Keep the journey short
Record the final destination and check it does not redirect back to the original. Several historical moves can produce a chain of hops. Where appropriate, update controlled internal links to the final address instead of making every customer follow an old chain.
Check more than appearance
Open the original public link and confirm the final content and address. A developer can verify the actual HTTP response code. A page saying moved, or an automatic visual refresh, is not by itself evidence that a correct server redirect is in place.
What to check
- The destination answers the original visitor need.
- There is no redirect loop.
- The status reflects a permanent or temporary change accurately.
Sources and further reading
Platform features can change. Check the provider’s current guidance before changing a live service.