Skip to content
PortMySite

Build your 301 redirect map.

Paste every URL from your current site. The generator suggests clean destinations. Wix patterns like /post/ and /services-1 get tidied automatically. Export in the format your new platform expects, and edit anything first.

Paste from your crawl, sitemap or Search Console export. Full URLs or bare paths both work.

Prefixed to destinations in .htaccess, nginx and CSV output. Leave empty for same-domain relative redirects.

Reference

What each platform turns your URLs into.

Builder-generated addresses follow predictable shapes, which is why most of a redirect map can be derived rather than typed. These are the transformations this tool applies, useful as a reference even if you build the map by hand.

From Wix

/post/{slug}
→ /blog/{slug}
/product-page/{slug}
→ /products/{slug}
/services-1, /about-1
→ /services, /about
/copy-of-{page}
→ the real page, or gone

From Squarespace

/blog/2024/3/14/{slug}
→ /blog/{slug}
/shop/p/{slug}, /store/p/{slug}
→ /products/{slug}
/store
→ /collections/all
/config/…
→ home, never a content page

From Shopify

/products/{slug}
→ /product/{slug} (Woo)
/collections/{slug}
→ /product-category/{slug}
/blogs/news/{slug}
→ /blog/{slug}
/pages/{slug}
→ /{slug}

The four mistakes

What actually goes wrong with redirect maps.

  1. 01

    Redirecting everything to the homepage

    Google reads a mass redirect to an irrelevant page as a soft 404 and discards the ranking value anyway. You do the work and get none of the protection. Map to the closest real equivalent, or let it 404 honestly.

  2. 02

    Shipping 302s instead of 301s

    A 302 says temporary, so Google keeps the old URL indexed and passes nothing on. Platform redirect managers sometimes default to it. Check the real status code after launch rather than the setting label.

  3. 03

    Chains from a previous migration

    Old URL → second URL → third. Each hop costs latency and Google stops following after a few. If the site moved before, repoint the old rules straight at the final destination.

  4. 04

    Mapping only what the exporter saw

    Automated tools map catalogue entities. Your service pages, dated blog archive and the campaign page that still earns links are not entities, so nothing maps them and they 404 silently.

A map is only as good as its completeness. The URLs you forget are the rankings you lose. If you would rather have this crawled, mapped, implemented and verified by people who do it weekly, get a fixed quote. Background reading: 301 redirects explained.

02 / Questions

Redirect questions, answered.

The ones that decide whether a migration keeps its rankings.

01What is a 301 redirect map?
A written list pairing every URL on your old site with the exact URL that replaces it, so each old address returns a 301 (permanent) redirect rather than a 404. It is the single artifact that decides whether a migration keeps its search rankings, a 301 tells Google the page moved and the accumulated authority should follow, while a 404 tells Google the page is gone and the authority evaporates. Build it before anything moves, not after launch.
02How do I create a redirect map for a website migration?
Four steps. Crawl the live site to inventory every URL (Screaming Frog’s free tier covers 500). Export Search Console and sort by clicks, so you know which URLs actually earn traffic and map those first. Pair each old URL with its new destination, most builder patterns transform mechanically, which is what this tool automates. Then verify after launch by re-crawling the old list and confirming each one resolves with a single 301.
03Is redirecting everything to the homepage acceptable?
No, and it is the most common shortcut that quietly fails. Google treats mass redirects to an irrelevant page as soft 404s and drops the accumulated ranking value anyway, so you get the work of redirecting with none of the protection. Map to the closest genuine equivalent. If no equivalent exists, letting the URL return a clean 410 or 404 is more honest and no worse than a homepage redirect.
04What is the difference between a 301 and a 302 redirect?
301 is permanent and passes ranking signals to the destination; 302 is temporary and tells Google to keep indexing the original address. Migrations need 301s. Platform redirect managers sometimes default to 302, so check the actual status code after launch with curl or your browser’s network tab rather than trusting the setting label.
05What are redirect chains and why do they matter?
A chain is old URL to a second URL to a third, usually created by a migration layered on an earlier migration. Each hop adds latency and Google limits how many it follows before giving up. If you have migrated before, resolve old rules to point directly at the final destination rather than stacking a new layer on top.
06Does this tool send my URLs anywhere?
No. Everything runs in your browser, the URLs you paste never reach a server, there is no signup and no email gate. That is deliberate: your URL inventory reveals your site structure and your traffic priorities, and there is no reason a free tool should collect it.