> For the complete documentation index, see [llms.txt](https://help.wislr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.wislr.com/getting-started/quick-tutorial.md).
# Redirects.net Documentation
## Our 3-minute Guide to Help You Use Redirects.net
If it’s your first time using Redirects.net, this quick start guide will help you process your files and read the matching results.
### Uploading Your Files
File Upload Input in Redirects.net Dashboard
Here’s a few things to know regarding file management:
File format compataibility:
* Uploaded files should only be Comma Separated Value (CSV) files
File sizes:
* Individual file size cannot exceed 50MB
* Inidividual files can have up to 150,000 URLs per file
### Import File Headers
Accepted CSV headers are:
* URL
* ⚠️ **URL** is a required header, where all URL values should be listed.
* Dimension
* (Optional)
* SKU
* (Optional)
When you build your file, values in the same row will be associated together in the URL matching:
| URL | Dimension | SKU |
| ------------------------------------- | ----------------------------- | ------ |
| | Sunny Days are in your Future | VACAY1 |
### How to Use the 'URL' field
The **URL** field is a required header in your CSV file and serves as the primary identifier for URL matching.
When building your CSV file, create a column header labeled **`URL`** where you'll list all the website URLs you want to include. Each URL value should be placed in its own row under this header.
### How to Use the 'Dimension' field
The Dimension field is built to accept any contextual and semantic text strings associated with a URL. Examples are:
* Title of the page
* Meta description
* H1 tag
The Dimension column only needs one of these values. We recommend choosing the data point that is the most descriptive for the URL.
There is a limit of 2,048 characters for all ‘Dimension’ cells in your CSV. The algorithm will truncate any strings that exceed this limit down to the threshold.
Here’s a File Upload Template to get you started. Send us a chat if you need help. Happy URL matching!
### How to Use the 'SKU' field
The SKU field is built for any product specific ids linked to a URL, commonly from an Ecommerce CMS. It's a datapoint you can use to match URLs if you have SKU level data for products.
There is a limit of 2,048 characters for all ‘SKU’ cells in your CSV. The algorithm will truncate any strings that exceed this limit down to the threshold.
***
### Reading the Returned Redirects.net Match File
When the algorithm has finished analyzing the URL datasets it will return a CSV file you can download. This file will include:
* All unique Origin URLs uploaded
* The (1) best Destination URL match
The final file will have these headers:
* url
* path
* best\_match\_url
* best\_match\_path
* score\_301
* sku\_match
* redirect\_loop\_absolute
* redirect\_loop\_releative
* multiple\_matches
* origin\_sku
* origin\_dimension
* destination\_sku
* destination\_dimension
* origin\_type
* destination\_type
#### Descriptions of Each Field in the Final Match File
| URL |
| ---------------------------- |
| The unique Origin URL string |
| Best\_Match\_URL |
| --------------------------------- |
| The unique Destination URL string |
| Score\_301 |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A value from 0 to 1, calculating the strength of the match. A score of (1) indicates the Origin and Destination URL are an exact match to one another, value for value. A score of (0) indicates that the match strength is very low quality. A value, such as 0.80, would indicate that the URL taxonomy between the Origin and Destination is a very strong pair. A low value, such as 0.20, does not indicate a poor match necessarily. It indicates that the URL taxonomy between the Origin and Destination is very different and this pairing was returned as the best result from the datasets provided. |
| SKU\_Match |
| ---------------------------------------------------------------------------------------------- |
| A binary value (True / False) that indicates if the SKU value was used to make the URL pairing |
| Redirect\_Loop |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A binary value (True / False) that indicates if implementing the Origin and Destination would create a redirect loop (pointing a URL with one value to another URL of the same value). False is the value you want to avoid Redirect loops. |
| Multiple\_Matches |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| A binary value (True / False). An experimental field at the moment. It will indicate if multiple matches are returned for an Origin URL and the Destination URL. It surfaces matches that have the same ‘Score\_301’ value from the analyzed datasets. |
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://help.wislr.com/getting-started/quick-tutorial.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.