Your first redirect map with RedirX

Start with an old URL list and a new URL list. RedirX proposes destinations; you decide which mappings to keep. Your first useful result is a downloaded map containing the redirects you approved.

Choose your project

For a real migration, use your own inventories. Each file needs one absolute URL per row, with an optional url header. Keep the original spelling, capitalization, encoding, and query strings. Include the new destinations you actually intend to publish.

For practice, download these fictional store inventories:

• Old URLs: 8 rows
• New URLs: 10 rows
• Full agent prompt

The sample uses reserved example domains. It needs no page crawling or website access. It includes a past sale without a clear replacement, so you can practice leaving a URL unresolved.

Running the sample can use your account's one-time free migration. If you have a real project ready, use that instead. The trial allows up to 500 old URLs and 2,000 new URLs. Check the current pricing and your account's allowance before starting. This tutorial never asks you to purchase a plan or approve extra usage.

Connect your agent

On the RedirX homepage, choose your client from Set up in and follow its connection instructions. Complete RedirX sign-in in the browser and return to your client. The client should discover the RedirX migration tools, including plan_migration, import_inventory, run_migration, resolve_matches, and export_redirects.

An installation command or a successful login is only the connection step. If the tools are missing, reconnect through your client's normal authorization flow. Do not paste account passwords or access tokens into the conversation. The agent reference has the current schemas and recovery instructions.

Import and run

Attach both CSVs to your agent. For the practice project, paste the full prompt. It tells the agent to check the connection, confirm the trial choice, import exactly eight old and ten new URLs, and stop at any payment request.

For your own project, use this request:

Use RedirX to map the attached old and new URL inventories. Confirm the origins and complete inventory counts before running. Show the applicable allowance or payment requirement first; do not purchase or approve extra usage. After the run, show the proposed destinations and unresolved URLs for my review. Wait for my explicit mapping decisions before exporting. Do not install anything on my site.

The agent should retain the migration and operation IDs, wait for completion, and show all proposed matches. It should not start a second migration just because a request times out.

Review the destinations

Check what each old page was for and whether its proposed destination serves that purpose. A confidence score is a model estimate, not evidence that the destination is correct. Correct a destination when needed, and leave a row unresolved when you need more context.

The practice files are deliberately simple. They demonstrate the workflow; they cannot establish accuracy on your site's URLs. For the fictional past sale, do not assume that the homepage or a new collection is the right replacement.

Give explicit decisions, for example:

Confirm the blue mug URL goes to the blue mug product URL. Keep the old sale unresolved while I decide what should happen to it.

Your agent should save those decisions and check each result. An unreviewed proposal should never become an approved mapping automatically.

Download and check the map

Ask for a CSV containing your approved mappings. If any rows remain unresolved, the agent should name them and ask before producing a partial export. Check the actual downloaded file, its included count, and its excluded count.

For the practice project, stop here: the domains are fictional and nothing has been installed. For a real project, choose the appropriate platform export and plan installation separately. A generated file does not establish that redirects are live or that traffic has been preserved.

If you get stuck, keep the migration ID and the step that failed. Contact Dylon@RedirX.dev with those details, excluding passwords and access tokens.