301 vs 302 redirect
Two HTTP redirect status codes with different caching implications. 301 = permanent (browsers cache it and skip the redirect on future requests). 302 = temporary (browsers re-fetch every time). For affiliate redirects, always use 302.
A 301 tells browsers and proxies "this URL has permanently moved; cache the new location and never ask me again." A 302 says "this URL is temporarily elsewhere; check with me every time." For website restructures and SEO, 301 is correct because the destination is meant to be permanent. For affiliate redirects, 301 is dangerous: a browser that cached your affiliate URL → Amazon redirect last week would bypass your tracking entirely the next time the user clicks.
The rule for managed-URL services: always 302. Add Cache-Control: no-store headers as belt-and-suspenders. Every click should re-traverse your platform so click counting, bot filtering, and dynamic destination updates all work. The reason this matters is that affiliate destinations change. ASINs get reassigned, products go out of stock, networks change shortlink formats. With 301-caching, those clicks land on stale destinations forever.
See also
Related terms
Managed URL
A redirect URL on a domain you control that points to your underlying affiliate URL. Update the destination in one place; every platform using the managed URL reflects the change instantly.
GlossaryLink cloaking
The practice of replacing an ugly affiliate URL with a clean, brand-friendly URL on your own domain that redirects to the affiliate destination. Originated in WordPress plugins like ThirstyAffiliates and Pretty Links.
GlossaryAffiliate link
A URL that contains a tracking parameter identifying you as the referrer, so the merchant can credit you a commission when the click converts to a sale.