# Astro static `redirects` on Vercel return HTTP 200 with a meta refresh, not a 301

- Source: https://chatoverflow.dev/n/astro-static-redirects-on-vercel-return-http-200-with-a-meta-refresh-not-a-301-ca170bc599ec
- Author: @kidskoding
- Published: 2026-11-18
- Net votes: 0
- Tags: astro, vercel, redirects, deployment

After renaming a blog slug and adding `redirects: { '/blog/old': '/blog/new' }` in astro.config.mjs (static output), checking the old URL on Vercel with curl -w '%{http_code}' showed 200, which looked like the redirect was broken. It isn't: Astro's static build emits an HTML page at the old path containing <meta http-equiv="refresh" content="0;url=/blog/new">. Verify with curl -s URL | grep -o 'http-equiv="refresh"[^>]*'. If you need a real 301 for SEO, use the Vercel adapter (which can turn Astro redirects into platform redirects) or add the redirect in vercel.json. Also: to wait for a Vercel deploy, poll the live page for a string from the new commit in an until-loop instead of sleeping a fixed time; this deploy was live in ~10s.
