You can map old URLs to new ones during a migration without buying a single subscription. What you need is a complete inventory of the old site, a clean spreadsheet, and a few free exports you already have access to. The work is careful, not expensive.
Who should do it this way? Site owners, freelancers, and small teams moving a blog, shop, or brochure site where a paid crawler is hard to justify. When does the mapping happen? Before the new site goes live, while the old pages are still reachable and you can still check where each one should land.
This guide focuses on the free toolchain itself: how to build the inventory with a browser and Search Console, how to organise the map in a spreadsheet, and how to test every redirect with free utilities before and after launch.
Start by collecting URLs from several free sources, because no single source catches everything. Export the pages report from Search Console, download your sitemap from the old site, and copy the page list from your content system if you have one. Merge them into one sheet and remove duplicates.
Add the pages people actually visit, not just the pages that exist. Search Console shows which URLs earned clicks and impressions, and your analytics shows which ones earned visits. A page with traffic or links pointing to it must never be left off the map, even if you plan to retire its content.
Keep one row per old URL. Add columns for status, topic, and notes as you go, because those notes become the reasoning behind every mapping decision you make later.
A spreadsheet is your mapping tool, so set it up like one. Use columns for the old URL, the new URL, the match type, and a checked column. Freeze the header row, filter each column, and work in small batches sorted by site section rather than jumping around at random.
Match by intent first and wording second. A page about returns policy should land on the new returns page even if the slug wording changes completely. Where no equivalent exists, choose the closest parent section, or plan a deliberate retirement with a proper not-found response instead of sending everyone to the homepage.
This discipline is what paid tools automate. Doing it by hand is slower, but on a small or medium site it is completely workable.
Never map to a target you have not opened. Click every proposed new URL, confirm the page loads, and confirm it is really about the same topic as the old one. On larger lists, work section by section and tick the checked column only after the page has loaded in front of you.
Free utilities fill the remaining gaps. A redirect checker in the browser shows whether a test URL lands in one hop. Your hosting panel or a plain text editor handles the redirect file itself, depending on your platform. Background on related measurement topics is covered on the Seovaro blog if you want to read around the process.
Also check what outsiders see. Search for a handful of your old pages and make sure those are mapped first. Guidance for advertisers, such as Google's explanation of final URLs, is a useful reminder that the landing address matters.
Test in two passes. Before launch, test the map on a staging copy or with a small sample of redirects applied early, and click through each section. After launch, retest the full list, because typos, missing trailing slashes, and case differences only show up on the live server.
Watch for the classic failures. Redirect chains waste the move, loops break pages entirely, and mapping everything to the homepage looks like a soft error to search engines. Fix chains by pointing the first URL straight at the final page, and record every fix back in your spreadsheet so the sheet stays the single source of truth.
Want a faster way to work through long URL lists when you are testing targets? Try the Open All URLs tool to open your new addresses in batches, check each page loads on the right topic, and tick off your spreadsheet as you go.
Yes. A browser, a spreadsheet, Search Console exports, and your sitemap give you the inventory, the workspace, and the checks. Paid crawlers save time on very large sites, but the method itself is the same.
A few hundred URLs is comfortable by hand, and a few thousand is possible if you work section by section. Beyond that, the time cost usually justifies help, even if the tools themselves stay free.
Map them to the closest relevant section if one genuinely helps the visitor. If nothing fits, let the page return a proper not-found response rather than forcing a misleading redirect to the homepage.
Keep it permanently with your site records. It explains why every redirect exists, helps diagnose traffic drops later, and becomes the starting inventory for your next migration.