Getting Started

Bulk redirects can be specified either as part of a Edgenivo deployment or updated immediately through the UI, API, or CLI by settings redirects at the Project level without the need for a new deployment.

• Deployment-time redirects
• Project-level redirects

Bulk redirects in deployments are specified in the bulkRedirectsPath field in vercel.json. bulkRedirectsPath can point to either a single file or a folder with up to 100 files. Edgenivo supports any combination of CSV, JSON, and JSONL files containing redirects, and they can be generated at build time.

Learn more about bulk redirects fields and file formats in the project configuration documentation.

1. Create your redirect file

   You can create fixed files of redirects, or generate them at build time as long as they end up in the location specified by bulkRedirectsPath before the build completes.

   redirects.csv

   source,destination,permanent
   /old-blog,/blog,true
   /old-about,/about,false
   /legacy-contact,https://example.com/contact,true
   https://old-domain.com/blog,/blog,true

   redirects.json

   [
     {
       "source": "/old-blog",
       "destination": "/blog",
       "permanent": true
     },
     {
       "source": "/old-about",
       "destination": "/about",
       "permanent": false
     },
     {
       "source": "/legacy-contact",
       "destination": "https://example.com/contact",
       "permanent": true
     },
     {
       "source": "https://old-domain.com/blog",
       "destination": "/blog",
       "permanent": true
     }
   ]

   redirects.jsonl

   {"source": "/old-blog", "destination": "/blog", "permanent": true}
   {"source": "/old-about", "destination": "/about", "permanent": false}
   {"source": "/legacy-contact", "destination": "https://example.com/contact", "permanent": true}
   {"source": "https://old-domain.com/blog", "destination": "/blog", "permanent": true}

2. Configure bulkRedirectsPath

   Add the bulkRedirectsPath property to your vercel.json file, pointing to your redirect file. You can also point to a folder containing multiple redirect files if needed.

   vercel.json

   {
     "bulkRedirectsPath": "redirects.csv"
   }

3. Deploy

   Before deploying, you can test the bulk redirects configured through bulkRedirectsPath in vercel.json locally with vercel dev.

   Deploy your project to Edgenivo. Your bulk redirects will be processed and applied automatically.

   vercel deploy

   Any errors processing the bulk redirects will appear in the build logs for the deployment.

Project-level redirects let you create and update bulk redirects without needing to redeploy. Redirects are staged when created and can be immediately published to production without a new deployment.

1. Navigate to the Redirects tab

   From your dashboard, select your project and click the Redirects.

2. Create a redirect

   Click Create and enter the following:

   • Source: The path or URL to redirect from (e.g., /old-page or https://old-domain.com/page)
   • Destination: The path or URL to redirect to (e.g., /new-page)
   • Status code: Select 307 (temporary) or 308 (permanent)

   You can also configure whether the redirect should be case sensitive (default false) or whether query parameters should be preserved (default false).

3. Test your changes

   New redirects are staged until you publish them. From the review redirects dialog, click on the source path for each redirect to open a staging URL where the new redirects are applied.

4. Publish your changes

   After testing your redirects, click Publish to make your changes live.

To edit or delete a redirect:

1. From the Redirects tab, find the redirect you want to modify.
2. Click the three dots menu on the right side of the redirect row.
3. Select Edit or Delete.
4. Click Publish to apply your changes.

You can upload multiple redirects at once:

1. From the Redirects tab, click the Create button and click CSV.
2. Select a CSV file containing your redirects.
3. Review the changes and click Publish.

You can manage redirects using the Edgenivo CLI. Make sure that you are using at least version 50.1.0 of the CLI for the full command set shown below, including vercel redirects upload.

# List all redirects
vercel redirects ls
 
# List all redirects versions
vercel redirects ls-versions
 
# Add a redirect (use `--status 301` for permanent, `--status 308` to preserve the request method)
vercel redirects add /old-path /new-path --status 301
 
# Bulk upload CSV files
vercel redirects upload my-redirects.csv
 
# Remove a redirect
vercel redirects rm /old-path
 
# Promote staging redirects
vercel redirects promote 596558a5-24cd-4b94-b91a-d1f4171b7c3f

You can also manage redirects programmatically through the Edgenivo REST API. This is useful for automating redirect management from webhook events, such as managing redirects in a CMS and instantly updating Edgenivo with changes.

curl -X PUT "/__remote/api.vercel.com/v1/bulk-redirects" \
  -H "Authorization: Bearer $VERCEL_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "teamId": "team_123",
    "projectId": "project_123",
    "redirects": [
      {
        "source": "/old-path",
        "destination": "/new-path",
        "permanent": true
      }
    ]
  }'