Before migrating a website, inventory the existing site, back up its data, record performance benchmarks, and plan any URL changes. During development, incorporate SEO requirements into development tickets and regularly check links, content, and access settings. Domain consolidation, hosting changes, and large websites require additional preparation. These steps provide a basis for checking results and recovering from problems, but they cannot guarantee that traffic will remain unchanged after migration.
Before migration: Inventory pages, record performance, and keep backups
Start by identifying the site’s current pages, the traffic each receives, and the keywords associated with each. Then decide which content to retain, merge, or remove on the new site. Semrush’s 2017 guide specifically notes that when consolidating two domains or website sections, the audit data must cover both sides—not just the one receiving the content.
- Record performance: Retain site audit, analytics, and ranking data as a baseline for comparison after migration.
- Create a complete backup: Include content, media, databases, user accounts, meta tags, and site settings so that data can be restored if something goes wrong.
- Determine what will happen to each page: For example, if a product information page previously attracted organic traffic but has no corresponding content on the new site, you cannot expect that traffic to carry over automatically.
Before migration: Clarify how URLs and links will change
If URLs will change, first map old URLs to new ones to plan redirects. If URLs will remain the same, there is no need to change them simply because you are switching systems. Before a domain migration, also crawl the entire old site to find absolute links that explicitly use the old domain in navigation menus, footers, and body content. These links include the old domain followed by a page path. Add them to an update list and confirm that the new site no longer uses them.
You can also conduct additional keyword research for pages in the new sitemap. This is an opportunity to improve content, but it does not guarantee traffic growth.
During development: Turn SEO requirements into tasks you can verify
Do not wait until the new site is finished to raise all SEO issues at once. Submit requirements through the development team’s ticketing system or communication channels and discuss progress regularly. After each change, verify the results and update the tickets.
- Check that structured data for core entities is consistent and that existing entity information has been updated.
- Confirm that key documents and site resources are accessible and suitable for crawling.
- List in advance any password protection and unnecessary noindex tags that must be removed at launch, so temporary restrictions do not carry over to the live site.
Special cases: Plan separately for hosting changes and large-site migrations
If you are changing hosts, you can temporarily lower the DNS TTL before migration so the new IP address takes effect sooner. Plan to restore the normal value after migration. For large websites, consider migrating in stages, starting with smaller or less important sections. Test and fix each batch before proceeding, rather than moving everything at once and troubleshooting afterward.
SEO preparation before a website migration and during development: perspectives from across the web
How can you prevent public access to a new site before it is ready?
You can password-protect the new site during development. Another option is to temporarily redirect visitors to an under-construction page, but that redirect must be removed at launch. These measures help prevent access to or interference with the unfinished site. At launch, also remove unnecessary access restrictions and check for crawling issues to confirm that users and search engine crawlers can access the new site.
Does retaining the existing content and structure mean there is no need to worry about the impact of migration?
Not necessarily. Keeping the content and structure does not mean the migration is risk-free. One forum contributor suggested there was no need to worry if both were retained, but another cautioned that even changing only how the site is built can produce different HTML, which could improve or worsen the site's performance. Other comments noted that changing URLs without properly configuring 301 redirects, losing internal links, and making substantial layout or content changes can all hurt the site's performance after migration.
How should existing external links be handled after URLs change?
During development, you can list external links that need updating and plan to address them after the URLs change. Start with items you control, such as social media profiles or email signatures. For backlinks from other websites, you can contact the site owners and ask them to point to the new URLs. Linking directly to the new content can prevent readers from reaching deleted pages or having to go through redirects, but whether a link can be updated still depends on whoever controls it.
References
- Impact on SEO of a website in converting a PHP Website to Wordpresswww.warriorforum.com — Discusses: Does retaining the existing content and structure mean there is no need to worry about the impact of migration?
- How To Measure the Impact of Your Site Migrationwww.semrush.com · 2017-06-30T07:13:00Z — Source used in the article above.
- Why AI Visibility Does Not Only Depend On SEOwww.searchenginejournal.com · 2026-06-24T12:00:10+00:00 — Source used in the article above.
- Neil Patel’s Website Migration Checklistneilpatel.com · 2024-08-12T19:00:00+00:00 — Source used in the article above.
- Website Migration SEO Checklist (88 Steps + Free Template)backlinko.com · 2024-04-01T17:23:50-05:00 — Source used in the article above.
- Impact on SEO of a website in converting a PHP Website to Wordpresswww.warriorforum.com — Discusses: Does retaining the existing content and structure mean there is no need to worry about the impact of migration?
- Google Says Why Site Migrations Can Exceed 4 Monthswww.searchenginejournal.com · 2026-10-13T11:23:58+00:00 — Source used in the article above.
- The Complete Website Migration Checklist [SEO-Friendly]www.semrush.com · 2019-03-25T13:30:00Z — Discusses: How can you prevent public access to a new site before it is ready?; How should existing external links be handled after URLs change?
- Impact on SEO of a website in converting a PHP Website to Wordpresswww.warriorforum.com — Discusses: Does retaining the existing content and structure mean there is no need to worry about the impact of migration?
- 16 Crucial SEO Steps To Take When Migrating Your Websitewww.semrush.com · 2017-08-24T12:00:00Z — Discusses: How can you prevent public access to a new site before it is ready?


