Use a 302 redirect only when the move is truly temporary. If a page has moved for good, use a 301 or 308 instead. That one choice can decide which URL ranks, which URL stays indexed, and how clean your migration feels.
TLDR: A 302 redirect says, “Send visitors here for now, but the old URL may come back.” Search engines may pass some link equity through it, but they often keep the original URL indexed. For example, a store that redirected /summer-sale to /clearance with a 302 for 21 days saw the old URL stay in Google, while clicks dropped by 12%. When they switched to a 301 after making the move permanent, indexing cleaned up in about two weeks.
What Is a 302 Redirect?
A 302 redirect is a temporary redirect. It tells browsers and search engines that a URL has moved, but only for a while.
Think of it like a sign on a shop door:
- 302: “We are serving customers next door today.”
- 301: “We moved. This is our new address.”
That small difference matters. Search engines do not just follow redirects. They also make decisions about ranking signals, canonical URLs, and indexation.
Honestly, it feels like one tiny status code should not cause this much SEO drama. But it does.
302 Redirects and Link Equity
Link equity is the ranking value a page earns from links. People often call it “PageRank,” though Google has changed a lot since the old toolbar days.
So, does a 302 pass link equity?
Often, yes. Modern search engines are smarter than they used to be. Google has said that 30x redirects can pass PageRank. That includes 301, 302, 307, and 308 redirects.
But here is the annoying part. A 302 still sends a different message than a 301.
A 302 says:
- The original URL may return.
- The old URL may still be the main URL.
- The destination may be a short-term substitute.
So even if ranking signals move, the indexing choice may not.
That means your new page might get traffic from users, but the old URL might still appear in search results. This can be fine. Or it can be a mess.
How 302 Redirects Affect Indexation
Indexation is about which URL search engines store and show.
With a 301 redirect, search engines usually replace the old URL with the new one over time. That is the expected behavior.
With a 302 redirect, search engines may keep the old URL indexed. Why? Because you told them the move is temporary.
This is useful when you want the old page to come back.
Good uses include:
- A product is out of stock for a few days.
- A landing page is being tested for one week.
- Users are sent to a seasonal offer page.
- A site is under short maintenance.
- You are running a short geo or device test.
Bad uses include:
- You changed your URL structure forever.
- You moved from HTTP to HTTPS.
- You merged two sites.
- You rebranded and changed domains.
- You removed an old page and replaced it fully.
If the move is permanent, a 302 creates mixed signals. Search engines may wonder, “Should I keep the old URL? Should I rank the new one? Is this temporary or not?”
Expect to waste time on cleanup if your redirect map is full of accidental 302s. One crawler export can turn into a 3-hour spreadsheet headache.
302 vs 301: Simple SEO Rule
Use this rule:
- Use 302 when the original URL should return.
- Use 301 when the original URL is gone for good.
- Use 308 for a permanent move when you need the request method preserved.
- Use 307 for a temporary move when you need the request method preserved.
For normal SEO work, most teams use 301 for permanent moves and 302 for temporary ones. Simple. Clean. Boring in the best way.
When a 302 Can Become Treated Like a 301
Search engines watch behavior over time.
If a 302 stays in place for months, Google may decide it is not really temporary. It may start treating it more like a permanent redirect.
That sounds helpful. Sometimes it is.
But do not build a migration plan around “Google will probably figure it out.” That is the SEO version of leaving your keys in the freezer and hoping future you understands why.
If you know the move is permanent, say so with the right status code.
How 302 Redirects Can Hurt Migration Planning
SEO migrations need clear signals. A messy redirect setup can hurt rankings, slow indexing, and confuse reporting.
Common problems include:
- Old URLs stay indexed. Search results show outdated URLs.
- New URLs rank slowly. Search engines hesitate to swap them in.
- Signals split. Links, canonicals, sitemaps, and redirects point in different directions.
- Analytics get messy. Landing page reports show old paths and new paths mixed together.
- Crawlers burn budget. Bots spend time following avoidable redirect chains.
A Quick User Case
A SaaS company changed its blog URL structure from /blog/post-name to /resources/post-name.
The developer used 302 redirects because the CMS had that as the default. Classic.
After 30 days:
- 42% of old blog URLs were still indexed.
- Organic clicks to the blog dropped by 9%.
- Google Search Console showed both old and new URLs getting impressions.
- Some reports took 6 to 8 seconds longer to filter because the URL data was split.
The fix was simple. They changed permanent moves to 301s. They updated internal links. They refreshed the XML sitemap. They kept only final URLs in canonical tags.
Four weeks later, most old URLs dropped from the index. Traffic was nearly back to normal.
Best Practices for 302 Redirects
Use 302s with a timer in mind. If “temporary” has no end date, it may not be temporary.
Follow this checklist:
- Set a review date. Check the redirect after 7, 14, or 30 days.
- Keep redirects direct. Avoid chains like URL A to B to C.
- Match intent. Redirect users to a page that answers the same need.
- Do not redirect everything to the homepage. That is lazy and usually bad.
- Update canonicals. They should support your preferred URL.
- Check sitemaps. Only include URLs you want indexed.
- Monitor Search Console. Watch indexing, clicks, and crawl issues.
Migration Planning: What to Do Before Launch
Before any site move, build a redirect map. List every old URL. Match each one to the best new URL.
Then label each redirect:
- Permanent: Use 301 or 308.
- Temporary: Use 302 or 307.
- Gone: Use 410 when the page is removed and has no replacement.
- Keep live: No redirect needed.
Test the redirects before launch. Use a crawler. Check status codes. Check final destinations. Check that internal links point to the new URLs, not through redirects.
After launch, crawl again. Then compare organic clicks, impressions, rankings, and indexed pages. Do this weekly for at least a month.
The Simple Takeaway
A 302 redirect is not “bad SEO.” It is just easy to misuse.
Use it when the move is short term. Use a 301 or 308 when the move is permanent. Keep your signals consistent. That means redirects, internal links, canonicals, and sitemaps should all point to the same answer.
Search engines like clear instructions. So do users. Give both the right sign, and your SEO migration has a much better chance of staying calm.
Published on August 26, 2026 under .
