You're Rebranding. Here's the Social Media Plan.
New name, new logo, new positioning — and an audience that only knows the old you. A practical plan for rebranding on social without starting over.
A rebrand looks like a design project. You pick a name, approve a logo, update the website, and ship it.
Then you get to social, and the hard part isn't the logo. It's that your audience knows you by a name you're about to stop using. Your handle is in old emails, podcast show notes, other people's bookmarks. Half your best-performing posts carry the old wordmark. And the moment the name changes, everyone who followed you for the old thing has to decide, again, whether they care about the new thing.
Most brands handle this by posting a logo reveal and hoping. Here's the version that works.
First, be honest about which rebrand this is
The plan changes completely depending on what you're changing. Three different things get called "rebranding":
A visual refresh. Same name, same promise, new logo, colours, templates. The easy one — no handle changes, no explaining. You just need everything to switch over at once and not look like two brands for a fortnight.
A name change. Same company, same product, different name. Handles move, links break, and you have to actively teach people a new word. This is where most of the risk lives.
A repositioning. The name might stay, but who you serve and what you claim has changed. Nothing technical breaks — and that's the trap. The audience you built came for the old promise, and some of them won't want the new one. The work here is content, not logistics.
Write down which of the three you're doing before you plan a single post. A repositioning announced like a logo reveal lands as noise. A name change announced like a repositioning leaves people unable to find you.
The pre-launch checklist nobody does
Do this a week before you announce, not on the day.
- Confirm you can actually get the handles. Check every platform, including ones you're not active on. If the name is taken somewhere, decide your fallback now rather than mid-announcement.
- List everywhere the old name appears. Bios, pinned posts, link-in-bio pages, highlight covers, ad accounts, email signatures, posts already in the queue. You'll be surprised how long the list is.
- Check who holds the keys. Changing a page name on some platforms needs admin or business-manager access, not just an editor login. If you don't know who has what, run an access audit first.
- Export your old creative. Once the new templates land, nobody rebuilds the old ones. Save your best posts and brand files into an asset library you can search later.
- Clear or rewrite the queue. Anything already scheduled will publish under the new identity in the old voice.
- Draft answers to the obvious questions. "Did you get acquired?" "Is the product changing?" "Do I need to do anything?" Write them once, paste them in DMs for a month.
What to post in the two weeks before
Don't go from silence to logo reveal. A short warm-up gives the announcement somewhere to land, and lets you talk about the why without the new name doing all the work. Three posts is enough:
- Name the shift, not the brand. Something you've learned, a kind of customer you keep attracting, a thing you've stopped doing. No teaser language — just the thinking.
- Show the work. Early name options, rejected directions, a messy whiteboard. People are far more interested in the decision than the output.
- Ask. A genuine question about the thing you're repositioning around. You'll get replies you can quote later, and the people who answer feel part of it.
Doing only a visual refresh? Skip the warm-up. Nobody needs two weeks of runway for a new colour palette.
Switch day: one post, not a campaign
On the day, you need exactly one post that a stranger could read in isolation and understand. It covers four things, in this order:
- What changed. Plainly. "We're now called X." Not "we've evolved into a new era of."
- What didn't. The line people actually scan for. Same team, same product, same login, same prices — whichever is true.
- Why. One or two sentences, about them rather than about your internal clarity.
- What they need to do. Usually nothing. Say "nothing changes for you" explicitly if that's the case.
Then make it findable: pin it, put the old name in the caption at least once so search still surfaces you, and keep "formerly Y" in your bio for the first month. That one parenthetical prevents most of the "wait, is this the same company?" confusion.
Post it early in the week, when you can reply to comments for a few hours. The replies under an announcement are more of the announcement than the post itself.
The 30 days after: repeat without boring yourself
Founders consistently get this wrong: you'll be sick of your own rebrand within four days. Your audience will barely have noticed it. A single post reaches a fraction of your followers — and that's before anyone has to remember a new word. So plan for repetition:
- Weeks 1–2: Reference the change in passing in normal posts. Not another announcement — a line in a caption, the new name said out loud in a video.
- Week 3: Publish the longer story. The reasoning, the rejected options, what you learned. This is the piece people share, and one outline gives you a post, a carousel, and a video script.
- Week 4: Back to normal, fully in the new identity. If you're still announcing after a month, the rebrand has become your content strategy.
Keep your content mix intact through all of it. A month of nothing but brand talk is a month of nothing useful.
What to do with your old content
Don't delete it. Wiping a year of posts to make the grid look consistent destroys the proof you've been around, and takes your best-performing content with it. Three options, in order of effort:
- Leave it. For most brands this is correct. Old posts with an old logo read as history, not as a mistake.
- Archive selectively. Hide only posts making a claim you no longer make — old pricing, an abandoned promise.
- Re-caption the top performers. Your handful of genuinely strong posts are worth updating: new caption, new CTA, new link. Same creative, extended life.
If links are involved, set up redirects on your own site before the announcement and update the link-in-bio first. Traffic lost in a rebrand mostly goes to dead links, not confused followers.
Expect the dip, and know what to measure
Something will go down. Reach usually dips for one to three weeks, because you changed the thing your audience recognises mid-scroll — the name, the colours, the profile picture. Announcement posts also tend to underperform your normal content, because they ask for attention without giving much.
Decide in advance which numbers you're watching, so you don't panic at the wrong one:
- Profile visits and link clicks — are people still finding you and following through?
- Saves and shares on the announcement — did the story land?
- Replies and DMs — where confusion shows up first, and where you fix it one person at a time.
- Follower count — expect a small net loss. People who followed the old promise leaving is a rebrand working, not failing.
If reach is still down after a month, treat it as a normal reach-drop diagnosis rather than blaming the rebrand. By then it's usually cadence, format, or a run of safe posts.
Run the whole thing from one calendar
A rebrand is the worst possible time to be coordinating content across a group chat, a doc, and three scheduling tabs. There's a hard date, assets changing underneath you, and copy that needs a second pair of eyes.
Put the whole sequence — warm-up, announcement, follow-ups, the week-3 story — in one calendar, on real dates, with the new assets attached and someone named on each item. That's the loop Trendly is built for: plan it in the content calendar, draft each piece with AI against your new brand voice, have a teammate approve it before it goes out, and schedule to every platform from one place. When the launch date moves — and it will — you move the plan, not twelve scattered reminders.
The rebrand your audience remembers isn't the one with the best logo. It's the one they never had to think hard about.
