ChatGPT answers, unedited

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.