ChatGPT answers, unedited

For a CMS migration, you typically need three categories of tooling:

1. Redirect validation (did every old URL redirect correctly?)
2. Indexation monitoring (is Google indexing the new URLs and dropping the old ones?)
3. Traffic & ranking retention (did you preserve organic visibility?)

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

1. Redirect validation

This is the highest-risk area during a CMS migration.

I recommend using:

• Screaming Frog SEO Spider

• Crawl the old URL list
• Verify every URL returns 301 → new URL → 200
• Detect redirect chains
• Detect loops
• Find URLs that incorrectly redirect to the homepage
• Sitebulb

• Similar functionality with more visual reporting
• URLMatcher

• Purpose-built for migration planning and post-launch redirect QA, including redirect mapping and Search Console comparisons. URLMatcher

Your redirect QA should verify:

• every legacy URL redirects
• status code = 301 (or 308)
• no 302s
• no redirect chains
• destination returns 200
• destination is the correct equivalent page (not just homepage)

2. Indexation monitoring

Google Search Console is the primary source of truth.

Track:

• Indexed pages
• Excluded pages
• Soft 404s
• Alternate canonical pages
• Crawl anomalies
• Page indexing report
• Crawl stats

Also inspect:

• XML sitemap coverage
• New URLs getting indexed
• Old URLs gradually disappearing

Google recommends monitoring Index Coverage, Crawl Stats, URL Inspection, and server logs after launch, while keeping permanent redirects in place for at least a year. Google for Developers

3. Traffic retention

Use:

GA4

Monitor:

• Organic sessions
• Landing pages
• Conversions
• Revenue
• Bounce/engagement

Google Search Console

Monitor:

• Clicks
• Impressions
• Average position
• CTR

Compare:

• 28 days pre-launch
• 7 days after
• 30 days after
• 60 days after
• 90 days after

4. Ranking monitoring

Ahrefs or Semrush are excellent for:

• keyword rankings
• keyword losses
• new rankings
• page-level visibility

Flag:

• high-value keywords dropping >5 positions
• pages losing >20% clicks
• pages disappearing from rankings

5. Technical SEO validation

Run a full crawl immediately after launch checking:

• canonicals
• noindex tags
• robots.txt
• hreflang
• structured data
• title tags
• meta descriptions
• H1s
• internal links
• orphan pages
• broken links

Most migration failures are caused by technical issues rather than redirects alone.

6. Ongoing monitoring

ContentKing is particularly strong because it continuously checks for:

• broken redirects
• accidental noindex
• robots.txt changes
• canonical changes
• 404s
• server errors

This catches regressions within minutes rather than days.

Recommended migration dashboard (KPIs)

Create a dashboard with daily tracking of:

• ✅ Organic sessions
• ✅ Organic conversions
• ✅ Indexed pages
• ✅ 404 count
• ✅ Redirect errors
• ✅ Redirect chains
• ✅ Top 100 landing pages
• ✅ Top 100 keywords
• ✅ Crawl errors
• ✅ Average ranking
• ✅ Sitemap coverage
• ✅ Core Web Vitals
• ✅ Server response codes (200/301/404/500)

An enterprise migration stack

If I were leading a medium-to-large CMS migration, I'd use:

• Redirects: Screaming Frog + URLMatcher
• Indexation: Google Search Console + URL Inspection
• Traffic: GA4
• Rankings: Ahrefs or Semrush
• Technical QA: Screaming Frog + Sitebulb
• Continuous monitoring: ContentKing

This combination provides comprehensive coverage from pre-launch redirect validation through post-launch indexation and traffic monitoring, and aligns well with Google's own migration guidance. Google for Developers URLMatcher

For a CMS migration, you'll typically want a combination of technical SEO crawlers, Google's own tools, analytics, and redirect testing. No single platform covers everything well.

Here's a practical stack by objective:

1. Redirect validation

This is usually the highest-risk area after a migration.

Recommended tools:

• Screaming Frog SEO Spider
  • Crawl your old URL list
  • Verify every URL returns:
    • Old URL → 301 → New URL → 200
  • Detect:
    • redirect chains
    • loops
    • orphan redirects
    • incorrect destinations

• URLMatcher
  • Excellent for generating redirect mappings before launch and validating them after launch. urlmatcher.com

• Bulk Redirect Checker
  • Useful if you already have a redirect mapping spreadsheet and simply want to verify implementation. serp.tools

Key metrics:

• 100% of important URLs redirected
• No redirect chains
• No 302s where permanent redirects are intended
• No 404s on legacy URLs

2. Indexation monitoring

Google Search Console is your primary source.

Monitor:

• Indexed pages
• Excluded pages
• "Page with redirect"
• Crawled – currently not indexed
• Duplicate without user-selected canonical
• Soft 404s
• New sitemap processing

Also monitor URL Inspection for your highest-value pages.

Google recommends keeping redirects active for at least one year and checking for crawl errors, robots.txt issues, and updated sitemaps after a site move. developers.google.com

3. Crawl comparison

Run crawls:

• Before migration
• On staging
• Immediately after launch
• 1 week after
• 1 month after

Compare:

• Status codes
• Titles
• Meta descriptions
• Canonicals
• H1s
• Structured data
• Internal links
• Images
• hreflang
• Pagination

Screaming Frog and Sitebulb both support crawl comparison workflows.

4. Traffic retention

Compare:

GA4

• Organic sessions
• Organic users
• Landing pages
• Conversion rate
• Revenue (if ecommerce)

Watch:

• Top 100 landing pages
• Category pages
• Product pages
• Blog traffic

Ideally compare:

• Last 28 days vs first 28 days
• Year-over-year if seasonality matters

5. Ranking retention

Use:

• Ahrefs
• Semrush
• STAT
• Sistrix

Track:

• Top keywords
• Top landing pages
• Visibility index
• Average position
• Click-through rate

Small fluctuations are expected, but significant losses on high-value pages warrant investigation.

6. Server log analysis

For larger sites, logs reveal whether Googlebot is behaving as expected.

Check:

• Are old URLs still being crawled?
• Are redirects returning 301?
• Is Google crawling the new URLs?
• Are important pages receiving crawl activity?

Tools include:

• Screaming Frog Log Analyzer
• Splunk
• ELK
• Botify

7. Search Console monitoring

Create a dashboard tracking:

• Clicks
• Impressions
• Indexed pages
• Crawl errors
• Sitemap status
• Coverage issues
• Core Web Vitals

Review daily for the first two weeks, then weekly.

8. Recommended post-launch dashboard

Track these KPIs daily for the first month:

Recommended tool stack by organization size

Small to mid-size sites

• Google Search Console
• GA4
• Screaming Frog
• Ahrefs or Semrush
• Looker Studio

Enterprise sites

• Google Search Console
• GA4 or Adobe Analytics
• Screaming Frog or Sitebulb
• Botify or OnCrawl
• Ahrefs/STAT/Semrush Enterprise
• Splunk or ELK for log analysis
• URLMatcher for redirect mapping and migration validation urlmatcher.com

This combination provides comprehensive coverage of the three success criteria for a CMS migration: redirect integrity, indexation health, and organic traffic retention.

For a CMS migration, you'll typically want a combination of technical SEO crawlers, Google's own tools, analytics, and redirect testing. No single platform covers everything well.

Here's a practical stack by objective:

1. Redirect validation

This is usually the highest-risk area after a migration.

Recommended tools:

• Screaming Frog SEO Spider
  • Crawl your old URL list
  • Verify every URL returns:
    • Old URL → 301 → New URL → 200
  • Detect:
    • redirect chains
    • loops
    • orphan redirects
    • incorrect destinations

• URLMatcher
  • Excellent for generating redirect mappings before launch and validating them after launch. urlmatcher.com

• Bulk Redirect Checker
  • Useful if you already have a redirect mapping spreadsheet and simply want to verify implementation. serp.tools

Key metrics:

• 100% of important URLs redirected
• No redirect chains
• No 302s where permanent redirects are intended
• No 404s on legacy URLs

2. Indexation monitoring

Google Search Console is your primary source.

Monitor:

• Indexed pages
• Excluded pages
• "Page with redirect"
• Crawled – currently not indexed
• Duplicate without user-selected canonical
• Soft 404s
• New sitemap processing

Also monitor URL Inspection for your highest-value pages.

Google recommends keeping redirects active for at least one year and checking for crawl errors, robots.txt issues, and updated sitemaps after a site move. developers.google.com

3. Crawl comparison

Run crawls:

• Before migration
• On staging
• Immediately after launch
• 1 week after
• 1 month after

Compare:

• Status codes
• Titles
• Meta descriptions
• Canonicals
• H1s
• Structured data
• Internal links
• Images
• hreflang
• Pagination

Screaming Frog and Sitebulb both support crawl comparison workflows.

4. Traffic retention

Compare:

GA4

• Organic sessions
• Organic users
• Landing pages
• Conversion rate
• Revenue (if ecommerce)

Watch:

• Top 100 landing pages
• Category pages
• Product pages
• Blog traffic

Ideally compare:

• Last 28 days vs first 28 days
• Year-over-year if seasonality matters

5. Ranking retention

Use:

• Ahrefs
• Semrush
• STAT
• Sistrix

Track:

• Top keywords
• Top landing pages
• Visibility index
• Average position
• Click-through rate

Small fluctuations are expected, but significant losses on high-value pages warrant investigation.

6. Server log analysis

For larger sites, logs reveal whether Googlebot is behaving as expected.

Check:

• Are old URLs still being crawled?
• Are redirects returning 301?
• Is Google crawling the new URLs?
• Are important pages receiving crawl activity?

Tools include:

• Screaming Frog Log Analyzer
• Splunk
• ELK
• Botify

7. Search Console monitoring

Create a dashboard tracking:

• Clicks
• Impressions
• Indexed pages
• Crawl errors
• Sitemap status
• Coverage issues
• Core Web Vitals

Review daily for the first two weeks, then weekly.

8. Recommended post-launch dashboard

Track these KPIs daily for the first month:

Recommended tool stack by organization size

Small to mid-size sites

• Google Search Console
• GA4
• Screaming Frog
• Ahrefs or Semrush
• Looker Studio

Enterprise sites

• Google Search Console
• GA4 or Adobe Analytics
• Screaming Frog or Sitebulb
• Botify or OnCrawl
• Ahrefs/STAT/Semrush Enterprise
• Splunk or ELK for log analysis
• URLMatcher for redirect mapping and migration validation urlmatcher.com

This combination provides comprehensive coverage of the three success criteria for a CMS migration: redirect integrity, indexation health, and organic traffic retention.

For a CMS migration, you'll typically want a combination of technical SEO crawlers, Google's own tools, analytics, and redirect testing. No single platform covers everything well.

Here's a practical stack by objective:

1. Redirect validation

This is usually the highest-risk area after a migration.

Recommended tools:

• Screaming Frog SEO Spider
  • Crawl your old URL list
  • Verify every URL returns:
    • Old URL → 301 → New URL → 200
  • Detect:
    • redirect chains
    • loops
    • orphan redirects
    • incorrect destinations

• URLMatcher
  • Excellent for generating redirect mappings before launch and validating them after launch. urlmatcher.com

• Bulk Redirect Checker
  • Useful if you already have a redirect mapping spreadsheet and simply want to verify implementation. serp.tools

Key metrics:

• 100% of important URLs redirected
• No redirect chains
• No 302s where permanent redirects are intended
• No 404s on legacy URLs

2. Indexation monitoring

Google Search Console is your primary source.

Monitor:

• Indexed pages
• Excluded pages
• "Page with redirect"
• Crawled – currently not indexed
• Duplicate without user-selected canonical
• Soft 404s
• New sitemap processing

Also monitor URL Inspection for your highest-value pages.

Google recommends keeping redirects active for at least one year and checking for crawl errors, robots.txt issues, and updated sitemaps after a site move. developers.google.com

3. Crawl comparison

Run crawls:

• Before migration
• On staging
• Immediately after launch
• 1 week after
• 1 month after

Compare:

• Status codes
• Titles
• Meta descriptions
• Canonicals
• H1s
• Structured data
• Internal links
• Images
• hreflang
• Pagination

Screaming Frog and Sitebulb both support crawl comparison workflows.

4. Traffic retention

Compare:

GA4

• Organic sessions
• Organic users
• Landing pages
• Conversion rate
• Revenue (if ecommerce)

Watch:

• Top 100 landing pages
• Category pages
• Product pages
• Blog traffic

Ideally compare:

• Last 28 days vs first 28 days
• Year-over-year if seasonality matters

5. Ranking retention

Use:

• Ahrefs
• Semrush
• STAT
• Sistrix

Track:

• Top keywords
• Top landing pages
• Visibility index
• Average position
• Click-through rate

Small fluctuations are expected, but significant losses on high-value pages warrant investigation.

6. Server log analysis

For larger sites, logs reveal whether Googlebot is behaving as expected.

Check:

• Are old URLs still being crawled?
• Are redirects returning 301?
• Is Google crawling the new URLs?
• Are important pages receiving crawl activity?

Tools include:

• Screaming Frog Log Analyzer
• Splunk
• ELK
• Botify

7. Search Console monitoring

Create a dashboard tracking:

• Clicks
• Impressions
• Indexed pages
• Crawl errors
• Sitemap status
• Coverage issues
• Core Web Vitals

Review daily for the first two weeks, then weekly.

8. Recommended post-launch dashboard

Track these KPIs daily for the first month:

Recommended tool stack by organization size

Small to mid-size sites

• Google Search Console
• GA4
• Screaming Frog
• Ahrefs or Semrush
• Looker Studio

Enterprise sites

• Google Search Console
• GA4 or Adobe Analytics
• Screaming Frog or Sitebulb
• Botify or OnCrawl
• Ahrefs/STAT/Semrush Enterprise
• Splunk or ELK for log analysis
• URLMatcher for redirect mapping and migration validation urlmatcher.com

This combination provides comprehensive coverage of the three success criteria for a CMS migration: redirect integrity, indexation health, and organic traffic retention.

For a CMS migration, you'll typically want a combination of technical SEO crawlers, Google's own tools, analytics, and redirect testing. No single platform covers everything well.

Here's a practical stack by objective:

1. Redirect validation

This is usually the highest-risk area after a migration.

Recommended tools:

• Screaming Frog SEO Spider
  • Crawl your old URL list
  • Verify every URL returns:
    • Old URL → 301 → New URL → 200
  • Detect:
    • redirect chains
    • loops
    • orphan redirects
    • incorrect destinations

• URLMatcher
  • Excellent for generating redirect mappings before launch and validating them after launch. urlmatcher.com

• Bulk Redirect Checker
  • Useful if you already have a redirect mapping spreadsheet and simply want to verify implementation. serp.tools

Key metrics:

• 100% of important URLs redirected
• No redirect chains
• No 302s where permanent redirects are intended
• No 404s on legacy URLs

2. Indexation monitoring

Google Search Console is your primary source.

Monitor:

• Indexed pages
• Excluded pages
• "Page with redirect"
• Crawled – currently not indexed
• Duplicate without user-selected canonical
• Soft 404s
• New sitemap processing

Also monitor URL Inspection for your highest-value pages.

Google recommends keeping redirects active for at least one year and checking for crawl errors, robots.txt issues, and updated sitemaps after a site move. developers.google.com

3. Crawl comparison

Run crawls:

• Before migration
• On staging
• Immediately after launch
• 1 week after
• 1 month after

Compare:

• Status codes
• Titles
• Meta descriptions
• Canonicals
• H1s
• Structured data
• Internal links
• Images
• hreflang
• Pagination

Screaming Frog and Sitebulb both support crawl comparison workflows.

4. Traffic retention

Compare:

GA4

• Organic sessions
• Organic users
• Landing pages
• Conversion rate
• Revenue (if ecommerce)

Watch:

• Top 100 landing pages
• Category pages
• Product pages
• Blog traffic

Ideally compare:

• Last 28 days vs first 28 days
• Year-over-year if seasonality matters

5. Ranking retention

Use:

• Ahrefs
• Semrush
• STAT
• Sistrix

Track:

• Top keywords
• Top landing pages
• Visibility index
• Average position
• Click-through rate

Small fluctuations are expected, but significant losses on high-value pages warrant investigation.

6. Server log analysis

For larger sites, logs reveal whether Googlebot is behaving as expected.

Check:

• Are old URLs still being crawled?
• Are redirects returning 301?
• Is Google crawling the new URLs?
• Are important pages receiving crawl activity?

Tools include:

• Screaming Frog Log Analyzer
• Splunk
• ELK
• Botify

7. Search Console monitoring

Create a dashboard tracking:

• Clicks
• Impressions
• Indexed pages
• Crawl errors
• Sitemap status
• Coverage issues
• Core Web Vitals

Review daily for the first two weeks, then weekly.

8. Recommended post-launch dashboard

Track these KPIs daily for the first month:

Recommended tool stack by organization size

Small to mid-size sites

• Google Search Console
• GA4
• Screaming Frog
• Ahrefs or Semrush
• Looker Studio

Enterprise sites

• Google Search Console
• GA4 or Adobe Analytics
• Screaming Frog or Sitebulb
• Botify or OnCrawl
• Ahrefs/STAT/Semrush Enterprise
• Splunk or ELK for log analysis
• URLMatcher for redirect mapping and migration validation urlmatcher.com

This combination provides comprehensive coverage of the three success criteria for a CMS migration: redirect integrity, indexation health, and organic traffic retention.

For a CMS migration, you'll typically want a combination of technical SEO crawlers, Google's own tools, analytics, and redirect testing. No single platform covers everything well.

Here's a practical stack by objective:

1. Redirect validation

This is usually the highest-risk area after a migration.

Recommended tools:

• Screaming Frog SEO Spider
  • Crawl your old URL list
  • Verify every URL returns:
    • Old URL → 301 → New URL → 200
  • Detect:
    • redirect chains
    • loops
    • orphan redirects
    • incorrect destinations

• URLMatcher
  • Excellent for generating redirect mappings before launch and validating them after launch. urlmatcher.com

• Bulk Redirect Checker
  • Useful if you already have a redirect mapping spreadsheet and simply want to verify implementation. serp.tools

Key metrics:

• 100% of important URLs redirected
• No redirect chains
• No 302s where permanent redirects are intended
• No 404s on legacy URLs

2. Indexation monitoring

Google Search Console is your primary source.

Monitor:

• Indexed pages
• Excluded pages
• "Page with redirect"
• Crawled – currently not indexed
• Duplicate without user-selected canonical
• Soft 404s
• New sitemap processing

Also monitor URL Inspection for your highest-value pages.

Google recommends keeping redirects active for at least one year and checking for crawl errors, robots.txt issues, and updated sitemaps after a site move. developers.google.com

3. Crawl comparison

Run crawls:

• Before migration
• On staging
• Immediately after launch
• 1 week after
• 1 month after

Compare:

• Status codes
• Titles
• Meta descriptions
• Canonicals
• H1s
• Structured data
• Internal links
• Images
• hreflang
• Pagination

Screaming Frog and Sitebulb both support crawl comparison workflows.

4. Traffic retention

Compare:

GA4

• Organic sessions
• Organic users
• Landing pages
• Conversion rate
• Revenue (if ecommerce)

Watch:

• Top 100 landing pages
• Category pages
• Product pages
• Blog traffic

Ideally compare:

• Last 28 days vs first 28 days
• Year-over-year if seasonality matters

5. Ranking retention

Use:

• Ahrefs
• Semrush
• STAT
• Sistrix

Track:

• Top keywords
• Top landing pages
• Visibility index
• Average position
• Click-through rate

Small fluctuations are expected, but significant losses on high-value pages warrant investigation.

6. Server log analysis

For larger sites, logs reveal whether Googlebot is behaving as expected.

Check:

• Are old URLs still being crawled?
• Are redirects returning 301?
• Is Google crawling the new URLs?
• Are important pages receiving crawl activity?

Tools include:

• Screaming Frog Log Analyzer
• Splunk
• ELK
• Botify

7. Search Console monitoring

Create a dashboard tracking:

• Clicks
• Impressions
• Indexed pages
• Crawl errors
• Sitemap status
• Coverage issues
• Core Web Vitals

Review daily for the first two weeks, then weekly.

8. Recommended post-launch dashboard

Track these KPIs daily for the first month:

Recommended tool stack by organization size

Small to mid-size sites

• Google Search Console
• GA4
• Screaming Frog
• Ahrefs or Semrush
• Looker Studio

Enterprise sites

• Google Search Console
• GA4 or Adobe Analytics
• Screaming Frog or Sitebulb
• Botify or OnCrawl
• Ahrefs/STAT/Semrush Enterprise
• Splunk or ELK for log analysis
• URLMatcher for redirect mapping and migration validation urlmatcher.com

This combination provides comprehensive coverage of the three success criteria for a CMS migration: redirect integrity, indexation health, and organic traffic retention.

For a CMS migration, you'll typically want a combination of technical SEO crawlers, Google's own tools, analytics, and redirect testing. No single platform covers everything well.

Here's a practical stack by objective:

1. Redirect validation

This is usually the highest-risk area after a migration.

Recommended tools:

• Screaming Frog SEO Spider
  • Crawl your old URL list
  • Verify every URL returns:
    • Old URL → 301 → New URL → 200
  • Detect:
    • redirect chains
    • loops
    • orphan redirects
    • incorrect destinations

• URLMatcher
  • Excellent for generating redirect mappings before launch and validating them after launch. urlmatcher.com

• Bulk Redirect Checker
  • Useful if you already have a redirect mapping spreadsheet and simply want to verify implementation. serp.tools

Key metrics:

• 100% of important URLs redirected
• No redirect chains
• No 302s where permanent redirects are intended
• No 404s on legacy URLs

2. Indexation monitoring

Google Search Console is your primary source.

Monitor:

• Indexed pages
• Excluded pages
• "Page with redirect"
• Crawled – currently not indexed
• Duplicate without user-selected canonical
• Soft 404s
• New sitemap processing

Also monitor URL Inspection for your highest-value pages.

Google recommends keeping redirects active for at least one year and checking for crawl errors, robots.txt issues, and updated sitemaps after a site move. developers.google.com

3. Crawl comparison

Run crawls:

• Before migration
• On staging
• Immediately after launch
• 1 week after
• 1 month after

Compare:

• Status codes
• Titles
• Meta descriptions
• Canonicals
• H1s
• Structured data
• Internal links
• Images
• hreflang
• Pagination

Screaming Frog and Sitebulb both support crawl comparison workflows.

4. Traffic retention

Compare:

GA4

• Organic sessions
• Organic users
• Landing pages
• Conversion rate
• Revenue (if ecommerce)

Watch:

• Top 100 landing pages
• Category pages
• Product pages
• Blog traffic

Ideally compare:

• Last 28 days vs first 28 days
• Year-over-year if seasonality matters

5. Ranking retention

Use:

• Ahrefs
• Semrush
• STAT
• Sistrix

Track:

• Top keywords
• Top landing pages
• Visibility index
• Average position
• Click-through rate

Small fluctuations are expected, but significant losses on high-value pages warrant investigation.

6. Server log analysis

For larger sites, logs reveal whether Googlebot is behaving as expected.

Check:

• Are old URLs still being crawled?
• Are redirects returning 301?
• Is Google crawling the new URLs?
• Are important pages receiving crawl activity?

Tools include:

• Screaming Frog Log Analyzer
• Splunk
• ELK
• Botify

7. Search Console monitoring

Create a dashboard tracking:

• Clicks
• Impressions
• Indexed pages
• Crawl errors
• Sitemap status
• Coverage issues
• Core Web Vitals

Review daily for the first two weeks, then weekly.

8. Recommended post-launch dashboard

Track these KPIs daily for the first month:

Recommended tool stack by organization size

Small to mid-size sites

• Google Search Console
• GA4
• Screaming Frog
• Ahrefs or Semrush
• Looker Studio

Enterprise sites

• Google Search Console
• GA4 or Adobe Analytics
• Screaming Frog or Sitebulb
• Botify or OnCrawl
• Ahrefs/STAT/Semrush Enterprise
• Splunk or ELK for log analysis
• URLMatcher for redirect mapping and migration validation urlmatcher.com

This combination provides comprehensive coverage of the three success criteria for a CMS migration: redirect integrity, indexation health, and organic traffic retention.

For a CMS migration, you'll typically want a combination of technical SEO crawlers, Google's own tools, analytics, and redirect testing. No single platform covers everything well.

Here's a practical stack by objective:

1. Redirect validation

This is usually the highest-risk area after a migration.

Recommended tools:

• Screaming Frog SEO Spider
  • Crawl your old URL list
  • Verify every URL returns:
    • Old URL → 301 → New URL → 200
  • Detect:
    • redirect chains
    • loops
    • orphan redirects
    • incorrect destinations

• URLMatcher
  • Excellent for generating redirect mappings before launch and validating them after launch. urlmatcher.com

• Bulk Redirect Checker
  • Useful if you already have a redirect mapping spreadsheet and simply want to verify implementation. serp.tools

Key metrics:

• 100% of important URLs redirected
• No redirect chains
• No 302s where permanent redirects are intended
• No 404s on legacy URLs

2. Indexation monitoring

Google Search Console is your primary source.

Monitor:

• Indexed pages
• Excluded pages
• "Page with redirect"
• Crawled – currently not indexed
• Duplicate without user-selected canonical
• Soft 404s
• New sitemap processing

Also monitor URL Inspection for your highest-value pages.

Google recommends keeping redirects active for at least one year and checking for crawl errors, robots.txt issues, and updated sitemaps after a site move. developers.google.com

3. Crawl comparison

Run crawls:

• Before migration
• On staging
• Immediately after launch
• 1 week after
• 1 month after

Compare:

• Status codes
• Titles
• Meta descriptions
• Canonicals
• H1s
• Structured data
• Internal links
• Images
• hreflang
• Pagination

Screaming Frog and Sitebulb both support crawl comparison workflows.

4. Traffic retention

Compare:

GA4

• Organic sessions
• Organic users
• Landing pages
• Conversion rate
• Revenue (if ecommerce)

Watch:

• Top 100 landing pages
• Category pages
• Product pages
• Blog traffic

Ideally compare:

• Last 28 days vs first 28 days
• Year-over-year if seasonality matters

5. Ranking retention

Use:

• Ahrefs
• Semrush
• STAT
• Sistrix

Track:

• Top keywords
• Top landing pages
• Visibility index
• Average position
• Click-through rate

Small fluctuations are expected, but significant losses on high-value pages warrant investigation.

6. Server log analysis

For larger sites, logs reveal whether Googlebot is behaving as expected.

Check:

• Are old URLs still being crawled?
• Are redirects returning 301?
• Is Google crawling the new URLs?
• Are important pages receiving crawl activity?

Tools include:

• Screaming Frog Log Analyzer
• Splunk
• ELK
• Botify

7. Search Console monitoring

Create a dashboard tracking:

• Clicks
• Impressions
• Indexed pages
• Crawl errors
• Sitemap status
• Coverage issues
• Core Web Vitals

Review daily for the first two weeks, then weekly.

8. Recommended post-launch dashboard

Track these KPIs daily for the first month:

Recommended tool stack by organization size

Small to mid-size sites

• Google Search Console
• GA4
• Screaming Frog
• Ahrefs or Semrush
• Looker Studio

Enterprise sites

• Google Search Console
• GA4 or Adobe Analytics
• Screaming Frog or Sitebulb
• Botify or OnCrawl
• Ahrefs/STAT/Semrush Enterprise
• Splunk or ELK for log analysis
• URLMatcher for redirect mapping and migration validation urlmatcher.com

This combination provides comprehensive coverage of the three success criteria for a CMS migration: redirect integrity, indexation health, and organic traffic retention.

For a CMS migration, you'll want a combination of technical SEO crawling, search engine monitoring, analytics, and log analysis tools. No single tool covers everything.

1. Redirect validation (highest priority)

The most common migration issue is broken or incorrect redirects.

Use:

• Screaming Frog SEO Spider (industry standard)
• Sitebulb
• HTTP status checkers

Validate:

• Every old URL returns 301 (not 302)
• One-hop redirects only (no chains)
• No redirect loops
• High-value pages redirect to their closest equivalent—not the homepage
• Final destination returns 200 OK

Google recommends maintaining redirects for at least a year after a URL migration. developers.google.com

2. Indexation monitoring

Google Search Console should be your primary tool.

Monitor:

• Indexed pages
• Coverage report
• Crawl errors
• Soft 404s
• "Crawled – currently not indexed"
• Canonical selection
• XML sitemap processing

Also submit:

• New XML sitemap
• (Optionally) old URL sitemap to help Google process redirects during migration. developers.google.com

3. Crawl comparison

Run a crawl:

Before launch

• Export all URLs
• Metadata
• Canonicals
• Internal links
• Status codes

After launch

• Crawl again
• Compare:
  • missing pages
  • duplicate titles
  • missing meta descriptions
  • broken links
  • canonical changes
  • orphan pages

Screaming Frog and Sitebulb both make before/after comparisons straightforward.

4. Traffic retention

Monitor daily for several weeks.

Key GA4 metrics:

• Organic sessions
• Organic conversions
• Landing pages
• Revenue
• Bounce/engagement
• Top-performing pages

Rather than only looking at total traffic, compare:

• Top 100 landing pages
• Brand vs non-brand traffic
• Device split
• Country/language
• Conversion rate

5. Rankings

Track rankings before and after.

Useful tools:

• Ahrefs
• Semrush
• STAT
• Sistrix

Create a benchmark of:

• Top keywords
• Top landing pages
• Visibility score
• Featured snippets
• Local rankings (if applicable)

6. Log file analysis

Often overlooked, but extremely valuable.

Use:

• Screaming Frog Log File Analyser
• Oncrawl
• Splunk / ELK

Check:

• Is Googlebot crawling the new URLs?
• Is it still spending time on old URLs?
• Which pages are being ignored?
• Are crawl budget issues emerging?

7. Dashboarding

Build a migration dashboard (Looker Studio, Power BI, or Tableau) that includes:

• Organic sessions
• Indexed pages
• Crawl errors
• 404s
• Redirect failures
• Keyword visibility
• Core Web Vitals
• Revenue/conversions
• Top landing pages

This makes it much easier to spot issues quickly after launch.

Recommended tool stack

Free

• Google Search Console
• Bing Webmaster Tools
• GA4
• Looker Studio
• PageSpeed Insights

Paid (strong combination)

• Screaming Frog
• Ahrefs or Semrush
• Sitebulb (optional alternative to Screaming Frog)
• Lumar or Oncrawl (large enterprise sites)
• Splunk/ELK for server logs

Post-launch validation checklist (first 30 days)

• ✅ All legacy URLs return a single 301 redirect
• ✅ No increase in 404 or 5xx errors
• ✅ New XML sitemap submitted and processing correctly
• ✅ Robots.txt allows crawling
• ✅ Canonical tags point to new URLs
• ✅ Organic landing pages remain stable
• ✅ Keyword rankings recover within expected fluctuation
• ✅ Googlebot increasingly crawls new URLs
• ✅ Indexed page count grows while old URLs drop from the index
• ✅ Revenue and conversions from organic search remain stable or recover as expected

This combination of tools and checks aligns well with Google's guidance for site moves, which emphasizes validating redirects, monitoring indexing in Search Console, tracking user and crawler traffic, and watching server logs during the migration period. developers.google.com

For a CMS migration, you'll want a combination of technical SEO crawling, search engine monitoring, analytics, and log analysis tools. No single tool covers everything.

1. Redirect validation (highest priority)

The most common migration issue is broken or incorrect redirects.

Use:

• Screaming Frog SEO Spider (industry standard)
• Sitebulb
• HTTP status checkers

Validate:

• Every old URL returns 301 (not 302)
• One-hop redirects only (no chains)
• No redirect loops
• High-value pages redirect to their closest equivalent—not the homepage
• Final destination returns 200 OK

Google recommends maintaining redirects for at least a year after a URL migration. developers.google.com

2. Indexation monitoring

Google Search Console should be your primary tool.

Monitor:

• Indexed pages
• Coverage report
• Crawl errors
• Soft 404s
• "Crawled – currently not indexed"
• Canonical selection
• XML sitemap processing

Also submit:

• New XML sitemap
• (Optionally) old URL sitemap to help Google process redirects during migration. developers.google.com

3. Crawl comparison

Run a crawl:

Before launch

• Export all URLs
• Metadata
• Canonicals
• Internal links
• Status codes

After launch

• Crawl again
• Compare:
  • missing pages
  • duplicate titles
  • missing meta descriptions
  • broken links
  • canonical changes
  • orphan pages

Screaming Frog and Sitebulb both make before/after comparisons straightforward.

4. Traffic retention

Monitor daily for several weeks.

Key GA4 metrics:

• Organic sessions
• Organic conversions
• Landing pages
• Revenue
• Bounce/engagement
• Top-performing pages

Rather than only looking at total traffic, compare:

• Top 100 landing pages
• Brand vs non-brand traffic
• Device split
• Country/language
• Conversion rate

5. Rankings

Track rankings before and after.

Useful tools:

• Ahrefs
• Semrush
• STAT
• Sistrix

Create a benchmark of:

• Top keywords
• Top landing pages
• Visibility score
• Featured snippets
• Local rankings (if applicable)

6. Log file analysis

Often overlooked, but extremely valuable.

Use:

• Screaming Frog Log File Analyser
• Oncrawl
• Splunk / ELK

Check:

• Is Googlebot crawling the new URLs?
• Is it still spending time on old URLs?
• Which pages are being ignored?
• Are crawl budget issues emerging?

7. Dashboarding

Build a migration dashboard (Looker Studio, Power BI, or Tableau) that includes:

• Organic sessions
• Indexed pages
• Crawl errors
• 404s
• Redirect failures
• Keyword visibility
• Core Web Vitals
• Revenue/conversions
• Top landing pages

This makes it much easier to spot issues quickly after launch.

Recommended tool stack

Free

• Google Search Console
• Bing Webmaster Tools
• GA4
• Looker Studio
• PageSpeed Insights

Paid (strong combination)

• Screaming Frog
• Ahrefs or Semrush
• Sitebulb (optional alternative to Screaming Frog)
• Lumar or Oncrawl (large enterprise sites)
• Splunk/ELK for server logs

Post-launch validation checklist (first 30 days)

• ✅ All legacy URLs return a single 301 redirect
• ✅ No increase in 404 or 5xx errors
• ✅ New XML sitemap submitted and processing correctly
• ✅ Robots.txt allows crawling
• ✅ Canonical tags point to new URLs
• ✅ Organic landing pages remain stable
• ✅ Keyword rankings recover within expected fluctuation
• ✅ Googlebot increasingly crawls new URLs
• ✅ Indexed page count grows while old URLs drop from the index
• ✅ Revenue and conversions from organic search remain stable or recover as expected

This combination of tools and checks aligns well with Google's guidance for site moves, which emphasizes validating redirects, monitoring indexing in Search Console, tracking user and crawler traffic, and watching server logs during the migration period. developers.google.com

For a CMS migration, you'll want a combination of technical SEO crawling, search engine monitoring, analytics, and log analysis tools. No single tool covers everything.

1. Redirect validation (highest priority)

The most common migration issue is broken or incorrect redirects.

Use:

• Screaming Frog SEO Spider (industry standard)
• Sitebulb
• HTTP status checkers

Validate:

• Every old URL returns 301 (not 302)
• One-hop redirects only (no chains)
• No redirect loops
• High-value pages redirect to their closest equivalent—not the homepage
• Final destination returns 200 OK

Google recommends maintaining redirects for at least a year after a URL migration. developers.google.com

2. Indexation monitoring

Google Search Console should be your primary tool.

Monitor:

• Indexed pages
• Coverage report
• Crawl errors
• Soft 404s
• "Crawled – currently not indexed"
• Canonical selection
• XML sitemap processing

Also submit:

• New XML sitemap
• (Optionally) old URL sitemap to help Google process redirects during migration. developers.google.com

3. Crawl comparison

Run a crawl:

Before launch

• Export all URLs
• Metadata
• Canonicals
• Internal links
• Status codes

After launch

• Crawl again
• Compare:
  • missing pages
  • duplicate titles
  • missing meta descriptions
  • broken links
  • canonical changes
  • orphan pages

Screaming Frog and Sitebulb both make before/after comparisons straightforward.

4. Traffic retention

Monitor daily for several weeks.

Key GA4 metrics:

• Organic sessions
• Organic conversions
• Landing pages
• Revenue
• Bounce/engagement
• Top-performing pages

Rather than only looking at total traffic, compare:

• Top 100 landing pages
• Brand vs non-brand traffic
• Device split
• Country/language
• Conversion rate

5. Rankings

Track rankings before and after.

Useful tools:

• Ahrefs
• Semrush
• STAT
• Sistrix

Create a benchmark of:

• Top keywords
• Top landing pages
• Visibility score
• Featured snippets
• Local rankings (if applicable)

6. Log file analysis

Often overlooked, but extremely valuable.

Use:

• Screaming Frog Log File Analyser
• Oncrawl
• Splunk / ELK

Check:

• Is Googlebot crawling the new URLs?
• Is it still spending time on old URLs?
• Which pages are being ignored?
• Are crawl budget issues emerging?

7. Dashboarding

Build a migration dashboard (Looker Studio, Power BI, or Tableau) that includes:

• Organic sessions
• Indexed pages
• Crawl errors
• 404s
• Redirect failures
• Keyword visibility
• Core Web Vitals
• Revenue/conversions
• Top landing pages

This makes it much easier to spot issues quickly after launch.

Recommended tool stack

Free

• Google Search Console
• Bing Webmaster Tools
• GA4
• Looker Studio
• PageSpeed Insights

Paid (strong combination)

• Screaming Frog
• Ahrefs or Semrush
• Sitebulb (optional alternative to Screaming Frog)
• Lumar or Oncrawl (large enterprise sites)
• Splunk/ELK for server logs

Post-launch validation checklist (first 30 days)

• ✅ All legacy URLs return a single 301 redirect
• ✅ No increase in 404 or 5xx errors
• ✅ New XML sitemap submitted and processing correctly
• ✅ Robots.txt allows crawling
• ✅ Canonical tags point to new URLs
• ✅ Organic landing pages remain stable
• ✅ Keyword rankings recover within expected fluctuation
• ✅ Googlebot increasingly crawls new URLs
• ✅ Indexed page count grows while old URLs drop from the index
• ✅ Revenue and conversions from organic search remain stable or recover as expected

This combination of tools and checks aligns well with Google's guidance for site moves, which emphasizes validating redirects, monitoring indexing in Search Console, tracking user and crawler traffic, and watching server logs during the migration period. developers.google.com

For a CMS migration, you'll want a combination of technical SEO crawling, search engine monitoring, analytics, and log analysis tools. No single tool covers everything.

1. Redirect validation (highest priority)

The most common migration issue is broken or incorrect redirects.

Use:

• Screaming Frog SEO Spider (industry standard)
• Sitebulb
• HTTP status checkers

Validate:

• Every old URL returns 301 (not 302)
• One-hop redirects only (no chains)
• No redirect loops
• High-value pages redirect to their closest equivalent—not the homepage
• Final destination returns 200 OK

Google recommends maintaining redirects for at least a year after a URL migration. developers.google.com

2. Indexation monitoring

Google Search Console should be your primary tool.

Monitor:

• Indexed pages
• Coverage report
• Crawl errors
• Soft 404s
• "Crawled – currently not indexed"
• Canonical selection
• XML sitemap processing

Also submit:

• New XML sitemap
• (Optionally) old URL sitemap to help Google process redirects during migration. developers.google.com

3. Crawl comparison

Run a crawl:

Before launch

• Export all URLs
• Metadata
• Canonicals
• Internal links
• Status codes

After launch

• Crawl again
• Compare:
  • missing pages
  • duplicate titles
  • missing meta descriptions
  • broken links
  • canonical changes
  • orphan pages

Screaming Frog and Sitebulb both make before/after comparisons straightforward.

4. Traffic retention

Monitor daily for several weeks.

Key GA4 metrics:

• Organic sessions
• Organic conversions
• Landing pages
• Revenue
• Bounce/engagement
• Top-performing pages

Rather than only looking at total traffic, compare:

• Top 100 landing pages
• Brand vs non-brand traffic
• Device split
• Country/language
• Conversion rate

5. Rankings

Track rankings before and after.

Useful tools:

• Ahrefs
• Semrush
• STAT
• Sistrix

Create a benchmark of:

• Top keywords
• Top landing pages
• Visibility score
• Featured snippets
• Local rankings (if applicable)

6. Log file analysis

Often overlooked, but extremely valuable.

Use:

• Screaming Frog Log File Analyser
• Oncrawl
• Splunk / ELK

Check:

• Is Googlebot crawling the new URLs?
• Is it still spending time on old URLs?
• Which pages are being ignored?
• Are crawl budget issues emerging?

7. Dashboarding

Build a migration dashboard (Looker Studio, Power BI, or Tableau) that includes:

• Organic sessions
• Indexed pages
• Crawl errors
• 404s
• Redirect failures
• Keyword visibility
• Core Web Vitals
• Revenue/conversions
• Top landing pages

This makes it much easier to spot issues quickly after launch.

Recommended tool stack

Free

• Google Search Console
• Bing Webmaster Tools
• GA4
• Looker Studio
• PageSpeed Insights

Paid (strong combination)

• Screaming Frog
• Ahrefs or Semrush
• Sitebulb (optional alternative to Screaming Frog)
• Lumar or Oncrawl (large enterprise sites)
• Splunk/ELK for server logs

Post-launch validation checklist (first 30 days)

• ✅ All legacy URLs return a single 301 redirect
• ✅ No increase in 404 or 5xx errors
• ✅ New XML sitemap submitted and processing correctly
• ✅ Robots.txt allows crawling
• ✅ Canonical tags point to new URLs
• ✅ Organic landing pages remain stable
• ✅ Keyword rankings recover within expected fluctuation
• ✅ Googlebot increasingly crawls new URLs
• ✅ Indexed page count grows while old URLs drop from the index
• ✅ Revenue and conversions from organic search remain stable or recover as expected

This combination of tools and checks aligns well with Google's guidance for site moves, which emphasizes validating redirects, monitoring indexing in Search Console, tracking user and crawler traffic, and watching server logs during the migration period. developers.google.com

For a CMS migration, you'll typically want a combination of crawling, technical SEO, analytics, and log analysis tools. Here's a practical stack organized by what you're validating.

1. Validate redirects

This is the highest priority immediately after launch.

Use Screaming Frog to:

• Crawl the old URL list.
• Verify every URL returns a 301.
• Confirm redirects go directly to the final destination (no chains).
• Identify:
  • 404s
  • 500s
  • redirect loops
  • 302s that should be 301s

Compare:

• Old URL inventory
• Redirect map
• Live crawl

Success target:

• >99% of legacy URLs correctly redirected.

2. Validate indexation

Google Search Console becomes your primary source.

Monitor:

• Indexed pages
• Excluded pages
• Soft 404s
• Duplicate pages
• Crawled – currently not indexed
• Noindex mistakes

Also submit:

• new XML sitemap
• updated sitemap index

Watch the Index Coverage report daily during the first few weeks.

3. Check crawlability

Run a full crawl of the new site.

Look for:

• orphan pages
• broken internal links
• canonical pointing to old URLs
• robots.txt blocking important sections
• incorrect noindex tags
• pagination
• hreflang
• structured data validation

4. Monitor traffic retention

In GA4 compare:

• Organic sessions
• Organic users
• Landing page traffic
• Conversion rate
• Revenue/leads
• Top 100 landing pages

Rather than looking only at total traffic, compare the top-performing landing pages before and after migration to identify isolated issues.

5. Monitor rankings

Using Ahrefs or Semrush:

Track:

• branded keywords
• top commercial keywords
• informational content
• category pages
• highest-value landing pages

Some ranking fluctuation is expected for 2–6 weeks, but large sustained drops often indicate migration issues.

6. Analyze server logs

If you have access to server logs, check:

• Is Googlebot crawling the new URLs?
• Is it still spending significant crawl budget on old URLs?
• Are important pages being crawled?
• Are redirects being repeatedly requested?

Log analysis often reveals issues before they're reflected in Search Console.

7. Set up automated monitoring

Real-time monitoring helps catch accidental regressions.

Track alerts for:

• new 404s
• robots.txt changes
• sitemap changes
• canonical changes
• pages becoming noindex
• sudden drops in indexed URLs

Recommended stack by organization size

Small sites (<10k URLs):

• Screaming Frog
• Google Search Console
• Google Analytics
• Ahrefs or Semrush

Medium sites (10k–500k URLs):

• Screaming Frog
• Sitebulb
• Google Search Console
• GA4
• Ahrefs/Semrush
• Log analysis (ELK or Splunk)

Enterprise sites (500k+ URLs):

• Botify
• ContentKing
• Screaming Frog
• Google Search Console
• GA4
• Server log analysis
• Enterprise rank tracking

Migration KPI checklist

A successful migration generally looks like this after the first few weeks:

• ✅ 99%+ of legacy URLs return correct 301 redirects
• ✅ No redirect chains or loops
• ✅ XML sitemaps submitted and processed
• ✅ No unexpected noindex or robots.txt blocks
• ✅ Canonical tags point to the new URLs
• ✅ Googlebot increasingly crawls the new URLs
• ✅ Organic traffic returns to within ~90–100% of pre-migration levels (allowing for seasonality)
• ✅ High-value keywords recover their rankings
• ✅ Conversions and revenue remain stable or recover quickly

This combination of redirect validation, crawl auditing, indexation monitoring, and analytics provides a comprehensive view of whether the migration has preserved both technical SEO integrity and organic performance.

For a CMS migration, you'll typically want a combination of crawling, technical SEO, analytics, and log analysis tools. Here's a practical stack organized by what you're validating.

1. Validate redirects

This is the highest priority immediately after launch.

Use Screaming Frog to:

• Crawl the old URL list.
• Verify every URL returns a 301.
• Confirm redirects go directly to the final destination (no chains).
• Identify:
  • 404s
  • 500s
  • redirect loops
  • 302s that should be 301s

Compare:

• Old URL inventory
• Redirect map
• Live crawl

Success target:

• >99% of legacy URLs correctly redirected.

2. Validate indexation

Google Search Console becomes your primary source.

Monitor:

• Indexed pages
• Excluded pages
• Soft 404s
• Duplicate pages
• Crawled – currently not indexed
• Noindex mistakes

Also submit:

• new XML sitemap
• updated sitemap index

Watch the Index Coverage report daily during the first few weeks.

3. Check crawlability

Run a full crawl of the new site.

Look for:

• orphan pages
• broken internal links
• canonical pointing to old URLs
• robots.txt blocking important sections
• incorrect noindex tags
• pagination
• hreflang
• structured data validation

4. Monitor traffic retention

In GA4 compare:

• Organic sessions
• Organic users
• Landing page traffic
• Conversion rate
• Revenue/leads
• Top 100 landing pages

Rather than looking only at total traffic, compare the top-performing landing pages before and after migration to identify isolated issues.

5. Monitor rankings

Using Ahrefs or Semrush:

Track:

• branded keywords
• top commercial keywords
• informational content
• category pages
• highest-value landing pages

Some ranking fluctuation is expected for 2–6 weeks, but large sustained drops often indicate migration issues.

6. Analyze server logs

If you have access to server logs, check:

• Is Googlebot crawling the new URLs?
• Is it still spending significant crawl budget on old URLs?
• Are important pages being crawled?
• Are redirects being repeatedly requested?

Log analysis often reveals issues before they're reflected in Search Console.

7. Set up automated monitoring

Real-time monitoring helps catch accidental regressions.

Track alerts for:

• new 404s
• robots.txt changes
• sitemap changes
• canonical changes
• pages becoming noindex
• sudden drops in indexed URLs

Recommended stack by organization size

Small sites (<10k URLs):

• Screaming Frog
• Google Search Console
• Google Analytics
• Ahrefs or Semrush

Medium sites (10k–500k URLs):

• Screaming Frog
• Sitebulb
• Google Search Console
• GA4
• Ahrefs/Semrush
• Log analysis (ELK or Splunk)

Enterprise sites (500k+ URLs):

• Botify
• ContentKing
• Screaming Frog
• Google Search Console
• GA4
• Server log analysis
• Enterprise rank tracking

Migration KPI checklist

A successful migration generally looks like this after the first few weeks:

• ✅ 99%+ of legacy URLs return correct 301 redirects
• ✅ No redirect chains or loops
• ✅ XML sitemaps submitted and processed
• ✅ No unexpected noindex or robots.txt blocks
• ✅ Canonical tags point to the new URLs
• ✅ Googlebot increasingly crawls the new URLs
• ✅ Organic traffic returns to within ~90–100% of pre-migration levels (allowing for seasonality)
• ✅ High-value keywords recover their rankings
• ✅ Conversions and revenue remain stable or recover quickly

This combination of redirect validation, crawl auditing, indexation monitoring, and analytics provides a comprehensive view of whether the migration has preserved both technical SEO integrity and organic performance.

For a CMS migration, you'll typically want a combination of crawling, technical SEO, analytics, and log analysis tools. Here's a practical stack organized by what you're validating.

1. Validate redirects

This is the highest priority immediately after launch.

Use Screaming Frog to:

• Crawl the old URL list.
• Verify every URL returns a 301.
• Confirm redirects go directly to the final destination (no chains).
• Identify:
  • 404s
  • 500s
  • redirect loops
  • 302s that should be 301s

Compare:

• Old URL inventory
• Redirect map
• Live crawl

Success target:

• >99% of legacy URLs correctly redirected.

2. Validate indexation

Google Search Console becomes your primary source.

Monitor:

• Indexed pages
• Excluded pages
• Soft 404s
• Duplicate pages
• Crawled – currently not indexed
• Noindex mistakes

Also submit:

• new XML sitemap
• updated sitemap index

Watch the Index Coverage report daily during the first few weeks.

3. Check crawlability

Run a full crawl of the new site.

Look for:

• orphan pages
• broken internal links
• canonical pointing to old URLs
• robots.txt blocking important sections
• incorrect noindex tags
• pagination
• hreflang
• structured data validation

4. Monitor traffic retention

In GA4 compare:

• Organic sessions
• Organic users
• Landing page traffic
• Conversion rate
• Revenue/leads
• Top 100 landing pages

Rather than looking only at total traffic, compare the top-performing landing pages before and after migration to identify isolated issues.

5. Monitor rankings

Using Ahrefs or Semrush:

Track:

• branded keywords
• top commercial keywords
• informational content
• category pages
• highest-value landing pages

Some ranking fluctuation is expected for 2–6 weeks, but large sustained drops often indicate migration issues.

6. Analyze server logs

If you have access to server logs, check:

• Is Googlebot crawling the new URLs?
• Is it still spending significant crawl budget on old URLs?
• Are important pages being crawled?
• Are redirects being repeatedly requested?

Log analysis often reveals issues before they're reflected in Search Console.

7. Set up automated monitoring

Real-time monitoring helps catch accidental regressions.

Track alerts for:

• new 404s
• robots.txt changes
• sitemap changes
• canonical changes
• pages becoming noindex
• sudden drops in indexed URLs

Recommended stack by organization size

Small sites (<10k URLs):

• Screaming Frog
• Google Search Console
• Google Analytics
• Ahrefs or Semrush

Medium sites (10k–500k URLs):

• Screaming Frog
• Sitebulb
• Google Search Console
• GA4
• Ahrefs/Semrush
• Log analysis (ELK or Splunk)

Enterprise sites (500k+ URLs):

• Botify
• ContentKing
• Screaming Frog
• Google Search Console
• GA4
• Server log analysis
• Enterprise rank tracking

Migration KPI checklist

A successful migration generally looks like this after the first few weeks:

• ✅ 99%+ of legacy URLs return correct 301 redirects
• ✅ No redirect chains or loops
• ✅ XML sitemaps submitted and processed
• ✅ No unexpected noindex or robots.txt blocks
• ✅ Canonical tags point to the new URLs
• ✅ Googlebot increasingly crawls the new URLs
• ✅ Organic traffic returns to within ~90–100% of pre-migration levels (allowing for seasonality)
• ✅ High-value keywords recover their rankings
• ✅ Conversions and revenue remain stable or recover quickly

This combination of redirect validation, crawl auditing, indexation monitoring, and analytics provides a comprehensive view of whether the migration has preserved both technical SEO integrity and organic performance.

For a CMS migration, you'll typically want a combination of crawling, technical SEO, analytics, and log analysis tools. Here's a practical stack organized by what you're validating.

1. Validate redirects

This is the highest priority immediately after launch.

Use Screaming Frog to:

• Crawl the old URL list.
• Verify every URL returns a 301.
• Confirm redirects go directly to the final destination (no chains).
• Identify:
  • 404s
  • 500s
  • redirect loops
  • 302s that should be 301s

Compare:

• Old URL inventory
• Redirect map
• Live crawl

Success target:

• >99% of legacy URLs correctly redirected.

2. Validate indexation

Google Search Console becomes your primary source.

Monitor:

• Indexed pages
• Excluded pages
• Soft 404s
• Duplicate pages
• Crawled – currently not indexed
• Noindex mistakes

Also submit:

• new XML sitemap
• updated sitemap index

Watch the Index Coverage report daily during the first few weeks.

3. Check crawlability

Run a full crawl of the new site.

Look for:

• orphan pages
• broken internal links
• canonical pointing to old URLs
• robots.txt blocking important sections
• incorrect noindex tags
• pagination
• hreflang
• structured data validation

4. Monitor traffic retention

In GA4 compare:

• Organic sessions
• Organic users
• Landing page traffic
• Conversion rate
• Revenue/leads
• Top 100 landing pages

Rather than looking only at total traffic, compare the top-performing landing pages before and after migration to identify isolated issues.

5. Monitor rankings

Using Ahrefs or Semrush:

Track:

• branded keywords
• top commercial keywords
• informational content
• category pages
• highest-value landing pages

Some ranking fluctuation is expected for 2–6 weeks, but large sustained drops often indicate migration issues.

6. Analyze server logs

If you have access to server logs, check:

• Is Googlebot crawling the new URLs?
• Is it still spending significant crawl budget on old URLs?
• Are important pages being crawled?
• Are redirects being repeatedly requested?

Log analysis often reveals issues before they're reflected in Search Console.

7. Set up automated monitoring

Real-time monitoring helps catch accidental regressions.

Track alerts for:

• new 404s
• robots.txt changes
• sitemap changes
• canonical changes
• pages becoming noindex
• sudden drops in indexed URLs

Recommended stack by organization size

Small sites (<10k URLs):

• Screaming Frog
• Google Search Console
• Google Analytics
• Ahrefs or Semrush

Medium sites (10k–500k URLs):

• Screaming Frog
• Sitebulb
• Google Search Console
• GA4
• Ahrefs/Semrush
• Log analysis (ELK or Splunk)

Enterprise sites (500k+ URLs):

• Botify
• ContentKing
• Screaming Frog
• Google Search Console
• GA4
• Server log analysis
• Enterprise rank tracking

Migration KPI checklist

A successful migration generally looks like this after the first few weeks:

• ✅ 99%+ of legacy URLs return correct 301 redirects
• ✅ No redirect chains or loops
• ✅ XML sitemaps submitted and processed
• ✅ No unexpected noindex or robots.txt blocks
• ✅ Canonical tags point to the new URLs
• ✅ Googlebot increasingly crawls the new URLs
• ✅ Organic traffic returns to within ~90–100% of pre-migration levels (allowing for seasonality)
• ✅ High-value keywords recover their rankings
• ✅ Conversions and revenue remain stable or recover quickly

This combination of redirect validation, crawl auditing, indexation monitoring, and analytics provides a comprehensive view of whether the migration has preserved both technical SEO integrity and organic performance.

For a CMS migration, it's useful to separate validation into three areas: redirects, indexation, and traffic/performance. No single tool covers everything, so the strongest approach is a combination of crawler, search engine data, analytics, and log analysis.

1. Redirect validation

This is the first thing to verify after launch.

Use a crawler like Screaming Frog to:

• Crawl all old URLs
• Confirm every important URL returns 301
• Ensure destination URL is correct
• Detect:
  • redirect chains
  • redirect loops
  • 302s that should be 301s
  • 404s
  • soft 404s

For enterprise sites (100k+ URLs), compare:

• old XML sitemap
• new XML sitemap
• URL mapping spreadsheet
• crawl results

Typical success metrics:

• >99% of legacy URLs resolve correctly
• No redirect chains longer than one hop
• No important URLs returning 404

2. Indexation validation

Immediately after migration, monitor:

Google Search Console

Check:

• Pages indexed
• Coverage report
• "Page with redirect"
• "Duplicate without user-selected canonical"
• Crawled, currently not indexed
• Submitted but not indexed

Also inspect:

• XML sitemap submission
• Sitemap freshness
• Canonical tags
• Robots.txt
• noindex tags

Watch indexation daily for the first 2–3 weeks.

3. Crawl validation

Run a complete crawl of the new site.

Validate:

• title tags
• meta descriptions
• canonicals
• H1s
• status codes
• hreflang
• pagination
• structured data
• internal links
• orphan pages
• broken images
• JS rendering (if applicable)

Compare crawl statistics before and after migration.

4. Traffic retention

Your analytics platform should answer questions like:

• Did organic traffic recover?
• Which landing pages lost visits?
• Which templates lost traffic?
• Did conversion rate change?

Useful reports include:

• Organic sessions
• Organic conversions
• Landing pages
• Revenue (for ecommerce)
• Device split
• Country split

Compare:

• Week over week
• Year over year (to account for seasonality)

5. Ranking validation

Track:

• Head terms
• Category terms
• Long-tail keywords
• Brand keywords

A rank tracker should monitor daily changes for the first month.

Typical expectations:

• Small fluctuations for 1–3 weeks
• Recovery within 4–8 weeks for well-executed migrations
• Persistent losses often indicate technical issues

6. Googlebot behavior

Server logs provide insight into how search engines interact with the new site.

Look for:

• Increased 404 requests
• Googlebot following redirects
• Crawl frequency
• Crawl budget shifts
• High-value pages being crawled

This often reveals issues before they appear in Search Console.

7. Core Web Vitals

A new CMS often changes:

• HTML structure
• JavaScript
• CSS
• images

Monitor:

• LCP
• CLS
• INP

Poor performance can affect rankings and user experience.

Useful monitoring dashboards

Create a migration dashboard with:

• Organic sessions
• Indexed pages
• 404 count
• Redirect errors
• Crawl errors
• Average ranking
• Top 100 landing pages
• Revenue (if applicable)
• Googlebot crawl volume
• Core Web Vitals

Update it daily for the first month.

Recommended tool stack by budget

Free

• Google Search Console
• Bing Webmaster Tools
• Google Analytics 4
• PageSpeed Insights
• Lighthouse

Mid-market

• Screaming Frog
• Ahrefs or Semrush
• Looker Studio
• Google Search Console
• Google Analytics 4

Enterprise

• Botify
• Conductor
• Deepcrawl (Lumar)
• Oncrawl
• Splunk or ELK for log analysis
• STAT Search Analytics
• Adobe Analytics (if already in use)

A practical post-migration checklist

During the first 30 days, monitor these key indicators:

• Redirects: No critical 404s, no redirect chains, all priority legacy URLs return a single 301 to the intended destination.
• Indexation: XML sitemaps submitted, indexed page count trending toward expected levels, no unexpected spikes in excluded pages.
• Traffic: Organic sessions and conversions remain stable or recover toward pre-migration baselines after initial fluctuations.
• Rankings: Priority keywords recover within expected timeframes, with no sustained losses across major page groups.
• Crawling: Search engine bots are increasingly crawling the new URLs and reducing requests to legacy URLs.
• Performance: Core Web Vitals and page load times remain at or above pre-migration levels.

Using these tools together provides a comprehensive view of whether the migration preserved SEO equity, maintained discoverability, and retained organic traffic.

A CMS migration is one of the highest-risk SEO projects because rankings can be affected by redirect errors, crawl issues, and changes to page structure. The best approach is to combine crawling tools, search engine data, analytics, and log analysis.

Here's a practical toolkit organized by what you need to validate.

1. Validate redirects

This is the highest priority immediately after launch.

Run a crawl of:

• Old URLs
• XML sitemap
• Top landing pages
• High-value pages from analytics
• Backlinked URLs

Verify:

• Every old URL returns 301
• No 302s unless intentional
• No redirect chains
• No redirect loops
• Final destination is a 200 OK
• Canonicals point to final URLs

A good benchmark is:

• 0 redirect loops
• <1% broken redirects
• No important URLs returning 404

2. Verify indexation

Within the first few days monitor:

• Indexed pages
• Excluded pages
• Crawl anomalies
• Submitted vs indexed URLs
• New sitemap processing

Watch for spikes in:

• Soft 404
• Duplicate without canonical
• Crawled—not indexed
• Blocked by robots.txt
• Noindex tags accidentally deployed

3. Monitor organic traffic retention

Compare:

• Week over week
• Year over year
• Pre-migration baseline

Track:

• Organic sessions
• Users
• Conversions
• Revenue
• Landing pages

Segment by:

• Blog
• Product pages
• Category pages
• Country
• Device

A migration can temporarily fluctuate, but large sustained drops deserve investigation.

4. Watch keyword rankings

Monitor:

• Brand terms
• High-value commercial terms
• Long-tail keywords
• Featured snippets

Look for:

• Sudden ranking drops
• Pages replaced by incorrect URLs
• Cannibalization
• Lost snippets

Daily tracking during the first 2–4 weeks is often worthwhile.

5. Crawl the new site

Perform a full crawl looking for:

• Broken links
• Missing metadata
• Canonical changes
• Missing H1s
• Duplicate titles
• Missing structured data
• Image issues
• Internal linking changes
• Orphan pages

Compare the crawl against the old site to identify pages that disappeared or changed unexpectedly.

6. Validate XML sitemaps

Confirm that:

• Only canonical URLs are included
• All URLs return 200
• No redirected URLs
• No noindex pages
• No parameter URLs
• Updated sitemap submitted to search engines

7. Review server logs

Log analysis reveals what search engines are actually doing, not just what should happen.

Check:

• Googlebot hits on old URLs
• Googlebot following redirects
• Crawl budget distribution
• Frequent 404 requests
• Crawl rate changes
• Important pages being crawled

8. Monitor Core Web Vitals

Ensure the migration hasn't introduced performance regressions.

Watch:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)

Also monitor:

• JavaScript errors
• Server response time
• CDN behavior
• Cache headers

9. Compare before vs after

Create a migration dashboard including:

10. Set up automated alerts

Configure alerts for:

• 404 spikes
• Organic traffic drops (e.g., >20%)
• Indexed page changes
• Sitemap errors
• Server downtime
• Robots.txt changes
• Noindex tag deployment
• Significant ranking losses

A recommended migration stack

For most organizations, this combination provides strong coverage:

• Redirect validation: Screaming Frog SEO Spider
• Technical SEO: Sitebulb or Lumar
• Indexation: Google Search Console and Bing Webmaster Tools
• Traffic & conversions: Google Analytics (GA4) or Adobe Analytics
• Rank tracking: Semrush or Ahrefs
• Log analysis: Splunk or ELK Stack
• Performance: Core Web Vitals reporting and real user monitoring

This setup covers the three outcomes you mentioned—redirect integrity, indexation health, and traffic retention—while also helping identify issues quickly if rankings or organic traffic decline after launch.

For a CMS migration, you'll typically want a combination of crawling, technical SEO, analytics, and log analysis tools. Here's a practical stack organized by what you're validating.

1. Validate redirects

This is the highest priority immediately after launch.

Use Screaming Frog to:

• Crawl the old URL list.
• Verify every URL returns a 301.
• Confirm redirects go directly to the final destination (no chains).
• Identify:
  • 404s
  • 500s
  • redirect loops
  • 302s that should be 301s

Compare:

• Old URL inventory
• Redirect map
• Live crawl

Success target:

• >99% of legacy URLs correctly redirected.

2. Validate indexation

Google Search Console becomes your primary source.

Monitor:

• Indexed pages
• Excluded pages
• Soft 404s
• Duplicate pages
• Crawled – currently not indexed
• Noindex mistakes

Also submit:

• new XML sitemap
• updated sitemap index

Watch the Index Coverage report daily during the first few weeks.

3. Check crawlability

Run a full crawl of the new site.

Look for:

• orphan pages
• broken internal links
• canonical pointing to old URLs
• robots.txt blocking important sections
• incorrect noindex tags
• pagination
• hreflang
• structured data validation

4. Monitor traffic retention

In GA4 compare:

• Organic sessions
• Organic users
• Landing page traffic
• Conversion rate
• Revenue/leads
• Top 100 landing pages

Rather than looking only at total traffic, compare the top-performing landing pages before and after migration to identify isolated issues.

5. Monitor rankings

Using Ahrefs or Semrush:

Track:

• branded keywords
• top commercial keywords
• informational content
• category pages
• highest-value landing pages

Some ranking fluctuation is expected for 2–6 weeks, but large sustained drops often indicate migration issues.

6. Analyze server logs

If you have access to server logs, check:

• Is Googlebot crawling the new URLs?
• Is it still spending significant crawl budget on old URLs?
• Are important pages being crawled?
• Are redirects being repeatedly requested?

Log analysis often reveals issues before they're reflected in Search Console.

7. Set up automated monitoring

Real-time monitoring helps catch accidental regressions.

Track alerts for:

• new 404s
• robots.txt changes
• sitemap changes
• canonical changes
• pages becoming noindex
• sudden drops in indexed URLs

Recommended stack by organization size

Small sites (<10k URLs):

• Screaming Frog
• Google Search Console
• Google Analytics
• Ahrefs or Semrush

Medium sites (10k–500k URLs):

• Screaming Frog
• Sitebulb
• Google Search Console
• GA4
• Ahrefs/Semrush
• Log analysis (ELK or Splunk)

Enterprise sites (500k+ URLs):

• Botify
• ContentKing
• Screaming Frog
• Google Search Console
• GA4
• Server log analysis
• Enterprise rank tracking

Migration KPI checklist

A successful migration generally looks like this after the first few weeks:

• ✅ 99%+ of legacy URLs return correct 301 redirects
• ✅ No redirect chains or loops
• ✅ XML sitemaps submitted and processed
• ✅ No unexpected noindex or robots.txt blocks
• ✅ Canonical tags point to the new URLs
• ✅ Googlebot increasingly crawls the new URLs
• ✅ Organic traffic returns to within ~90–100% of pre-migration levels (allowing for seasonality)
• ✅ High-value keywords recover their rankings
• ✅ Conversions and revenue remain stable or recover quickly

This combination of redirect validation, crawl auditing, indexation monitoring, and analytics provides a comprehensive view of whether the migration has preserved both technical SEO integrity and organic performance.

A CMS migration can affect three major areas: redirect accuracy, search engine indexation, and organic traffic/performance. The most effective approach is to use a combination of crawling, analytics, and search engine tools rather than relying on a single platform.

Here's a practical toolkit organized by objective:

1. Redirect validation (highest priority)

Before launch:

• Crawl the old site.
• Crawl the staging site.
• Compare every legacy URL.
• Verify every important URL returns:
  • Old URL → 301
  • New URL → 200
• Eliminate:
  • 302 redirects
  • redirect chains
  • redirect loops
  • orphan pages
  • 404s

A good benchmark is 95–100% of indexed URLs successfully redirected.

2. Indexation monitoring

Immediately after launch:

Monitor in Google Search Console:

• Submitted vs indexed pages
• Coverage errors
• Excluded pages
• Soft 404s
• Canonical issues
• Crawl anomalies
• Sitemap status

Also inspect:

• robots.txt
• XML sitemaps
• noindex tags
• canonical tags
• hreflang (if applicable)

3. Traffic retention

Compare:

• 30 days pre-migration
• 30 days post-migration
• 60–90 days after launch

Track:

• Organic sessions
• Revenue
• Leads
• Top landing pages
• Bounce/engagement
• Conversion rate

Segment by:

• Device
• Country
• Directory
• Template type

4. Ranking retention

Daily for the first few weeks:

• Top keywords
• Brand keywords
• Non-brand keywords
• Local rankings
• Featured snippets
• AI Overviews (if relevant to your market)

Expect some short-term movement, but significant sustained losses can indicate migration issues.

5. Crawl health

Run a full crawl after launch and verify:

• No internal links point to old URLs
• All internal links use the final destination (not redirected URLs)
• No broken links
• No duplicate title tags
• No duplicate meta descriptions
• Correct canonicals
• Correct status codes
• Images load properly
• Structured data validates

6. Server log analysis

This is often overlooked but highly valuable.

Analyze:

• Googlebot requests
• Bingbot requests
• Most-crawled URLs
• 404 hits
• Redirect frequency
• Crawl budget usage

This can reveal important pages that search engines still request but users rarely visit.

7. Core migration dashboard

A simple dashboard should include:

• Indexed pages
• Organic traffic
• Top 100 landing pages
• Revenue/conversions
• 404 errors
• Redirect errors
• Crawl errors
• Average position
• Click-through rate
• Sitemap status
• Page speed/Core Web Vitals

Recommended tool stack by budget

Small websites

• Google Search Console
• Google Analytics 4
• Screaming Frog SEO Spider

Mid-size sites (10k–500k URLs)

• Google Search Console
• Google Analytics 4
• Screaming Frog SEO Spider
• Ahrefs or Semrush
• Sitebulb

Large enterprise migrations (500k+ URLs)

• Google Search Console
• Google Analytics 4
• Lumar (formerly Deepcrawl)
• Botify
• Splunk or ELK Stack
• Semrush or Ahrefs
• Datadog (or similar observability platform)

For enterprise CMS migrations, teams often define success with measurable thresholds, such as:

• ≥99% of legacy URLs returning valid 301 redirects
• No increase in 404 errors on high-value pages
• 95–100% of priority pages reindexed within several weeks (timing varies by site size and crawl frequency)
• Organic traffic returning to roughly pre-migration levels within 4–12 weeks, assuming no major content or structural changes
• No persistent loss of rankings for critical keywords beyond normal post-migration volatility

Using these tools together provides visibility into whether the migration preserved SEO equity and user traffic, and helps identify issues quickly if performance deviates from expectations.

A CMS migration can preserve SEO, but it's worth validating three areas separately: redirects, indexation, and traffic/performance. No single tool does everything well, so most teams use a combination.

1. Redirect validation

This is usually the highest-risk area after launch.

Screaming Frog SEO Spider

• Crawl the old URL list.
• Confirm every old URL returns a 301.
• Verify it resolves to the intended new page.
• Detect:
  • redirect chains
  • redirect loops
  • 404s
  • soft 404s
  • incorrect destination pages

If you have thousands of URLs, import your redirect mapping and crawl in List Mode.

Also compare:

• old XML sitemap
• new XML sitemap
• analytics landing pages
• top pages from Search Console

These datasets often uncover URLs that were forgotten.

2. Indexation monitoring

Google Search Console

This becomes your primary dashboard.

Watch:

• Pages indexed
• Pages excluded
• Crawl stats
• Submitted vs indexed
• Canonical selection
• Soft 404s
• Redirect errors

Submit:

• new XML sitemap
• image sitemap (if applicable)
• news sitemap (if applicable)

Inspect important URLs individually to confirm:

• Google sees the correct canonical
• robots directives are correct
• page is crawlable

3. Traffic retention

Migration success is usually measured over 4–12 weeks.

Monitor:

• Organic sessions
• Organic conversions
• Revenue
• Landing pages
• Average ranking
• Clicks
• Impressions
• CTR

Compare:

• 7 days before vs after
• 28 days before vs after
• Year-over-year where seasonality matters

4. Crawl comparison

Run a crawl:

Before migration

• Export all URLs
• Titles
• Meta descriptions
• H1s
• Canonicals
• Status codes
• Internal links

Run the same crawl after launch.

Compare:

• missing pages
• duplicate titles
• broken canonicals
• orphan pages
• noindex pages
• robots blocks

5. Log file analysis

For larger sites (50k+ URLs), server logs provide valuable insight.

Tools include:

• Screaming Frog Log File Analyser
• Splunk
• ELK Stack

Look for:

• Googlebot hitting redirected URLs
• crawl budget shifts
• repeated 404s
• excessive redirects

6. Ranking monitoring

Track:

• highest-traffic keywords
• highest-converting keywords
• branded terms
• non-branded terms
• category keywords

Visibility should remain relatively stable. Some fluctuation is normal for a few weeks, but sustained declines warrant investigation.

7. Internal link validation

Common migration issues include:

• links pointing to redirects instead of final URLs
• broken navigation
• incorrect breadcrumbs
• outdated canonical URLs
• outdated image URLs

A crawl will identify these quickly.

8. Core Web Vitals

Many CMS migrations affect performance.

Measure:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)

Use:

• Google Search Console Core Web Vitals report
• Lighthouse
• PageSpeed Insights
• Chrome DevTools

9. Automated monitoring

Set alerts for:

• spikes in 404 errors
• increases in 5xx responses
• drops in organic traffic
• decreases in indexed pages
• sitemap fetch failures

These help surface issues before they significantly impact SEO.

Recommended tool stack

For most migrations, a practical combination is:

• Screaming Frog — crawl validation, redirects, metadata, canonicals, internal links
• Google Search Console — indexation, crawl errors, sitemap status, search performance
• Google Analytics 4 — traffic, engagement, conversions
• Ahrefs or Semrush — keyword visibility and backlink monitoring
• Looker Studio — unified migration dashboard combining GA4 and Search Console data

A practical migration validation checklist

• ✅ All legacy URLs return a single 301 to the correct destination.
• ✅ No redirect chains or loops.
• ✅ XML sitemap contains only canonical, indexable URLs.
• ✅ No accidental noindex directives on production pages.
• ✅ Canonical tags point to the new URLs.
• ✅ Internal links reference final URLs, not redirected ones.
• ✅ Robots.txt allows crawling of key content.
• ✅ Search Console shows the new sitemap processed successfully.
• ✅ Top landing pages retain traffic and rankings after launch.
• ✅ Core Web Vitals remain stable or improve.
• ✅ 404s, 5xx errors, and crawl anomalies are monitored continuously for at least the first month after launch.

Following this workflow gives you good coverage of both technical correctness (redirects and crawlability) and business outcomes (traffic, rankings, and conversions).