Agency_

Solutions/Technical SEO & Migrations
Site 2 Pre-Migration GA4 Trawler

Trawl Pre-Migration & Orphaned URLs from Google Analytics 4 Before You Lose Traffic

If a historical page on your old domain (Site 2) isn’t linked anywhere on your new build (Site 1), crawling your new site will never find it—yet users, bookmarks, and backlinks still hit it daily. Agency auto-discovers Site 2’s GA4 property, trawls 1 Year or All Time of traffic URLs backwards from your exact Migration Date with strict hostName filtering, strips tracking parameters, and batch-verifies every 301 hop toward 100/100 on your Migration Progress Dial.

By Shaun Anderson•AI Specialists: Shaun AI & James AI•Route: /site-migration
Per-Project 1-Click OAuth / API Connector
AES-256-GCM Encrypted VaultManaged by Shaun AI & James AI

Trawl Site 2 Historical & Orphan URLs Backwards from Migration Date

Connect Google Analytics once, enter your Old / Redirected Domain in Slot 2 and your Migration Date in /site-migration, and import 1 Year or All Time of parameter-clean Site 2 URLs—never mixing Slot 1 URLs even in shared GA4 properties.

1Set Slot 2 (Old / Redirected Domain) and your Migration Date inside SEO → Migration (/site-migration).
2Choose 1 Year Before Migration or All Time—Agency auto-discovers Site 2’s GA4 property, filters strictly by hostName, and strips UTM/session parameters.
3Click Import URLs into Step 3, run paced 25-URL HTTP checks saved permanently to PostgreSQL, and drive the Migration Progress Dial to 100.
⚡Migration-Date Anchored Lookback (1y / All Time) + Strict Site 2 HostName Isolation + Permanent PostgreSQL Workspace
Start in Under 60 Seconds
Choose your plan & launch Site 2 GA4 Pre-Migration Trawler inside your workspace
View Plans & Connect Site 2 GA4 Pre-Migration TrawlerSign In & Open Site 2 GA4 Pre-Migration Trawler →

1. Why Crawling Your New Site Misses Old-Domain Orphan URLs That Need 301s

During a domain move or replatforming, standard crawlers inspect what exists on your current project domain (Slot 1). Meanwhile, years of marketing campaigns, retired product slugs, and legacy articles on your Old Domain (Site 2) vanish completely unless you inspect Site 2’s historical Google Analytics traffic right up to launch day.

Inside Step 2 of SEO → Migration (/site-migration), Agency automatically searches your accessible projects and Google Analytics Admin streams to match your Slot 2 Old Domain, anchors a 1-Year or All-Time date window ending precisely on your Migration Date, filters raw rows strictly by hostName so Slot 1 URLs never leak from cross-domain tags, removes utm_*/gclid/fbclid/session query noise, aggregates clean views per canonical path, and lets you probe every URL’s HTTP redirect permanently into PostgreSQL.

Auto-Discovered Slot 2 GA4 Property Matching

Scans your connected Google Analytics Admin accountSummaries, dataStreams, and workspace projects to surface the matching GA4 property for Site 2 automatically.

Migration-Date Anchored Lookback (1 Year or All Time)

Rewinds 365 days or back to GA4 inception (2015-08-14) ending directly on your Migration Date—excluding noisy post-launch dates cleanly.

Strict HostName Filtering + Parameter Stripping

Guards shared cross-domain GA4 properties by keeping only Site 2 hostName rows while collapsing ?utm_*, gclid, fbclid, and sort noise onto canonical paths.

HTTP Status Validation Toward 100/100 Dial

Feeds imported orphan URLs straight into Step 3’s 25-URL HTTP checker so every legacy Site 2 slug resolves with a verified 301 onto Slot 1 (example-1 / active domain) in PostgreSQL.


2. Step-by-Step: How to Trawl & Verify Site 2 URLs with GA4

Make sure zero traffic-earning legacy slugs on Site 2 slip into post-launch 404s:

Step 1: Enter Slot 2 (Old Domain) & Migration Date in /site-migration

Step 1 • Select Site 2 & Date

Leave your active site locked in Slot 1, enter your Old / Redirected Domain in Slot 2, and set the exact cutover Migration Date so Analytics looks strictly backwards from launch.

Step 2: Import Parameter-Cleaned Site 2 URLs (1y or All Time)

Step 2 • Trawl & Clean

Confirm the auto-selected GA4 property for Site 2, switch between 1 Year Before Migration and All Time if needed, and import deduplicated clean URLs in one click.

Includes secondary Import CSV and Crawl Sync options whenever a legacy site lacks GA4 access.

Step 3: Run HTTP Checks & Close Broken Backlinks to Reach 100

Step 3 • Probe & Persist

Execute paced 25-URL HTTP probes to verify that Site 2 URLs redirect cleanly (301 → 200 on Slot 1), fix any lingering 404s, and export longest-first redirect rules.


3. Four Real-World Site 2 GA4 Trawling Scenarios

Pre-Migration Safety

Pull 1 Year Before Cutover Without Post-Launch Distortion

Set your upcoming or historical Migration Date so Analytics extracts strictly the pre-migration traffic window on Site 2.

Post-Launch Recovery Audit

Catch Residual 404s & Old-Host Redirects After DNS Switch

Trawl Site 2 All-Time URLs months after launch—Agency flags URLs still returning 404 or redirecting only within the old host instead of landing on Slot 1.

Cross-Domain Tag Safety

Separate Site 2 URLs Inside Shared GA4 Properties

Built-in hostName filtering guarantees active Slot 1 paths are excluded even when old and new domains shared one GA4 Measurement ID.

Iterative Cleanup

Prune Dead Noise & Use 2-Step Nuke Controls Anytime

Delete individual noisy paths inline or arm Nuke Filtered / Nuke All URLs while keeping your saved Slot 2 property and Migration Date intact in PostgreSQL.


4. Frequently Asked Questions

Why does Step 2 pull Analytics for Slot 2 instead of my current Slot 1 project?

During a site migration you test old-domain URLs (Site 2) to prove they 301-redirect onto your new operating domain (Site 1). Pulling Slot 2’s historical GA4 traffic gives you the exact legacy URLs that matter most.

What if my Migration Date was several months ago—can I still pull old data?

Yes! Because the GA4 lookback rewinds backwards directly from your entered Migration Date (1 Year Before Migration or All Time), you can audit both fresh and historical migrations accurately.

What happens if both my old site and new site shared the same GA4 property?

Agency queries GA4 with both hostName and pagePathPlusQueryString dimensions and strictly excludes any row belonging to Slot 1 or unrelated hostnames.

Do imported and probed URLs stay saved if I refresh or leave the page?

Yes—everything saves permanently per client project in PostgreSQL, including HTTP status codes, final redirect targets, and your Migration Date configuration.


Related Solutions & Guides

Shaun Anderson

Shaun Anderson

Shaun Anderson, AKA @hobo_web, is the Lead AI Architect behind Agency (thisisagency.ai). Shaun has over 25 years of experience in forensic SEO auditing. He was a primary investigator of the Google Search Leak of 2024, the writer of The Hobo SEO Quadrilogy, and a Keynote speaker at SMX Paris 2026.

Disclosure: I use generative AI when specifically writing about my own experiences, ideas, stories, concepts, tools, tool documentation or research, across the Hobo Web and Agency platforms. My tool of choice for this process is Agency—the publishing architecture I created and licensed to Candlestickoperations Ltd—using Google Gemini Pro (2.5 / 3) Deep Research and Reasoning and later models (as default). I have been writing about Google Search for 2 decades. This content is a direct result of cutting-edge HITL AI content production, using a process I designed myself and described in my 2025 ebook, Strategic AI SEO. Also note: This content has not been created to “pass off” as human, or “write as Shaun Anderson” (me). It is raw, factually correct content. Agency can produce content with certain styles, but it is not my aim to fool anyone with it. This is the state of AI content in 2026, an example of the default Agency creative output. All content was conceived, directed, edited, fact-checked and verified as correct by me (and is under constant development). This article is amongst the first “beta-test” of Agency, the autonomous AI-powered Agency as presented in my March 2026 SMX Paris keynote presentation. Edited by Shaun Anderson AKA Hobo. Corrections welcome. Read my AI policy.

Sign Up for Agency Updates

Subscribe for product updates, new AI workflows, and SEO research. Unsubscribe anytime.

Agency (Thisisagency.ai) is in public beta. Agency is an AI workplace simulation. Agency was conceived, bootstrapped, and architected solo by Shaun Anderson AKA Hobo (@hobo_web). “This Is Agency” and “Agency” are trading names of Candlestickoperations Ltd. Registered in England and Wales, Company No. 17503419. Registered Office: 3rd Floor, 86-90 Paul Street, London, England, EC2A 4NE.
All team members are AI entities powered by Google Gemini technology (by default). When API are available, Agency is a multi-provider, multi-model, multi-modal, multi agent system.