An SEO migration checklist should connect every important old page to its intended outcome after launch. Save the current URLs and performance, compare the new pages, test redirects and indexing rules, then check enquiries as well as search traffic. Keep a rollback copy and clear launch criteria before you change the live site.
A redesign can change search visibility without changing the domain. New menus may hide useful pages. A template may drop headings, overwrite descriptions or block indexing. A cleaner page may also remove the details that helped buyers choose you. A successful design review does not answer those questions.
This checklist fits a business that plans to change its website, CMS or URL structure. It also helps when a recent launch coincides with a traffic drop. A drop after launch deserves investigation, but timing alone does not prove the redesign caused it. Start with the changes you can verify.
Define what the migration will change
Separate changes to the domain, URLs, hosting, templates and content before you plan the release. Each change needs different checks. A visual redesign with unchanged URLs still needs content and indexing review. A domain move also needs a destination map and control of both sites during the transition.
Write a short change list against the current site. Include URL paths, navigation, page copy, form handling, analytics, images and downloadable files. Mark the items you intend to keep. That list becomes a way to detect accidental changes during review, rather than another promise that everything will stay the same.
For example, a hypothetical B2B company might replace its WordPress theme while keeping its service URLs and form tool. That job needs template, content and form checks. If the same company also removes half its service pages, the release now includes a content consolidation. Treat that as a separate decision with separate evidence.
Ask the build team to identify which changes can ship separately. Combining a domain move, CMS replacement and full content rewrite makes a later drop harder to diagnose. Our website service connects the rebuild to the actions buyers need to complete; the migration plan should protect those paths too.
Save the baseline before anyone rebuilds
Capture the current site while it still works. Save URLs, page content, titles, descriptions, index directives, canonical tags, internal links and form behaviour. Add search and enquiry data for the pages that matter commercially. A backup protects recovery; a readable baseline helps explain what changed and whether the new site meets the brief.
Start with the sitemap, then add URLs from analytics, Search Console, the CMS and known campaigns. A sitemap alone may omit an old landing page that still brings enquiries. Keep valuable PDFs and image URLs in scope when buyers or other sites link to them.
Record the exact reporting dates. Use comparable days and avoid comparing a complete month with a few days after launch. Save branded and unbranded search queries separately where the data allows it. Keep notes about promotions, seasonal changes or campaigns that could affect the comparison.
Take screenshots of key desktop and phone paths. Submit a clearly marked test enquiry in an approved test environment and record where it arrives. Save the form fields, confirmation behaviour and CRM mapping. If your numbers already disagree, use our lead-tracking cleanup guide before treating the redesign as a measurement fix.

Give each old URL a clear outcome
Every URL in the migration inventory needs a destination or an explicit decision to keep or retire it. Match pages by the job they do for the reader. Preserve a useful existing URL when the redesign does not require a change. Review important exceptions individually before anyone turns the map into redirect rules.
| Old page | Intended outcome | Check before release |
|---|---|---|
| Service page with the same offer | Keep its URL | Confirm the new template retains the offer and enquiry path |
| Old service URL with a direct replacement | Move to the equivalent new page | Test the final destination and permanent redirect |
| Several guides with one complete replacement | Consolidate | Check that the replacement answers their distinct useful questions |
| Withdrawn offer with no replacement | Retire | Check inbound links and explain the removal where appropriate |
| Campaign landing page outside navigation | Keep or move deliberately | Check active ads and campaign links |
Google recommends a URL map and relevant destinations for moves. Sending unrelated old pages to the homepage can produce soft-404 treatment. Its site-move guidance also recommends keeping redirects for at least a year in general. Keep control of the old domain and routing for that period when the move needs them.
Do not mark a row complete because the new address opens. Check that it contains the expected service, location or answer. A working page with the wrong content still gives the visitor a broken path.
Compare the new pages with the old pages
Review the new site against the saved baseline before judging the visual finish. Compare the promise, main heading, useful copy, proof, internal links and next action on important pages. Record intentional removals. Investigate accidental losses before launch, especially when a shared template affects many pages at once.
Choose pages that exercise different layouts: a service page, article, case study, contact page and any important location or product template. Then check the full URL inventory for fields that software can compare. Manual review and broad checks serve different purposes; neither replaces the other.
A hypothetical service page may keep its attractive hero while losing a paragraph about who qualifies, a price boundary and its case-study link. Those details help buyers decide whether to enquire. Restore them or explain why the new page answers the decision better.
Check titles and descriptions for accidental duplication, empty values and old staging names. Confirm that tables, accordions and comparison text remain readable on a phone. Our traffic-without-leads checklist helps separate a search problem from a page that attracts visitors but fails to earn action.
Keep structured data tied to visible content. If a redesign replaces the questions in an FAQ, update the corresponding markup. A migration should not leave old service claims in machine-readable fields after the page itself changes.
Test redirects and indexing signals together
Test the entire old-to-new URL path, then inspect the destination. A redirect can work while the new page returns an error, points its canonical elsewhere or tells search engines not to index it. Record the HTTP response and final URL, and check the page content before declaring that route ready.
Google recommends permanent server-side redirects such as 301 or 308 for permanent moves. Its redirect documentation distinguishes those signals from temporary redirects. Point the old URL straight to the final relevant destination where possible instead of adding avoidable hops through old naming schemes.
Keep internal links, canonical preferences and the sitemap consistent. Google treats redirects and canonical annotations as strong canonicalization signals, and sitemap inclusion as a weaker signal. Those preferences still do not force Google’s selection. See its canonical URL guidance.
Staging protection needs a deliberate release check. Confirm that the live site does not inherit staging noindex rules or access restrictions. Google must access a page to see its noindex rule; a robots.txt block does not serve the same purpose. Google’s noindex documentation explains that distinction.
Use our AI crawler access checker as a separate access check for supported AI crawlers. A successful access check does not establish indexing, citation or recommendation.

Test one enquiry through the new CMS
For a custom CMS migration, use one old service URL to test the whole route on staging. In this example, a manufacturer moves /cnc-milling.html to /services/cnc-milling/.
- Start with the old URL. Open it on the staging host. It should issue one permanent redirect to the new path. The destination should return HTTP 200.
- Inspect the new service template. Check the heading, the machining capabilities and the quote form on a phone. Confirm that the canonical points to the intended new URL and that staging still blocks indexing.
- Send a marked test enquiry on staging. Submit a request for a CNC milling quote. Check that the form shows a success message and the test inbox or CRM receives exactly one record with the message and the CNC milling page URL.
Record the redirect status, final URL and test receipt. If the redirect works and the enquiry fails, keep that route off the launch list until it passes the whole test.
Make the launch decision from evidence
Approve launch only when the agreed checks pass on the version you plan to release. Keep the tested build, URL map and rollback copy together. If the site changes after testing, rerun the affected checks. A screenshot from yesterday does not prove that today’s deployed form or redirect still works.
Use clear stop conditions rather than a broad instruction to fix issues later. Stop for a blocked commercial section, missing primary offer, broken enquiry path or destination map that sends important pages to errors. Decide how to handle minor visual defects without allowing them to hide more serious failures.
For a hypothetical 60-page service site, you might require a complete response-code check, manual review of every service page and successful tests across each form type. That is an example scope, not a universal sample size. A larger store with filters and product variants needs a different test plan.
Ask for a recovery demonstration before the release window. The team should know which database copy, media files and code version belong together. Restoring files alone may not restore changed content or routing. Specify how new enquiries during a rollback will survive so recovery does not silently discard business records.
Check the live site before watching rankings
Immediately after launch, verify the live URLs and buyer paths. Confirm that the production site contains the tested content, uses the right domain and sends enquiries to the intended place. Run the old-URL checks again. Only then start interpreting search performance, which can lag behind the release and change for several reasons.
Check the homepage and important landing pages on a phone as well as a desktop. Open the navigation, follow an article link, use a contact method and inspect the confirmation. Check consent-dependent analytics separately from the underlying receipt so a tracking issue does not look like a lost enquiry.
In Search Console, distinguish the indexed version of a URL from a live test. Google’s URL Inspection documentation explains the two views. A live result can help identify current access problems, but it does not prove Google has already indexed the new version.
Submit the updated sitemap and check that it contains the intended current URLs. A successful submission confirms that you supplied information; it does not guarantee indexing or recovery. Keep a dated launch note so later reporting can separate pre-release and post-release periods without guessing. Check active ad destinations and saved campaign links too. A redesign can preserve organic URLs while leaving paid visitors on an obsolete offer.
Diagnose a drop by the affected pages
When traffic falls after a migration, group the affected pages and compare their actual changes. Check access, destinations, index directives, content and internal links before assigning a cause. A sitewide decline, one missing template and a change in tracking can look similar in a top-level chart but need different fixes.
| What you observe | What to inspect next |
|---|---|
| Old URLs fail or land on unrelated pages | The redirect map and deployed rules |
| A whole section disappears | Template index rules, navigation and content availability |
| Analytics drops but enquiries hold steady | Tag loading, consent, event definitions and reporting |
| Impressions hold but clicks fall | Search result appearance, query mix and competing results |
| Visits hold but enquiries fall | Forms, mobile paths, offer changes and response handling |
Avoid rewriting every page while you investigate. Preserve the release evidence, fix a confirmed problem and record the scope of the repair. Compare the affected pages with pages that did not change in the same way. That comparison may help narrow the explanation, but it still does not prove causation on its own.
If the issue touches several parts of the site, our SEO service can connect the technical review with the content and buyer paths. Keep the repair brief tied to observable failures rather than a promised ranking date.

Ask for a handover you can use
A useful migration handover includes the final URL map, completed checks, known exceptions, recovery instructions and reporting baseline. It should let another capable person explain what changed and investigate a problem without rebuilding the project history. Keep account access in the business’s control and retain the evidence after the launch meeting.
Ask when the team will review production again and what will trigger further work. Agree a practical review schedule based on the site’s size and commercial risk. Do not turn those review dates into promises that Google will recover or rank a page by a particular day.
Bring your current URL list, planned changes and main enquiry paths to a website and CRO audit. We can use that scope to identify the checks your redesign needs before you approve the release. If the site already launched, include the launch date and the pages that changed most. That gives the review a concrete starting point.
FAQ
Does every website redesign need redirects?
No. Keep existing URLs when they still fit the page. Add redirects when a permanent move changes the address and a relevant replacement exists. A design-only change still needs content, internal-link, indexing and form checks. Do not create a new URL solely to make the redesign look more extensive.
Can an SEO migration guarantee that traffic will not drop?
No. A checklist reduces preventable mistakes and gives the team evidence to diagnose problems. It cannot guarantee how search engines or buyers respond. Separate technical failures from reporting changes and broader search variation. Keep the baseline and launch record so the team can compare the right pages and periods.
Should every retired page redirect to the homepage?
No. Choose a destination that genuinely replaces the old page’s purpose. Google warns that irrelevant mass redirects can create soft-404 treatment. Where no useful replacement exists, review the page’s retirement deliberately rather than sending visitors somewhere unrelated. Document the choice so the release team does not invent a destination.
How long should migration redirects stay active?
Google generally recommends keeping redirects for at least one year during a site move. The business may need them longer for visitors following old links. Keep the old domain and redirect infrastructure under your control, and update important links you control so visitors can reach the current destination directly.
What should we check first if leads fall after a redesign?
Test the live enquiry path and compare the actual form or CRM receipts with analytics. Confirm the right destination, fields, confirmation and phone experience. Then inspect the pages that lost traffic. A tracking fault, a broken form and a search decline can produce similar charts while requiring different repairs.
You're All Set!
We have your request.
Expect a reply from our team within 24 hours. Want to talk sooner? Pick a time below.
Or call us at +1 (914) 297-6638


