302 redirect
A 302 redirect ("Found") is an HTTP response that sends the browser to another address temporarily: the browser asks the original address again on every visit.
Updated September 24, 2026
Example
GET /k7Rp2x HTTP/1.1
Host: qrtada.com
HTTP/1.1 302 Found
Location: https://bluedoorcafe.com/menu
Cache-Control: no-storeWhy it matters
If a QR code service used a permanent redirect (301), browsers could cache it: someone who already scanned your code would keep landing on the old page after you edit it. With a 302 and a no-store header, every scan asks the server and gets the current destination. It is also what makes counting each scan possible. See how it compares with the 301 redirect.
Frequently asked questions
Does a 302 redirect hurt my page's SEO?
No. QR codes are not an SEO lever: the 302 does not affect how your landing page ranks.
Does the redirect slow things down?
Barely: a few milliseconds on the server before your page starts loading.
Sources
Ready to print a QR code that never dies?
7 days for $0, card required, a reminder 2 days before the first charge, cancel in 2 clicks.