How to Change Your Company Name

Three things to settle before you touch anything

A rename is one of the few naming decisions with genuine switching costs, so it deserves a higher bar than a first name did. These three gates come before any of the work below.

1. The new name is scored, not just lovedYou are about to spend months moving everything you own onto this word. Score it the way you would score a stranger’s candidate: domain availability, memorability, phonetics, cross-language safety. A rename that lands on a name no better than the old one is the worst outcome available, and it happens more often than anyone admits.
2. The legal check is done and written downA knock-out search on the registers that matter for your class and markets, and a lawyer’s opinion if there is anything close. Doing this after the announcement is how a rename turns into two renames. Namoly does not check trademarks, so this step is yours and it is not optional.
3. Everything is secured before anyone is toldDomain, the obvious variants, the handles, the entity filing if you need one, and any code or package namespaces. The moment you announce, the name is public, and the gap between announcement and ownership is exactly when somebody registers the .com you were about to buy.

If any of those is still open, stop here. The decision itself is worked through in when to rename your startup, generating the replacement is in how to brainstorm brand names, and the legal groundwork is in trademark basics for startup naming.

The migration inventory

Your name is in more places than you think, and the ones you forget are the ones customers find. Work through these ten categories and write down every item that applies to you before you schedule anything. The list is the deliverable: a rename fails from incompleteness far more often than from bad execution.

• Domain and redirectsThe new domain live, the old one kept and renewed for years rather than dropped, and a permanent redirect from every old URL to its exact new equivalent. Not a blanket redirect to the homepage: page for page, or you throw away the ranking of everything except the front door.
• Website, docs, and searchEvery mention in copy, meta titles, structured data, and image assets. Then the search plumbing: verify the new property, submit the new sitemap, and use your search console’s change-of-address flow if the domain moved. Internal links should point at the new URLs directly rather than hopping through redirects.
• Email and everything that sends itNew addresses, old ones still receiving, and the sending domain reauthenticated so your mail does not start landing in spam on launch week. Transactional email, notification templates, calendar invites, and the address on every automated receipt all carry the name.
• The legal and financial layerEntity or trade-name filings, tax registrations, the bank, the payment processor, invoices and invoice templates, and any contract that names you. Some of this is a form and some of it needs a lawyer; none of it is optional, and several parts run on somebody else’s schedule.
• Product surfacesApp store listings, the app icon and title, OAuth consent screens, API documentation, error messages, in-product copy, PDF exports, and email footers. This category is the one teams underestimate, because the name is scattered through code as strings rather than sitting in one config file.
• Code and package namespacesRepository names, package registry entries, container images, CLI commands, environment variable prefixes, and anything a customer types. Published package names in particular cannot always be moved cleanly, so plan a deprecation path rather than a rename.
• Third-party listingsMarketplaces, partner directories, review sites, job boards, conference profiles, and every integration page that displays your name. Each is an account you have to find, log into, and update. The ones you forget are the ones customers find first, because directories rank well.
• Social handles and communitiesHandles, display names, pinned posts, community servers, and the group chats where customers already talk about you. Handles are claimed by other people while you are still deciding, which is why this belongs in the pre-announcement lockdown rather than in launch week.
• Printed and physicalSignage, packaging, business cards, merchandise, slide templates, email signatures, and anything already in a warehouse. This is the visible part, the part with a real invoice attached, and the part that makes the change feel real to the team.
• The human layerSupport macros, sales decks, onboarding scripts, the way people answer the phone, and a one-line answer to “didn’t you used to be called something else?” that every employee can give without hesitating. A rename that the team cannot explain in a sentence is a rename customers will find confusing.

Notice how much of this belongs to someone else: registries, stores, directories, banks, partners. That is why a rename takes months rather than a sprint, and why the calendar is set by the slowest third party rather than by your team.

The order of operations

Everything above can be done in almost any sequence except these six steps, where the order is the whole point.

1. Lock everything down, quietlyDomain, variants, handles, filings, namespaces. Nothing is announced, nothing is public, and the whole surface belongs to you before a single person outside the company hears the word.
2. Build the new surface in parallelStand up the new site, the new email, and the new product copy while the old ones keep running. A rename executed as a big-bang switch on a Friday is a rename with an outage in it.
3. Tell the people who will be surprised, firstCustomers on contracts, big partners, and anyone whose integration references your name should hear it directly and before the public post. Being surprised by your rename in a newsletter is how a supportive customer becomes an annoyed one.
4. Switch, redirect, and keep both aliveFlip the site, put the permanent redirects in place, and leave the old domain, the old email addresses, and the old handles working. Both worlds run in parallel for a long time, and the old one is retired far later than feels necessary.
5. Chase the long tail for monthsWork the third-party listings, the directories, the old links you can politely ask to be updated, and the search results still showing the previous name. This is unglamorous, it is where most of the recovered value is, and it is the step teams abandon at week three.
6. Watch the numbers that would show a problemBranded search for both names, direct traffic, referral sources, and support tickets mentioning the old name. You are not looking for a dip, which is normal. You are looking for a dip that is not recovering.

Step one has its own guide, because the order in which you claim things matters too and some of it is cheaper than founders expect: how to secure a brand name.

What redirects preserve, and what they do not

The single most valuable technical detail in a rename: redirect page to page. Every old URL should send visitors and crawlers to its exact new equivalent, permanently. A blanket redirect that dumps every old page on the new homepage is the most common and most expensive mistake in the entire process, because it tells search engines that none of those pages exist any more.

Done properly, redirects carry much of your accumulated ranking across. They do not carry all of it, they do not do it instantly, and they cannot fix the fact that the words around your inbound links still say the old name. Verify the new property in your search console, submit the new sitemap, and use the change-of-address flow if the domain itself moved. Then wait, because recovery is measured in months and it is not a straight line.

One thing worth doing on day one: keep a plainly-worded page that says the old name, says the new name, and explains the change. It gives search engines an unambiguous signal and gives confused customers somewhere to land.

The parts you cannot control

Every rename has a residue, and knowing what it is in advance stops you burning energy on it.

• Links you do not ownEvery article, forum post, and directory entry pointing at the old name belongs to someone else. Redirects carry much of that value across, and the text around the link keeps saying the old name forever. Ask nicely for the important ones and accept the rest.
• Search demand for the old namePeople will keep searching for what they remember, for a long time. Keep a page that answers it plainly, keep the old domain renewed, and make sure the query lands somewhere useful rather than on a competitor.
• The recovery curveSearch recovery after a domain move is measured in months rather than weeks, and it is uneven. Anyone who promises you a specific number is guessing. Plan for a period of reduced discoverability and do not panic in week two.
• What people call you in conversationThe old name lives in habits, saved contacts, and internal wikis at customer companies. It fades on its own. Correcting it aggressively costs goodwill and buys almost nothing.

None of this argues against renaming. It argues for renaming once, deliberately, onto a name that measurably beats the one you have, because you only want to pay this bill a single time. If you are not certain the new candidate clears that bar, put both names side by side and look at the gap before the migration starts.

Frequently asked questions

How do you change your company name?

In four stages. First secure everything under the new name quietly: domain, handles, filings, namespaces. Then build the new site, email, and product copy in parallel with the old ones still running. Then switch, redirect every old URL to its exact new equivalent, and tell major customers before the public announcement. Then spend months updating third-party listings and monitoring search for both names.

Will changing my company name hurt SEO?

It carries real risk that careful execution mostly manages. Permanent redirects from each old URL to its exact new equivalent preserve much of the ranking you built, but not all of it and not instantly. Recovery after a domain move is measured in months, the links you do not control never update their wording, and blanket-redirecting everything to the new homepage throws away most of what you had.

How long should I keep the old domain after a rebrand?

Years, not months. The old domain has to keep redirecting for as long as links, bookmarks, printed material, and search results point at it, and all of those outlive the rebrand announcement by a long way. Keep the registration renewed and the redirects live; letting it lapse hands your remaining traffic and reputation to whoever registers it next.

What is the most commonly forgotten item in a company rename?

Third-party surfaces you do not log into often: marketplace and directory listings, partner pages, review sites, OAuth consent screens, invoice templates, and published package or repository names. They rank well and they are seen by exactly the people evaluating you, so a stale listing is the version of your brand a new customer meets first.

Should I announce a name change before or after switching?

Secure first, then tell the people who would be blindsided, then switch publicly. Announcing before you own the domain and handles invites someone else to take them. Announcing after the switch, with no warning to customers on contracts or partners with integrations, turns a supportive audience into a confused one.