ChatGPT answers, unedited

For a large shop migration, you usually want a stack, not one SEO tool. The key jobs are:

1. Inventory every old URL
2. Create and validate the redirect map
3. Compare old vs new site signals
4. Monitor rankings, traffic, indexing, and technical issues after launch

A practical stack:

Sitebulb HighLevel Playbooks## Recommended migration workflow

1. Before migration: build your URL baseline

Crawl the current store and export:

• All indexable URLs
• Canonicals
• Status codes
• Titles/H1s
• Product/category relationships
• Internal links
• XML sitemap URLs
• Structured data
• Page templates

Also export:

• Top organic landing pages from Search Console
• Revenue-driving URLs from analytics
• Backlink-heavy URLs from Ahrefs/Semrush

This gives you the URLs that must not be lost. Sitebulb Screaming Frog

2. Build the redirect map

For a large ecommerce store, I would not redirect blindly. Prioritize:

• Product pages with organic traffic
• Category pages ranking for valuable terms
• URLs with strong backlinks
• Old URLs still receiving visits
• Discontinued products with close replacements

Avoid:

• Redirecting everything to the homepage
• Chains (old URL → intermediate URL → final URL)
• Redirecting valuable pages to irrelevant replacements

Sitebulb Screaming Frog### 3. Test redirects before launch

Useful checks:

• Every old URL returns the intended 301
• No 404s for important URLs
• No 302s where permanent redirects are needed
• No redirect loops
• Redirect targets are indexable

Screaming Frog is particularly useful here because you can upload a URL list and crawl it in list mode to validate redirects at scale. Screaming Frog

4. Monitor after launch

Watch daily for the first few weeks:

Google Search Console

• Index coverage
• Crawl stats
• Sitemap processing
• Query/page performance

Rank trackers

• Lost keywords
• Ranking URL changes
• Category/product page drops

Crawlers

• New 404s
• Canonical mistakes
• Missing metadata
• Internal links still pointing to old URLs

Sitebulb Saffron Edge## A solid ecommerce migration stack

For a very large shop, I’d typically combine:

• Screaming Frog → URL discovery + redirect validation
• Sitebulb → crawl comparisons and stakeholder-friendly reports
• Ahrefs or Semrush → ranking/backlink prioritization
• Google Search Console → Google’s view of the migration
• GA4 + Looker Studio → traffic/revenue dashboards
• Lumar or Botify (if millions of URLs) → enterprise crawling/log analysis

Sitebulb Saffron EdgeIf you’re moving from something like Magento → Shopify, WooCommerce → Shopify, Salesforce Commerce Cloud, or a custom platform, the URL strategy changes quite a bit (especially for product variants, filters, faceted navigation, and category structures).

For a large ecommerce replatform, I’d use a combination rather than rely on one SEO tool. The key is to cover three jobs: build the URL map, validate redirects at scale, and detect organic/ranking problems quickly.

Recommended stack

• Screaming Frog SEO Spider — probably the most useful migration-specific crawler. Crawl the old site, crawl the staging/new site, compare URLs, test redirect chains, identify 404s/5xxs, canonicals, noindex, internal links, hreflang, etc. It can also crawl URL lists rather than relying only on discoverability.
• Semrush — useful for maintaining your keyword/ranking baseline and monitoring post-launch visibility. Its Site Audit can supplement the crawl, while Position Tracking helps identify ranking/visibility changes.
• Ahrefs — particularly useful for preserving your backlink/organic landing-page inventory. Export the old site's pages receiving organic traffic and/or backlinks and make sure every valuable URL has an intentional destination.
• Google Search Console — essential rather than optional. Use the old and new properties, sitemaps, Page Indexing, URL Inspection, and Performance reports to watch the migration from Google's perspective. Google specifically recommends monitoring old and new URLs during a migration. Google for Developers Google Help
• Server-log analysis — for a genuinely large shop, don't overlook logs. They show what Googlebot and real users are actually requesting, including old URLs that weren't in your crawl/export.

How I'd structure the migration

1. Build the "master old URL" inventory

Don't get the URL list from just the sitemap. Combine:

• XML sitemaps
• Screaming Frog crawl
• Google Search Console URLs
• Analytics organic landing pages
• Ahrefs/Semrush organic landing pages
• URLs with backlinks
• server logs
• important product/category URLs from the ecommerce platform

Google explicitly recommends using sitemaps, analytics, Search Console links, CMS data and server logs when constructing the migration URL inventory. Google for Developers

Then create something like:

2. Test the redirects before launch

Give Screaming Frog the old URL list and have it crawl the redirects. Look specifically for:

• 404/410 where a page should have moved
• 301 → 301 chains
• redirect loops
• redirects to irrelevant pages
• redirects to the homepage
• 302s where permanent redirects are intended
• redirect destinations returning 4xx/5xx
• old URLs that aren't redirecting at all

Google recommends server-side permanent redirects such as 301 or 308, and specifically advises avoiding redirect chains. Google for Developers Google for Developers

3. Establish a ranking/traffic baseline

Before launch, export at least 4–8 weeks of:

• Google Search Console clicks/impressions/average position
• rankings for your important commercial keywords
• organic landing-page traffic
• revenue/conversions from organic
• indexed URL counts
• top linked pages

This is important because a migration can cause temporary ranking fluctuations while Google recrawls and reindexes URLs. Google for Developers

4. Watch the first 2–4 weeks aggressively

I'd have dashboards/alerts for:

• organic clicks and impressions
• rankings for priority keywords
• indexed vs. non-indexed URLs
• 404/410/5xx volume
• crawl activity
• old-URL requests
• new-URL organic landing pages
• redirect errors/chains
• organic revenue

Search Console's Page Indexing report is particularly useful for spotting unexpected indexing problems and redirect errors. Google Help

If I had to keep the stack lean

For a large shop, my minimum would be:

Screaming Frog + Google Search Console + Semrush/Ahrefs + server logs.

Screaming Frog handles the technical migration QA, GSC tells you what Google is actually doing, Semrush/Ahrefs provide the ranking/backlink baseline, and logs catch URLs that your normal crawls never knew existed.

One particularly important point: don't treat "all redirects return 301" as migration success. The destination has to be the right equivalent page, and the new site needs to retain the appropriate canonicals, internal links, indexability and content. Google explicitly warns against funneling unrelated old URLs into a single destination such as the homepage. Google for Developers

If you tell me roughly how many URLs the shop has (e.g. 100k, 1M, 10M) and whether you're moving Shopify, Magento, Salesforce Commerce Cloud, WooCommerce, etc., I can lay out a practical migration toolchain and QA checklist for that scale.

For a large ecommerce migration, you usually want a tool stack, not a single SEO tool. The core jobs are:

1. Inventory every old URL
2. Build and QA the old → new redirect map
3. Validate redirects at scale
4. Monitor rankings, traffic, indexing, and crawl issues after launch

Here are the tools commonly used for each stage:

1. URL discovery and mapping (pre-launch)

Screaming Frog SEO Spider

Best for: building the URL inventory and comparing old vs. new sites.

Use it to:

• Crawl the current store and export every URL
• Crawl staging/new platform URLs
• Compare status codes, titles, canonicals, H1s, word counts, internal links
• Find orphan URLs, duplicate pages, broken links, redirect chains

A common migration workflow is:

• Crawl old site → export URLs
• Crawl new site → export URLs
• Build redirect rules from the two datasets

Sitebulb

Best for: easier-to-read technical audits and migration reporting.

Good when stakeholders need visual explanations of:

• lost pages
• changed architecture
• crawl problems
• indexability issues

URLMatcher

Best for: very large redirect mapping projects where spreadsheets become difficult. It can crawl/import old and new URLs, suggest mappings, validate redirects, and monitor post-launch URL/query movement. URLMatcher URLMatcher

2. Redirect planning and validation

Ahrefs

Best for: deciding which old URLs are most valuable.

Before redirecting, prioritize URLs with:

• organic traffic
• ranking keywords
• backlinks
• historical visibility

A product page with 500 backlinks deserves more attention than an old category page nobody visits.

Semrush

Useful for:

• keyword position tracking before/after launch
• competitor visibility comparisons
• site audits
• identifying pages that lose rankings

Redirect Path

Good lightweight tool for manually checking:

• 301 vs 302 mistakes
• redirect chains
• incorrect destinations

For enterprise migrations, pair this with automated crawl validation.

3. Ranking-drop monitoring after launch

Google Search Console (free)

Essential. Monitor:

• indexed pages
• crawl errors
• sitemap processing
• query/page performance
• sudden drops in clicks or impressions

Google specifically recommends preparing URL mappings, deploying redirects, and monitoring traffic and indexing during URL-changing migrations. Google for Developers

Google Analytics

Track:

• organic revenue
• landing page traffic
• conversion changes
• category/product page performance

Sistrix

Useful for:

• daily visibility monitoring
• spotting large ranking shifts
• tracking keyword losses by directory/category

STAT Search Analytics

Good for enterprise SEO teams tracking thousands of keywords and segments.

4. Ecommerce-specific checks

For a shop migration, I would also monitor:

• Top-selling product URLs before/after
• Category pages with the most organic traffic
• Faceted navigation URLs
• Canonical changes
• Product schema changes
• Internal linking changes
• Pagination behavior
• Image URLs
• XML sitemap coverage

A practical stack for a large shop

Enterprise migration:

• Screaming Frog → crawl old/new platforms
• Ahrefs or Semrush → prioritize valuable URLs
• URLMatcher (or a similar migration mapper) → create/QA redirect map URLMatcher
• Google Search Console → indexing and query monitoring
• Semrush/Sistrix/STAT → ranking monitoring
• Screaming Frog again → post-launch crawl validation

Budget-conscious:

• Screaming Frog
• Google Search Console
• Google Analytics
• Looker Studio dashboard
• Spreadsheet-based redirect map

A few migration metrics I’d put on a daily dashboard for the first 2–4 weeks:

• Organic clicks vs. baseline
• Organic revenue vs. baseline
• Number of 404s
• Number of redirect chains
• Indexed URL count
• Top 1,000 keyword movements
• Lost ranking URLs
• New ranking URLs
• Crawl stats

For a large shop (tens/hundreds of thousands of URLs), I’d avoid a purely manual spreadsheet redirect process—URL inventory, prioritization, and QA are where migrations usually fail. Google for Developers URLMatcher

For a large e-commerce replatform, I’d use a stack rather than rely on one SEO tool. The key is to cover three jobs: build/validate the URL map, monitor redirects at scale, and detect organic visibility losses quickly. Google itself recommends preparing an old→new URL mapping, implementing server-side permanent redirects, testing them, and monitoring both old and new URLs throughout the move. Google for Developers Google for Developers

My recommended stack

1. Screaming Frog — URL mapping and redirect QA

This would be my core migration tool.

Use it to:

• Crawl the old site and export every important URL.
• Crawl the staging/new site.
• Compare old vs. new URLs.
• Identify 301/302/404/410 responses.
• Find redirect chains and loops.
• Check canonical tags, hreflang, robots directives, internal links and XML sitemaps.
• Re-crawl the old URLs after launch to verify they land on the intended new URLs.

For a big shop, I'd create a migration spreadsheet/database with at least:

Old URL → New URL → HTTP status → redirect type → canonical → indexability → organic traffic → backlinks → priority

Google specifically recommends generating an old-to-new mapping and testing redirects, and explicitly mentions Screaming Frog as a useful way to crawl and verify redirects. Google for Developers

2. Google Search Console — your source of truth for Google

Don't treat this as optional.

Before launch, establish a baseline for:

• Clicks/impressions
• Queries
• Top landing pages
• Indexed pages
• Sitemap URLs
• Page indexing errors

After launch, watch whether old URLs disappear from the index while corresponding new URLs become indexed, and watch for spikes in 404s or other indexing problems. That's essentially the migration pattern Google recommends. Google for Developers Google Help

If you're also changing domains, use Search Console's Change of Address tool. Google Help

3. Semrush or Ahrefs — ranking-drop detection

I'd pick Semrush if your emphasis is ongoing rank/visibility monitoring and technical SEO, or Ahrefs if backlinks and organic-search analysis are particularly important.

For the migration, snapshot your important keywords before launch, then monitor:

• Position changes
• Lost keywords
• Lost landing pages
• Organic visibility
• Branded vs. non-branded traffic
• Competitor movements
• Backlink changes

The important thing is to monitor URL-level changes, not just "site traffic." A migration can look fine overall while hundreds of high-value category/product URLs quietly lose rankings.

4. Botify — if this is genuinely huge

If you're talking hundreds of thousands or millions of URLs, I'd seriously consider Botify.

It's particularly useful when you need to correlate:

crawl behavior → indexation → organic performance → server logs

That's a different level of migration monitoring than a conventional SEO crawler.

5. Little Warden — automated guardrails

This is useful as the "something broke at 2 AM" layer.

You can automate checks for things such as:

• Redirects
• Status codes
• Canonicals
• Robots.txt
• Indexability
• Sitemaps
• DNS/SSL
• Important page availability

I'd use it alongside, rather than instead of, a full crawler.

The migration workflow I'd use

Before launch

1. Crawl the entire old site with Screaming Frog.
2. Export Search Console's top landing pages and queries.
3. Export organic landing-page data from analytics.
4. Pull backlink data from Ahrefs/Semrush.
5. Combine those sources to create your priority URL inventory.
6. Generate the old → new URL mapping.
7. Crawl the new site/staging environment.
8. Validate the mapping and identify missing URLs.
9. Test redirect rules in bulk.
10. Establish ranking/indexation baselines.

Launch day

• Keep old → new 301/308 redirects active.
• Crawl the old URLs against production.
• Check for redirect chains, loops and unexpected 404s.
• Check canonicals and robots directives.
• Submit the new XML sitemap.
• Watch Search Console, server logs and analytics continuously.

Google recommends server-side permanent redirects and advises avoiding redirect chains; ideally each old URL should go directly to its final destination. Google for Developers Google for Developers

First 2–4 weeks

Set up a dashboard showing:

Old organic landing pages → New landing pages → clicks → impressions → rankings → index status → HTTP status

Then segment ranking losses by:

• Product pages
• Category pages
• Brand pages
• Faceted URLs
• Editorial/content
• High-backlink URLs
• High-revenue URLs

That makes it much easier to distinguish a normal migration fluctuation from a genuine technical failure.

If I had to buy only three

For a large shop, I'd go:

Screaming Frog + Semrush/Ahrefs + Google Search Console

And if the site is 1M+ URLs or has sophisticated infrastructure/log access, add Botify.

One particularly important point: don't build the redirect map solely from the current XML sitemap. Google recommends combining sitemap URLs with server logs, analytics, Search Console links, CMS URL inventories, and other sources so you don't accidentally omit old URLs that still receive traffic or backlinks. Google for Developers

For a large e-commerce migration, I’d use a stack rather than rely on one SEO platform. The key is to establish a URL-level baseline before launch, validate redirects at scale, then compare organic performance after launch.

Best tools by job

• Screaming Frog — probably the most important migration tool. Crawl the old site, staging site, and new live site; export URLs, status codes, canonicals, titles, internal links, etc. It’s particularly useful for crawling your old URL list against the new site to find 404s, redirect chains, 302s, bad destinations, and unexpected canonicals. Google itself specifically recommends crawling redirects with Screaming Frog during migrations. Google for Developers Google Developers
• Sitebulb — excellent alternative/complement to Screaming Frog, especially for very large migrations. It has migration-oriented comparisons, URL-level Search Console/GA data, change monitoring, and prioritization features. Sitebulb
• Google Search Console — essential and free. Use it for the pre-migration baseline and to watch clicks, impressions, average position, indexing, crawl issues, and individual URL status after launch. Google Help Google Help
• Ahrefs or Semrush — use one for rank/backlink baselines and ongoing ranking monitoring. Particularly useful for identifying high-value old URLs that have backlinks and therefore absolutely need a good redirect destination. Sitebulb
• GA4 — not really an SEO crawler, but crucial for determining whether an apparent ranking issue actually translates into organic sessions, revenue, conversions, and landing-page losses. Sitebulb

My preferred stack

For a large shop, I'd go:

Screaming Frog + Google Search Console + Semrush/Ahrefs + GA4

And optionally Sitebulb if the migration is sufficiently large/complex that you want another layer of visualization and historical crawl comparison.

The migration workflow I'd use

1. Before launch — build the master URL inventory

Pull URLs from:

• Old XML sitemaps
• Screaming Frog crawl
• Google Search Console
• Analytics
• Server logs
• CMS/database
• Backlink data from Ahrefs/Semrush

Google specifically recommends using sitemaps, analytics/server logs, Search Console links, and your CMS to identify important old URLs. Google for Developers

Then create:

old URL → new URL → redirect status → priority → notes

Don't just map the URLs that happen to be internally linked today. For an e-commerce site, old product, category, faceted-navigation and editorial URLs with organic traffic/backlinks can be extremely valuable.

2. Create a ranking/traffic baseline

Export your important queries and landing pages from Search Console and your rank tracker.

I'd segment them into:

• Brand
• Category
• Product
• Editorial/content
• High-revenue landing pages
• High-backlink URLs

That gives you something much more useful than simply saying "organic traffic is down 15%."

3. Test the redirect map before launch

Crawl the old URLs against the new environment and look specifically for:

• 301 → expected destination
• 302 → usually a migration red flag
• 404/410
• Redirect chains
• Redirect loops
• Redirecting to irrelevant pages
• Redirecting everything to the homepage
• Destination pages returning errors
• Canonical pointing somewhere unexpected
• noindex
• Robots.txt blocking
• HTTP/HTTPS inconsistencies

Google recommends that moved pages return a redirect to their new equivalent and warns about incorrect redirects and redirect chains/loops. Google Help Google for Developers

4. Launch and watch GSC aggressively

For the first few days/weeks, monitor:

• Organic clicks
• Impressions
• Average position
• Indexed pages
• Not-indexed pages
• 404s
• Redirect errors
• Crawl activity
• Sitemap processing

Search Console's URL Inspection tool is particularly useful when a specific important URL suddenly disappears from Google. Google Help

5. Automate ranking-drop alerts

Don't wait for a monthly SEO report.

I'd create alerts around:

• Top 100/500 keywords losing >X positions
• High-revenue landing pages losing >X% organic clicks
• Category pages dropping out of the top 10
• Large increases in 404s
• Large increases in "Crawled – currently not indexed"
• Organic revenue/session drops
• Significant decreases in indexed URLs

One important nuance: don't panic over a short-term ranking wobble immediately after launch. Google explicitly expects some fluctuation during migrations; you're looking for persistent or systematic deterioration. Sitebulb

If I had to pick only 3

1. Screaming Frog — URL/redirect/crawl validation
2. Google Search Console — Google indexing + actual search performance
3. Ahrefs or Semrush — rankings + backlinks + competitive visibility

For a truly large migration, I'd also preserve the old crawl data indefinitely. Six weeks after launch, being able to answer "Which old URLs disappeared, where did they redirect, and what happened to their rankings/traffic?" is enormously valuable.

developers.google.com is also worth making the team's migration checklist from.

For a large ecommerce migration, I’d use a stack rather than rely on one SEO platform. The key jobs are: build a defensible old→new URL map, validate redirects at scale, and detect organic visibility losses quickly.

My recommended stack

• Screaming Frog SEO Spider — migration workhorse

• Crawl the old site and export the complete URL inventory.
• Crawl staging/new site and compare it with the old site.
• Upload your old URLs in List Mode and have it follow redirects all the way to the final destination.
• Detect 404s, redirect chains, loops, 3xx→3xx→200 paths, redirecting to non-indexable pages, etc.
• Its migration workflow specifically recommends combining crawl URLs with Search Console, analytics, backlinks and sitemap data. Screaming Frog Screaming Frog
• Google Search Console — ranking/indexing truth source

• Compare clicks, impressions, queries and indexed URLs before/after launch.
• Monitor the old and new properties/sitemaps separately.
• Watch for spikes in indexing/crawl errors.
• Google explicitly recommends Search Console for monitoring migrations. Google for Developers
• search.google.com
• Ahrefs — backlinks + rankings + secondary crawl

• Particularly useful for identifying high-value old URLs based on backlinks/organic traffic.
• Site Audit catches redirect chains and problematic redirects.
• Rank tracking gives you a before/after ranking baseline. Ahrefs Help Center Ahrefs Help Center
• Semrush — alternative/all-in-one monitoring

• Good if your team already uses it for position tracking, technical auditing and competitive visibility.
• I'd choose Ahrefs or Semrush, rather than paying for both purely for the migration.

For the URL mapping itself

Don't build the redirect spreadsheet from the old site's crawl alone.

I'd create a master URL inventory by merging:

1. Old-site crawl
2. XML sitemaps
3. Google Search Console top pages
4. Analytics landing pages
5. Backlink URLs
6. CMS/product/category database
7. Server logs, if available
8. Any URLs already present in your redirect rules

Then give each old URL a destination:

old URL → new URL → redirect status → final status → indexability → organic clicks → revenue → backlinks

Google itself recommends constructing an old→new URL mapping and prioritizing important URLs using things such as sitemaps, analytics, server logs and Search Console. Google for Developers

The particularly important bit

Don't just check "does this URL return a 301?"

Check:

Old URL → 301 → final URL → 200 → indexable → canonical = final URL

You want to catch cases like:

old-product → 301 → intermediate-product → 301 → new-product

or:

old-product → 301 → new-category → 200

or:

old-product → 301 → new-product → noindex

Google recommends permanent server-side redirects and specifically advises avoiding redirect chains. Google for Developers

How I'd monitor the launch

Before launch: establish a baseline of rankings, organic traffic, indexed URLs, crawlability, top landing pages, backlinks and revenue-driving URLs.

Immediately after: run the entire old URL list through Screaming Frog List Mode and export the redirect chains. This is one of the places Screaming Frog is especially strong at migration scale. Screaming Frog

First 1–2 weeks: monitor GSC daily for:

• impressions/clicks
• indexed pages
• crawl errors
• pages suddenly disappearing
• old URLs still appearing
• new URLs receiving impressions

Also monitor rankings in Ahrefs/Semrush and compare page-by-page, not just the site's aggregate ranking.

Don't panic over every ranking fluctuation. Google says temporary visibility fluctuations are normal while it recrawls and reindexes a migration; larger sites can take longer to settle. Google for Developers

If this is a very large shop

I'd make Screaming Frog + GSC mandatory, then add Ahrefs or Semrush depending on what your SEO team already uses. If you're talking hundreds of thousands or millions of URLs, I'd also bring server-log analysis into the stack because it lets you see what Googlebot is actually crawling rather than just what your crawler expects it to crawl.

If you tell me roughly how many URLs/products you have and whether the URL structure is changing, I can lay out a concrete migration workflow—including the exact pre-launch crawl, redirect QA, and post-launch ranking-drop dashboard I'd use.

old-product → 301 → intermediate-product → 301 → new-product

or:

old-product → 301 → new-category → 200

or:

old-product → 301 → new-product → noindex

Google recommends permanent server-side redirects and specifically advises avoiding redirect chains. Google for Developers

How I'd monitor the launch

Before launch: establish a baseline of rankings, organic traffic, indexed URLs, crawlability, top landing pages, backlinks and revenue-driving URLs.

Immediately after: run the entire old URL list through Screaming Frog List Mode and export the redirect chains. This is one of the places Screaming Frog is especially strong at migration scale.

For a large ecommerce replatform, I’d avoid relying on a single SEO suite. The safest migrations usually combine:

1. URL discovery + redirect mapping
2. Redirect QA/crawling
3. Rank and traffic monitoring
4. Search engine validation

Here are the tools I’d consider:

A migration stack I’d use for a large shop

Before launch

1. Build a master URL inventory
Pull URLs from:

• Current site crawl
• XML sitemaps
• Google Search Console
• Analytics landing pages
• Backlink tools
• Database/product catalog exports

Google specifically recommends creating a mapping between old and new URLs and using server-side permanent redirects for URL changes. Google for Developers

2. Create the redirect map

For a large store, I’d have columns like:

Prioritize:

• Top organic landing pages
• Category pages
• Product pages with backlinks
• Pages driving revenue
• Pages ranking top 10

Tools like URLMatcher are designed around crawling old/new sites, building redirect maps, validating changes, and monitoring post-launch movement. URLMatcher

Before go-live

Run:

• Redirect crawl
• Canonical checks
• Sitemap checks
• Robots/noindex checks
• Internal link checks
• Structured data checks

Important checks:

• Every old URL → one relevant 301
• No redirect chains
• No redirect loops
• No mass redirects to homepage
• New URLs return 200
• Canonicals point to new URLs

Google recommends avoiding redirect chains and using direct permanent redirects where possible. Google for Developers

After launch monitoring

For the first 2–8 weeks, watch daily:

Ranking signals

• Keyword position drops
• Lost featured snippets
• Category page declines
• Product page URL swaps
• SERPs showing old URLs

Crawl/index signals

• 404 spikes
• Excluded pages
• Indexed page count changes
• Crawl stats
• Sitemap processing

Revenue signals

Don’t only monitor rankings. Ecommerce migrations often lose money through:

• Category page visibility loss
• Faceted navigation mistakes
• Product variant URL changes
• Internal linking changes
• Tracking breaks

My preferred tool combinations

Enterprise ecommerce (100k+ URLs)

• Screaming Frog + Ahrefs/Semrush + Google Search Console + URL mapping tool

Shopify/Magento/Adobe Commerce migration

• Screaming Frog crawl exports
• Redirect mapping automation
• Search Console monitoring
• Analytics revenue comparison

Very large catalog (500k–millions of URLs)

Add:

• Log file analysis
• Enterprise rank tracker
• Automated redirect monitoring
• Database-driven redirect management

A key practice: freeze a pre-launch SEO baseline (rankings, clicks, impressions, indexed URLs, organic revenue, top landing pages) so you can tell whether a post-launch change is normal migration turbulence or a real failure. Google for Developers

If you share your platform move (for example Magento → Shopify, custom → Shopify Plus, Salesforce Commerce Cloud, etc.) and approximate URL count, I can suggest a more specific stack and migration workflow.

For a large ecommerce migration, I’d use a combination rather than rely on one SEO platform. The key is to separate URL mapping/redirect QA from Google visibility monitoring.

My recommended stack

1. Build the master URL map with Screaming Frog.

Before launch, crawl the existing store and combine that inventory with URLs from:

• Google Search Console
• Analytics
• XML sitemaps
• backlink tools
• server logs
• your ecommerce platform/database

Screaming Frog specifically supports uploading an old-URL list and auditing every redirect through to its final destination, including redirect chains, loops, status codes and final indexability. Screaming Frog Screaming Frog

I'd make your mapping sheet roughly:

Old URL → New URL → redirect status → priority → organic clicks → backlinks → notes

2. Use Screaming Frog again immediately after launch.

Run the old URL list against production and look for:

• 301 → 200
• 301 → 404
• redirect chains
• redirect loops
• 302s where you expected 301s
• redirects to irrelevant pages
• canonical mismatches
• accidental noindex
• robots.txt blocks
• orphaned new URLs

This is particularly important at ecommerce scale because a migration can have thousands of individually broken product/category URLs that aren't obvious from manually checking the site. Screaming Frog

3. Make Google Search Console your source of truth for Google impact.

Monitor clicks, impressions, average position and indexing against a pre-migration baseline. Search Console also gives you URL Inspection and indexing reports for diagnosing individual pages. Google Google Help

I'd create segments for:

• top revenue-driving URLs
• top organic landing pages
• category pages
• product pages
• brand pages
• informational/content pages
• URLs with substantial backlinks

Don't panic over a small visibility wobble immediately after launch: Google explicitly says rankings can fluctuate temporarily during a migration while URLs are recrawled and reassessed. Google for Developers

4. Add Ahrefs or Semrush for ranking surveillance.

I'd pick one, not necessarily both.

• Ahrefs → particularly useful if backlinks are a major part of your migration risk.
• Semrush → particularly good if you want extensive rank tracking and visibility reporting.

For a big shop, track a representative keyword set before the migration, then compare positions/visibility at roughly 1, 3, 7, 14, 30 and 60 days afterward.

One tool I'd consider specifically for this project

URLMatcher is interesting if you want a migration-focused workflow rather than assembling everything yourself. It explicitly combines crawling, URL mapping, redirect planning, launch validation, and post-launch monitoring of URL/query movement and indexation. URLMatcher

One important migration rule

Don't just map URLs that currently rank.

Map every meaningful legacy URL, especially URLs with backlinks, organic traffic, conversions, or historical importance. Google recommends keeping redirects for as long as possible—generally at least a year—and submitting the new sitemap after the move. Google for Developers

If this is a 100k+ URL ecommerce migration, I'd lean toward Screaming Frog + GSC + Ahrefs/Semrush, with a database/spreadsheet-driven redirect map underneath. That's a much safer setup than expecting an all-in-one SEO suite to catch everything.

For a large ecommerce migration, I’d use a stack rather than rely on one SEO platform. The key is to separate URL discovery/mapping, redirect QA, and post-launch ranking/indexation monitoring.

My recommended stack

• Screaming Frog SEO Spider — probably the most useful tool for the actual migration QA. Crawl the old site, crawl the new site, export URL inventories, compare versions, and test redirect behavior at scale. Google specifically recommends tools such as Screaming Frog for checking redirects during migrations. Google Developers
• Ahrefs Site Audit + Site Explorer — excellent for finding high-value old URLs based on backlinks, checking redirect chains, broken backlinks, and comparing organic performance before/after launch. Its Site Audit explicitly monitors redirects and redirect loops. Ahrefs Ahrefs
• Semrush — strong all-around option if you want crawling, rank tracking, organic traffic visibility, and migration reporting in one platform. Its migration guidance recommends combining crawl data with GSC, GA4, backlinks, sitemaps, and CMS URL data to build the migration URL inventory. Semrush
• Google Search Console — essential and free. Use it as the source of truth for indexing, impressions, clicks, queries, sitemap processing, and emerging crawl errors. Google recommends monitoring both old and new properties during a migration. Google Developers
• GA4/server logs — not strictly SEO tools, but very useful for identifying URLs that actually receive traffic and detecting whether old-site traffic is transitioning to the new URLs. Google explicitly recommends analytics and server-log monitoring during a move. Google Developers

For a really large shop

I'd build the migration around a master URL map, rather than letting the CMS generate redirects ad hoc:

Build the old-URL inventory from multiple sources: old XML sitemaps, CMS exports, GSC, analytics, crawl data, server logs, and backlinks. This is important because any single crawl will miss URLs that aren't currently internally linked. Google Developers Semrush

What I'd monitor immediately after launch

Set up automated checks for:

1. Old URL → expected new URL
2. 301/308 vs. accidental 302/307
3. Redirect chains and loops
4. Redirects landing on 404/410 pages
5. New URLs returning 200
6. Canonical tags
7. robots/noindex changes
8. XML sitemap URLs
9. Internal links still pointing to old URLs
10. GSC indexed pages and crawl errors
11. Organic clicks/impressions by URL
12. Keyword rankings by URL
13. Organic revenue by landing page

Google recommends permanent server-side redirects and specifically advises avoiding redirect chains; direct old → final-new URLs are preferable. Google Developers

One important ecommerce trick

Don't monitor just average rankings. Create a pre-migration list of your top revenue/traffic/ backlink URLs and their primary keywords, then compare those exact URL/keyword pairs after launch.

That lets you distinguish:

"Average rankings fell 8%"

from the much more actionable:

"17 of our top 100 revenue-generating category pages lost their old URLs, and 11 of those have either a redirect problem or aren't indexed."

For a large shop, Screaming Frog + Ahrefs + GSC + GA4 would be my preferred combination. If you want an all-in-one commercial platform, Semrush is a strong alternative.

Also, Google's current migration guidance recommends keeping redirects in place for at least a year where possible and submitting the new sitemap after launch. Google Developers

For a large ecommerce migration, I’d use a combination rather than rely on one platform. The key jobs are: build a defensible old→new URL map, validate redirects at scale, and establish a ranking/traffic baseline before launch.

My recommended stack

1. Screaming Frog — the workhorse for URL mapping

For a big migration, this would be my first purchase. You can crawl the current site, export the full URL inventory, combine it with URLs from GSC/analytics/backlinks, and use that as the source for your redirect map. Screaming Frog specifically recommends combining crawl data with analytics, GSC, backlink tools, sitemaps and logs to avoid missing valuable old URLs. Screaming Frog Screaming Frog

It is particularly good after the redirects are implemented: upload the old URLs in List Mode, enable "Always Follow Redirects," and it will follow each URL through to the final destination so you can catch chains, loops, 404s, 5xxs, and incorrect targets. Screaming Frog Screaming Frog

screamingfrog.co.uk

2. Semrush — best for watching the migration's SEO impact

Semrush is particularly useful for the before/after ranking baseline. Its Position Tracking can track rankings and visibility over time and break performance down by URL, which is useful for identifying which categories/products suffered after launch. Semrush Semrush

I'd export your important keywords before the migration, then keep the same tracking set afterward. Don't just watch overall visibility—segment by:

• Category
• Product
• Brand/non-brand
• High-revenue landing pages
• High-backlink pages
• Keywords that were previously positions 1–3
• Keywords that dropped >5 or >10 positions

semrush.com

3. Ahrefs — particularly valuable for backlinks and redirect problems

Ahrefs Site Audit can continuously crawl the new site and flag redirect chains, redirecting pages, broken links, canonical problems, indexability issues, sitemap problems, etc. Ahrefs Ahrefs Help Center

Its Rank Tracker is also useful for monitoring keyword movement by location/device, while its backlink data helps identify valuable old URLs that absolutely need a good destination. Ahrefs

ahrefs.com

4. Google Search Console — don't skip this

This is your ground truth for Google's view of the migration. I'd monitor:

• Search clicks/impressions
• Average position
• Indexed pages
• Page indexing errors
• 404s/soft 404s
• Crawl stats
• Sitemap processing
• Core Web Vitals
• Queries/pages losing impressions

Most importantly, submit the new XML sitemap(s) immediately after launch and keep the old/new URL mapping around so you can investigate unexpected indexing changes.

The migration workflow I'd use

Before launch

1. Crawl the entire old site with Screaming Frog.
2. Export URLs from GSC, GA4, your CMS/database, XML sitemaps and backlink tools.
3. Combine and deduplicate those lists.
4. Assign each old URL a destination: - Exact new equivalent
5. Closest relevant replacement
6. 410/404 if genuinely gone
7. Prioritize URLs by organic traffic + revenue + backlinks + rankings, not simply URL count.
8. Establish a ranking baseline in Semrush/Ahrefs.
9. Crawl the staging site and compare technical/indexability signals.

Immediately before launch

• Freeze the redirect map.
• Test a sample of your highest-value URLs.
• Then bulk-test the entire old URL list with Screaming Frog.

Immediately after launch

Run the old URL list through Screaming Frog again. You want:

OLD URL → 301 → FINAL NEW URL → 200

Not:

OLD → 301 → 301 → 302 → 404

Screaming Frog specifically recommends auditing redirects at scale and checking for incorrect destinations, multiple hops, errors, loops and non-indexable targets. Screaming Frog

First 2–4 weeks

Run daily/very frequent checks on:

• GSC clicks/impressions
• Rankings
• Organic revenue
• 404/5xx volume
• Indexed pages
• Redirect errors
• Crawl stats
• Top landing pages

A temporary ranking wobble isn't necessarily a disaster, but a persistent loss concentrated in a category or group of URLs is a red flag. Semrush's migration guidance similarly recommends comparing rankings by URL and investigating pages that don't recover as expected. Semrush

If I had to pick only three

Screaming Frog + Semrush + Google Search Console.

Screaming Frog handles the URL/redirect engineering, Semrush handles ranking/visibility monitoring, and GSC tells you what Google is actually doing.

For a very large shop (100k+ URLs), I'd add Ahrefs primarily for backlink/value discovery and continuous technical monitoring.

For a large ecommerce migration, I’d use a stack rather than rely on one tool. The key is to establish a complete old-URL inventory, map it to the new URLs, validate redirects at scale, and then watch rankings/indexation after launch. Google explicitly recommends this workflow for URL-changing migrations. Google Developers

My recommended stack

• Screaming Frog SEO Spider — best core migration tool

• Crawl the old site and export the complete URL inventory.
• Crawl staging/new site and compare technical elements.
• Upload the old URL list in List Mode and verify every redirect.
• Finds 404s, redirect chains/loops, 3xx issues, canonical problems, etc.
• Particularly good when you have hundreds of thousands or millions of URLs and want granular control. Screaming Frog Screaming Frog
• Sitebulb — best for migration diagnostics

• Excellent visual reporting and crawl comparisons.
• Can combine crawl data with Search Console/GA data.
• Useful for spotting changes in internal linking, indexability, canonicals, content, and information architecture.
• Its migration workflow specifically supports old → staging → live comparisons. Sitebulb
• Ahrefs or Semrush — prioritize what matters

• Use backlink data to identify old URLs that have valuable external links.
• Use organic traffic/ranking data to identify high-value URLs that absolutely need a destination.
• This is especially important for ecommerce where you may have millions of low-value faceted/filter URLs but a relatively small set of URLs responsible for most organic revenue. Sitebulb Screaming Frog
• Google Search Console — mandatory monitoring layer

• Establish a pre-migration baseline for clicks, impressions, queries and indexed URLs.
• After launch, watch indexing, sitemap processing, crawl errors and query/page performance.
• For a domain change, use Change of Address.
• Google recommends monitoring both the old and new properties during the transition. Google Developers Google Developers

For ranking-drop detection

I'd maintain a daily migration dashboard combining:

GSC clicks/impressions + rank tracking + organic revenue + indexed URLs + crawl errors + redirect failures

For rank tracking, Ahrefs/Semrush are fine, but the important thing is to preserve the pre-migration keyword → old URL relationship. After launch, you want to see whether those same queries move to the expected new URLs—not merely whether overall visibility changed.

One important ecommerce trick

Don't build your redirect map from the crawl alone.

Combine:

1. Old-site crawl
2. XML sitemaps
3. GSC top landing pages
4. Analytics/revenue landing pages
5. Backlinked URLs from Ahrefs/Semrush
6. Server logs, if available
7. CMS/product database
8. New-site crawl/sitemap

Then assign every valuable old URL a specific closest-equivalent destination. Google specifically warns against dumping unrelated old URLs onto the homepage and recommends direct permanent redirects rather than chains. Google Developers

If I were running the migration

Screaming Frog + GSC + Ahrefs/Semrush would be my minimum stack.

Add Sitebulb if the migration is sufficiently complex that you want much better crawl comparisons and diagnostic reporting.

And I'd do a full crawl of the old site immediately before launch, followed by a full redirect audit immediately after launch. Screaming Frog's migration workflow is designed specifically for this. Screaming Frog Screaming Frog

For a really large shop, I can also lay out a migration spreadsheet/database schema for the URL map—e.g. old URL → new URL → redirect status → traffic → revenue → backlinks → priority → validation status—which is often the difference between a manageable migration and chaos.

For a large ecommerce migration, I’d use a stack rather than rely on one SEO platform. The key is to separate URL mapping, redirect QA, and post-launch ranking/indexation monitoring.

My recommended stack

Google itself recommends creating a URL mapping, implementing redirects, testing them, and monitoring both old and new URLs during the move. Google for Developers

For URL mapping

I'd start with Screaming Frog + Search Console + your analytics/backlink data.

Build a master spreadsheet/database with:

old URL → new URL → redirect status → final URL → page type → organic traffic → organic keywords → backlinks → priority

Don't generate the map solely from the old site's crawl. Include URLs that may not currently be crawlable but still have SEO value—especially URLs with backlinks, historical traffic, or Search Console impressions.

For a very large shop, Ahrefs can help identify heavily linked URLs, and its Site Audit can expose redirect destinations and final status codes. Ahrefs

For redirect monitoring

Screaming Frog is my first choice for QA. Crawl the old URL list against the production site and flag:

• 404/410 responses
• 301/302 mistakes
• redirect chains
• redirect loops
• redirects to irrelevant pages
• old URLs that weren't redirected
• new pages with incorrect canonicals
• internal links still pointing at old URLs

Ahrefs is also strong here; its Site Audit explicitly monitors temporary/permanent redirects and redirect loops, and can identify redirect chains. Ahrefs Help Center Ahrefs

One important distinction: don't just check that an old URL returns a 301. Check where it ultimately lands and whether that destination is the correct equivalent page.

For catching ranking drops

I'd establish a pre-launch baseline at least a few weeks before migration:

• rankings by keyword
• organic clicks/impressions
• landing-page organic traffic
• indexed URLs
• top-performing category/product pages
• backlinks to important URLs

Then monitor daily during the first couple of weeks.

Semrush or Ahrefs is useful for keyword/ranking surveillance, while Search Console gives you Google's actual clicks, impressions, indexing and query/page data. Google specifically recommends watching the old site's traffic decline while the new site's traffic increases, along with sitemap/indexing reports. Google for Developers

The setup I'd choose

For a large ecommerce store, my practical combination would be:

Screaming Frog → migration/redirect QA
Ahrefs → backlinks + organic visibility + valuable URL discovery
Semrush → rank tracking + ongoing visibility alerts
Search Console → Google indexing/crawl validation
GA4/server logs → actual traffic and bot behavior

You don't necessarily need both Ahrefs and Semrush if budget is constrained. Screaming Frog + Search Console + either Ahrefs or Semrush is a very solid migration stack.

And don't panic over every ranking fluctuation immediately after launch: Google says significant migrations can produce temporary ranking volatility while URLs are recrawled and reindexed; larger sites can take longer. Google for Developers

One migration-specific rule I'd make non-negotiable: keep the old-to-new URL map and redirect monitoring running well after launch. Google recommends keeping redirects for at least a year for URL migrations. Google for Developers

If you tell me roughly how many URLs/products the shop has (e.g. 100k vs. 5M) and whether URLs are changing, I can give you a concrete migration-tool stack and QA workflow for that scale.

For a large e-commerce migration, I’d use a stack rather than rely on one SEO platform. The key is to separate URL mapping/redirect QA from ranking/traffic monitoring.

My recommended stack

1. URL mapping: Screaming Frog is the workhorse

For a big shop, I'd start with a complete crawl of the old site, then combine that URL inventory with:

• Google Search Console landing pages
• Analytics landing pages
• XML sitemaps
• URLs receiving backlinks
• High-revenue/conversion URLs
• URLs in the old CMS/database

Screaming Frog specifically recommends combining crawl data with sources such as GA, GSC, backlink tools and log files so important/orphan URLs don't get missed. Screaming Frog

If your URL structures are changing substantially, its URL Mapping and crawl-comparison functionality can compare old vs. staging URLs and identify changed, missing, added and removed pages. Screaming Frog

2. Redirect QA: definitely Screaming Frog

This is probably the most useful tool for the actual launch.

Give it your entire old URL list, enable "Always Follow Redirects," and crawl it. It can produce an All Redirects report showing the starting URL, final URL, every hop, status codes, redirect type, loops and final indexability. Screaming Frog Screaming Frog

I'd specifically flag:

• Old URL → 404/410
• Old URL → wrong product/category
• 301 → 301 → 200 chains
• Redirect loops
• 302s where you intended 301s
• Redirects to noindex pages
• Redirects to noncanonical URLs
• Redirects to irrelevant category/home pages
• Old high-value URLs with no equivalent destination

For a huge catalog, this is much safer than checking redirects manually or relying exclusively on the new platform's redirect manager.

3. Ranking-drop detection: Semrush/Ahrefs + GSC

Use Semrush Position Tracking or Ahrefs Rank Tracker to establish a baseline before launch.

Don't just track a few hundred head keywords. For an e-commerce migration, segment the monitoring:

• Brand
• Category keywords
• Product keywords
• High-revenue queries
• High-margin categories
• Long-tail queries
• Previously top-3/top-10 terms
• Queries associated with your most valuable landing pages

Semrush's Site Audit + Position Tracking combination is explicitly designed to connect technical changes with ranking changes. Semrush

Then use GSC as your source of truth for Google clicks/impressions/query/page behavior, particularly comparing pre- and post-migration periods.

4. Don't panic over the first few days

Google explicitly says that ranking fluctuations during a migration are normal while it recrawls and reindexes the new URLs. Larger sites can take longer to settle. Google for Developers

So I'd establish three monitoring windows:

Pre-launch: baseline
→ rankings, clicks, impressions, indexed URLs, crawl stats, organic revenue, top landing pages.

Launch + first 72 hours: technical fire drill
→ redirects, 404s/5xxs, robots.txt, noindex, canonicals, sitemap, internal links, server logs, analytics.

Weeks 1–6: visibility recovery
→ rankings, GSC clicks/impressions, indexed pages, organic revenue, crawl behavior, lost URLs.

One important point

Don't make the migration mapping simply:

old URL → nearest-looking new URL

Instead, create a spreadsheet/database with something like:

Old URL | New URL | Status | Traffic | Revenue | Backlinks | Priority | Redirect Tested | Final Status | Canonical | Indexable

That lets you prioritize the URLs that actually matter when the shop has hundreds of thousands or millions of URLs.

And keep the 301s in place for at least a year; Google recommends that timeframe so it has time to transfer signals and recrawl old URLs. Google for Developers

If I were choosing only three: Screaming Frog + Google Search Console + Semrush/Ahrefs. Screaming Frog handles the migration mechanics; GSC tells you what Google is actually doing; the third gives you much more granular ranking/backlink monitoring.

For a large ecommerce migration, I’d avoid relying on a single SEO suite. The best setups usually combine:

1. URL discovery + redirect mapping
2. Redirect validation
3. Pre/post migration crawling
4. Ranking and traffic monitoring

Here are the tools I’d shortlist:

1. URL mapping and redirect planning

Screaming Frog SEO Spider

Best all-around technical migration workhorse.

Use it for:

• Crawling the old store and exporting every URL
• Comparing old vs. new URL inventories
• Finding orphaned URLs
• Testing redirect status codes
• Detecting redirect chains and loops
• Bulk redirect validation

Good workflow:

• Crawl old site → export URLs
• Crawl staging/new site → export URLs
• Build old → new mapping spreadsheet
• Upload redirect list and verify after launch

BestPage### URLMatcher

More migration-specific: designed around building redirect maps, validating changes, and monitoring URL/query movement after launch. It can crawl/import old and new URLs, help review redirect matches, and connect migration checks with Search Console data. URLMatcher URLMatcher

Useful for very large catalogs where manual spreadsheet matching becomes painful.

2. Prioritizing which URLs matter most

A common migration mistake is mapping every URL equally. Your highest-value URLs should get the most review.

Use:

Ahrefs

Good for:

• Backlink discovery
• Identifying URLs with external authority
• Finding top organic landing pages
• Monitoring keyword movement

Prioritize redirects for:

• Pages with strong backlinks
• High-revenue product/category pages
• Pages ranking in positions 1–20
• Pages with historical traffic

Semrush

Useful if your team already uses it for:

• Position tracking
• Site audits
• Competitor visibility comparisons
• Automated reporting

3. Redirect monitoring after launch

You want to catch:

• 404 spikes
• Redirects pointing to wrong pages
• Redirect chains
• Missing redirects
• Canonical mistakes

Tools:

Screaming Frog

Run crawls:

• Before launch (baseline)
• Launch day
• 24–72 hours after
• Weekly for the first month

Sitebulb

A good alternative if stakeholders need clearer visual reports. It highlights crawl issues and redirect problems in a more presentation-friendly way. BestPage

Google Search Console

Essential and free:

• Indexing changes
• Coverage issues
• Sitemap processing
• Search performance changes

Google specifically recommends preparing URL mappings, implementing redirects, testing them, and monitoring old/new URLs during site moves. Google for Developers

4. Catching ranking drops

Use at least one rank tracker plus analytics:

Rank tracking

• Ahrefs Rank Tracker
• Semrush Position Tracking
• STAT Search Analytics (better for enterprise-scale SEO teams)

Track:

• Top 1,000–10,000 keywords
• Category pages
• Brand + non-brand queries
• Product queries
• SERP features

Traffic monitoring

Connect:

• Google Search Console
• Google Analytics 4
• Revenue dashboards

Watch:

• Organic clicks
• Organic revenue
• Landing page sessions
• Conversion rate
• Indexed page count

A practical enterprise migration stack

For a large shop, I’d typically use:

Migration checklist I’d insist on

Before launch:

• Export every existing URL from: - XML sitemaps
• CMS database
• Search Console
• Analytics landing pages
• Backlink tools
• Create an old → new URL map
• Avoid redirecting everything to the homepage
• Preserve category/product intent where possible
• Crawl staging and compare: - titles
• canonicals
• hreflang
• indexability
• internal links

After launch:

• Crawl the new site immediately
• Check redirect coverage
• Monitor 404s daily for 2–4 weeks
• Compare rankings and Search Console queries
• Fix pages where rankings transferred to the wrong URL

For a large ecommerce migration (50k+ URLs), I’d usually pair Screaming Frog + Ahrefs + Search Console, and add a dedicated migration mapper like URLMatcher if the catalog structure is changing significantly. URLMatcher BestPage

• Crawl the new site immediately
• Check redirect coverage
• Monitor 404s daily for 2–4 weeks
• Compare rankings and Search Console queries
• Fix pages where rankings transferred to the wrong URL

For a large ecommerce migration (50k+ URLs), I’d usually pair Screaming Frog + Ahrefs + Search Console, and add a dedicated migration mapper like URLMatcher if the catalog structure is changing significantly. URLMatcher BestPage

For a large ecommerce migration, I’d use a small stack rather than rely on one SEO platform. The key is separating URL/redirect QA from ranking and traffic monitoring.

My recommended stack

• Screaming Frog SEO Spider — best for URL mapping + redirect QA.

Crawl the old store, export the complete URL set, crawl staging, compare old vs. new, and audit every redirect after launch. Its crawl comparison supports URL mapping between different URL structures, and its redirect report exposes chains, loops, final destinations, status codes, and indexability. Screaming Frog Screaming Frog
screamingfrog.co.uk

• Semrush — best all-around monitoring layer.

Use Position Tracking to establish a pre-migration keyword baseline and watch visibility/positions afterward. Its migration guidance specifically recommends monitoring rankings by URL and investigating pages that underperform after launch. Semrush
semrush.com

• Google Search Console — essential, and free.

This is your source of truth for Google organic clicks/impressions, indexing, sitemap status, crawl behavior and post-launch problems. Sitebulb's migration guidance also recommends watching GSC indexing and Crawl Stats closely after launch. Sitebulb
search.google.com

• Sitebulb — excellent alternative/complement to Screaming Frog.

Particularly useful if you want a more visual migration audit, crawl comparisons, URL-level Search Console data, prioritized issues, and change monitoring. Sitebulb
sitebulb.com

• Ahrefs — useful for backlink-driven redirect prioritization.

Its backlink data can help identify old URLs with valuable external links that absolutely need a good destination. Sitebulb specifically recommends Ahrefs/Semrush for benchmarking rankings and finding broken backlinks to removed pages. Sitebulb
ahrefs.com

For a big shop, I'd structure the migration like this

Before launch

1. Crawl the entire old site with Screaming Frog.
2. Combine that URL list with: - GSC top landing pages
3. GA4 landing pages/revenue pages
4. XML sitemaps
5. backlink URLs
6. historically important URLs
7. Create an old URL → new URL mapping.
8. Crawl staging and compare old vs. new.
9. Check canonicals, robots.txt, noindex, internal links, titles, H1s and content—not just redirects.
10. Establish a ranking baseline in Semrush/Ahrefs.

Immediately after launch

1. Upload the entire old URL list to Screaming Frog and follow redirects.
2. Flag anything returning: - 404/410
3. 5xx
4. 302 where a permanent move is intended
5. redirect chains
6. redirect loops
7. redirects to irrelevant/non-indexable pages
8. Crawl the new site from scratch.
9. Submit the new XML sitemap(s) in GSC.
10. Watch GSC indexing/crawl stats and Semrush ranking visibility daily.

Screaming Frog specifically recommends combining the crawl's URL list with analytics, GSC, backlink and log-file sources so valuable URLs aren't omitted from the redirect map. Screaming Frog Screaming Frog

If I had to pick only three

Screaming Frog + Google Search Console + Semrush.

That gives you:

Old URLs → redirect map → redirect validation → new-site crawl → Google indexing → rankings/visibility

For a 100k+ URL ecommerce migration, I'd also put the URL mapping into a database/spreadsheet with columns for old_url, new_url, redirect_status, final_url, organic_clicks, organic_revenue, backlinks, and priority. That makes it much easier to distinguish a harmless long-tail fluctuation from a migration failure.

For a large e-commerce migration, I’d use a stack rather than one tool. The key is to establish a complete pre-migration URL baseline, validate every redirect, and compare organic performance before/after launch.

My recommended stack

• screamingfrog.co.uk — best for URL mapping + redirect QA

• Crawl the entire old site and save it as your baseline.
• Export the old URLs and build your 1:1 redirect map.
• Crawl staging and use URL Mapping/Compare to compare old vs. new URLs.
• After launch, upload the old URL list in List Mode and enable Always Follow Redirects to identify redirect chains, loops, 404s, temporary redirects, and redirects landing on non-indexable pages. Screaming Frog Screaming Frog Screaming Frog
• Particularly valuable for a shop with hundreds of thousands or millions of URLs.
• ahrefs.com — strong ongoing technical monitoring

• Useful for recurring crawls after launch.
• Tracks redirects, redirect chains, broken links, indexability, canonicals, duplicate content, sitemaps, etc.
• Its historical crawl data is useful for spotting regressions after the migration. Ahrefs
• Google Search Console — essential for actual Google visibility

• Compare clicks, impressions, CTR and average position before/after migration.
• Monitor indexing and sitemap coverage.
• Keep both old and new properties verified when appropriate.
• If you're changing domains/subdomains, use Change of Address.
• Google specifically recommends monitoring both old and new URLs during a migration. Google for Developers Google for Developers
• A rank tracker such as semrush.com or ahrefs.com

• Track a fixed set of high-value commercial keywords daily/weekly.
• Segment by category, brand, product, location/device, etc.
• More importantly, maintain a pre-migration keyword baseline so you can distinguish normal SERP volatility from a genuine migration-related loss.

For a big shop, I'd structure it like this

One important point: don't build the redirect map from the old crawl alone

For a large store, I'd merge URLs from:

• Old-site crawl
• Google Search Console top landing pages
• Analytics landing pages
• XML sitemaps
• CMS/database URL inventory
• Backlink tools
• Server logs
• URLs generating meaningful revenue/conversions

Screaming Frog itself recommends combining crawl data with sources such as analytics, GSC, log files, and backlink/ranking platforms when constructing the migration URL set. Screaming Frog

Then give every old URL a disposition such as:

Old URL → New URL → redirect status → indexability → canonical → traffic → revenue → backlinks → priority

That makes it much easier to catch the dangerous case where a technically valid 301 points to the wrong product/category, rather than merely checking whether the redirect returns 301.

What I'd consider the minimum viable stack

If you want to keep the tooling lean:

Screaming Frog + Google Search Console + GA4 + one rank tracker

That's enough to handle the core migration workflow. Google explicitly recommends creating a URL mapping, implementing redirects, testing them, submitting the new sitemap, and monitoring traffic/indexing during a URL migration. Google for Developers

And don't panic over every ranking movement immediately after launch: Google says significant migrations can produce temporary ranking fluctuations while URLs are recrawled and reindexed, with larger sites potentially taking longer. Google for Developers Google for Developers

If you tell me roughly how many URLs the shop has (e.g. 100k, 1M, 10M) and whether the URL structure is changing, I can lay out a practical migration QA checklist and the exact reports I'd export from each tool.

For a large ecommerce migration, I’d use a combination rather than rely on one SEO platform.

My recommended stack

For the URL mapping itself

I'd build the migration map from multiple URL sources, not just a crawl:

1. Old-site Screaming Frog crawl.
2. Google Search Console's top/linked pages.
3. Analytics landing pages.
4. Ahrefs/Semrush backlink URLs.
5. XML sitemaps.
6. CMS/database export.
7. Server logs, if available.

Screaming Frog specifically recommends combining crawl URLs with sources such as Analytics, GSC, backlink tools, sitemaps and logs when constructing a migration redirect set. Screaming Frog

Then create something like:

old URL → new URL → redirect status → final status → canonical → indexable → organic traffic → backlinks → priority

For redirect QA

Screaming Frog is probably my first choice. Upload the entire old URL list in List Mode and enable Always Follow Redirects. It can follow each URL through to its final destination and produce an "All Redirects" report showing the hops. Screaming Frog Screaming Frog

That catches things like:

• old → 301 → new ✅
• old → 301 → intermediate → 301 → new ⚠️
• old → 302 ⚠️
• old → 301 → 404 ❌
• redirect loops ❌
• JavaScript redirects ⚠️
• redirects pointing to irrelevant pages ⚠️

Semrush and Ahrefs can provide useful secondary checks; Semrush Site Audit explicitly checks redirect chains and loops. Semrush Ahrefs

For catching ranking drops

Don't just watch overall organic traffic. Create a pre/post migration benchmark for your important URLs and keywords.

I'd monitor:

• Organic clicks/impressions by URL
• Average position by keyword
• Number of ranking keywords
• Indexed pages
• Organic landing-page traffic
• Revenue/conversions from organic
• 404/5xx volume
• Crawl stats
• Canonical changes
• Sitemap/indexation coverage
• Backlinks to redirected URLs

GSC + Ahrefs/Semrush is a particularly good combination here: GSC tells you what Google is actually doing with the site, while the third-party rank/backlink data gives you broader competitive and historical visibility.

One important point: if you're changing domains, Google recommends using the Search Console Change of Address tool after the redirects are in place. Google also recommends maintaining redirects for at least 180 days, and longer if the old URLs continue receiving Google traffic. Google Help

If I were running the migration:
Screaming Frog → URL/redirect control, GSC → Google/indexation control, Ahrefs → backlinks/rank visibility, Semrush → recurring technical monitoring, GA → business impact.

If you tell me roughly how many URLs you're migrating (e.g. 50k, 500k, 5M) and whether it's domain + platform + URL structure changes, I can lay out a practical migration QA workflow and spreadsheet schema for it.

For a large ecommerce replatform, I’d treat SEO migration tooling as a stack rather than a single tool. You need four capabilities:

1. URL inventory + redirect mapping
2. Redirect validation at scale
3. Pre/post crawl comparisons
4. Ranking + organic traffic monitoring

Here are the tools I’d shortlist:

A practical migration workflow

1. Before development finishes

Create a "source of truth" URL spreadsheet/database:

Columns I’d keep:

• Old URL
• New URL
• HTTP status expected (usually 301)
• Page type (product/category/blog/etc.)
• Organic clicks (GSC)
• Organic sessions (analytics)
• Ranking keywords
• Backlinks
• Priority tier
• Redirect owner/status

Sources:

• Old site crawl
• XML sitemaps
• Google Search Console
• Analytics landing pages
• Backlink tools

2. Build and test redirects

Use:

• Screaming Frog for bulk redirect testing
• A redirect mapping tool for large URL sets
• Server/CDN logs after launch

Check for:

• 404s
• 410s accidentally introduced
• redirect chains
• redirect loops
• old URLs redirecting to irrelevant pages
• canonical tags pointing to old URLs

3. Crawl staging before launch

Run old vs. new comparisons:

• URL count
• indexable pages
• titles/descriptions
• canonical tags
• schema
• internal links
• pagination
• hreflang (if applicable)
• robots directives

4. Monitor the first 30–90 days

Track:

Daily

• Organic revenue
• Organic sessions
• Indexed pages
• 404 volume
• Redirect errors
• Crawl stats

Weekly

• Keyword rankings
• Lost landing pages
• Query movement
• Category/product visibility

Google Search Console is particularly important here because it shows whether Google is transferring queries and impressions to the new URLs rather than just whether your rank tracker sees movement. URLMatcher

My typical stack for a large shop

For a 100k+ URL ecommerce migration, I’d usually combine:

• Screaming Frog → crawl/diff/redirect QA
• Ahrefs or Semrush → prioritize valuable URLs + monitor rankings
• Google Search Console → Google indexing truth
• Botify or Lumar → if millions of URLs
• URLMatcher or similar migration tooling → accelerate URL mapping and post-launch validation URLMatcher

A key mistake with large shops is mapping every URL equally. I’d prioritize:

1. URLs with organic traffic
2. URLs ranking top 20
3. URLs with backlinks
4. High-margin product/category pages
5. Everything else

That makes the migration much safer when you’re dealing with hundreds of thousands or millions of URLs. shopify.com

For a large ecommerce replatform, I’d use a stack rather than rely on one SEO platform. The key is to establish a complete pre-migration URL inventory, test the redirect map at scale, and then compare rankings/indexation/traffic against the baseline.

Best tools by job

• screamingfrog.co.uk — best core migration crawler. Crawl the old site and staging/new site, export URLs/status codes/canonicals/titles/internal links, then crawl the redirect list after launch. It’s particularly good for finding 404s, redirect chains, bad canonicals, orphaned URLs, and other technical differences. Google specifically recommends crawling redirects with Screaming Frog during migrations. Google for Developers
• sitebulb.com — best for comparing old vs. new sites. It can save multiple crawls and compare them, while incorporating Search Console/GA data. Its migration workflow is designed around benchmarking, URL mapping, redirect testing, and post-launch monitoring. Sitebulb
• search.google.com — essential, not optional. Use it for the pre-migration performance baseline, indexing/sitemap monitoring, crawl stats, URL inspection, and post-launch clicks/impressions. If you're changing domains, Google's Change of Address tool is also relevant. Google Help Google for Developers
• semrush.com or ahrefs.com — best for ranking/backlink-risk monitoring. Before launch, export ranking keywords and important landing pages; also identify valuable backlinks pointing to URLs that are changing or disappearing. After launch, monitor ranking movements and lost/broken backlinks. Sitebulb's migration guidance specifically recommends Ahrefs/Semrush for this role. Sitebulb
• lookerstudio.google.com — useful for a migration dashboard, particularly when you want old-vs-new Search Console/analytics data by URL or page category. Sitebulb

For a big shop, I'd build this workflow

Before launch

1. Crawl the entire old site with Screaming Frog/Sitebulb.
2. Export all historical URLs, not just currently linked URLs: - XML sitemaps
3. organic landing pages
4. high-traffic/product/category pages
5. Search Console URLs
6. URLs with external backlinks
7. old PDFs/images where relevant
8. Crawl the new/staging site.
9. Build an old URL → new URL mapping.
10. Flag every old URL as: - exact replacement
11. category replacement
12. product replacement
13. intentionally removed → 410/404
14. needs manual review
15. Crawl/test the proposed redirect map before launch.

Google explicitly recommends creating this mapping and using permanent server-side redirects; it also recommends avoiding redirect chains and pointing directly to the final destination. Google for Developers

Launch day

Run a crawl against the old URLs and verify:

old URL → 301/308 → final new URL → 200

You want to catch:

• 404/410 where there should be a replacement
• 302s instead of permanent redirects
• redirect chains/loops
• redirects to the homepage
• redirects to irrelevant products/categories
• canonical URLs still pointing at the old site
• staging noindex
• robots.txt blocking important sections
• broken internal links
• missing structured data
• missing hreflang
• major changes in titles/content
• sitemap containing old URLs

First 2–6 weeks

Monitor daily at first:

• organic clicks/impressions
• rankings for high-value keywords
• indexed URL count
• crawl errors
• server logs/Googlebot activity
• traffic and revenue by landing-page category
• 404s and unexpected redirects
• old URLs still appearing in Google
• new URLs failing to index

Some ranking volatility is expected while Google recrawls/reindexes a large migration; Google says larger sites can take considerably longer than smaller ones to settle. Google for Developers

My preferred stack

For a large ecommerce migration, I'd probably choose:

Screaming Frog + Google Search Console + Sitebulb + Semrush/Ahrefs + GA4

The important part isn't having five dashboards, though. It's having a single migration spreadsheet/database keyed by URL that combines:

old URL | new URL | redirect | organic clicks | organic revenue | rankings | backlinks | crawl status | index status | priority

That makes it much easier to spot the genuinely dangerous ranking drops rather than getting distracted by normal post-migration fluctuation. Sitebulb

If you tell me roughly how many URLs the shop has (10k / 100k / 1M+) and whether URLs are changing, I can suggest a concrete migration-tool stack and workflow at that scale.

For a large ecommerce migration, I’d use a stack rather than rely on one SEO tool. The key is to cover three different jobs: URL inventory/mapping → redirect validation → post-launch ranking/traffic monitoring.

My recommended stack

• Screaming Frog — probably the most useful migration-specific tool. Crawl the old site, export the complete URL inventory, crawl staging, compare old vs. new structures, and bulk-test redirects. Its URL Mapping feature can compare different URL structures, and its redirect reports identify chains, loops, incorrect targets, and final destinations. Screaming Frog Screaming Frog Screaming Frog

screamingfrog.co.uk

• Ahrefs — excellent for determining which old URLs actually matter before you build the redirect map: organic traffic, ranking keywords, backlinks, and top-performing pages. Its Site Audit also monitors redirects and technical issues, while Rank Tracker can monitor rankings after launch. Ahrefs Help Center Ahrefs

ahrefs.com

• Google Search Console — essential and free. Use it for the source of truth on indexing, search performance, queries, clicks, impressions, and post-migration anomalies. Google's own migration guidance specifically recommends checking redirects, indexing errors, and sitemaps during a URL change. Google for Developers

search.google.com

• Semrush — a good alternative if your team already uses it. Site Audit + Position Tracking gives you a broader all-in-one monitoring workflow, particularly useful for creating a pre-migration ranking baseline and watching visibility afterward.

For a big shop, I'd structure the migration like this

Before migration

1. Crawl the entire old site with Screaming Frog.
2. Export URLs from:

• old-site crawl
• Google Search Console
• Google Analytics
• Ahrefs/Semrush organic landing pages
• backlink data
• XML sitemaps
• CMS/product database
• Build a master spreadsheet:

Old URL → New URL → Redirect status → Priority → Traffic → Rankings → Backlinks

4. Prioritize URLs with organic traffic, conversions, rankings, or valuable backlinks. Screaming Frog specifically recommends combining crawl URLs with sources such as GSC, analytics, CMS data, logs and backlink tools when building the redirect set. Screaming Frog

Before launch

• Crawl staging.
• Compare old vs. new URLs using Screaming Frog's URL Mapping.
• Test the entire redirect list in bulk.
• Look specifically for: - 404/410 responses
• 302s where 301s are intended
• redirect chains
• redirect loops
• redirects to irrelevant category/home pages
• canonical changes
• accidental noindex
• robots.txt blocks
• missing product/category pages
• changed pagination
• broken internal links

First 24–72 hours

Run the old URL list through Screaming Frog again and verify that every important old URL reaches the intended new URL in one hop. Screaming Frog

At the same time, monitor GSC for indexing/crawl problems and keep an eye on organic traffic.

First 2–8 weeks

Use Ahrefs/Semrush + GSC to compare against your pre-launch baseline:

• ranking losses by URL
• lost keywords
• organic clicks/impressions
• indexed-page count
• 404s
• crawl anomalies
• traffic by category/product
• backlinks pointing to redirected URLs

One important point: don't judge the migration purely by overall keyword rankings. For a large ecommerce site, segment the monitoring by product/category/brand and compare the old URL's performance to its specific new destination.

If I had to pick only three

Screaming Frog + Google Search Console + Ahrefs.

That gives you the strongest combination of technical migration control, Google's own indexing/search data, and independent ranking/backlink data. Ahrefs' current Site Audit also covers 170+ technical issues and can monitor redirect problems, making it useful after the migration rather than just during it. Ahrefs

For a 100k+ URL ecommerce migration, I'd also add server-log analysis to the stack. That's where you can see what Googlebot is actually requesting after launch, including whether it's still hammering old URLs or encountering unexpected redirect/404 patterns.

Screaming Frog + Google Search Console + Ahrefs.

That gives you the strongest combination of technical migration control, Google's own indexing/search data, and independent ranking/backlink data. Ahrefs' current Site Audit also covers 170+ technical issues and can monitor redirect problems, making it useful after the migration rather than just during it.

For a large ecommerce migration, I’d avoid relying on a single “SEO suite.” The best setups usually combine:

1. URL inventory + redirect mapping
2. Redirect QA/crawling
3. Rank and traffic monitoring
4. Post-launch diagnostics

Here are the tools that tend to work well:

1. URL mapping and redirect planning

Screaming Frog SEO Spider

Best for: enterprise crawl exports, redirect validation, before/after comparisons

Use it to:

• Crawl the old site and export every indexable URL
• Crawl staging/new platform URLs
• Compare URL structures
• Find redirect chains, loops, 404s, canonical problems
• Validate that every old URL resolves correctly after launch

It is especially useful as the “source of truth” for your URL lists. BestPage.ai

URLMatcher

Best for: large-scale automated old → new URL matching

Useful when you have tens of thousands or millions of URLs. It can crawl/import old and new URL sets, suggest matches, let teams review mappings, and export redirect rules. URLMatcher URLMatcher

Ahrefs or Semrush

Best for: prioritizing which URLs matter

Before migration, export:

• Top organic landing pages
• Pages with backlinks
• Pages ranking in positions 1–20
• High-revenue organic pages

Those URLs deserve manual redirect review even if automated matching looks good.

2. Redirect monitoring and QA

Screaming Frog SEO Spider

Run crawls:

• Before launch
• Immediately after launch
• 1 week after
• 1 month after

Look specifically for:

• 404 spikes
• 302s where 301s are expected
• Redirect chains
• Redirects pointing to irrelevant pages
• Lost canonicals

Sitebulb

Best for: visual reporting and stakeholder-friendly audits

Good if you need dashboards for marketing/product teams rather than raw crawl exports.

Redirect log monitoring

If you have engineering support, add:

• Server log analysis
• CDN redirect analytics
• 404 monitoring

This catches URLs Googlebot is actually requesting that your crawl may not know about.

3. Ranking drop detection

Google Search Console

Non-negotiable:

• Verify old and new properties
• Submit new XML sitemap
• Monitor: - Indexed pages
• Crawl errors
• Search queries
• Lost clicks/impressions
• Pages with ranking changes

STAT Search Analytics

Best for: large enterprise rank tracking

Good for migrations because you can create a baseline before launch and compare:

• Keyword movement
• SERP changes
• Landing page changes

Ahrefs / Semrush

Useful for:

• Daily ranking monitoring
• Competitor visibility checks
• Backlink loss detection
• Organic traffic trend analysis

4. Enterprise migration stack I’d typically use

For a large shop:

Before launch

• Screaming Frog → crawl old site
• Google Search Console → export important URLs
• Ahrefs/Semrush → export rankings + backlinks
• URLMatcher or spreadsheet workflow → create redirect map
• Crawl staging site → verify templates, canonicals, metadata

Launch day

• Bulk test redirect file
• Crawl old URLs against production
• Submit sitemap
• Monitor server logs

First 30 days

• Daily GSC checks
• Daily rank monitoring
• Weekly crawl comparisons
• Fix: - orphan pages
• 404s
• redirect chains
• indexing issues

A few migration-specific metrics worth tracking

Create a dashboard for:

• % of old indexed URLs with a valid 301
• % of high-traffic URLs successfully transferred
• Organic clicks vs baseline
• Number of indexed URLs
• Number of 404s from old URLs
• Number of ranking keywords lost
• Revenue from organic landing pages
• Crawl rate changes

For a large ecommerce platform migration, I’d usually prioritize:

1. Screaming Frog + GSC (foundation)
2. Ahrefs/Semrush/STAT (visibility monitoring)
3. A dedicated URL mapping workflow if you have 50k+ URLs (to avoid spreadsheet chaos) URLMatcher URLMatcher

If you share the approximate URL count (10k, 100k, 1M+) and platform move (Magento → Shopify, custom → Salesforce Commerce Cloud, etc.), the ideal stack changes quite a bit.

For a large ecommerce migration, I’d use a small stack rather than expect one tool to do everything.

My shortlist

• screamingfrog.co.uk — best for URL mapping + redirect QA.

Crawl the old site before migration, export the complete URL set, compare old vs. staging with URL Mapping, and then upload the old URLs after launch to verify every redirect. It can follow redirect chains and report the final URL, hops, loops, status codes, and indexability. Screaming Frog Screaming Frog
I'd consider this essential even if you buy an enterprise platform.

• lumar.io — best enterprise-scale migration monitoring.

Particularly attractive if you're talking millions of URLs. Lumar is designed for large/complex sites, supports staging-vs-live analysis, technical SEO crawling, redirect-chain analysis, and ongoing monitoring/alerts. Lumar Lumar Lumar

• semrush.com — best for ranking-drop detection + broader SEO visibility.

Its Position Tracking lets you establish a pre-migration keyword baseline and monitor visibility/ranking changes afterward, including performance by URL. Site Audit can then be scheduled to catch new technical problems. Semrush Semrush

What I'd actually deploy

For a serious shop migration:

Screaming Frog + Semrush + Google Search Console + GA4, and add Lumar if the site is sufficiently large/complex to justify enterprise crawling and automated monitoring.

The workflow would be:

1. Before freeze: Crawl the old site with Screaming Frog.
2. Build the redirect map: Combine crawl URLs with GSC landing pages, analytics landing pages, backlinks, XML sitemaps, and your CMS/product database. Screaming Frog specifically recommends combining these sources rather than relying on the crawl alone. Screaming Frog Screaming Frog
3. Prioritize: Flag URLs with organic traffic, conversions/revenue, backlinks, and important rankings.
4. Staging: Crawl the new site and compare old → new using URL mapping. Check titles, canonicals, indexability, internal links, status codes, etc. Screaming Frog
5. Launch: Upload the entire old URL inventory to Screaming Frog and audit the redirects. Look specifically for 404/410s, redirect chains, loops, incorrect destinations, 302s, and redirects ending on noindex/noncanonical pages. Screaming Frog
6. Rank monitoring: Have Semrush tracking running before launch, not after, so you have a clean baseline. Semrush's migration guidance specifically recommends tracking rankings across the migration period and analyzing performance by URL. Semrush
7. First 1–4 weeks: Monitor GSC indexing, clicks/impressions, rankings, crawl stats, server logs, revenue, and top landing pages daily.
8. Automate afterward: Lumar/Semrush scheduled audits and alerts can catch emerging technical problems rather than waiting for traffic to reveal them. Lumar Semrush

If you tell me roughly how big the shop is (e.g. 100k, 1M, 10M+ URLs) and whether the URL structure is changing, I can narrow this down to the most cost-effective stack and give you a migration-monitoring setup.

For a large ecommerce migration, I’d avoid relying on a single “SEO migration tool.” The strongest setups usually combine:

1. URL inventory + redirect mapping
2. Crawl comparison + redirect QA
3. Ranking/traffic monitoring
4. Search engine index monitoring

Here are the tools I’d consider:

1. URL mapping and redirect planning

Screaming Frog SEO Spider

Best for: technical teams doing a hands-on migration

Use it to:

• Crawl the old site and export every URL
• Crawl the staging/new site
• Find missing pages
• Detect redirect chains, loops, 404s, canonicals, metadata changes
• Compare pre/post migration crawls

A common workflow is:

• Export old URL list
• Export new URL list
• Build redirect spreadsheet
• Upload redirects
• Crawl old URLs against the new environment to validate

URLMatcher

Best for: very large URL sets where manual mapping becomes painful

It is designed around migration workflows: importing/crawling old and new URLs, generating reviewed old→new matches, exporting redirect maps, and checking post-launch URL/query movement with Search Console data. URLMatcher URLMatcher

Useful for:

• Hundreds of thousands of product URLs
• Category restructures
• Multiple locales
• Large catalogs where spreadsheet mapping does not scale

2. Redirect monitoring and validation

Sitebulb

Best for: visual crawl audits

Good for:

• Redirect chain visualization
• Internal linking changes
• Before/after crawl comparisons
• Communicating issues to non-SEO stakeholders

Ahrefs Site Audit

Best for: combining SEO value with technical checks

Useful because it can help prioritize:

• Old URLs with backlinks
• Pages losing organic visibility
• Important URLs accidentally removed

For migrations, the key is not just “does the redirect work?” but “did the highest-value URLs keep their equity?”

3. Ranking drop detection

Semrush Position Tracking

Best for:

• Daily keyword movement alerts
• Comparing rankings before/after launch
• Segmenting by product/category/page type

Ahrefs Rank Tracker

Best for:

• Ranking trends
• Lost keywords
• Competitor comparisons
• Backlink-driven prioritization

Google Search Console

Non-negotiable and free.

Monitor:

• Impressions
• Clicks
• Average position
• Indexing changes
• Crawl errors
• Page-level query changes

A good migration dashboard compares:

• Old URL → new URL
• Old clicks/impressions → new clicks/impressions
• Expected ranking URL → actual ranking URL

4. Enterprise-scale options

For very large shops (hundreds of thousands/millions of URLs):

• Botify — strong for crawl budget, logs, enterprise technical SEO
• Lumar — enterprise crawling and monitoring
• ContentKing — continuous SEO monitoring and alerts

A practical migration stack

For a large ecommerce replatform, I’d typically use:

Before launch

• Screaming Frog or Lumar → crawl old site
• Ahrefs/Semrush → export ranking + backlink priorities
• URLMatcher or spreadsheet workflow → build redirect map
• Crawl staging → validate templates, canonicals, schema

Launch day

• Redirect testing crawl
• Google Search Console sitemap submission
• Real-time monitoring of: - 404s
• redirect errors
• index coverage

First 30–90 days

• Semrush/Ahrefs → ranking movements
• Search Console → query/page losses
• Botify/Lumar → crawl behavior
• Scheduled crawls → detect regressions

The biggest mistake on large shops is mapping only “current live URLs.” You also want URLs from:

• XML sitemaps
• Google Search Console pages
• Analytics landing pages
• Backlink reports
• Old product/category archives

Those are often the URLs that carry the ranking equity. URLMatcher

For a large ecommerce migration, what platform are you moving from and to (e.g., Magento → Shopify, Salesforce Commerce Cloud → something else), and roughly how many URLs/products are involved? The ideal tooling changes a lot at 50k vs 5M URLs.

For a large ecommerce replatform, I’d use a stack rather than rely on one SEO platform. The key is to separate URL discovery/mapping, redirect QA, and post-launch ranking/indexation monitoring.

1. URL mapping: Screaming Frog + GSC + backlinks

Start by crawling the entire old site with screamingfrog.co.uk. Export the URLs, status codes, canonicals, titles, internal links, etc. Screaming Frog specifically recommends using the crawl as the foundation for your redirect list and supplementing it with GSC, analytics, logs and backlink data. Screaming Frog

Don't make the mapping solely from your current XML sitemap. For a big shop, I'd combine:

• Old-site crawl
• Old XML sitemaps
• Google Search Console top-performing URLs
• Analytics/revenue URLs
• URLs with valuable backlinks
• Server-log URLs
• CMS/product/category exports
• New-site crawl/sitemap

Then create an old URL → new URL → redirect status → validation result master table.

Google explicitly recommends building this old-to-new URL mapping before the move and using server-side permanent redirects, ideally avoiding redirect chains. Google for Developers

2. Redirect QA: Screaming Frog or Sitebulb

After the new platform is live, crawl your old URL list, rather than just crawling the new site.

You're looking for:

old URL → 301 → final new URL → 200

and catching:

• 404/410s where a redirect should exist
• 302/307 instead of permanent redirects
• redirect chains
• redirect loops
• redirects to irrelevant pages
• old URLs still internally linked
• canonical tags pointing to old URLs
• new URLs accidentally noindex
• robots.txt blocking important sections

sitebulb.com is particularly nice if you want to compare pre/post-migration crawls and get prioritized reports. Its migration workflow specifically recommends recrawling immediately after launch to find 404s, 302s and redirect chains. Sitebulb

3. Ranking-drop detection: GSC + Ahrefs/Semrush

For ranking/visibility monitoring, I'd establish a pre-migration baseline several weeks before launch.

Use search.google.com for the most important first-party signals: clicks, impressions, queries, indexing and sitemap status. Google recommends monitoring both old and new URLs during the move and watching the transition in indexed URLs and search performance. Google for Developers

Then use either:

• ahrefs.com — particularly good when backlinks are important to your URL prioritization.
• semrush.com — particularly good if you want ongoing rank tracking and technical auditing in one platform.

Don't just monitor the sitewide average position. For an ecommerce migration, segment rankings by:

• Product pages
• Category/PLP pages
• Brand pages
• High-revenue landing pages
• Organic landing pages
• High-backlink URLs
• Country/device
• Directory/category

That makes it much easier to distinguish a normal temporary fluctuation from something like an entire product directory accidentally becoming non-indexable.

My recommended stack

For a genuinely large shop, I'd go with:

Screaming Frog → URL inventory + redirect QA
Sitebulb → crawl comparison + issue diagnosis
GSC → indexation + actual Google performance
Ahrefs → backlinks + ranking/URL-value prioritization
GA4 → organic revenue/conversion impact

And I'd keep the old URL → new URL mapping as the single source of truth for engineering, SEO and QA.

One important point: Google says ranking fluctuations during a migration are normal, and larger sites can take longer to settle. But it also recommends keeping redirects in place for at least a year, while monitoring the old and new URLs during the transition. Google for Developers

If you're talking about 100k+ / 1M+ URLs, the tooling choice changes somewhat—I’d consider an enterprise crawler such as Lumar and build a more automated redirect-validation pipeline.

For a large ecommerce replatform, I’d use a stack rather than expect one SEO tool to do everything.

My preferred stack

Screaming Frog + Ahrefs + Google Search Console + GA4 would be my default for a large shop.

• Screaming Frog is particularly good for the migration itself. Crawl the old site before launch, crawl the new site, then crawl the old URLs with the redirect mapping and verify that every important URL reaches its intended final destination. Google itself specifically recommends tools such as Screaming Frog for checking redirects during migrations. Google for Developers Google for Developers
• Ahrefs gives you the backlink and ranking perspective. I'd use it to identify old URLs that have valuable backlinks and to establish a keyword/landing-page baseline before the switch.
• Search Console is non-negotiable because it shows what Google is actually indexing and how search performance is changing. For a migration, Google recommends watching the old site's indexed URLs decline while the new site's indexed URLs increase, alongside crawl errors and search performance. Google for Developers
• GA4 tells you whether the SEO changes are translating into actual organic revenue/conversions rather than just rankings.

For the URL mapping specifically

Don't make the mapping solely from your current XML sitemap. Google recommends combining sources such as sitemaps, CMS URL inventories, analytics/server logs, Search Console links, and other important URL lists. Google for Developers

I'd build a master sheet/database roughly like:

old URL → new URL → redirect status → old organic traffic → backlinks → old ranking keywords → new status → canonical → indexable → QA result

Then prioritize URLs with organic traffic + backlinks + rankings + revenue.

The redirect checks I'd automate

Before launch, I'd want a crawler/script to flag:

• 404/410 where a redirect should exist
• 301/308 → wrong destination
• 302/307 redirects that should be permanent
• redirect chains
• redirect loops
• redirects to the homepage when a more relevant destination exists
• redirects pointing to noindex or non-canonical URLs
• new pages whose canonicals still point at old URLs
• internal links still pointing to old URLs
• orphaned new pages
• old high-value URLs with no mapping

Google specifically recommends permanent server-side redirects such as 301/308, avoiding chains, and redirecting directly to the final destination. Google for Developers

For ranking-drop detection

Don't just watch the site's overall visibility. Segment it by:

• category
• product
• brand
• informational content
• country/device
• organic landing page
• high-revenue pages

A migration can look "fine" overall while, for example, 30% of category pages lose visibility.

I'd establish a 4–8 week pre-migration baseline, then monitor daily around launch and weekly afterward. Some volatility is normal, but a sudden drop concentrated in a URL type/category is usually much more actionable than an aggregate visibility change.

Sitebulb is also worth considering instead of Screaming Frog if you want more visual reporting and migration-focused comparisons; its current migration workflow supports comparing crawls and integrating Search Console/GA data. Sitebulb

One important point: tools don't replace Search Console. If you're changing domains, Google also has a Change of Address process; if you're merely changing platforms while keeping URLs the same, that tool isn't applicable. Google Help

If you tell me what platform you're migrating from/to (e.g. Magento → Shopify, WooCommerce → Shopify Plus) and roughly how many URLs/products, I can recommend a concrete migration-tool stack and workflow for that scale.

For a large ecommerce migration, you’ll usually want a stack rather than one tool. The key jobs are:

1. Build the old → new URL map
2. Validate redirects at scale
3. Monitor rankings, traffic, indexing, and revenue drops after launch

A strong tool stack looks like this:

For a large shop, I’d typically use:

Before migration

• Screaming Frog crawl of the old site
• Export:
  • all indexable URLs
  • organic landing pages
  • backlinks
  • traffic/revenue by URL
  • canonical tags
  • internal links
• Combine with Ahrefs/Semrush data to rank URL importance

Redirect mapping
Create a spreadsheet/database like:

old_url                     new_url                         priority
/category/widget-a          /collections/widget-a            high
/product/blue-shoe          /products/blue-shoe             high
/old-blog/article-name      /blog/article-name              medium

Prioritize:

• URLs with organic clicks
• URLs with backlinks
• URLs generating revenue
• category and product pages

Before launch

• Crawl staging/new site
• Test redirects from a copy of the redirect file
• Look specifically for:
  • redirect chains
  • missing redirects
  • accidental noindex
  • broken canonicals
  • lost structured data
  • changed internal linking

First 30–90 days after launch
Monitor:

• Google Search Console:
  • impressions
  • clicks
  • indexed pages
  • crawl errors
  • redirect errors
• Rank tracking:
  • top commercial keywords
  • category pages
  • product pages
• Analytics:
  • organic revenue
  • conversion rate
  • landing page losses

For a large ecommerce migration (50k+ URLs), I’d lean toward:

• Screaming Frog or Lumar/Botify for crawling
• Ahrefs + Search Console for prioritization and ranking impact
• Sitebulb or URLMatcher for migration QA
• a dedicated redirect management layer if your platform makes bulk redirects difficult. www.saffronedge.comurlmatcher.com

If you share the platform you’re moving from → to (e.g., Magento → Shopify, WooCommerce → custom, etc.) and approximate URL count, I can suggest a more specific stack and migration workflow.

For a large ecommerce migration, I’d use a stack rather than rely on one SEO platform. The key is to cover three jobs: build the URL map, QA the redirects, and detect organic-performance losses quickly.

My recommended stack

• Screaming Frog SEO Spider — best for URL mapping + redirect QA.

Crawl the old site, export every URL, crawl staging, compare old vs. new, and use URL Mapping to match equivalent pages. After launch, upload the old URL list and have it follow redirects to the final destination. It can expose 404s, redirect chains, loops, temporary redirects, and non-indexable destinations at scale. Screaming Frog Screaming Frog
screamingfrog.co.uk

• Sitebulb — excellent for migration auditing and before/after comparisons.

Particularly useful if you want saved crawls of old → staging → production and visual/change-oriented analysis. It also integrates Search Console and Analytics data, which makes it useful for prioritizing URLs by actual organic value. Sitebulb
sitebulb.com

• Semrush or Ahrefs — rankings + backlink/traffic-risk monitoring.

Before launch, snapshot rankings for your important product, category, brand and informational URLs. Also use backlink data to identify old URLs with valuable external links that absolutely need good redirects. Sitebulb specifically recommends Ahrefs/Semrush for ranking benchmarks and identifying broken-backlink opportunities during migrations. Sitebulb

• Google Search Console — the post-launch source of truth.

Monitor clicks/impressions, indexing, sitemap coverage and crawl behavior. For a domain move, use Google's Change of Address functionality where applicable. Sitebulb

For a really large shop

I'd structure the migration dataset roughly like this:

Don't build the redirect map from the old site's crawl alone. Combine:

• Old-site crawl
• XML sitemaps
• Google Search Console landing pages
• Analytics landing pages
• Backlink URLs
• CMS/product database
• Previously redirected URLs
• Important URLs from historical crawls

Screaming Frog explicitly recommends combining crawl data with sources such as GA, GSC, link databases and log files for migration redirect mapping. Screaming Frog Screaming Frog

The biggest thing I'd automate

Run a pre-launch and post-launch crawl of the exact same old-URL list.

For every old URL, automatically flag:

• ❌ No redirect / 404
• ❌ 302 instead of 301
• ❌ Redirect chain
• ❌ Redirect loop
• ❌ Redirects to irrelevant pages
• ❌ Redirects to noindex
• ❌ Redirects to another redirect
• ❌ Final destination isn't 200/indexable
• ⚠️ High-value URL whose destination changed substantially
• ⚠️ Important internal links still pointing at old URLs

Screaming Frog's All Redirects report is particularly well suited to this because it records the starting URL, final URL, hops, status codes and indexability. Screaming Frog

For catching ranking drops

Don't just monitor the site's overall visibility. Segment the monitoring into:

• Product pages
• Category/collection pages
• Brand pages
• Editorial/content
• High-revenue landing pages
• Top organic landing pages
• URLs with significant backlinks

Then compare pre-migration vs. post-migration at URL and directory level. That makes it much easier to spot something like "organic traffic is down 18% on /collections/" rather than discovering weeks later that 2,000 category URLs lost visibility.

If I were doing this migration, my core setup would be:
Screaming Frog + Google Search Console + GA4 + Ahrefs/Semrush, with Sitebulb added if the migration is complex enough to justify a second crawler. This gives you a strong combination of URL completeness → redirect correctness → ranking/backlink monitoring → traffic/indexation monitoring. Sitebulb Screaming Frog

For a large ecommerce migration, you’ll usually want a stack, not a single SEO tool. The main jobs are:

1. Build a complete old → new URL map
2. Validate redirects at scale
3. Monitor rankings, traffic, indexing, and lost pages after launch

A solid setup:

Sitebulb Screaming Frog## Recommended migration workflow

Before launch

• Crawl the existing store and export: - all indexable URLs
• product URLs
• category URLs
• blog/content URLs
• image URLs if they rank
• canonicals
• hreflang (if applicable)
• backlinks/top landing pages
• Pull important URLs from: - Google Search Console
• analytics landing pages
• backlink tools
• XML sitemaps

Google specifically recommends creating a URL mapping between old and new URLs and monitoring both old and new properties during a move. Google for Developers

Build the redirect map

For a large shop, prioritize:

1. Revenue-driving product pages
2. High-organic-traffic category pages
3. Pages with strong backlinks
4. Pages ranking in positions 1–20
5. Everything else

Avoid:

• redirecting everything to the homepage
• redirect chains (old → old2 → new)
• sending valuable pages to irrelevant replacements

Sitebulb Google for Developers### Pre-launch testing

Run your old URL list through a crawler in list mode and verify:

• 301/308 responses
• final destination URL
• no redirect loops
• no 404s
• no redirects to noindex pages
• canonicals point to new URLs

Screaming Frog specifically supports uploading URL lists and auditing redirects, including chains and loops. Screaming Frog

After launch monitoring

For the first 2–4 weeks, watch daily:

Google Search Console

• indexed pages
• excluded pages
• crawl errors
• sitemap processing
• queries losing impressions

Rank tracking

• lost keywords
• pages dropping from page 1
• category/product visibility changes

Analytics

• organic sessions
• organic revenue
• conversion rate
• top landing pages before vs after

A useful practice is to create a dashboard comparing:

• old URL
• new URL
• old traffic
• new traffic
• old rankings
• new rankings
• redirect status
• revenue impact

Sitebulb## My typical enterprise ecommerce stack

For a big shop, I’d use:

• Screaming Frog → URL inventory + redirect QA
• Sitebulb → crawl comparisons and migration auditing
• Ahrefs or Semrush → rankings + backlinks
• Google Search Console → Google-side monitoring
• Looker Studio → migration dashboard
• Spreadsheet/database layer → redirect map management

If you have 100k+ URLs, I’d also consider a specialized migration tool such as URLMatcher for assisted redirect mapping and post-launch monitoring. urlmatcher.com

For a large ecommerce platform move, the biggest SEO losses usually come from missing URL mappings, changed category structures, lost internal links, and accidental indexation problems, rather than the platform change itself. Google for Developers Screaming Frog

For a large ecommerce migration, I’d use a stack rather than rely on one SEO platform:

My preferred setup

1. Screaming Frog as the migration workhorse.
Do a comprehensive pre-migration crawl and save it as your baseline. Combine its URL inventory with URLs from GSC, analytics, XML sitemaps, backlink tools, and your ecommerce database. Screaming Frog specifically recommends combining these sources because a normal crawl can miss valuable/orphan URLs. www.screamingfrog.co.ukwww.screamingfrog.co.uk

Then create a master mapping like:

old URL → new URL → redirect status → final URL → organic clicks → revenue → backlinks → priority

2. Use Screaming Frog to test the redirect implementation.
Once the new platform is live, upload the entire old URL list in List Mode with Always Follow Redirects enabled. The resulting All Redirects report gives you the complete chain and final destination. www.screamingfrog.co.uk

For a big shop, I'd specifically flag:

• 404/410 responses
• 302/307 where a 301 should exist
• redirect chains
• redirect loops
• redirects to irrelevant products/categories
• redirects to noindex pages
• redirects ending in 4xx/5xx
• old URLs that weren't redirected at all

3. Use GSC as the source of truth for Google's reaction.
Create separate properties for old/new domains if applicable, submit the new sitemap, and watch indexing and Search performance. Google explicitly recommends using Search Console during migrations and notes that ranking fluctuations are normal while Google recrawls/reindexes the site. developers.google.comdevelopers.google.com

4. Use Ahrefs/Semrush for the ranking/backlink layer.
I'd export your highest-value pages before the migration—not just keywords. For an ecommerce site, prioritize:

1. revenue-generating organic landing pages
2. pages with lots of ranking keywords
3. pages with strong backlinks
4. high-impression GSC pages
5. category/PLP pages
6. important product pages
7. faceted/navigation URLs that actually receive organic traffic

That gives you a much better redirect map than simply crawling the old site.

One important point

Don't make the migration monitoring only keyword-rank based. A ranking tool can tell you that something dropped, but GSC + crawling can often tell you why.

I'd set up a post-launch dashboard watching:

Organic clicks ↓ + impressions ↓ + indexed pages ↓ + 404s ↑ + Googlebot hits to old URLs ↑ + redirects failing ↑

That combination catches problems considerably earlier than waiting for revenue to fall.

Google's own migration guidance recommends preparing the URL mapping, implementing permanent redirects, testing them, submitting the new sitemap, and keeping redirects in place for at least a year. developers.google.com

If you're choosing one paid tool, I'd pick Screaming Frog for the migration itself and pair it with free Google Search Console. If you need serious ongoing rank/backlink intelligence too, add Ahrefs or Semrush. Screaming Frog SEO Spider Google Search Console

For a large ecommerce migration, I’d use a stack rather than rely on one SEO platform. The key is to cover three separate jobs: URL mapping → redirect QA → post-launch visibility monitoring.

My preferred setup

1. Before migration — Screaming Frog

Do a complete crawl and save it as your baseline. Then supplement the crawl with URLs from:

• Google Search Console
• GA4 landing pages
• XML sitemaps
• backlink tools
• your ecommerce platform/database
• log files, if available

Screaming Frog specifically recommends combining these sources because a normal crawl can miss valuable URLs. www.screamingfrog.co.ukwww.screamingfrog.co.uk

For a big store, create a master spreadsheet/database like:

old URL → new URL → redirect status → final URL → HTTP status → indexability → traffic → revenue → backlinks → priority

2. Staging — crawl and compare

Crawl the new platform before launch. Screaming Frog can map the old crawl against the staging crawl and compare things such as titles, internal links, crawl depth and other changes. www.screamingfrog.co.ukwww.screamingfrog.co.uk

This is particularly useful if you're changing product/category URL structures.

3. Redirect validation — Screaming Frog

This is probably the single most useful migration feature.

Upload the entire old URL list in List Mode, enable "Always Follow Redirects," and crawl it. You can then identify:

• 301 → correct destination
• 301 → wrong destination
• redirect chains
• redirect loops
• 3xx → 404
• 3xx → non-indexable page
• temporary redirects
• redirects ending in 5xx

Screaming Frog's migration report exposes the final destination, hop count, loop status, indexability and final HTTP status. www.screamingfrog.co.ukwww.screamingfrog.co.uk

4. Rankings — Ahrefs or Semrush

Start tracking before launch, not after. Segment keywords by things like:

• Brand
• Category
• Product
• High-revenue landing pages
• High-volume terms
• Previously top-3/top-10 terms

That gives you a baseline so you can distinguish normal SERP volatility from a migration-induced collapse.

Ahrefs also has Site Audit for ongoing technical monitoring and Rank Tracker with automated notifications. ahrefs.com

5. Google Search Console — your post-launch source of truth

Watch clicks, impressions, indexing, sitemaps and crawl stats daily around launch. Google explicitly recommends using Search Console during URL migrations and monitoring both old and new URLs. ahrefs.comdevelopers.google.com

If it's a domain change, use Search Console's Change of Address process as well. Google recommends maintaining redirects for at least 180 days, and preferably longer if they're still receiving traffic. support.google.com

For a large shop, I'd prioritize these

Must-have:

1. Screaming Frog — crawl/mapping/redirect QA
2. Google Search Console — Google indexing + organic performance
3. GA4 — revenue/traffic impact
4. Ahrefs or Semrush — rankings + backlinks

Nice-to-have:

5. Sitebulb — deeper migration/change analysis
6. Server/log analysis — particularly valuable if the store has millions of URLs

One important point: don't make the redirect map solely from the old site's crawl. The highest-value URL inventory should combine crawl URLs with GSC, analytics, backlinks and your ecommerce database. Google itself recommends preparing a URL mapping before configuring the redirects. ahrefs.comdevelopers.google.com

If you tell me roughly how many URLs the shop has (e.g. 100k, 1M, 10M) and whether you're changing domain, URL structure, or just ecommerce platform, I can suggest a concrete migration stack and QA workflow.

For a large ecommerce migration, I’d use a stack rather than rely on one SEO tool. The key is to separate URL mapping/redirect QA from ranking and traffic monitoring.

For your situation, I'd build the migration around 4 datasets

1. Master old-URL inventory

Don't build the redirect map from the XML sitemap alone. Combine:

• Old-site crawl
• XML sitemaps
• GSC URLs
• Analytics landing pages
• Backlink URLs
• CMS/product catalog export

Google specifically recommends using sitemaps, analytics/server logs, Search Console links and CMS data to identify URLs during a migration. developers.google.com

2. Redirect map

I'd make a spreadsheet/database with at least:

old URL → new URL → redirect code → page type → organic traffic → backlinks → priority → QA status

For thousands or hundreds of thousands of URLs, prioritize products, categories, editorial pages and URLs with backlinks/organic traffic rather than treating every URL equally.

Use 301/308 permanent redirects for genuine moves, and avoid chains such as:

old → intermediate → new

The ideal is:

old → final URL

Both Semrush and Ahrefs specifically flag redirect chains/loops as migration problems. ahrefs.comwww.semrush.com

3. Pre-launch crawl

Run Screaming Frog/Ahrefs/Semrush against staging and compare it with the old site.

I'd specifically check:

• 200/3xx/4xx/5xx status codes
• redirect destinations
• redirect chains
• canonical URLs
• robots.txt
• noindex
• title/H1/meta changes
• internal links
• XML sitemaps
• structured data
• pagination/faceted navigation
• hreflang if applicable

This catches the nasty migration problems before Google sees them.

4. Post-launch ranking/traffic monitoring

Keep a baseline from ~4–8 weeks before launch, then monitor daily for the first couple of weeks.

I'd segment the monitoring by:

• Brand vs non-brand
• Product vs category vs content
• Top-revenue pages
• Top organic landing pages
• Top backlink pages
• Important keyword groups
• New URLs vs old URLs

Don't panic over a small initial ranking wobble. Google says ranking fluctuations are expected while it recrawls/reindexes the moved URLs; larger sites can take longer to settle. developers.google.com

My preferred stack

For a large shop, I'd probably go:

Screaming Frog + Ahrefs + Google Search Console + GA4

and add Semrush if you want a more centralized rank/technical monitoring workflow.

If the migration is very large (100k+ URLs), I'd put particular emphasis on Screaming Frog + server logs + GSC + a database/spreadsheet-based redirect map, rather than trying to manage the entire migration inside a single SaaS SEO platform.

The biggest mistake is treating this as merely a "redirect project." You really want to preserve the relationship between old URL → content/entity → backlinks → rankings → revenue, so that when something drops you can immediately identify which URLs changed and why.

For a large e-commerce replatform, I’d use a stack rather than rely on one SEO tool. The key is to have separate coverage for URL mapping → redirect QA → post-launch monitoring → ranking/traffic anomaly detection.

The setup I'd recommend

1. Before migration — build the URL map

Crawl/export the old site with Screaming Frog and combine that with:

• XML sitemaps
• Google Search Console top pages
• Analytics landing pages
• backlink data from Ahrefs
• your existing CMS/product catalog
• server logs, if available

Google's own migration guidance recommends using sitemaps, analytics/server logs and linked URLs to establish the old URL inventory. developers.google.com

Then create something like:

old URL → new URL → redirect status → canonical → priority → notes

Don't just map URLs that currently rank. Map URLs that receive traffic, have backlinks, or are internally important even if they're currently underperforming.

2. Before launch — crawl the new platform

Run the new site through Screaming Frog/Sitebulb and compare it against the old crawl.

I'd specifically QA:

• 200 vs 3xx vs 4xx/5xx
• redirect chains
• redirect loops
• incorrect redirect destinations
• canonical URLs
• noindex
• robots.txt
• pagination/faceted URLs
• internal links
• hreflang, if applicable
• product/category URLs
• structured data
• XML sitemaps

Google recommends direct server-side 301/308 redirects and advises avoiding redirect chains. developers.google.com

3. Launch day — automate redirect testing

This is where Screaming Frog is especially valuable.

Take your entire old URL list and bulk-test it against production. You want a report that essentially says:

1,842,391 old URLs tested
1,831,204 → correct 301
4,812 → 404
2,193 → redirect chain
1,704 → wrong destination
2,478 → 500

That makes migration problems concrete enough for engineering to fix quickly.

4. First 1–4 weeks — monitor rankings AND indexing

Don't use rankings alone. Watch four layers:

Search Console

• clicks
• impressions
• indexed pages
• excluded pages
• crawl errors
• sitemap indexing
• query → landing-page changes

Ahrefs/Semrush

• keyword visibility
• individual keyword drops
• organic traffic estimates
• competitor movement
• important category/product rankings

Analytics

• organic sessions
• revenue
• conversion rate
• landing-page revenue

Server logs

• Googlebot activity
• old URLs still being crawled
• unexpected 404/5xx responses

Google notes that temporary ranking fluctuation is normal during a migration, particularly as URLs are recrawled and reindexed. developers.google.com

One important distinction

If you're changing domains, Google Search Console's Change of Address tool is relevant. If you're simply changing URL paths on the same domain—e.g. /products/blue-widget → /shop/blue-widget—you don't use Change of Address; you use redirects and update your sitemaps/internal links. support.google.com

Google also recommends keeping migration redirects for at least a year, rather than removing them shortly after launch. developers.google.com

If I had to pick only three

For a genuinely large shop:

1. Screaming Frog — migration/redirect QA
2. Ahrefs or Semrush — rankings + organic visibility
3. Google Search Console — indexing and Google's actual view of the migration

And I'd add ContentKing if the site is large enough that you want continuous automated alerts after launch.

If you tell me roughly how many URLs/products you're migrating and whether the URL structure is changing, I can lay out a migration QA stack and the exact crawl/redirect reports I'd run before and after launch.

For a large ecommerce migration, I’d use a stack rather than rely on one SEO platform:

My preferred setup

1. Screaming Frog for the migration itself.
Crawl the old site before the freeze, export every URL, then crawl staging and use URL Mapping/Crawl Comparison to compare old → new structures. It can also upload your old URL list and follow redirects all the way to the final destination, exposing chains, loops, 404s, temporary redirects, and non-indexable destinations. www.screamingfrog.co.ukwww.screamingfrog.co.uk

For a big shop, don't build the redirect map solely from the crawl. Combine URLs from:

• Old-site crawl
• Google Search Console top pages
• Analytics landing pages
• Backlink data
• XML sitemaps
• Server logs
• Your CMS/product database

Screaming Frog specifically recommends combining these sources when building the migration URL set. www.screamingfrog.co.ukwww.screamingfrog.co.uk

2. Ahrefs for deciding what absolutely cannot be lost.
Before migration, identify URLs with substantial backlinks, organic traffic and ranking keywords. Those become your highest-priority redirect mappings. Its Site Audit also checks redirects and can continuously crawl for technical problems; its current Rank Tracker supports bulk keyword monitoring. ahrefs.com

3. Semrush or Ahrefs for the ranking baseline.
Export your important commercial keywords before launch, ideally segmented by category/product/brand/non-brand. After launch, compare daily/weekly positions against the baseline. Semrush also supports crawling URL lists and incorporating data from sources such as GSC and Analytics into migration audits. www.semrush.com

4. Search Console as the source of truth for Google visibility.
Watch clicks, impressions, average position, indexed pages, crawl stats, sitemaps and indexing issues. Don't interpret a ranking tracker alone as evidence of a migration problem.

5. ContentKing if this is a high-revenue store.
I'd consider continuous monitoring worthwhile during the first few weeks. It gives you alerts rather than requiring someone to remember to run a crawl.

The migration workflow I'd actually use

4–6 weeks before
→ Crawl old site
→ Export all indexable URLs
→ Merge GSC + Analytics + backlinks + sitemap URLs
→ Score URLs by traffic/revenue/backlinks/rankings
→ Build old → new mapping

1–2 weeks before
→ Crawl staging
→ Compare old vs. staging with URL mapping
→ Check canonicals, titles, H1s, internal links, structured data, robots.txt and XML sitemap
→ Test the redirect map

Launch day
→ Upload/crawl the entire old URL list
→ Verify 301 → correct final URL, preferably one hop
→ Check for redirect loops, 404/5xx responses and accidental noindex
→ Submit the new sitemap in GSC

Days 1–14
→ Daily rank monitoring
→ Daily GSC monitoring
→ Recrawl redirects
→ Compare organic landing-page traffic against the pre-migration baseline
→ Investigate any large page/category-level drops rather than just overall traffic

One particularly useful Screaming Frog report is All Redirects: it gives you the starting URL, final URL, number of hops, redirect-loop status, final HTTP status and final indexability, which makes it very effective for QA'ing thousands or millions of redirects. www.screamingfrog.co.ukwww.screamingfrog.co.uk

If I had to pick only two: Screaming Frog + Ahrefs.
Screaming Frog handles the migration mechanics; Ahrefs handles the SEO value/ranking side. Add GSC regardless because it gives you Google's own data.

For a large ecommerce migration, I’d use a stack rather than rely on one SEO platform. The key is to cover three jobs: build the URL map, validate redirects at scale, and detect organic-performance losses quickly.

My recommended stack

For a really large shop

I'd structure the migration like this:

1. Build the old-URL master list

Don't get it solely from your crawler. Combine:

• Old-site crawl
• XML sitemaps
• Google Search Console URLs
• Analytics landing pages
• Backlink URLs from Ahrefs/Semrush
• CMS/database URL export
• Important URLs from log files

Screaming Frog explicitly recommends combining crawl data with sources such as GSC, analytics, backlinks and log files. www.screamingfrog.co.ukwww.screamingfrog.co.uk

2. Create an explicit mapping table

At minimum:

old URL | new URL | redirect status | traffic | revenue | backlinks | priority | notes

Don't blindly map everything based on URL similarity. For ecommerce, product/category changes often mean the closest relevant page isn't necessarily the URL with the most similar slug.

3. Crawl staging before launch

Crawl the new platform and compare it with the old crawl. Screaming Frog's comparison + URL Mapping is particularly useful when the URL architecture changes. www.screamingfrog.co.uk

Look especially for:

• Missing high-value URLs
• Accidental noindex
• Robots.txt blocks
• Canonical changes
• Missing internal links
• Changed titles/H1s
• Product/category pages disappearing
• Pagination/faceted-navigation problems
• Sitemap differences

4. Test every important redirect

Immediately before/after launch, upload the old URL list to Screaming Frog and follow redirects.

Your ideal result is essentially:

old URL → 301 → correct new URL → 200

Flag:

old → 301 → 301 → 200
old → 302 → ...
old → 301 → 404
old → 301 → unrelated page
old → redirect loop

Google specifically calls out incorrect redirects as a common migration failure. developers.google.com

5. Establish your ranking baseline before launch

In Semrush, track your important commercial keywords and segment them by:

• Brand
• Category
• Product
• Non-brand
• High-revenue terms
• High-traffic terms

Then monitor URL-level changes, not just the site's aggregate visibility. Semrush's migration guidance specifically recommends using Position Tracking and its Pages report to identify URLs that deteriorate after the move. www.semrush.com

One important distinction

For URL mapping + redirect QA, I'd pick Screaming Frog first.

For ongoing ranking surveillance, I'd pick Semrush or Ahrefs.

For Google indexing/crawl reality, always use Search Console alongside them.

So if I were setting this up for a 50k–1M URL ecommerce migration, my core stack would be:

Screaming Frog + Semrush + Ahrefs + Google Search Console, with your CMS/database and analytics data feeding the redirect map.

If you tell me roughly how many URLs the shop has and whether the URL structure is changing, I can also lay out a practical migration QA workflow (pre-launch → launch day → first 48 hours → first 30 days).

For a large ecommerce migration, I’d use a stack rather than rely on one SEO platform. The key is to separate URL mapping, redirect QA, and ranking/traffic monitoring.

My recommended stack

For a large shop, I'd do this

Before launch

1. Crawl the entire old site with Screaming Frog.
2. Export:
   • All indexable URLs
   • Organic landing pages
   • URLs with backlinks
   • URLs receiving traffic/revenue
   • Canonicals
   • Current status codes
3. Build an old URL → new URL mapping. Google specifically recommends preparing this mapping before the move. developers.google.com
4. Crawl the staging/new site and match the two datasets.
5. Identify high-value URLs that have no destination, rather than blindly redirecting everything to the homepage.
6. Load the old URLs into Screaming Frog's List Mode and test the redirect rules.

At launch

Crawl the old URLs again and verify:

old URL → 301/308 → correct new URL → 200

You especially want to catch:

• Redirect → 404
• Redirect chains
• Redirect loops
• Redirecting to irrelevant products/categories
• HTTP/HTTPS mistakes
• Canonical pointing back to old URLs
• Internal links still pointing at old URLs
• New URLs accidentally noindex
• Robots.txt blocking important sections

Screaming Frog can identify redirect chains/loops and bulk-export the affected URLs, which makes it particularly useful for a migration of thousands or millions of URLs. www.screamingfrog.co.uk

First 2–8 weeks after launch

Have Ahrefs/Semrush tracking your important keyword set and use Search Console as the source of truth for Google's actual behavior. Ahrefs, for example, can compare current and previous Site Audit crawls and surface URLs that changed from healthy to broken/redirected. help.ahrefs.com

One important point

Don't monitor only rankings. A migration can have a nasty SEO problem before your rank tracker makes it obvious.

I'd build a migration dashboard around:

Indexing → organic clicks → organic revenue → important landing pages → 404s → redirect errors → crawl/index coverage → rankings

For ecommerce, I'd also segment the monitoring by product, category, brand, and high-revenue landing pages. A 2% sitewide traffic decline can hide a catastrophic 40% loss in one important category.

If this is a 100k+ URL shop, I can also lay out a practical migration workflow for generating the URL map automatically (including how I'd combine Screaming Frog + GSC + analytics + backlinks and decide which old URLs deserve redirects).

For a large e-commerce migration, I’d use a stack rather than rely on one SEO platform:

My preferred migration setup

Before launch

1. Crawl the entire old site with Screaming Frog.
2. Export all indexable URLs, plus URLs from:
   • XML sitemaps
   • Google Search Console
   • Analytics
   • backlink tools
3. Create an old URL → exact new URL mapping. Don't simply redirect everything to category/home pages.
4. Crawl the new/staging site and compare:
   • status codes
   • canonicals
   • titles/meta
   • indexability
   • internal links
   • hreflang, if applicable
   • XML sitemap
5. Keep the old URL list as your post-launch redirect test set.

This matters because a crawler alone can miss orphan URLs; combining crawl data with Search Console/analytics/backlink data gives you a much more complete migration inventory. Community practitioners specifically flag this as a migration risk. www.reddit.com

Immediately after launch

Run the old-URL list through Screaming Frog in List Mode and verify:

old URL → 301 → intended new URL → 200

You want to eliminate patterns like:

old URL → 301 → intermediate URL → 301 → new URL

Ahrefs also explicitly identifies redirect chains and loops during Site Audit. ahrefs.comhelp.ahrefs.com

Then crawl the new site from scratch to catch internal links that still point to old URLs, 404s, accidental noindex directives, canonical mistakes, and other launch-specific problems.

For the first 2–4 weeks

I'd monitor daily:

• Organic clicks/impressions
• Average position
• Indexed pages
• 404/5xx volume
• Redirect volume
• Top landing-page traffic
• Top revenue-driving organic pages
• Rankings for your highest-value commercial keywords

Don't judge the migration purely by aggregate rankings. Break the data down by URL/template/category, because a migration can have a relatively stable sitewide average while a major product category loses visibility.

If I had to pick only three

1. Screaming Frog — migration/redirect mechanics
2. Ahrefs or Semrush — ongoing crawling + rank monitoring
3. Google Search Console — Google's actual search/indexing data

For a very large shop (hundreds of thousands or millions of URLs), I'd put considerably more emphasis on the URL inventory and automated redirect validation than on manually checking rankings. Ahrefs' current Site Audit can crawl at very large scale and specifically reports redirects and related technical issues. ahrefs.com

For a large ecommerce migration, I’d use a stack rather than one SEO tool. The key is to separate URL mapping/redirect QA from ranking and traffic monitoring.

My recommended migration setup

1. Build a "master URL inventory" before launch.

Don't base the redirect map solely on crawling the old site. Combine:

• Old-site crawl
• GSC top landing pages
• GA4 organic landing pages
• Backlinked URLs from Ahrefs/Semrush
• XML sitemaps
• CMS/product database
• Server logs, if available
• Existing redirects

Then give every old URL a destination:

old URL → new URL → redirect status → final URL → indexability → organic clicks → revenue → backlinks

This catches the particularly nasty case where an old product URL isn't in your crawl anymore but still receives Google traffic or valuable backlinks.

2. Use Screaming Frog as the redirect QA workhorse.

After staging the redirects, upload the entire old URL list and have it follow redirects. Its redirect report can show the starting URL, final destination, hop count, redirect type, loops, and final status/indexability. www.screamingfrog.co.uk

You're looking for:

• old → new 301/308 → 200
• old → redirect → redirect → new (chain)
• old → new → old (loop)
• old → 404/410 unexpectedly
• redirect → noindex
• redirect → noncanonical URL
• redirect → wrong product/category
• HTTP → HTTPS → www/non-www chains
• internal links still pointing at redirected old URLs

Ideally, internal links on the new site should point directly to the final canonical URLs, rather than relying on redirects. www.screamingfrog.co.uk

3. Establish a ranking baseline before flipping the switch.

With Ahrefs/Semrush, create a migration keyword set containing:

• highest-revenue product terms
• highest-traffic category terms
• brand terms
• important long-tail terms
• terms representing each major template/category
• terms for pages undergoing URL changes

I'd tag them by template, category, revenue tier, and migration status. Then compare roughly:

7 days pre-launch → 1 day → 3 days → 7 days → 14 days → 28 days

Don't panic over individual keyword movements; look for clusters of losses associated with a particular directory, template, category, or URL migration.

The part I'd emphasize most

For a large shop, I'd make Screaming Frog + GSC + a rank tracker the core stack.

Screaming Frog answers:

"Did we migrate the URLs correctly?"

GSC answers:

"Is Google actually crawling/indexing and sending traffic to the new site?"

Ahrefs/Semrush answers:

"Which keywords and competitors are moving?"

And I'd keep the old-vs-new crawl files permanently. That gives you an objective technical baseline rather than trying to reconstruct what changed after rankings have already fallen.

Screaming Frog SEO Spider · Google Search Console · Ahrefs Rank Tracker

If this is a 100k+ URL ecommerce migration, I can also lay out a practical pre-launch → launch day → first 30 days SEO migration monitoring plan, including exactly what reports/exports to generate and what thresholds should trigger an emergency rollback.

For a large e-commerce migration, I’d use a stack rather than one SEO tool. The key is to establish a pre-migration URL/ranking baseline, validate the redirect map, then compare crawls and rankings after launch.

My preferred setup

1. Screaming Frog for the URL map

Before launch, crawl the entire old shop and export at least:

• Old URL
• Status code
• Canonical URL
• Indexability
• Title/H1
• Organic traffic
• Internal links
• External backlinks
• Crawl depth

Then crawl the new platform and create a 1:1 old → new URL mapping wherever possible.

For a big catalog, don't map URLs purely by matching URL strings. Use product/SKU/category data as the underlying key, because platform migrations often change URL structures.

2. Ahrefs or Semrush for the ranking baseline

I'd pick one, not necessarily both.

Ahrefs' current Rank Tracker supports location-specific tracking, target-URL monitoring, historical ranking data and competitor comparisons. Its Site Audit also checks redirects, indexability, links, sitemaps and other technical issues. ahrefs.com

Semrush is similarly useful if you already use its Site Audit and Position Tracking ecosystem. www.semrush.com

Before the switch, export your top-ranking keywords and landing pages, particularly:

• Top 3 / top 10 keywords
• High-traffic category pages
• High-revenue product pages
• Pages with significant backlinks
• Pages with lots of impressions but lower rankings

Those become your migration watchlist.

3. GSC is your source of truth after launch

Set up/verify the new property before launch and retain the old property. Watch:

• Indexed pages
• 404/soft-404 trends
• Redirect problems
• Impressions
• Clicks
• Average position
• Top queries
• Top landing pages

Third-party rank trackers are great for alerts and controlled keyword sets, but GSC tells you what Google is actually doing with your site.

The particularly important migration workflow

I'd structure it like this:

T-30 to T-7
→ Crawl old site
→ Export URLs
→ Export GSC data
→ Export ranking data
→ Export backlinks
→ Build old → new URL map
→ Identify high-value URLs

T-7 to T-1
→ Crawl staging/new site
→ Test every redirect
→ Check for redirect chains
→ Check canonical tags
→ Check robots/noindex
→ Check XML sitemap
→ Check internal links
→ Make sure important old URLs have a relevant destination

Launch day
→ Crawl the live site immediately
→ Test a sample/all critical redirects
→ Check status codes
→ Check robots.txt
→ Check canonicals
→ Submit new XML sitemap
→ Monitor GSC

Days 1–30
→ Daily ranking/traffic monitoring initially
→ Compare old vs. new landing pages
→ Watch 404s and indexing
→ Investigate ranking losses by URL
→ Re-crawl periodically

The biggest mistake is monitoring only overall organic traffic. A large shop can look "fine" overall while hundreds of valuable category/product URLs have fallen out of the index.

For a large migration, I'd probably choose Screaming Frog + GSC + either Ahrefs or Semrush as the core stack. Ahrefs explicitly supports scheduled technical audits and ranking monitoring, which makes the post-launch comparison particularly useful. ahrefs.com

If you tell me roughly how many URLs you're migrating (e.g. 50k, 500k, 5M) and whether the URL structure is changing, I can lay out a concrete migration monitoring stack and spreadsheet/schema for the redirect map.

For a large ecommerce migration, you’ll want a mix of URL discovery/mapping, redirect validation, technical crawl monitoring, and ranking/traffic monitoring. No single SEO tool does all of this perfectly, so most teams use a stack.

1. URL inventory + redirect mapping

These help you build a reliable “old URL → new URL” map before launch.

• Screaming Frog SEO Spider
  • Crawl the existing shop and export:
    • current URLs
    • status codes
    • canonicals
    • titles/meta
    • internal links
    • indexability
  • Excellent for generating redirect lists at scale.

• Sitebulb
  • Similar to Screaming Frog but with stronger visual audits and prioritization.
  • Useful when stakeholders need understandable migration reports.

• Ahrefs or Semrush
  • Help find URLs you might miss:
    • pages with backlinks
    • ranking URLs
    • orphaned pages
    • old product/category URLs still receiving traffic

Tip: Don’t rely only on your current crawl. Combine:

• current site crawl
• XML sitemaps
• Google Search Console URL data
• analytics landing pages
• backlink tools

2. Redirect testing and monitoring

For a large migration, redirect quality matters as much as the mapping.

• Screaming Frog SEO Spider

Use the List Mode crawl:

• upload your old URLs
• verify they return the expected 301
• confirm final destinations
• detect redirect chains and loops

• Little Warden

Good for ongoing monitoring:

• important URLs changing unexpectedly
• redirects breaking
• titles/meta changes
• robots.txt changes

• ContentKing (now part of Conductor)

Useful for enterprise sites:

• continuous crawling
• alerts when pages become noindex
• canonical changes
• broken redirects
• template issues

3. Ranking drop detection

You want tools that compare pre-launch vs post-launch performance.

• Google Search Console

Essential:

• clicks
• impressions
• average position
• indexing coverage
• crawl errors

Export a baseline before migration:

• top landing pages
• queries
• impressions/clicks
• indexed pages

• STAT Search Analytics

Enterprise-grade rank tracking:

• large keyword sets
• SERP features
• migration monitoring

• Semrush Position Tracking

Good for:

• daily ranking movement
• competitor comparisons
• visibility trends

• Ahrefs Rank Tracker

Strong if you already use Ahrefs for backlinks/content.

4. Log file analysis (very valuable for large shops)

For millions of URLs, crawler data alone can hide problems. Log analysis shows what Googlebot is actually doing.

• Screaming Frog Log File Analyser
• Botify
• Oncrawl

These can reveal:

• Googlebot wasting crawl budget on old URLs
• redirects being crawled repeatedly
• important pages not being discovered
• server response issues

5. Ecommerce-specific checks

For a shop migration, pay special attention to:

• product URLs
• category URLs
• faceted navigation/filter URLs
• discontinued products
• pagination
• international URLs (hreflang)
• structured data
• canonical changes

Useful tools:

• Google Rich Results Test — validate product schema
• Schema.org — structured data reference

A practical migration stack

For a large ecommerce migration, a common setup:

Migration timeline I’d recommend

4–8 weeks before launch

• Crawl old site
• Export top organic landing pages
• Export indexed URLs
• Build redirect map
• Capture ranking baseline

Launch day

• Validate 301s
• Check robots.txt
• Check canonicals
• Submit new sitemap
• Monitor crawl errors

First 30–90 days

• Daily ranking/traffic monitoring
• Weekly redirect audits
• Log file review
• Fix unexpected 404s quickly

For a very large shop (hundreds of thousands or millions of URLs), I’d prioritize Screaming Frog + Google Search Console + a log analyzer + enterprise rank tracking over trying to do everything inside one SEO suite.

For a large ecommerce migration, I’d use a stack rather than one SEO tool:

• Screaming Frog SEO Spider — crawl old/new sites, export URL inventories, compare status codes, canonicals, titles, hreflang, internal links, and identify redirect chains/loops.
• Semrush — useful for ongoing rank/visibility monitoring and comparing organic performance before vs. after launch.
• Ahrefs — strong for historical/current rankings, backlinks, lost pages, and identifying URLs whose organic traffic or visibility deteriorates.
• Google Search Console — essential for monitoring indexing, impressions/clicks, queries, crawl issues, and post-migration ranking changes directly from Google.
• Sitebulb — particularly good for large technical audits and visualizing crawl/indexation problems.
• Botify — worth considering for very large sites where you need enterprise-scale log-file analysis and crawl-budget monitoring.

A practical migration setup

1. Before migration — build the URL map

• Crawl the entire old site.
• Export every indexable URL, canonical, status code, title, organic traffic, backlinks, and important query/ranking data.
• Create an old URL → new URL mapping, ideally at the most specific equivalent page level.
• Flag URLs that should intentionally return 410/404 rather than being redirected.

2. During launch — validate redirects
Run crawls against the new site and specifically test:

Old URL → 301 → correct New URL → 200

Watch for:

• redirect chains
• redirect loops
• 302s where 301s are intended
• redirects to irrelevant pages
• 404/5xx responses
• canonical URLs still pointing to the old platform
• internal links still using old URLs
• incorrect robots.txt/noindex directives
• XML sitemaps containing old URLs

3. After launch — monitor rankings and indexation
Use Search Console + Ahrefs/Semrush to establish a pre-migration baseline and compare it against daily/weekly post-launch performance.

I'd pay particular attention to non-brand clicks/impressions, rankings for high-value category/product queries, indexed pages, crawl errors, and organic landing-page traffic. Don't panic over a small ranking fluctuation immediately after launch; look for sustained losses or clusters affecting particular templates/categories.

If the shop is very large

For millions of URLs, I'd lean toward Screaming Frog/Sitebulb + Search Console + Botify + either Ahrefs or Semrush, with server/CDN logs feeding into the analysis. Log files can reveal whether Googlebot is actually discovering and crawling the new URL structure rather than merely telling you that the pages are technically accessible.

If you tell me roughly how many URLs you have (100k, 1M, 10M+) and whether the URL structure is changing, I can suggest a concrete migration-tool stack and a URL-mapping/redirect QA workflow.

For a large ecommerce migration, I’d use a stack rather than one tool:

• Screaming Frog SEO Spider — crawl old/new sites, build URL inventories, identify redirect chains/loops, broken links, canonicals, noindex issues, and compare crawl data before vs. after launch.
• Google Search Console — monitor indexing, queries, clicks, impressions, CTR, and ranking changes after the migration.
• Semrush or Ahrefs — track large sets of keywords and landing pages, compare visibility before/after launch, and surface ranking losses.
• Sitebulb — excellent for visualizing crawl architecture and finding technical SEO problems; particularly useful for QA alongside Screaming Frog.
• ContentKing — useful if you want continuous, near-real-time monitoring of redirects, indexability, canonical changes, broken URLs, and other SEO-critical changes during the migration.
• Botify or Lumar — worth considering for very large sites where you need enterprise-scale crawling, log analysis, segmentation, and migration monitoring.

A practical migration setup

Before launch

1. Crawl the old site and export every indexable URL.
2. Create an old URL → new URL mapping, ideally at the most specific equivalent page level.
3. Crawl the staging/new site and compare:
   • status codes
   • canonicals
   • titles/meta
   • robots directives
   • internal links
   • XML sitemaps
4. Establish baseline rankings/traffic for important URL groups.

At launch

• Validate that old URLs return 301/308 redirects to the intended new URLs.
• Look specifically for redirect chains, loops, mass 404s, soft 404s, and irrelevant redirects.
• Keep an eye on server logs to confirm Googlebot is actually being redirected/crawling the right destinations.

First 1–4 weeks

• Watch Search Console for indexing and performance changes.
• Track priority keywords in Semrush/Ahrefs.
• Re-crawl the new site regularly.
• Segment losses by category, template, country, device, and URL type. A 10% sitewide drop means something very different from a 10% drop concentrated in one product template.

For a large shop, my preferred combination would be Screaming Frog + Google Search Console + Semrush/Ahrefs, with ContentKing or Lumar/Botify added if the migration is business-critical or the site is huge.

For a large ecommerce migration, it's usually worth combining a few specialized tools rather than relying on one platform. The core jobs are:

• Building and validating URL mappings
• Testing redirects before and after launch
• Monitoring crawling, indexing, and errors
• Tracking keyword rankings and organic traffic
• Comparing the old and new sites over time

A workflow that works well for enterprise migrations looks like this:

1. URL mapping

Before launch, crawl the existing site and export:

• Every indexable URL
• Canonicals
• Status codes
• Titles
• H1s
• Meta descriptions
• Internal links
• Product/category IDs (if available)

Your redirect sheet should include:

Avoid redirecting everything to the homepage—Google generally treats those as soft 404s.

2. Crawl both environments

Run crawls against:

• Current production
• Staging
• New production after launch

Compare:

• Status codes
• Canonicals
• Robots directives
• Internal linking
• Duplicate titles
• Missing metadata
• Missing pages

This catches a surprising number of migration issues before search engines do.

3. Validate redirects

After launch, crawl the legacy URL list.

Look for:

• 404s
• 302s that should be 301s
• Redirect chains
• Redirect loops
• Incorrect destination pages
• Mixed HTTP/HTTPS behavior

Ideally every old URL returns:

301
↓
Final destination
200

4. Monitor rankings daily

For the first month, daily tracking is worthwhile.

Track separately:

• Brand keywords
• High-revenue products
• Categories
• Long-tail terms
• Local keywords (if applicable)

Set alerts for:

• Position drops
• URL changes
• Lost featured snippets
• Lost rich results

5. Watch Google Search Console closely

Monitor:

• Pages not indexed
• Crawl anomalies
• Soft 404s
• Redirect errors
• Sitemap coverage
• Performance by page
• Performance by query

It's normal to see some volatility after a migration, but sustained increases in crawl errors or large drops in indexed pages deserve investigation.

6. Compare traffic

Build dashboards comparing:

• Organic sessions
• Revenue
• Transactions
• Landing pages
• Category traffic
• Product traffic

Compare against:

• Previous week
• Same week last year
• Pre-launch baseline

This helps distinguish migration effects from normal seasonality.

7. Check server logs

For very large sites (100k+ URLs), server log analysis becomes valuable.

Questions to answer:

• Is Googlebot spending time on redirected URLs?
• Is it discovering new URLs?
• Are important pages being crawled?
• Are crawl budgets being wasted on parameter URLs?

Enterprise migration checklist

• ✅ Crawl the old site
• ✅ Export every URL
• ✅ Build a complete redirect map
• ✅ Test redirects on staging
• ✅ Crawl staging
• ✅ Launch
• ✅ Submit new XML sitemap
• ✅ Validate redirects
• ✅ Monitor Search Console daily
• ✅ Track rankings daily for 2–4 weeks
• ✅ Compare organic traffic and revenue
• ✅ Recrawl after one week and one month

For large ecommerce sites (roughly 50,000+ URLs), a strong stack is:

• Screaming Frog SEO Spider for crawling and redirect validation.
• Google Search Console and Google Analytics for indexing and traffic monitoring.
• STAT Search Analytics or Semrush for daily keyword monitoring.
• Botify or Lumar if you need enterprise-scale crawl and log analysis. This combination provides good coverage for URL mapping, redirect validation, and early detection of ranking or indexing issues during a migration.

For a large e-commerce migration, you'll usually want a combination of crawling, URL mapping, log analysis, rank tracking, and monitoring. No single tool does everything well.

Here's a stack that works well for most enterprise migrations:

1. URL mapping

For migrations involving tens or hundreds of thousands of URLs:

• Crawl the existing site.
• Export all indexable URLs.
• Create a mapping table:

Avoid:

• many-to-one redirects where possible
• redirect chains
• blanket redirects to the homepage
• changing URL structure unnecessarily

2. Redirect testing

Before launch:

• crawl every old URL
• confirm each returns:
  • 301
  • destination = correct page
  • no chain
  • no loop
  • final page = 200

After launch:

Run another crawl of the old URLs and look for:

• 404s
• 302s that should be 301s
• soft 404s
• redirect chains
• canonical mistakes

3. Ranking monitoring

Track rankings:

• 2–4 weeks before migration (baseline)
• daily for first month
• weekly afterward

Track:

• branded keywords
• top revenue keywords
• category pages
• product pages
• local keywords (if applicable)

Enterprise sites often monitor hundreds or thousands of keywords.

4. Search Console monitoring

Watch for:

• indexed pages dropping
• spikes in excluded pages
• increase in 404s
• "Page with redirect"
• crawl anomalies
• Core Web Vitals changes

Also compare:

• clicks
• impressions
• average position
• CTR

Page-by-page if possible.

5. Crawl comparison

Run a crawl:

Before migration

• URL inventory
• metadata
• canonicals
• hreflang
• structured data

Then crawl again immediately after launch.

Compare:

• page count
• internal links
• orphan pages
• canonical tags
• robots directives
• indexability

This catches many migration issues before search engines do.

6. Log file analysis

For larger sites (typically 100k+ URLs), log analysis is particularly valuable.

Look for:

• Googlebot still spending time on old URLs
• Important pages not being crawled
• Excessive redirect hops
• Crawl budget wasted on parameters or duplicates

7. Automated alerts

Set alerts for:

• sudden organic traffic drops
• spikes in 404 errors
• indexing declines
• rankings dropping by more than a chosen threshold
• increases in server errors (5xx)
• robots.txt changes
• accidental noindex tags

Alerts can come from analytics, Search Console integrations, uptime monitoring, or your observability platform.

A practical migration stack

For many organizations, this combination provides broad coverage:

• Crawling & redirect validation: Screaming Frog SEO Spider
• Technical auditing: Sitebulb or Lumar
• Rank tracking & backlink monitoring: Ahrefs or Semrush
• Search visibility: Google Search Console
• Traffic & revenue: Google Analytics
• Server logs (large sites): Botify or your existing log analytics platform

If you're migrating an enterprise catalog with hundreds of thousands or millions of URLs, it's also worth building an automated URL validation pipeline that tests every redirect, flags missing mappings, and reports unexpected status codes before and after launch. That kind of automation often catches issues that are impractical to find manually.

For a large ecommerce migration, it's helpful to think about SEO tooling in three phases:

1. Before launch: inventory URLs and build redirect maps.
2. Launch: validate redirects and detect crawl issues.
3. After launch: monitor rankings, indexing, and traffic.

A combination of tools usually works better than relying on one platform.

URL mapping

The most important deliverable is a complete redirect map.

A good mapping spreadsheet typically contains:

For large stores (50k–1M+ URLs), prioritize:

• Pages receiving organic traffic
• URLs with backlinks
• High-revenue products
• Important category pages
• Evergreen content

Everything else can often be redirected using predictable rules.

Monitoring redirects

After launch, crawl:

• old URLs
• XML sitemap
• top landing pages
• backlink URLs

Look for:

• 404s
• redirect chains
• redirect loops
• 302s that should be 301s
• canonicals pointing to old URLs
• internal links still using old URLs

A good target is:

• one 301
• no chains
• final destination returns HTTP 200

Catching ranking drops

Don't wait until traffic declines.

Track:

• top 100–500 revenue keywords
• category keywords
• branded keywords
• high-volume product keywords

Daily tracking for the first 2–4 weeks helps identify issues quickly.

Watch for:

• average position
• impressions
• clicks
• indexed pages
• pages losing impressions
• pages disappearing from search

A small fluctuation is normal after a migration. Larger, sustained drops—especially if they coincide with indexing or redirect problems—deserve investigation.

Crawl comparisons

One of the highest-value checks is comparing crawls before and after launch.

Compare:

• page titles
• meta descriptions
• H1s
• canonicals
• indexability
• structured data
• internal link counts
• status codes
• XML sitemap URLs

This catches accidental SEO regressions that are easy to miss.

Enterprise migration dashboard

Many teams build a dashboard (using tools such as Looker Studio, Power BI, or Tableau) combining:

• Organic sessions (GA4)
• Search Console clicks/impressions
• Indexed pages
• 404 errors
• Redirect failures
• Top keyword rankings
• Revenue from organic search
• Crawl health score

This gives stakeholders a single place to monitor migration health.

A practical tool stack

For most large ecommerce migrations, a balanced stack looks like:

• Crawling & URL inventory: Screaming Frog SEO Spider
• Site auditing: Sitebulb or Lumar
• Performance & indexing: Google Search Console + Google Analytics
• Rank tracking: Semrush or Ahrefs
• Server log analysis (optional but valuable): Splunk or ELK Stack
• URL mapping: Excel or Google Sheets, often supplemented with SQL or Python for large-scale matching

This combination covers the full migration lifecycle—from planning redirects through validating the launch and monitoring recovery—without relying on a single vendor.

For a large e-commerce migration, it's helpful to think of the SEO tooling in three phases:

1. Pre-migration: inventory every URL and create redirect mappings.
2. Launch: validate redirects, crawl the new site, and find errors quickly.
3. Post-migration: monitor indexing, rankings, traffic, and technical issues.

A combination of tools generally works better than relying on one platform.

1. Build the URL mapping

Start by creating the most complete inventory possible:

• Crawl the current site with Screaming Frog.
• Export all indexed URLs from Google Search Console.
• Export top landing pages from Google Analytics.
• Export URLs with backlinks from Ahrefs or Semrush.
• Include XML sitemap URLs.
• Include discontinued products and category pages if they have backlinks.

Create a mapping spreadsheet with columns like:

For enterprise migrations (100k–1M+ URLs), teams often generate much of this mapping programmatically and manually review the highest-value pages.

2. Validate redirects before launch

Before DNS changes:

• Crawl the old URL list against a staging environment.
• Verify every URL returns exactly one 301 to the intended destination.
• Look for:
  • redirect chains
  • redirect loops
  • accidental 302s
  • 404s
  • soft 404s
  • homepage redirects

A good migration should have very few unexpected redirect failures.

3. Monitor after launch

The first few weeks are critical.

Watch:

• Google Search Console Coverage
• Crawl Stats
• Indexing
• Core Web Vitals
• 404 errors
• Soft 404s
• Canonical issues
• Sitemap processing

Also compare:

• Organic sessions
• Revenue
• Conversions
• Indexed pages
• Crawl frequency

Daily monitoring for the first two weeks is common on large migrations.

4. Track rankings

Rather than tracking every keyword, prioritize:

• Top revenue keywords
• Brand keywords
• Category terms
• Product terms
• Long-tail keywords that drive conversions

Enterprise teams often track thousands to hundreds of thousands of keywords during a migration.

Useful tools include:

• Ahrefs
• Semrush
• STAT Search Analytics (particularly strong for very large keyword sets)
• AccuRanker

Set up alerts for significant

For a large e-commerce migration, the most valuable SEO tools are the ones that help in three phases:

1. Before launch: inventory URLs, map redirects, and identify high-value pages.
2. During launch: validate redirects and crawlability.
3. After launch: monitor rankings, traffic, indexing, and errors.

Here's a stack that many enterprise SEO teams use.

1. URL mapping

For migrations involving tens or hundreds of thousands of URLs:

• Crawl the old site.
• Export every indexable URL.
• Pull organic traffic and backlinks.
• Create a spreadsheet with columns like:

Useful data sources include:

• Screaming Frog crawl
• Google Search Console top pages
• Google Analytics landing pages
• Ahrefs top pages
• XML sitemaps
• CMS exports

2. Test redirects before launch

Screaming Frog is excellent here.

Upload the old URL list in List Mode and verify:

• 301 (not 302)
• final destination
• redirect chains
• loops
• 404s
• canonical tags
• hreflang
• noindex
• robots issues

Aim for:

• one-hop redirects
• no redirect chains
• no orphaned pages
• no accidental 200s on removed pages

3. Monitor ranking drops

Daily tracking is important for the first 4–8 weeks.

Good choices:

• Semrush Position Tracking
• Ahrefs Rank Tracker
• STAT (excellent for enterprise sites)
• Google Search Console Performance report

Track separately:

• branded keywords
• category terms
• product terms
• high-revenue keywords

Expect some fluctuation immediately after launch, but investigate sustained declines.

4. Watch indexing

Google Search Console should be monitored daily for:

• Coverage
• Crawl Stats
• Page indexing
• Sitemaps
• Manual actions
• Core Web Vitals

Compare:

• indexed pages before vs. after
• excluded pages
• soft 404s
• redirect errors

5. Monitor crawl errors

During the first month, check for:

• 404 errors
• 500 errors
• redirect loops
• blocked resources
• robots.txt issues
• sitemap errors

Many teams run Screaming Frog daily during the first week after launch.

6. Compare traffic

Create dashboards comparing:

• Organic sessions
• Revenue
• Transactions
• Landing pages
• Conversions

Compare against:

• previous week
• same day last week
• same period last year (to account for seasonality)

7. Monitor backlinks

If important URLs changed:

• Identify high-authority backlinks pointing to redirected URLs.
• Reach out to partners where practical and ask them to update links to the new URLs, reducing reliance on redirects over time.

Ahrefs is particularly useful for this.

Recommended migration stack

For a large commerce migration, a practical combination is:

• Crawling: Screaming Frog (or Lumar for very large sites)
• URL mapping: Google Sheets/Excel/Airtable with exports from analytics and crawl data
• Rank tracking: STAT for enterprise-scale keyword sets, or Semrush if you already use it
• Backlink monitoring: Ahrefs
• Performance: Google Analytics 4
• Indexing & crawl health: Google Search Console
• Technical validation: Screaming Frog before launch and repeatedly after launch
• Log analysis (optional but valuable): Screaming Frog Log File Analyser or Splunk to verify how Googlebot is crawling the new site

For enterprise migrations (100k+ URLs), it's also worth automating daily checks that compare:

• old URLs returning anything other than 301,
• new URLs returning non-200 responses,
• unexpected changes in canonical tags,
• missing metadata,
• sharp drops in indexed pages, and
• ranking or traffic declines on your highest-value landing pages.

This combination gives you early warning of issues before they have a significant impact on organic visibility.