Website migration checklist for industrial firms: protect search equity and client traffic

A website migration is one of the highest-risk technical events a B2B firm can run. Done without a clear plan, you lose rankings, referral paths and client trust in days. This checklist covers every stage from pre-migration audit to 90-day post-launch monitoring.

A website migration is not a design project. It is a live infrastructure change that touches your search rankings, your inbound referral paths and every client who has bookmarked a page on your site. Industrial firms with mature sites, firms in construction, engineering or energy and petrochemical, often carry years of accumulated search equity. That equity can be wiped out in 48 hours if the migration is handled carelessly.

This checklist gives you the sequence. Follow it in order.

1. Pre-migration audit: know what you have before you touch anything.

Before a single page is moved, you need a full inventory of what your current site is worth.

Traffic baseline. Export 12 months of Google Analytics or GA4 data. Note which pages drive the most organic sessions and which pages convert visitors into enquiries. These are your protected assets.

Keyword map. Pull your current keyword rankings from Google Search Console (GSC) or a rank tracker. Record the URL, the keyword and the position. You will use this after launch to confirm nothing was lost.

Backlink audit. Export your backlink profile from Ahrefs, Semrush or a comparable tool. Every external link pointing to a specific URL is a vote that took time to earn. If those URLs change without a redirect, the vote disappears.

URL inventory. Crawl your live site with Screaming Frog or a similar crawler. Export every indexed URL. This becomes the left column of your redirect matrix.

Skip this step and you are guessing. Guessing costs you rankings.

2. Redirect matrix and 301 strategy.

A 301 redirect tells search engines and browsers that a page has moved permanently. It passes the bulk of link equity from the old URL to the new one.

Build a spreadsheet with two columns: old URL and new URL. Map every old URL to its closest equivalent on the new site. Rules:

• A service page maps to the new service page for that exact service. Not the homepage.
• A project case study maps to the nearest matching case study on the new site.
• If a page has no equivalent, map it to the most relevant category or parent page. The homepage is a last resort, not a default.
• Never leave a URL unmapped. A broken link is a lost ranking and a poor experience for any client who follows an old link from an email or document.

Test every redirect before you flip the DNS. Stage the redirect rules on the new hosting environment and crawl the staging site to confirm each 301 fires correctly and returns a 200 at the destination.

3. DNS cutover risk mitigation.

The DNS cutover is the moment the domain points to the new server. It is the highest-risk window in the entire process.

Time it carefully. Cut over on a Tuesday or Wednesday morning in your main timezone. Avoid Fridays. If something goes wrong on a Friday afternoon, your team is unavailable for two days.

Lower your DNS TTL (time-to-live) to 300 seconds (five minutes) at least 48 hours before cutover. This means DNS changes propagate faster and a rollback takes minutes, not hours.

Keep the old server live and pointed to the old codebase for at least two weeks after cutover. If the new site has a critical failure, you can repoint DNS and restore service within minutes.

Confirm SSL is provisioned and tested on the new server before you change the DNS record. An SSL error on launch day is visible to every client who visits the site.

4. Google Search Console: submit and monitor from day one.

As soon as the new site is live, take these actions in GSC:

• Verify the new property if the domain or subdomain structure has changed.
• Submit an updated XML sitemap that lists all new URLs.
• Use the URL Inspection tool to request indexing for your highest-value pages: homepage, key service pages and any pages that ranked for competitive terms.
• If you are migrating from HTTP to HTTPS (you should already be on HTTPS, but if not), confirm the property is set up for the HTTPS version.

Google can take days to weeks to re-crawl and re-index a large site. The sitemap submission shortens that window. Do not wait for Google to find the new site on its own.

5. Client communication during the migration window.

Your clients do not care about DNS propagation. They care about accessing your site, finding your contact details and downloading documents they have bookmarked.

Send a brief email to active clients and key contacts two to three days before the migration. Tell them the site is being updated, the date it will happen and that they may briefly see a different-looking page. Give them a direct contact number or email in case anything is unclear.

If your site hosts client-specific documents, portal logins or tender submission pages, confirm with your project team that all those paths are accounted for in the redirect matrix before the cutover date.

This is not a marketing moment. It is a service communication. Keep it short and factual.

6. Post-launch monitoring: the 90-day window.

The work is not finished on launch day. Rankings shift for weeks after a migration. Some shifts are normal. Some signal problems.

Week one. Check GSC daily for crawl errors, 404s and coverage issues. Any 404 that appears on a previously indexed URL means a redirect is missing or broken. Fix it the same day.

Weeks two to four. Compare keyword rankings to your pre-migration baseline. A drop of a few positions on competitive terms is normal while Google re-evaluates the new site. A drop of 20 or more positions on a high-value term needs investigation: check the redirect, check the page content, check the internal linking structure.

Months two and three. Run a full backlink audit again. Confirm that high-authority links pointing to old URLs are now resolving correctly through the redirect chain. If a link still lands on a 404, reach out to the linking site and ask them to update the URL directly. A direct link to the live URL is stronger than a redirected one.

Track organic sessions weekly against your pre-migration baseline. Most sites recover to baseline within 60 to 90 days if the migration was executed correctly. If you are still down at 90 days, the problem is structural, not temporary.

---

A migration handled this way is not a risk. It is a controlled infrastructure upgrade. The firms that lose traffic are the ones that treat migration as a design handoff rather than a technical project with its own disciplines.

If you are planning a redesign and want to understand the full scope of what it involves, the conversion-instrumented launch covers how to build for measurable outcomes from day one. For a broader look at what a new site costs to do properly, see our guide to company website costs in 2026.