> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/blocking-and-redirect-rules/bulk-upload-redirect-rules.md).

# Bulk Upload Redirect Rules

Redirect rules can also be uploaded and configured in bulk with a .XLSX or .CSV file. Not all file columns may be available for use—Refer to the [impact.com Routing Rule Bulk upload Data Fields](https://docs.google.com/spreadsheets/d/1wt39bVgv9p4XVNzF8MaBdRFTAD5DUPwZKM6jnR5OAnM/edit?usp=sharing) spreadsheet to learn more about each column.

1. From the top navigation bar, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F210dEQa93qyQgoJDkieL%2FUser%20profile.svg?alt=media\&token=f84c5b17-fae4-4a30-990a-9de5e57a150b) **\[User profile] → Settings**.
2. On the right, under *Technical*, select **Blocking & Redirect**.
3. In the top-right corner, select **Bulk Upload**.
4. Select **Choose File**, then select your file.
   * Refer to the [impact.com Routing Rule Bulk upload Data Fields](https://docs.google.com/spreadsheets/d/1wt39bVgv9p4XVNzF8MaBdRFTAD5DUPwZKM6jnR5OAnM/edit?usp=sharing) spreadsheet to see how your file should be formatted.
5. Select **Next**.
6. If validation errors exist, select **Back** to upload a new file. Otherwise, select **Accept & Create Rules**.
   * Any redirect rules with validation errors will not be created.

{% hint style="info" %}
**Note:** Redirect rules uploaded in a bulk file can take up to a day to process.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/blocking-and-redirect-rules/bulk-upload-redirect-rules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.