ArticlesPlan a website

Changing web agencies: plan the migration and protect your SEO

A handover checklist for URLs, content, access and launch, helping reduce avoidable losses during a website migration.

GlomivaUpdated November 10, 20263 min read

The sensitive parts of an agency change may be absent from the design proposal: an old service page that brings enquiries, a domain in the wrong account or a form sending to a former employee. Inventory these before building the replacement.

This plan can reduce avoidable errors; it cannot guarantee unchanged rankings or traffic.

Define what will actually change

Separate who manages the website, where it is hosted and which URLs or content change. A new supplier does not require a new domain or page names. Ask for a reason for each change.

Write a short description, such as “same domain and service pages, new hosting and design.” Identify article consolidation or language restructuring separately so each part can be tested.

List the pages that must survive

Combine the sitemap, existing website, Search Console and relevant visitor data. Include useful low-traffic pages such as terms and linked documents.

Old URLDecisionNew URLOwnerChecked
/engine-serviceKeep content and URL/engine-serviceContent ownerNo
/old-pricesReplace with relevant pricing/pricesDeveloperNo
/manual.pdfRetain document/manual.pdfProject leadNo

These are invented examples, not customer project URLs. Decide deliberately when no relevant replacement exists. Do not redirect everything to the homepage.

Secure access and responsibilities

Check administrative control of the domain, DNS, hosting, content system and relevant Google accounts. Document contacts and recovery routes. Transfer secrets securely.

Review source code, content, licensing and export terms. Obtain a copy of the website and data before ending the old agreement. Test that it can be read: a file labelled “backup” is not a verified recovery plan.

Keep website and email plans separate

Ask explicitly whether email will move. Changing web servers does not automatically require changing mailbox providers. Inventory DNS records and document precisely which website records need changing.

Include external bookings, payments, downloads and form recipients; these may use other providers.

Approve the test version before switching

Follow the customer journey from service and price information to enquiry. Check mobile, links and documents, including pages outside the main navigation.

Have the developer check status codes, canonical URLs and redirects. Keep the test environment out of indexing and confirm the public environment has the correct settings at launch.

Check again after launch

Verify form delivery, important old URLs and public access. Assign incident handling and rollback responsibility. Record the launch date, then compare indexing and traffic with consistent filters and periods. One day is not a final result, and every change is not necessarily caused by migration.

Google distinguishes hosting changes without URL changes from moves with URL changes. Use the appropriate instructions. Include the migration in the quote using our agency checklist.