Website Relaunch Handover: Protect Email, Enquiries and Search

Business Rebranding Checklist: Protect Domains, Email, Search and Customer Trust
November 10, 2026
Scope Changes Across Specialists: A Practical Decision Log
November 15, 2026

Website Relaunch Handover: Protect Email, Enquiries and Search

A practical website relaunch acceptance checklist covering domain and DNS ownership, email delivery, enquiry forms, redirects, search visibility and rollback.

A website relaunch is not complete when the homepage looks right. For a business with more than one specialist company, the real test is whether a customer can still find the correct business, contact it, and receive a reply. A change to the domain, hosting, forms or navigation can break that journey even when the design appears finished. The checklist below turns a website handover into a set of practical acceptance tests. It can be used for a new website, a move to a different host, a redesign with changed URLs, or a change of website supplier.

1. Assign one owner to the whole handover

Start by identifying a business owner, technical lead and person who will receive test enquiries. One person should own the decision to go live, even if different suppliers manage hosting, email, design and SEO. Record who can approve DNS changes, who can restore a backup, who manages the domain renewal, and who can update the website. A handover is unsafe if each supplier assumes another supplier owns the final test.

For a group of businesses, record the destination company for each type of enquiry. A customer asking for a prototype may need a different business from someone asking about branding or engineering. The group directory should introduce those companies without suggesting that the parent company performs every specialist service. See XGEN Group’s company directory for the intended business-navigation starting point.

2. Take a baseline before changing anything

Capture the current homepage, main service pages, contact routes, navigation, forms and the URLs that receive search traffic. Export a list of existing URLs and their page titles. Record where the contact forms deliver notifications, but do not put mailbox passwords or API keys in the handover document. If you are changing a domain or site structure, capture current Search Console performance and the highest-value landing pages. That baseline makes it possible to distinguish a new issue from an existing one.

Make a small acceptance sheet with four columns: test, expected result, actual result and owner. Add an evidence link or screenshot after each test. A row marked “done” without evidence may hide a problem that becomes visible only after customers arrive.

3. Verify domain ownership and DNS responsibilities

Confirm the domain registrant, registrar, renewal contact, authoritative name servers and DNS editor. A domain registration transfer is not the same operation as moving website hosting or changing nameservers. Avoid treating them as one task. For Australian domains, auDA explains domain transfers, including differences between registrar and registrant changes.

Before editing DNS, copy the existing zone and identify records used by the website and email. Agree on a rollback plan and a change window. After the cutover, check the intended hostname, www/non-www behaviour, TLS certificate, and DNS resolution from more than one network. Keep account access restricted and protected with multifactor authentication, consistent with Australian Cyber Security Centre website guidance.

4. Treat email as a separate critical service

A website may use one host while staff email uses Microsoft 365, Google Workspace or another provider. A website migration must not silently remove or replace mail-routing records. Identify MX, SPF, DKIM and DMARC settings before changes, then check the published records afterwards. Have a colleague send a real test message from an external mailbox and confirm it arrives. Reply to that message and confirm that the response is received, rather than relying only on a dashboard’s “sent” status.

Test any address that receives website leads, supplier quotes or customer support. If a form depends on a plugin or external sending service, verify that its mail authentication still functions. For more detail on business ownership of these services, read Website Hosting, Email and DNS: What Business Owners Should Control.

5. Test forms from start to finish, not merely the submit button

Complete a test enquiry on a phone and on a desktop. Check that validation messages are understandable, consent text is accurate, the confirmation screen appears, and the business receives a readable notification. Confirm the correct team receives the enquiry and that someone can reply without copying private customer information into the wrong mailbox. If multiple companies share the group site, choose test questions that clearly belong to different specialists.

Record the time sent and the time received, plus the destination inbox. A success message on the page does not prove an email arrived. A more detailed testing method is available in Website Contact Form Testing: From Submit to Reply. Do not publish real customer submissions as test evidence. Use fictional data and keep screenshots free of personal details.

6. Preserve important URLs and search signals

If URLs change, create a one-to-one mapping from each useful old URL to the most relevant new URL. Implement permanent redirects where appropriate and test them. Redirecting every old page to the homepage is not a good substitute for page matching. Inspect new canonical links, accidental noindex settings, robots rules, internal links and the XML sitemap. Check the site’s ownership and performance in Google Search Console after the change.

Google’s site-move guidance recommends checking redirects, canonical annotations, robots settings and sitemaps. The same guidance explains that search visibility can fluctuate during site moves. A design sign-off therefore cannot guarantee stable rankings the next day. Keep the before-and-after query and landing-page reports so changes can be investigated on evidence.

7. Review what visitors understand about each business

For a parent company, check more than the menu labels. A visitor should understand which organisation owns the group website, which company actually provides the requested service, and where a specialist enquiry will go. Use correct company names and straightforward descriptions. Verify that every business-card link reaches the intended subsidiary, not an outdated campaign page, an unrelated service, or a generic contact page.

Check the same journey on mobile. Short navigation labels may become ambiguous in a compact menu. If a contact button goes to the parent company rather than the specialist, explain that distinction. A clear handover reduces misdirected enquiries and prevents businesses from claiming expertise they do not offer. See how XGEN Group works for the group’s approach to directing enquiries.

8. Include accessibility and mobile acceptance tests

Use a keyboard to reach the main navigation and forms. Confirm that focus is visible, headings are in a sensible order, buttons have understandable labels, and links are distinguishable. On mobile, check tap targets, text size, horizontal scrolling, menu expansion and form errors. Test at least one slower network or device when practical, because a page that feels fast on an office computer may behave differently for a customer travelling or using mobile data.

Measure performance using consistent tools and record device conditions rather than promising one universal load time. If a new design introduces unusually large images, scripts or layout shifts, capture the change and assign the correct supplier to fix it. Do not treat a performance score as a substitute for real enquiry testing.

9. Plan rollback and post-launch monitoring

Before approval, establish how to return to the previous hosting or content state if the release fails. Identify what will be restored, who can initiate it and which data might have changed since the backup. A database restoration can overwrite real enquiries received after launch, so decide how to protect or reconcile new records. Recheck HTTPS, contact forms and mail flow immediately after any rollback.

For the first week, monitor support messages, site errors, email delivery, form confirmations, relevant Search Console pages and key links. Record a named owner and deadline for every exception. A “watch” item is not a completed fix. If the issue affects enquiry delivery, give it higher priority than cosmetic adjustments or another general blog post.

10. Use a practical go-live decision

Agree on simple acceptance criteria before the change window. The domain resolves to the right site; HTTPS works; priority old URLs redirect correctly; relevant pages are indexable; the sitemap points to live URLs; forms reach the intended recipient; two-way email is working; company links identify the correct specialists; and a restore method is documented. If one critical criterion fails, record a decision to delay or roll back rather than hiding the defect in an informal chat.

A good release record is short enough to use: who approved, what changed, the URLs affected, the result of each test, open risks and the next review. That makes the next website project easier to manage and gives management clear evidence of what is actually ready. For a multi-business group, it also separates the parent company’s coordination role from the specialist work of each subsidiary.

Final handover checklist

  • Domain registrant, renewal contact, registrar and DNS administrator recorded.
  • Old DNS zone and current URL inventory securely retained.
  • Website, www redirect and HTTPS tested on multiple devices.
  • Mail flow checked with both incoming and outgoing messages.
  • Forms tested end-to-end with fictional data and verified recipient inboxes.
  • Changed URLs mapped to relevant destinations with redirects tested.
  • Canonicals, index directives, robots and sitemap reviewed.
  • All subsidiary links and enquiry destinations verified.
  • Rollback owner and recovery method confirmed.
  • One-week monitoring plan assigns owners and deadlines to exceptions.

The best handover does not need to be complicated. It needs to prove that the right customer can reach the right business and that the team can identify and recover from a failure. For general group enquiries, contact XGEN Group; for specialist work, select the relevant business first.

Comments are closed.