302 vs meta-refresh vs JS redirect — choose your redirect mechanism

302 vs meta-refresh vs JS redirect — choose your redirect mechanism

Three ways to bounce a click. Speed, referrer handling, and detectability differ. Pick deliberately.

302 server redirect — default:
— Fastest, no page render. Pure HTTP.
— Referrer behavior is predictable and controllable.
— Use for every standard tracker hop.

Meta-refresh:
— Page must load first, then redirect — slower.
— Strips referrer in many browsers (sometimes the point).
— Use only when you specifically need referrer stripping cheaply.

JS redirect:
— Lets you read screen size, fire a pixel, or run a bot check before bouncing.
— Dies if JS is blocked or the bot doesn't execute it — which is sometimes a feature for filtering.
— Use when you need a client-side decision before the redirect.

Tradeoffs:
— 302 is fast but exposes referrer chains some sources dislike.
— JS adds filtering power but a render delay and a failure mode.

Rule: 302 unless you specifically need referrer control (meta) or client-side logic (JS).

Save this SOP. Run this before every launch.