Your migration has to ship this week, and the URL map is the piece that protects your traffic while everything else changes. Who is this plan for? Anyone moving pages to new addresses under deadline pressure, whether the move is a redesign, a domain change, or a platform switch. What is a URL map? A simple list pairing every old address with the new address that should replace it.
Why does this matter so much? When an old URL disappears without a redirect, visitors hit an error and search engines lose the signals that URL had earned. Where do mistakes happen? In rushed spreadsheets, skipped low-traffic pages, and redirects pointed at the homepage instead of a true replacement. How do you finish in seven days? You triage hard, work day by day, and cut only the corners that are safe to cut.
This is a compressed plan, not a leisurely one. It assumes you start today, ship within the week, and check the result immediately after launch.
Not every URL deserves equal effort. With a week to work, your first job is deciding which pages must be mapped perfectly, which need a reasonable match, and which can be retired honestly.
Triage is the corner you may cut: depth of analysis on low-value pages. Destination quality on important pages is never a safe corner to cut.
Seven days is enough if each day has one clear output. Do not start redirect rules before the inventory exists, and do not write rules for new URLs that have not been confirmed final.
Export every old URL you can find. Combine your sitemap, analytics landing pages, search console data, and a crawl of the current site. Merge them into one spreadsheet and remove duplicates. This list is your source of truth for the week.
On day two, add a column for traffic and one for inbound links, then sort. The top of the list is where your care goes. Pages nobody visits move to the bottom, where triage handles them quickly.
Get the final list of new URLs from whoever is building the new site, in writing. Map against confirmed addresses only. If a new page is still a placeholder, flag it and keep moving; chasing unfinished pages is how migration weeks collapse.
Work from the top of the sorted list downward. For each old URL, choose the new page a visitor would actually want if they followed the old link today. Read the old page title and the new page title side by side. If you would be annoyed by the swap as a reader, choose again.
Turn the spreadsheet into redirect rules, then test a sample from every group: top pages, merged pages, retired pages, and a few from the long tail. Every test should land on a live page with the correct content, in one hop.
Ship, then immediately re-test the same sample on the live site. Submit the new sitemap, watch error reports, and keep the spreadsheet open. Most launch-day problems are a handful of wrong destinations, cheap to fix in the first hours.
Deadline pressure forces choices, so make them consciously. Here is the split experienced teams rely on when a migration cannot wait.
There is a reason top pages deserve this protection. Search engines pass signals along links and redirects in ways resembling the flow described in the original PageRank concept: value follows connections. Break the connection or point it somewhere irrelevant, and that value dissipates.
Your map is a working document other people will touch under pressure, so keep it boring. Use exactly these columns: old URL, new URL, status, and notes. Freeze the header row. Never keep a second, private version.
The Seovaro blog has more migration and technical guides for background reading after launch. During the week itself, protect your time: the spreadsheet and the test list matter more than extra theory.
Sort and filter instead of scrolling. Work in filtered views by section, mark rows done as you go, and count remaining rows each evening. A shrinking number keeps a tired team honest about whether day seven is realistic.
Short on time and facing hundreds of old addresses at once? Try Open All URLs to open your old and new URLs in batches while you map and test them. It turns the slowest part of this week, checking pages one by one, into a fast visual pass.
Redirect the old URL to the closest live, relevant page rather than leaving it broken, and note it in the spreadsheet. Revisit that row as soon as the real page ships and update the destination.
No. Search engines generally treat mass homepage redirects like soft errors, and visitors land somewhere irrelevant. It saves an hour now and costs far more in lost trust and traffic later.
Test every top landing page individually, then sample each group of similar redirects. If a sample fails, test the whole group, because group failures usually share one wrong rule.
Yes, keep it permanently. It explains later traffic changes, helps diagnose old links still in use, and becomes the starting inventory if you ever migrate again.