Traffic & Conversion Mapping

Context

A migration that ignores value treats a checkout page and an archived press release as equals — and that is how revenue paths end up as 404s while nobody-reads-it URLs get perfect 1:1 redirects. Traffic and conversion mapping fixes the priority order: it attaches measured sessions, conversions, and revenue to every URL in the inventory so redirect effort, QA depth, and rollback sensitivity all follow business value. Webmasters, SEO engineers, site architects, and technical PMs run it inside the Pre-Migration Auditing & Risk Assessment window, after the crawl baseline exists and before the redirect map is frozen.

The output is a value-tiered URL list plus a continuity plan for attribution itself — because a migration that preserves rankings but breaks GA4 cross-domain tracking has still blinded the business during its most fragile week.

Joining the inventory to analytics revenue splits URLs into tiers, each mapping to a redirect and QA policy.

Pre-flight Checks

Capture indexation, traffic, and conversion states quantitatively before touching architecture.

Run a full crawl via Crawl Baseline Generation to document status codes, link equity, and render-blocking resources.
Map GA4 conversion events to current URL paths using BigQuery exports and custom-dimension tagging.
Record DNS TTLs, CDN cache headers, and WAF rules to prevent stale delivery during propagation.
Complete readiness scoring in the Pre-Migration Auditing & Risk Assessment repo before freezing CMS content.
Verify database snapshot integrity and enforce a strict content freeze across environments.

Execution Steps

1. Join Inventory to Revenue and Tier It

Make priority objective by attaching money to each URL. Export GA4 sessions, conversions, and assisted revenue plus Search Console clicks, join them to the crawl inventory on path, and split into high/medium/low tiers. Feed the tiers forward as the redirect priority matrix so high-value paths get 1:1 mappings and full QA.

2. Preserve Attribution Across the Domain Boundary

Stop the migration from blinding analytics. Implement Mapping Legacy Traffic to New URL Structures to carry UTM parameters, referral paths, and session IDs across the transition, and configure GA4 cross-domain linker plus server-side GTM to avoid attribution fragmentation.

3. Validate Tracking in Staging

Catch tracking breaks before they cost a launch week. Verify conversion pixels and data streams in staging with browser network inspectors and Tag Assistant, confirming events fire with correct parameters before DNS cutover.

4. Run Dual-Stream During Propagation

Keep continuity while the world resolves to two answers. Maintain dual-domain GA4 data streams until global propagation completes and _ga cookies stabilise, and hand the value tiers to Stakeholder Communication Plans so monitoring focus follows revenue post-launch.

Configs / Commands

# Nginx: preserve query strings on 301 — use $is_args$args to append the original
location ~ ^/legacy-category/(.*)$ {
    return 301 /new-structure/$1$is_args$args;   # keeps UTM + tracking params intact
}

# dig: verify SOA TTL and reduce 48 h before cutover via the registrar API
dig @ns1.example.com example.com SOA +short      # confirm current minimum TTL

// GA4 cross-domain linker (GTM container init) — preserves attribution across domains
gtag('set', 'linker', { domains: ['old-domain.com', 'new-domain.com'] });

# Identify 4xx/5xx in access logs for post-launch triage, ranked by frequency
awk '$9 ~ /^[45]/ {print $9, $7}' access.log \
  | sort | uniq -c | sort -rn > migration_errors.csv   # top offenders first

Validation

Systematic checks before production traffic routing.

Canonical tags, hreflang, and robots.txt verified on staging (Screaming Frog list mode)
Redirect chains tested single-hop via curl -sIL; no 301 loops or orphaned paths
JavaScript hydration, structured-data parity, and sitemap readiness checked in GSC URL Inspection
_ga cookie persistence verified across subdomains in dev tools
High-value tier URLs each confirmed mapped 1:1 with correct Location header

Avoid these deployment failures:

Regex over-matching that silently creates redirect chains — test representative samples first.
GA4 session fragmentation from missing _ga cookie preservation across subdomains.
CDN cache invalidation failures serving a legacy robots.txt to Googlebot.
Headless CMS hydration delays stalling server-side rendering and indexation.
rel="canonical" left pointing at the legacy domain, causing duplicate-content dilution.

Rollback Triggers

Pre-author scripts and assign ownership; fire automatically on threshold breach.

5xx error rate exceeds 2% across monitored endpoints.
Organic traffic drops >30% within 2 h of cutover.
Any critical conversion endpoint returns a non-200 status.
Crawl-budget exhaustion or conversion-rate drop flagged by Datadog/New Relic synthetic monitors.

FAQ

How do I preserve conversion attribution during DNS propagation? Configure cross-domain linker tracking in GTM, run dual-domain GA4 streams until propagation completes, and verify _ga cookie persistence in browser dev tools during synthetic testing.

What is the optimal TTL reduction timeline? Lower TTL to 300 s 48 h before cutover, verify propagation with dig @8.8.8.8 domain.com +short, run the record swap in a low-traffic window, and watch resolver latency for the first 2 h.

How can I validate redirect mapping without crawling the live site? Use staging curl -sIL batch scripts and Screaming Frog list mode against the pre-exported inventory to confirm 301 accuracy, single-hop chains, and destination parity before touching production DNS.

What triggers an immediate rollback? A 5xx rate above 2%, organic traffic down >30% within 2 h, or any critical conversion endpoint returning non-200 — with rollback scripts pre-tested in staging before the cutover window opens.

← Back to Pre-Migration Auditing & Risk Assessment