Guides · Crawling & indexing
301 plan for a site migration: from the URL map to day 30
Collect every old URL, map each to a new URL, set single-hop 301s and monitor 404s, indexing and traffic for 30 days after the move.
- By
- OSKIT team (Afformation)
- Updated
- 2 min read
On this page
Summary
- Collect old URLs from the sitemap, Search Console page report, analytics landing pages and external links.
- Map each old URL 1:1 to its closest new URL. Do not send everything to the home page.
- Keep 301s for at least a year.
Steps
- 1
Collect old URLs
Pull URLs from the sitemap, Search Console page report, analytics landing pages and backlink reports, then dedupe.
- 2
Build the URL map
Write a new URL for each old URL, 1:1. With no match, choose the closest parent page.
- 3
Set 301s
Redirect straight to the final address with no chains.
- 4
Clean the new site
Update internal links, canonicals, sitemap and hreflang to new URLs.
- 5
Use Change of Address
If the domain changes, use Search Console’s Change of Address tool and submit the new sitemap.
- 6
Monitor for 30 days
Check 404s, indexed page count and key page impressions and clicks daily.
The short answer
Collect every old URL, map each one to a new address 1:1, set single-hop 301s and check 404s, indexing and impressions daily for 30 days. Google recommends keeping permanent redirects for at least a year.
1. Collect old URLs
| Source | What it gives you |
|---|---|
| Old sitemap | URLs the owner published |
| Search Console page report | URLs Google knows, indexed or not |
| Analytics landing pages (12 months) | URLs that received visits |
| Backlink report | URLs other sites link to |
Merge, normalise parameters and dedupe. Include files such as PDFs that receive search traffic.
2. Build the URL map
| Old URL | New URL | Type |
|---|---|---|
| /sub/treat01.html | /treatments/lifting | 1:1 |
| /sub/treat01_jp.html | /ja/treatments/lifting | 1:1 per language |
| /event/2023-summer | /treatments | Parent page |
| /old-page-no-match | (410) | Removed |
Rules: map 1:1 when a match exists, use the closest parent when it does not, never send everything to the home page (Google may treat it as a soft 404), return 410 for URLs with no match and no traffic, and keep language versions within the same language.
3. Set the 301s
Redirect straight to the final address. Check that https and www rules do not create chains with migration rules. Use server or platform redirects, not JavaScript.
while IFS=, read -r old new; do
curl -s -o /dev/null -w "$old -> %{http_code} %{redirect_url}\n" "https://old.example.com$old"
done < redirects.csv4. Clean the new site
Update internal links, canonicals, the sitemap and hreflang pairs to new URLs.
5. Search tools
If the domain changes, use Search Console’s Change of Address tool with both properties verified. Submit the new sitemap to Search Console, Bing and Naver, and send the new URLs through IndexNow.
6. Monitor for 30 days
| Days | Check | Action |
|---|---|---|
| 1–7 | 404 logs, redirect errors | Add missing URLs to the map |
| 1–14 | Indexed pages, old vs new | If new URLs do not grow, check sitemap and links |
| 1–30 | Key page impressions and clicks | Verify mappings for pages that drop |
| 30 | Top linking sites | Ask them to update links |
Short swings after a move are common. Judge in two-week windows.
In OSKIT
Import Engine moves pages and content into section data and builds the old-to-new map in the redirects table. A person approves the map, the 301s go live with the deploy, and post-move 404s collect daily in Signal Engine.
Sources
- [1]Google Search Central — Redirects and Google Searchhttps://developers.google.com/search/docs/crawling-indexing/301-redirects
- [2]Google Search Central — Site moves with URL changeshttps://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
Summarize in an AI chat
Only the page URL is sent.
A free check shows your search and AI answer visibility
Enter your website address and see search engine and AI bot access and index status right away.
3 minutes · Free · No contract