A business rebrand is not just a new logo. Customers may know your old trading name, suppliers may recognise an email address, and Google may have indexed years of URLs. Change everything at once without a handover plan and an otherwise positive announcement can lead to missed enquiries, broken links and confused customers.
For Australian organisations, particularly groups operating several specialist businesses, the safer approach is to separate the decisions about identity, ownership, digital systems and customer communication. This checklist helps owners and project teams coordinate those moving parts. It is a practical planning guide, not legal or cybersecurity advice for a particular organisation.
Start with a one-page change statement. Are you refreshing the visual identity while keeping the trading name and website? Are you changing a registered business name? Is one subsidiary being renamed while the parent company stays the same? Or are you also migrating to a new domain and mail system?
These are different projects with different risks. A logo change may need updated templates and signage but no website redirects. A new web domain needs URL mapping, search monitoring and mail planning. A legal-entity change needs advice about records, contracts and registrations. Do not treat these as interchangeable.
For a multi-business group, record which business owns each client relationship and who will continue providing the service after the announcement. XGEN Group’s company directory illustrates why the parent name and specialist trading brands need distinct customer pathways.
Search the ASIC business names register and IP Australia’s trade mark resources. The Australian Government’s business-name guidance explains why registering a business name does not automatically provide exclusive trade mark rights. Check the intended name against competitors, existing domains, social handles and common misspellings.
Confirm whether a change to your business-name registration or ABN details is required for your circumstances. Involve your accountant or legal adviser where the underlying entity or contracting party is changing. Avoid publishing a new brand on invoices before the relevant business information has been checked.
List every asset using the old name and assign a responsible owner. Include website pages, logos, stationery, quotations, contracts, business profiles, directories, software accounts, social media, sales presentations, digital advertisements and third-party supplier portals. Record whether each is to be renamed, redirected, retained for historical context or retired.
Separate what the business controls from what an agency or supplier administers. You need to know who can change DNS records, update the website, approve invoices and maintain email. The shared digital suppliers ownership map offers a starting point for documenting accountability rather than relying on one person’s memory.
If you are considering a different domain, check that it can be registered and that the right legal owner will hold it. Save the registrar account, expiry dates, renewal settings, domain contacts and DNS-hosting details in the controlled handover register. Do not assume paying a web-design supplier means the business owns the underlying domain licence.
For .au names, consult auDA’s official transfer guidance when ownership or providers must change. Transferring a registration and switching the website or email services are separate activities. Keep renewal and access arrangements for the old domain during any transition.
A domain may serve both the website and the organisation’s email. Website changes and email changes should have independent checklists. Record the current MX records, mail platform, aliases, shared mailboxes, third-party senders, contact forms and transactional mail services. Changing nameservers without preserving essential mail records can interrupt enquiries and invoices.
If the new domain will send email, arrange authentication with the administrator. The Australian Cyber Security Centre recommends SPF, DKIM and DMARC controls to reduce domain spoofing; see its account compromise guidance. These controls need testing and sensible rollout; copying another company’s DNS values is not a safe shortcut.
Decide how long addresses at the old domain will continue receiving mail, who monitors them and how replies will explain the new address. Test contact-form delivery to both internal and external recipients before a public announcement.
Changing the brand name does not automatically require changing every URL. Keeping a functioning domain and established pages can reduce unnecessary migration risk. If a move is justified, crawl the existing site and produce an old-to-new URL mapping before rebuilding the navigation.
Map each important service page, article, landing page and downloadable resource to the closest relevant new destination. Preserve meaningful content and useful internal links. Do not send every old URL to a generic homepage just because it is easier. That can leave visitors stranded and may be interpreted as a soft-404 experience.
Google Search Central’s site-move documentation recommends server-side permanent redirects, typically HTTP 301 or 308, for a URL-changing move. Test that each old URL reaches its intended new destination without needless redirect chains. Update internal links and canonical tags to the final URLs, ensure important new pages are indexable, and submit the appropriate sitemap after the migration.
Use Search Console’s Change of Address tool when moving a site from one domain or subdomain to another, where applicable. Monitor both properties. Google cautions that visibility can fluctuate while the move is processed and recommends maintaining redirects for at least a year, often longer for users with old bookmarks.
Do not change URL structures solely because a new brand name looks better in a slug. A controlled brand update with stable URLs may serve customers better than a full migration.
A rebrand affects more than the website. Check Google Business Profile where eligible, genuine business directories, social profiles, industry memberships, supplier panels, email signatures and paid campaigns. Keep the displayed business name, contact details and destination URL accurate. Do not create duplicate business profiles simply to support a new name.
Update navigation and company introductions so visitors understand whether they are dealing with a parent company or its specialist business. A group can maintain a clear parent identity while directing engineering enquiries, website support and branding requests to different service teams. XGEN’s How We Work page explains that distinction.
Prepare a short, factual message covering what is changing, when it takes effect, whether the team or legal entity changes, which addresses and phone numbers remain valid, and whom a customer should contact with questions. Notify high-dependency customers and suppliers directly before broad advertising when appropriate.
Fraudsters sometimes exploit changed account details and unfamiliar domains. If bank or invoice instructions change, use an established independent verification method rather than asking recipients to trust the new email alone. The supplier-payment verification checklist explains how to reduce this risk.
Assign a tester who was not responsible for implementing each change. Check the homepage and key service pages on desktop and mobile; submit real test enquiries; check email delivery; verify page titles and contact details; and inspect the actual HTTP response codes for important redirects. Open the main links from your directory, social accounts and advertisements.
Record the result, tester, date and any defects. Keep a short rollback plan covering DNS, hosting, site backups and mail routing. Some changes, such as a domain-registration transfer or public announcement, cannot be instantly reversed, so the acceptance gate needs to happen before launch.
Before launch: Agree the name, confirm legal and domain checks, inventory assets, map URLs if needed, prepare email authentication, and obtain content and customer-communication approval.
Launch day: Implement only the approved changes, validate mail and forms first, test major redirects and navigation, check public mobile pages, and keep a single issue log with owners and priorities.
First week: Review customer enquiries, failed mail delivery, Search Console coverage and top landing pages. Fix confirmed failures, update important third-party profiles, and contact customers who may have missed earlier communications.
Following weeks: Monitor old-domain referrals, search performance, backlinks, billing correspondence and renewal obligations. Close the project only when the responsible owners accept the handover, not simply when the new logo is visible.
A parent company can coordinate the change, but the specialist doing the work should own the technical acceptance criteria. A rebrand may call for brand identity and communications help, a domain move for technical website and mail support, and a search transition for careful redirect and indexing review. If you need the appropriate specialist, browse XGEN Group’s businesses or use the group contact page for parent-company enquiries.
Sources: Australian Government business-name guidance; auDA domain transfers; Google Search Central site moves; Australian Cyber Security Centre email guidance.