Company Name Change Runbook: Protect Your Search Traffic

Changing a company name costs little on paper. In the UK, it costs £20 to file online, or £83 for the same-day service, and the name changes only when Companies House registers it. Search performance is where teams tend to get hurt. Google says permanent redirects don't cause a loss in PageRank, yet still warns site owners to expect ranking fluctuation, and Sitebulb argues that a redirect alone will not make Google connect the old name with the new one. This covers when a rename makes sense, the legal filings, domain choice, SEO steps, and a launch day runbook. It is not legal advice, and it gives no traffic guarantees.

Rename or refresh: which one do you actually need?

A refresh changes presentation and tone: new logo, new colours, tighter messaging. The name and domain stay where they are, and branded queries resolve as before. If the real complaint is that the identity looks dated, a refresh is almost always the right call.

A rename changes what users type into Google. That is a different tier of risk, because every branded query, backlink anchor, and directory listing still carries the old name.

So when is it worth it?

• The name is too close to another company's name or trade mark. GOV.UK says a name that is too similar to another company's name or trade mark may have to be changed if someone complains, and a forced rename is a worse time to do this than a planned one.
• A merger, acquisition or split has left the old name describing something that no longer exists.
• The name is tied to one product or one town and the business has outgrown it.

There is a middle route. A UK company can trade under a different business name without altering its registered corporate name, provided the business name avoids words such as 'Ltd', 'LLP', and 'plc', and contains no sensitive words without permission (GOV.UK). This lets you test a new brand before committing to legal filings.

Settle the name before doing anything else. I have documented a brand naming process to run before approaching Companies House. Rename once, not twice. Google advises site owners during migrations to change only one thing at a time, so do not pair the rename with a template overhaul or a CMS switch in the same week.

The legal steps: UK first, then US notes

UK: Companies House

A UK company can change its name by special resolution or by permission given in its articles of association. The new name has to follow the usual naming rules, so check availability on the Companies House register before you fall in love with anything. And remember: the name won't officially change until Companies House registers it.

There are three filing routes:

• Online, special resolution only: £20 to file, or £83 for the same-day service.
• Post, special resolution: form NM01 with a copy of the resolution attached and a £30 cheque.
• Post, permission from the articles: form NM04 and a £30 cheque.

WebFiling requires your registered account email, password, and an authentication code, and you may also need to verify your identity with GOV.UK One Login. If nobody at your company has used the service before, Companies House posts that code to your registered office. Start early: a paper letter in the post can stall your target launch date.

Once registered, Companies House issues a certificate showing the new name and registration date. That date governs the switch, regardless of internal preferences.

On deadlines, the overview page lists name changes among reportable company updates, setting 14 days for records location, directors, and secretaries, 15 days for constitutional articles, a month for issuing shares, and 21 days for all other changes. Name is absent from the shorter categories. Because the name only changes upon registration anyway, file early and verify deadline queries directly with Companies House. You may also need to notify HMRC.

One statutory obligation directly affects web teams: a company must display its name at its registered office, other places of business, on business documents and on websites. Footers, invoices, email signatures, and legal pages all need updating the moment the certificate arrives.

US notes

The US has no unified process. For LLCs and corporations, legal names change by filing articles of amendment, or the state equivalent, with the Secretary of State or corporate registry. Forms, fees, and processing times vary by state. Start with your state business registry, confirm IRS requirements for your entity type, and audit state licences, tax accounts, and contracts carrying the legacy name. If you only want a customer-facing brand, many states allow a trading name or DBA registration instead, which works like the UK business-name option above.

Keep the domain, redirect it, or run both for a while

This is the decision that sets your SEO workload. Three options:

Retaining the domain carries the lowest search risk, because URLs stay identical. If the legacy domain is not embarrassing, keep it for a year or two and handle any domain migration later as an isolated project. That fits Google's one-thing-at-a-time advice.

Migrating and redirecting is standard procedure when the old domain reflects the former name and you want the new identity in the browser bar. It is a full site move, and the detail follows below.

Running both needs care. Google's 2012 guidance warns against two crawlable sites with largely identical content unless you use a 301 or a canonical. So 'both' should mean the new domain is live and the old one redirects, with the old domain still registered, renewed and answering email. It shouldn't mean two copies of the site.

Whichever you choose, hold on to the old domain. Redirects only work while the domain does.

The SEO steps: redirects, Change of Address, schema and listings

Skip this section if you plan to keep the domain, apart from the schema and directory listings instructions. For a domain migration, follow this order.

Build the redirect map

Google recommends server-side permanent redirects such as 301 and 308 from old URLs to new URLs, following a mapping. Route each legacy URL to its closest counterpart, not to the homepage. Send traffic straight to the final destination: Googlebot can follow up to 10 hops, but Google advises keeping chains ideally no more than 3 and fewer than 5. Small and medium sites should move all URLs at once, while larger properties can migrate section by section. My redirect map guide for large migrations details the mechanics.

If you face thousands of legacy URLs without a clean mapping, our site migration service covers the redirect map and cut-over execution.

Tell Google with Change of Address

Google instructs site owners to run Change of Address in Search Console on the old property when migrating domain names or subdomains. It is not needed for HTTP to HTTPS, www to non-www switches on the same domain, or subfolder path shifts. Search Engine Journal reports the guidance now says to submit requests for all subdomains as well as www and non-www variants of the old domain, even when unused, with every variant verified. Verify every old and new variant first, www, non-www, HTTP, HTTPS, then submit.

Clean up the new site

• Self-referencing canonical tags on each new URL.
• Hreflang annotations pointing at the new URLs.
• Internal links updated to the new addresses, so you aren't leaning on redirects inside your own site.
• A new sitemap submitted in Search Console.
• Enough server capacity, because Google says it will temporarily crawl the new site more heavily than usual.

Structured data and sameAs

Update your Organization structured data: name , url , logo , and a sameAs array pointing to active official profiles, including LinkedIn, social channels, and genuine brand properties. During the transition, add the old name as alternateName. This guarantees nothing on its own, but it gives another consistent, low-cost entity signal.

Business listings and profiles

Google's migration documentation instructs site owners to update profile links, ad campaigns and internal links, and to contact sites that link to your old URLs. In practice, update your Google Business Profile, social pages, directories, marketplaces, app stores, payment processors, and email footers. Assemble this list before launch day, or half of it will get missed.

What to expect afterwards

Google states that medium-sized sites can take a few weeks or more for new URLs to replace old addresses in search results, and longer for larger sites. Recrawl guidance indicates crawling can take a few days to a few weeks. Ranking volatility during that window is normal. Nobody can guarantee you retain the same traffic. For the full migration procedure, use our site migration SEO checklist.

Teaching search engines and AI assistants the new name

Most rebranding projects cut corners here. Technical redirects route URLs; they do not tell search systems that Brand B is the same corporate entity as Brand A.

Sitebulb argues a 301 isn't enough in a rebrand: you can lose branded search traffic if customers don't recognise the new name, backlink authority can slip if third-party sites don't update their links, and Google's Knowledge Graph may not connect the old and new names. It points to WooCommerce's rebrand to Woo as an example where Google might not understand the new brand is the same entity, even with redirects, structured data and backlinks handled. (Sitebulb sells SEO software, so read it as a warning, not a measurement.)

Predicting how any given AI assistant will synthesise brand updates is impossible, and source documentation offers no guarantees. The practical move is still the same: feed every system the same facts, repeatedly, in locations it already indexes.

• One canonical set of entity facts. Same legal name, trading name, address, description and founding details on your About page, schema, listings and profiles. Inconsistencies are what make a model or a knowledge panel hedge.
• 'Formerly known as' signals. A plain sentence on your About page, in the homepage copy for the first months, in your announcement post and in press or partner mentions: 'New Name, formerly Old Name.' Say it in ordinary prose, not just in markup.
• Third-party updates. Ask the sites that link to you or describe you to change the name and the URL. Your own pages are only part of the picture.
• Companies House. Your registered name is public. Make sure what you publish elsewhere matches it, including punctuation.

Do not erase the former name overnight. Keep it findable in context for at least the redirect period, ensuring searchers using legacy brand queries land on pages that explain the transition.

The rename runbook

Order matters. The legal date can slip (that postal authentication code again), so the site changes should be ready, not live, until the certificate exists.

Before launch

1. Settle the name, check it against the Companies House register, and decide on a rename, trading name or refresh.
2. Pass the special resolution (or confirm permission in the articles) and file by your chosen route.
3. Decide the domain: keep, move, or move with a period of overlap.
4. Verify every variant of the old and new domains in Search Console.
5. Build the redirect map, test it on staging, and flatten any chains.
6. Prepare the new site: canonicals, hreflang, internal links, sitemap, Organization schema with sameAs and the old name as alternateName.
7. Draft the 'formerly known as' copy, announcement, email footers and invoice templates.
8. List every listing, profile, ad account and partner site that carries the old name.

Launch day

This starts only when the Companies House certificate arrives showing the new name and registration date.

1. Switch on the 301 or 308 redirects from old URLs to new ones.
2. Spot-check your most-linked and highest-traffic old URLs: one hop, landing on a 200 page.
3. Submit Change of Address for each verified old variant (domain or subdomain moves only).
4. Submit the new sitemap.
5. Update the site name, footer, legal pages, invoices and email signatures.
6. Publish the announcement and the About-page 'formerly known as' wording.
7. Update Google Business Profile, social profiles and live ad campaigns.

After launch

1. Check the Index Status and Sitemaps reports for both properties, and look at branded queries for the old and new name.
2. Chase the sites that link to you and ask for the new name and URL.
3. Tell HMRC about the change if it applies to you.
4. Keep the redirects. Google says generally at least 1 year, and consider keeping them indefinitely for users.
5. Renew the old domain for as long as the redirects run.

FAQ

Can I announce the new name before Companies House registers it?

You can discuss the change, but the corporate name changes legally only upon registration, confirmed by the certificate date. Keep the former name on invoices and in site footers until then. If you intend to trade under the new identity early, the business-name route provides a cleaner path.

If I keep my domain, do I need Change of Address?

No. Google reserves the Change of Address tool for domain or subdomain migrations. It is not required for HTTP to HTTPS, www to non-www, or directory path reorganisations. You still update title tags, copy, schema, and directory listings, but you bypass domain redirect maps and Search Console submissions.

Should I use temporary redirects while I test?

Never on a production site. Google's documentation states that permanent redirects show the new target in search results, while temporary redirects show the source page. Test response codes on staging, then launch using 301 or 308 redirects.

What happens to my branded search traffic?

Expect traffic to shift as users continue searching for the legacy name for some time. Sitebulb warns that branded traffic drops when customers do not recognise the new name. Track both queries in Search Console and keep explanatory 'formerly known as' copy visible until search volume for the old term fades.

The primary constraint is clear: a 301 transfers URLs, and Google says PageRank is preserved, but server redirects do not teach search engines that your new brand is the same business. File the legal paperwork first, migrate the site only after the certificate arrives, and treat 'formerly known as' entity signals as a required part of the migration rather than an afterthought.