How to use the Redirect Map Generator.
Redirect by equivalent purpose, not by a shared word in the URL. Unmatched old pages need a deliberate decision rather than a blanket redirect to the homepage.
Make the workflow fit your task.
Match each old URL to a destination that serves the same purpose. Record unmatched pages separately, choose the intended redirect behavior and test representative paths for loops and unnecessary hops.
- What you provide
- Old and new URL inventories.
- What you get
- Suggested one-to-one redirects and unresolved matches.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Old path /guides/import-csv/ is replaced by /help/csv-import/ with equivalent content. Produce a migration mapping with a permanent redirect and one nonmatching test.
Completed example
old_path,new_path,status /guides/import-csv/,/help/csv-import/,301 Expected test: /guides/import-csv/ redirects once to /help/csv-import/. Negative test: /guides/export-csv/ remains unaffected by this mapping. Confirm query-string handling in the target server before deployment.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should every removed page redirect to the homepage?
Choose a genuinely relevant replacement when one exists. An unrelated destination does not preserve the purpose of the old page.
Why does the redirect map create a chain?
Follow the destination until it stops redirecting, then point the old URL directly to the intended final page where appropriate.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑