How to announce a rebrand or company name change

A rebrand release has one job no other announcement has: making the old name findable next to the new one. Name both entities plainly in the headline or the first paragraph and again in the boilerplate, keep the announcement itself short, and treat the release as one part of the repair rather than the whole of it. The site move that carries your old URLs across is separate work with separate mechanics.

A rebrand announcement is the only release written for people who are looking for something else. Everyone who needs it will arrive searching the old name — customers, suppliers, journalists checking an old quote, procurement teams matching an invoice to a supplier record. That single fact determines the copy, and it is the opposite of the instinct, which is to write about the new identity.

Name both entities, plainly, more than once

The sentence that does the work is the dull one: "Corradine Cold Storage, formerly Northgate Chilled Logistics". It needs to appear in the headline or the first paragraph, and again in the boilerplate. Not "we are excited to unveil" — the literal old legal or trading name, adjacent to the new one, in a construction a person and a machine can both parse.

Two further specifics for this category. Give the effective date, because contracts, invoices and purchase orders reference it. And state explicitly what has not changed: legal entity, company number, VAT registration, bank details, contract terms, account managers. In practice that paragraph is the most-read part of a rebrand release, because the first question a finance team asks is whether they now have to re-paper anything.

If the rename follows a transaction, the acquisition announcement and the rebrand release should tell one story and cross-reference each other. Two disconnected releases leave two half-trails.

The site move is the other half, and it is not optional

The release is not what preserves your search presence — the redirects are. Google's guidance on moving a site with URL changes is worth reading in full before the domain changes, but three points bear directly on the announcement's timing:

• Permanent redirects do not cost you credit. The documentation states that "301 and other permanent redirects don't cause a loss in PageRank".
• It is not instant. "For medium-sized websites, it can take a few weeks or more for Google to gradually start showing the new URLs instead of the old ones (and for larger sites, even longer)."
• Keep them. Google's own summary of the process says to maintain redirects for at least a year.

Which means the release should go out after the redirects are live, not before, and that the weeks following are the period when both names need to resolve. The other mechanism worth knowing is the canonical: where the same content exists at more than one URL, search engines pick one copy and you do not choose which. During a rename that is a feature — it is how the old and new pages get consolidated — but only if the redirects tell it which one you want.

Your old name is published, permanently, on other people's servers

Here is the constraint specific to this category. Every release you have ever distributed still carries the old name, on pages you cannot edit. We opened a February 2026 release still live and unchanged in late August; financial terminals keep these archives indefinitely.

Two further behaviours we measured make this messier than it sounds. On one outlet, the published slug of a release was changed after delivery, so the originally indexed URL now 301s — meaning a link recorded in a delivery report can quietly stop resolving to what the report said it was. And on Digital Journal, five whole reseller-wire sections returned 410 Gone when we checked, the status a publisher uses to tell search engines a page is permanently removed. So the old name's trail is partly frozen, partly rewritten and partly deleted, entirely at the publishers' discretion.

You cannot fix that by asking. Google's own documentation on removals is scoped to pages you host and sends anyone who does not own the page somewhere else. What you can do is make sure there is a well-distributed, correctly dated release that connects the two names, so that anyone — or anything — reading the old trail finds the bridge. That is the actual job of a rebrand release, and it is a job worth doing properly once.

If you have distributed before, this is a good moment to check what is still live under the old name. It takes ten minutes and it tells you what your old identity still looks like from outside.

Clear the name before you announce it

The wires push the risk onto you. 24-7PressRelease's terms require the submitter to warrant they hold "all necessary rights, licenses, permissions, and consents" for the submitted content including "logos, videos, trademarks", and that the submission does not infringe third-party trademark rights, with an indemnity attached. A rebrand release is the one submission where you are asserting rights in a name you may have owned for a fortnight. Have the clearance and the registration status settled before the release goes out, not while it is on the wire.

The shape that clears editorial

A headline and lede you could file

Northgate Chilled Logistics becomes Corradine Cold Storage from 1 December 2026

>

MANCHESTER, United Kingdom, 3 November 2026 — Northgate Chilled Logistics will trade as Corradine Cold Storage from 1 December 2026, following its acquisition by Halden Freight in January. The legal entity, company number, contracts, pricing and account contacts are unchanged; existing purchase orders remain valid and no re-contracting is required.

Both names, an effective date, a cause, and the finance department's question answered in the second sentence.

What the announcement can and cannot do

It can create the durable public bridge between two names, dated and hosted somewhere other than your own site — which is exactly what a reader arriving from an old invoice or an old article needs. It can pre-empt the "is this the same company" support queue. It can give suppliers a document to attach to a record change.

It cannot move your rankings; the redirects do that, on their own schedule, over weeks or longer. It will not pass link credit from press pages to the new domain — press links are overwhelmingly nofollow, and the wire decides that, not the masthead. It cannot retrieve the old name from pages you do not control. And a distribution receipt confirming the release went out is not evidence anyone has updated their records: what a send receipt actually confirms is a smaller thing than it sounds, and a sample report shows the larger one.

The check before you send

• Redirects live and tested from every old URL before the release goes out.
• Old name and new name adjacent in the headline or first paragraph, and again in the boilerplate.
• Effective date stated, and what has not changed spelled out.
• Trademark clearance and registration status settled.
• New domain resolving, new email addresses working, old ones still receiving.
• Redirects diarised to stay in place for at least a year.