⚠️ Important: What This Upload Does
This upload imports URLs as "dead URLs" (404s) that need redirects.
If you upload a GA4 "Pages and screens" report, it will include ALL pages (both live and dead). This will create incorrect redirect suggestions where pages redirect to themselves.
Instead, you should only upload URLs that are actually 404s and need redirects to working pages.
📊 How to Get Dead URLs
Option 1: Filter GA4 for 404s
- Go to Reports → Engagement → Pages and screens
- Click Add filter → Page title → contains → "404" (or "Not Found")
- Click Share → Download CSV
Note: Only works if your 404 pages have "404" or "Not Found" in the title
Option 2: GA4 Exploration (Advanced)
- Go to Explore → Create new exploration
- Add dimensions: Page path, Page title
- Add metric: Views
- Add filter: Page title contains "404"
- Export as CSV
Option 3: Server/CDN Logs
Export 404 errors from your server/CDN logs (Cloudflare, Vercel, Netlify, etc.) with URL and hit count.
Option 4: Manual List
Create a CSV with two columns: url and hits. List only the 404 URLs you know need redirects.
Option 5: Crawl (Coming Soon)
Use our crawler to automatically discover 404s on your site.
✅ Required Columns
💡 What Happens Next
- • We automatically detect column headers
- • URLs are normalized and deduplicated
- • Traffic data prioritizes redirects
- • You'll see results in your dashboard
⚠️ Common Issues
"No valid rows found" error
Make sure your CSV includes both URL/path and traffic count columns. GA4 exports sometimes hide these - try exporting from a different report.
Wrong column names
We automatically detect: page path, url, views, event count, hits, pageviews. If your export uses different names, they should still work.
File too large
Try filtering by date range in GA4 before exporting. We recommend 3-6 months of data for the best results.
Don't use GA4?
Any CSV with URL and traffic columns will work. Just make sure it has:
- • A column with page paths (e.g., /blog/post-title)
- • A column with numbers (visits, views, etc.)