Make an inventory before changing DNS
Record the domain registrar and owner, current nameservers, A/CNAME records, MX records for mail, SPF/DKIM/DMARC records where used, and any verification records. Confirm who has access. A website DNS change should target the web records that need changing; replacing nameservers or deleting mail records without a plan can interrupt email.
List important existing URLs from the current site, sitemap and Search Console. Note pages that receive search traffic or external links. Map each old URL to a relevant new page. If a page moves, use a permanent redirect to its closest useful replacement. Avoid sending every old service URL to the homepage.
Test the new site before switching
Check mobile pages, forms, phone links, canonical URLs, navigation, language versions and the receiving inbox. Keep access to the old site and a copy of content until the launch has been verified. After the DNS change, test both the root and www domain, send and receive email from an external address, and check redirects and Search Console coverage.
Example: A trades business has its website at one host but its mailbox at another. Moving the web A record may leave mail untouched; moving all DNS management to a new provider without carrying over MX and authentication records may break delivery. Verify the exact DNS setup for that business instead of following a generic “delete everything” instruction.
Know what can and cannot be promised
Search engines need time to process redirects and new pages. Even a careful migration can change rankings temporarily. Track important queries, indexed pages and enquiries over comparable periods. The goal is to preserve useful URLs, content and contact routes, then identify problems quickly.
Read our website delivery and approval process, what website support includes and the package terms. Book a migration review with your current domain and email setup before changing records.