Vercel redirect CSV:
check the status column.

1. Use the schema’s exact field name

Vercel’s bulk-redirect schema calls the field statusCode. On September 25, 2026, its CLI file-format example instead showed status. Check the current schema before preparing your own file.

statusCode selects an explicit code. The schema lists 301, 302, 303, 307 and 308. Without it, the documented fallback is permanent, then 307. Choose the code for your intended behavior; do not make every redirect permanent automatically.

These instructions concern bulk redirects, not every Vercel routing mechanism. Bulk redirects do not support wildcard or header matching. Use explicit source paths here; check the separate configuration-redirect documentation if you need patterns.

2. Start with a clearly labeled example

These three fictional mappings show two permanent redirects and one temporary redirect. They are learning files, not a map for your site. No example URL is visited by our audit.

source,destination,statusCode
/field-notes/old-trail-map,/guides/trail-map,301
/gear/old-lantern,/gear/camp-lantern,308
/help/shipping-times,/help/delivery,302

source,destination,status
/field-notes/old-trail-map,/guides/trail-map,301
/gear/old-lantern,/gear/camp-lantern,308
/help/shipping-times,/help/delivery,302

Our structural audit returns the same result for both: 3 rows · 0 errors · 0 needs review · 3 clear.

The source/destination pairs are identical. Changing only this status header does not change our audit result. A downloaded findings report is not a Vercel import file.

3. Check your map’s structure separately

1. Keep your original provider CSV. Use the current schema and your intended status codes there.
2. Open the optional free audit. Paste either example, or choose its downloaded CSV. For these fictional paths, keep https://example.com as the source website. For your own map, enter your actual source origin.
3. Review source/destination findings. The audit accepts these two column names and ignores the extra status column. It checks up to 1,000 rows and files up to 4 MB locally in your browser, without an account.
4. Export findings if useful. Correct your original map, then recheck it. The report does not carry a verified Vercel status configuration.

Want a worked example of chains and conflicting destinations? Our general audit workflow explains those findings. The examples above intentionally isolate the header distinction.

4. Review staged changes, then test live

1. Confirm the current bulk schema and availability. Check Vercel’s current bulk-redirect documentation, including plan eligibility and limits.
2. Review the staged result. For runtime updates, inspect each intended source, destination and HTTP status before publishing. Check additions, edits and removals against your existing redirects. The source-control workflow applies changes on deployment instead.
3. Verify actual responses after your release. Test representative URLs on the intended domain. Confirm the HTTP status, destination and final page. Check query handling, case and trailing slashes where your migration relies on them.

Neither a successful upload nor a clear structural audit proves live routing, page content, indexing or search rankings. RedirectAtlas does not install these redirects or verify provider acceptance.

What we checked

Checked September 25, 2026 against Vercel CLI source commit c628be7 and its CSV validation code. Our local reproduction finds that both examples pass the CLI’s shallow CSV check and their bytes are passed through unchanged. That is not a test of Vercel’s server-side parser.

We did not upload to a Vercel account or verify a staged/live status. A user-reported wrong-status issue motivates checking carefully; it does not establish how every current deployment behaves.

This article runs no analytics. The optional audit has a separate consent choice. RedirectAtlas is an independent RTG Product Labs tool, not a Vercel service.