Yes, you can use Screaming Frog for website migration mapping, and it is a common, legitimate choice. It is a desktop crawler that walks a site and lists every URL it finds, which is exactly the inventory a migration depends on. The usual workflow is to crawl the old site for the full URL list, crawl the new or staging site, and match the two so you can build the 301 redirect map. It does the crawling part well. What it does not remove is the real work: matching old URLs to new ones is still a manual judgement, the desktop tool takes configuration, and it inventories URLs rather than shaping content for import. The rules a good map follows are the same whatever tool produces it, and WPBuildAI produces that inventory and redirect map from the live site directly.
What Screaming Frog does well for migration mapping
Its strength is thorough crawling. Pointed at a site, it follows links and discovers URLs the owner has often forgotten: paginated archives, tag pages, old parameters, and orphaned pages. It pulls each URL’s status code, title, meta description, headings, and canonical, which is precisely the data you want when building a redirect map and checking parity. For an established site, that completeness is the point, because the URLs that hide outside the menu are the ones a rushed migration drops. As a way to answer “what URLs does this site actually expose,” it is dependable, which is why it is a fixture in many SEO toolkits.
How to map a migration with it, step by step
- Crawl the old site in full and export the URL list with status codes and metadata.
- Crawl the new or staging site the same way to get its URL list.
- Match old URLs to new in a spreadsheet, pairing each old address with its counterpart.
- Flag the gaps: old URLs with no obvious new home need a decision, not a guess.
- Build the 301 map from the matched pairs, each a single hop.
- After launch, re-crawl to confirm the redirects resolve and nothing 404s.
The crawl steps are where the tool shines; steps 3 and 4 are where your judgement does the work, and where most of the time goes.
Where it gets fiddly
The friction is in setup and matching, not crawling. As a desktop application it needs installing, configuring, and enough memory for a large crawl, and crawling a big site can be slow. More importantly, the old-to-new matching is manual: the tool gives you two lists, but pairing a redesigned URL to its true new equivalent is a human decision, especially when slugs change shape. It also inventories URLs and on-page elements rather than exporting your content reshaped for a new platform’s import, so if you also need the content in an import-ready form, that is a separate job. None of this makes it the wrong tool; it just means it is one part of the workflow, not the whole of it.
What a complete migration map actually needs
Whatever tool you use, a sound migration map has the same three properties. It is complete: every old URL is on it, because a missing URL is a 404 waiting to happen, the failure Google describes in its site move guidance. It is exact: each old URL points to its true counterpart, not a generic page, because a bulk redirect to the homepage reads as a soft 404 and passes nothing. And it is clean: each redirect is a single 301 hop, per Google’s redirects guidance. A tool can help you reach those properties; it cannot guarantee them, which is why the map is reviewed, not just generated. The techniques carry over to any tool, as in finding all URLs and a URL mapping template.
Matching old URLs to new is the real work
The matching step deserves its own attention because it is where rankings are won or lost. Traffic is uneven: the Ahrefs search traffic study found a small share of pages earns most organic visits, so the high-value URLs must be matched exactly right while the long tail can follow patterns. A good approach is to sort the old URLs by their traffic or rankings and handle the top ones by hand, then map the rest by rule where the structure is consistent. This is the same prioritised mapping described in mapping 301 redirects in bulk. The tool lists the URLs; deciding where each one should land is the judgement that no crawler makes for you.
Verifying the redirects after launch
Mapping is only half the job; verifying is the other half. After launch, confirm every redirect resolves in a single hop to a live page, not a chain and not a 404, the check covered in checking that 301 redirects work correctly. A re-crawl of the old URL list against the live site surfaces any that were missed or misrouted. Then watch Search Console for 404s over the following weeks, because a few URLs always slip through the first pass. Skipping verification is how a map that looked complete on paper still loses pages in practice, since an untested redirect is just an assumption.
A worked example
An agency mapped a 500-page site migration. They crawled the old site and found 500 pages plus 180 archive, tag, and parameter URLs, then crawled staging. They sorted the old URLs by Search Console clicks, hand-matched the top 60 that drove most traffic, and rule-mapped the rest by path pattern. Gaps, old URLs with no new home, were reviewed individually and pointed to the nearest relevant page rather than the homepage. They built single-hop 301s from the matched pairs, launched, re-crawled to confirm, and watched Search Console. A dozen 404s appeared from missed URLs and were redirected within days, and rankings held. The crawl made the inventory easy; the matching and verification, done by hand, made it correct.
When a simpler approach makes sense
Screaming Frog is a fine fit when you want hands-on control and already know the tool. A simpler approach makes sense when you want the inventory and a first-pass redirect map without desktop setup, or when you also need the content exported in an import-ready form, not just URLs listed. In that case a hosted scan that takes a URL and returns the inventory, a draft old-to-new map, and a content export covers more of the workflow in one step. The choice is about how much of the job you want to do by hand versus have prepared for you; the map’s requirements do not change either way.
Common mistakes mapping a migration
- Crawling only the menu pages and missing tags, archives, and parameter URLs.
- Redirecting unmatched URLs to the homepage instead of their nearest counterpart.
- Treating the generated list as a finished map without reviewing the matches.
- Building the map but never re-crawling to verify the redirects after launch.
- Mapping every URL by rule and not hand-checking the high-traffic ones.
Key points to remember
You can use Screaming Frog for migration mapping, and it is good at the crawling part: a thorough URL inventory of the old and new sites. The work it does not remove is the old-to-new matching, which is manual judgement, and the verification afterwards. Any map, whatever tool builds it, must be complete, exact, and single-hop, and the high-traffic URLs must be matched by hand. Because the CMS is not a ranking factor, as Backlinko’s analysis of 11.8 million results found, what protects rankings is the map, not the platform. WPBuildAI produces the inventory and a draft redirect map from the live site, without desktop setup. Send your site URL for a free migration assessment.
Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.