Changing Your Business Name: What Moves With You and What Does Not

Section 30 of the Companies Act 2014 is admirably calm about renaming a company. A change of name, it says, "shall not affect any rights or obligations of the company, or render defective any legal proceedings by or against the company". In law you are the same entity on Tuesday that you were on Monday. Contracts hold. Debts follow you. The registration number on file does not move.

Google has not read the Companies Act.

That gap, between legal continuity and digital continuity, is where most rebrands quietly lose money. The paperwork is the easy part. Everything else is not, because a decade of search rankings, inbound links, directory entries and customer bookmarks are all attached to a name and a web address that you are about to retire, and none of them update themselves.

Two of the migration requests on my desk this month are renames rather than moves. The pattern is consistent enough to be worth writing down properly.

What a Rename Actually Touches

A business rename is four separate changes that happen to share a launch date. Treating them as one job is how pieces get missed.

Layer	What actually moves	What you have to do
Legal identity	Automatically, once filed	File with the CRO, update stationery
Domain name	Nothing, unless you move it	Decide, then redirect deliberately
Search index	Slowly, and only if told	Map URLs, redirect, notify Google
Third-party listings	Never	Update each one by hand

The legal layer is the only one that behaves. A company changes its name by special resolution with the approval of the Registrar, and under section 30(5) the Registrar enters the new name in the register and issues an altered certificate of incorporation ^[5]. Your company number is untouched. If you trade under a registered business name rather than a company name, that is a separate registration with its own filing, so check which one you are actually changing before you order signage.

Everything below that line is manual. That is the whole article.

Decide the Domain Question Before Anything Else

Renaming your business does not oblige you to change your web address. This is the decision most owners skip past, and it is the one with the largest consequences.

You have three options, and they are not equal.

Keep the existing domain. Zero search risk. Your address no longer matches your name, which confuses people reading a van or an invoice, but nothing breaks. For a modest rename, a shortening or a change of legal form, this is often the correct answer.

Move to a new domain. Clean brand alignment, at the cost of a temporary dip and a permanent maintenance obligation. This is the option that needs the sequence in this article.

Run both. New domain as the public identity, old domain redirecting to it. In practice this is what a proper move looks like anyway.

A pattern we see in migration requests: an agricultural contracting business in Offaly had traded under the founder's own name for thirty years, then rebranded when the second generation came into the business. New name on the trucks, new name on the quotes, new domain bought and pointed at a new site. The old address was left to lapse. Every quote issued in the previous three years carried a web address that now resolved to nothing, and the first anyone knew of it was a customer ringing to ask whether they had gone out of business.

That call is the cost of getting the sequence wrong. It is entirely avoidable.

Your Old URLs Are Assets, Not Rubbish

Every page on your current site has a history. Some of it you know about. The rest is the local paper linking to your opening, a supplier directory entry from 2019, a customer who bookmarked your price list, a chamber of commerce page nobody has touched in years.

That accumulated history is the single most valuable thing your website owns, and it is attached to specific addresses. Not to your business. To the URLs.

Google's own guidance on redirects is unambiguous about how you carry it across: Googlebot follows the redirect, and the indexing pipeline uses that redirect as a signal that the target should be canonical ^[2]. A permanent server side redirect is the mechanism, and Google explicitly recommends it whenever a URL needs to change. This is not a trick. It is the documented, supported way to tell a search engine that a page has moved.

The part people get wrong is the mapping. Google's site move documentation states it plainly: do not redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site ^[1]. Each old page goes to its closest new equivalent, so your old services page goes to the new services page and your old contact page to the new contact page. Pointing all two hundred of them at the homepage is functionally the same as deleting them, and it is the most common shortcut in a rushed rebrand.

Which means the redirect map is written before the new site is built, not after. You cannot map to pages that do not exist yet, and you cannot discover which old pages mattered on launch morning.

Build the renamed site somewhere the public cannot see it, apply the map there, and verify a sample of old addresses actually land where you intended. A one-click staging environment where you can rehearse the whole move before it touches production turns launch day into a deployment rather than an experiment. Verify in staging. Deploy once.

The limit of what a redirect can do

A redirect moves a page. It does not move a name.

If people have been searching your old trading name for years and finding you, those searches keep running for months after the sign changes. A redirect carries the ranking of the page across. It cannot make the new name rank for a query nobody is typing yet, and it cannot stop the old name from slowly fading out of the index once every reference to it has been updated. Nothing you deploy fixes that. It resolves with time, and with everyone else catching up to your new name, which is a marketing job rather than a technical one. Know that going in and the first month of numbers will not frighten you.

Telling Google You Have Moved

Redirects do the work. Search Console tells Google to expect it.

If you are moving to a different domain, Google provides a Change of Address tool in Search Console for exactly this. It requires both the old site and the new site to be verified properties, including the www and non-www variants, so that verification is a prerequisite rather than an afterthought. If you have never set the tool up, our guide to Google Search Console for business owners covers verification from the beginning.

Set expectations honestly with whoever signs off on the rebrand. Google's guidance is that a small to medium sized website can take a few weeks for most pages to move, and that you should expect temporary fluctuation in site ranking during the move ^[1]. Google describes that fluctuation as normal. It is not a sign that the move failed, and the worst decision available in week two is to start undoing correct work because the graph dipped.

The performance fundamentals do not change either. A renamed site on slow infrastructure ranks like a slow site, and everything in the complete WordPress performance guide for business owners applies to the new address exactly as it did to the old one. Renaming is not an optimisation.

How long the old domain has to live

Google recommends keeping the redirects for as long as possible, generally at least one year, and notes that from a user perspective you might consider keeping them indefinitely ^[1]. Read that as an operating instruction: the old domain is now infrastructure. It needs renewing, it needs its redirects verified occasionally, and it needs to stay in someone's diary.

We learned that one the hard way. On a rename we handled, the redirect map was thorough and the launch was clean, and four months later the traffic fell off a cliff for no reason visible in the new site's logs. The old domain had quietly hit its renewal date and nobody had connected it to the redirects running on it. Now the old domain's renewal goes in the calendar at the same time the map is built.

The .ie Detail That Catches Irish Businesses Out

This one is specific to us and it is worth handling early.

Every .ie domain holder has to demonstrate a connection to the island of Ireland, evidenced by something like a CRO number, a VAT number or a business registration. That requirement does not disappear once you are registered. The registry's guidance routes changes of registrant through a reassignment process in which the incoming registrant must meet the registration criteria and supply supporting documentation ^[4], and a domain can sit on hold while that documentation is reviewed.

So changing the registrant name on a .ie domain after a company rename is not always a field you edit and save. Depending on your registrar and how the change is filed, it can be treated as a registrant change with documents attached. The practical consequence for a business owner is simple: raise it with your registrar weeks before launch, not on the morning you want the new name live. Your certificate of change of name from the CRO is the document that usually settles it.

If your domain is a .com or similar, none of this applies to you. The registrar's own process governs, and it is generally lighter.

Everything That Points At You From Somewhere Else

Your website is the part you control. It is not the part that generates the awkward phone calls.

Google Business Profile. Edit the name to match your real world signage. Google reviews changes before they go live on the profile, and its guidance notes that if you change your business name after verification you might need to verify the business again ^[3]. Budget time for that. For a shop or a service business, the profile is often the first result a customer sees, and a mismatch between the profile name, the sign over the door and the website is exactly the kind of inconsistency that erodes trust before anyone has read a word of your copy.

Email. If the domain changes, so do your addresses. Keep the old mailboxes receiving for at least as long as you keep the redirects, because suppliers and long standing customers will write to the old address for years.

Everywhere else. Directory entries, professional body listings, industry associations, review sites, social profiles, the footer of your invoice template, your email signature, sponsorship pages from local clubs. Make the list once and work it down. Nobody enjoys this part and it cannot be automated.

The Rename Sequence in Five Steps

1. Map. Write down every existing page address and its new equivalent before the new site is built.
2. Stage. Build the renamed site privately, apply the map there, and confirm the old addresses land where you intended.
3. Deploy. Push to production, put the redirects live, then spot check a sample of real old addresses from an outside connection.
4. Notify. Submit the Change of Address in Search Console and update your Google Business Profile the same day.
5. Monitor. Review Search Console weekly for two months, fix anything reporting as not found, and keep the old domain renewed.

Five steps, in that order. Steps one and two are the ones under time pressure that get skipped, and they are the two that determine whether step five is quiet or busy.

One honest exception to all of the above. If your website is only a few months old, has little organic traffic and almost no inbound links, there is nothing meaningful to preserve. Buy the new domain, build the new site, put a basic redirect in place and get on with running the business. Hosted site builders handle that case perfectly well on their own, and the full mapping exercise would be effort spent protecting an asset you have not built yet. The sequence matters in proportion to your history.

Conclusion

A rename is a sequencing problem rather than a design problem. The new logo will be fine. What determines whether the rebrand costs you a quarter of trading is whether the redirect map was written before the new site, whether Google was told, whether the old domain stays renewed, and whether the twenty places that mention your old name got updated by someone whose job it was.

Everything on that list is knowable in advance, which makes it plannable. If you are carrying years of search history into a new name, do the mapping first and let the launch date follow the work rather than the other way around.

Frequently Asked Questions

Do I have to change my domain name if I change my business name?

No. A rename creates no technical requirement to move domains, and keeping your existing address carries zero search risk. The question is whether the mismatch between your web address and your trading name will confuse customers reading a quote, a van or a shopfront. For a small change of name, staying put is often the right call. A complete change of identity usually justifies the temporary disruption of moving.

Will I lose my Google rankings if I move to a new domain?

Not permanently, if the move is done properly. Google treats a permanent server side redirect as a signal that the new URL should be the canonical one, so ranking signals transfer. Expect temporary fluctuation while Google processes the move, which its own documentation describes as normal for a site move. Google indicates a small to medium sized site can take a few weeks for most pages to move across.

How long should I keep the old domain and its redirects running?

Google recommends keeping redirects for as long as possible, generally at least one year, and suggests considering keeping them indefinitely from a user perspective. Treat the old domain as live infrastructure: renew it, diary the renewal, and check occasionally that the redirects still resolve. An expired old domain takes every redirect with it.

Can I just point all my old pages at my new homepage?

You can, and you will lose most of the benefit. Google's site move guidance specifically advises against redirecting many old URLs to one irrelevant destination such as the new homepage. Each page should redirect to its closest equivalent so the history attached to that specific page carries across. Page to page mapping is the difference between a move and a restart.

What do I need to do with my Google Business Profile?

Update the name so it matches your real world signage and branding. Google reviews profile edits before publishing them, and its guidance notes you might need to verify your business again after a name change. Do this on launch day rather than weeks later, because a profile showing your old name alongside a website showing the new one reads as a red flag to anyone checking you out.

Does a company name change affect my .ie domain?

It can. Every .ie holder has to evidence a connection to Ireland, and the registry routes changes of registrant through a process requiring the registrant to meet the registration criteria and provide supporting documents. Depending on how your registrar handles it, updating the registrant name may need your certificate of change of name attached. Raise it with your registrar well before your launch date so the domain is not sitting on hold when you need it.

Sources