First, prove the fall is real and started with the change
A rename moves so many systems at once that the reports describing the fall are themselves suspect. Take enquiries and sales from the system that records money and work: the job book, the order system, the invoicing tool or the CRM rather than analytics or an ad platform. Those records did not change when the website did. Kaushik's measurement model begins with the business objective and derives the measures from it; read the same way, the outcome the business cares about comes first and every channel figure sits beneath it.
Next, choose the comparison. The weeks before a launch are usually busy and disrupted, so setting the month after against the month before mostly measures the season and the upheaval. The guide to comparing periods fairly explains why a Year-on-Year ComparisonComparing a period with the same period a year earlier, aligned by weekday and by holidays that move, so that the seasonal pattern drops out of the change. with weekdays and holidays aligned is the better test, and how to treat a period whose tracking broke partway through. If a week holds only a handful of enquiries, the guide to reading small numbers shows how to pool periods before reading a change.
Then date each part of the launch. A measurement change log records what changed in which system and when; if nobody logged the rollout, rebuild the entries from release notes, ad account histories, agency emails and the registrar's records. A Change LogA dated record of changes made to tracking, accounts, reports, lists or rules, with who made each and why, so later movements in the figures can be traced. entry per launch task shows whether the fall began on launch day, when the listings changed, or before the rebrand at all. A fall that predates the change, or that hits every channel with no link to the launch, belongs to the diagnosis of results down across every channel.
| What to establish | Where it comes from | What it rules out |
|---|---|---|
| The fall in enquiries and sales | The job book, order system or CRM | A fall that exists only in analytics or an ad platform |
| The fall against the same weeks a year earlier | The same record, aligned by weekday and holiday | A seasonal dip blamed on the rename |
| When each part of the launch went live | The change log, rebuilt if necessary | A cause that predates the rebrand |
| Which sources lost the most | Enquiry source fields, call records, analytics by channel | Treating a fall in one route as a fall everywhere |
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Branded search clicks and direct enquiries fell; customers say they could not find you | Search the old name: who appears, and where do the results lead? | Searches for the old name now find a rival, a directory or nothing | Keep catching the old name with a campaign, an explanation page and mentions on the site |
| Organic visits fell, mostly on pages that used to rank | Request each top old address and note where it lands | Old addresses not redirected page to page | Point each old address at its matching new page, permanently |
| Analytics or ad platform conversions fell more than the job book or order system | Tags, conversion triggers, click identifiers and datasets on the new site | Tracking changed with the site or domain | Restore tags and triggers, then annotate the gap and restate the comparison |
| Calls and visits from maps and directories fell; some customers rang an old number | Search the old and new name, address and phone in quotes | Listings and profiles show the old name or mixed details | Correct the source record, then the profile, the website and the directories |
| Email clicks and replies fell from the first send under the new name | Engagement by mailbox provider; sender name and sending domain changes | Subscribers do not recognise the new sender, or mail stopped reaching them | Show both names for a while; authenticate and warm any new sending domain |
| Returning customers and referrals fell while new prospects held steady | Which colours, shapes, phrases and characters changed at launch | Customers do not recognise the identity because familiar cues were dropped | Restore or bridge the famous, unique cues and measure recognition |
Fix, verify and prevent each cause
Searches for the old name now find someone else
A name keeps being searched for long after it changes, by former customers, by friends who passed it on and by anyone holding an old leaflet. If nothing of yours answers that search, a directory page, a review site or a rival's ad will. The rebrand rollout tutorial makes catching those searches a launch step of its own.
Fix: advertise on the old name and send those clicks to a short page saying what the business is now called and why, with a clear route onward; mention the former name on the homepage and about page too, so organic results tie the two together. Look at who else now shows up for the old name: the competitor keywords guide describes a campaign on your own name as usually the least expensive protection when a rival targets it. If the old name was given up after a dispute, ask your legal advisers before advertising on it.
Verify: your page or ad appears first for the old name, and its Branded SearchSearch queries that contain a company's or product's brand name. clicks reach the explanation page and go on to the new site.
Prevent: give the old name an owner and keep its campaign until its searches have dwindled and the new name's have taken their place.
Old addresses that land on the wrong page
A new domain or rebuilt site is a site migration, whatever the brand team called it. Old addresses carry the rankings, other sites' links and customers' bookmarks; if they lead nowhere, or all to the homepage, organic visits fall on the very pages that used to bring enquiries. The diagnosis of traffic lost after a migration owns this cause and its neighbours, such as redirect chains and staging rules left on the live site.
Fix: list the old addresses that brought the most organic visits and enquiries, request each one, and send every address to the matching new page with a permanent redirectA permanent server redirect telling browsers and search engines a URL has moved for good., using the redirect map template as the working record. Keep the old domain registered and redirecting.
Verify: each sampled old address reaches its matching page in a single hop and organic visits to those pages begin to recover.
Prevent: before any future domain or structure change, build the full redirect map and follow the site migration guide, so the redirects are tested on staging rather than discovered missing after launch.
Tracking that moved badly with the site
Part of a post-rebrand fall is often not real. New templates ship without the tag, conversion triggers still name the old thank-you address, redirects strip the click identifier that ties a conversion to an ad, or a new platform installs a second pixel. The measurement change log owns this cause: a change recorded with its date, system and expected effect is what lets a reader separate a measurement break from a real loss.
Fix: check the tag on every new template, test each conversion end to end, and confirm that click identifiers survive every redirect pattern. The Google Ads website migrations guide covers final URLs, conversion triggers, click identifiers and feeds, and the Meta Ads website move tutorial covers the dataset, events, URL rules and the domain. Record the broken window as a change log entry, and restate or footnote any comparison that crosses it.
Verify: conversions in analytics and the ad platforms track the job book or order system again.
Prevent: add tracking checks to the launch plan for any site or domain change, with a named person who tests real conversions on launch day.
Listings that still show the old name or a mix
Maps, directories, review sites and trade listings were built up over years. After a rename some show the old name, some the new, some an old phone number, and a customer who spots the mismatch starts to doubt the business is the one they meant. For the citations and NAP guide, a new name is the most difficult change a listing record can go through, since old and new circulate side by side for a time.
Fix: correct the master record of name, address and phone (NAPA business's name, address and phone number as they appear across the web.) before anything else, then the business profile, then the site and its structured data, and only then the aggregators and directories, most important first. Where a field reverts after correction, the guide to business profile details that change on their own explains how to find the stale source and correct it before the profile.
Verify: a search for the old name, the old phone number and the old address in quotes returns only listings that redirect or explain the change.
Prevent: keep a listings inventory with the login and owner for each, change the profile name only when the signs and the real-world name change, and re-audit for stragglers after each change.
A sender name subscribers do not recognise
Email tests recognition most bluntly: a message from an unfamiliar sender is ignored, deleted or reported as unwanted. The diagnosis of a falling open rate lists a changed sender name among its causes and warns that opens alone are an unreliable signal, so read clicks and replies as well.
Fix: show both names for a period, with the new name and a "formerly" line or the old name in the sender field or first line, and send a short message explaining the change. If the sending domain also changed, it begins without a reputation of its own, and the deliverability guide explains setting up its authentication and building sending volume in stages.
Verify: clicks and replies per send, read by mailbox provider, return towards their level before the change.
Prevent: change one element of the sender identity at a time, record each change with its date, and plan a transition period for the sender name in any future rebrand.
Familiar cues dropped overnight
Customers know a business by more than its name: a colour, a shape, a van livery, a phrase or a style of photograph. Replace them all at once and every returning customer and referral starts again. The refresh or rebrand guide owns this cause and argues for keeping the cues buyers already recognise, and the distinctive brand assets framework scores a cue on how widely buyers link it to the business and how few link it to anyone else.
Fix: list the cues that changed, identify those that were both well known and unique to the business, and restore or bridge them on the surfaces customers meet first: the website header, the vans or signs, email templates and social profile images.
Verify: returning customer enquiries and referrals recover, and branded search and any recognition questions you ask customers move in the right direction. Branded search is only a stand-in for recognition, and the awareness and lift guide says when a survey is needed instead.
Prevent: decide in the design brief which cues stay, and treat dropping a famous cue as a cost to be justified rather than a design detail.
Prevention: both names measured, a freeze around launch and a clean-up pass
Most of the causes above are rollout tasks left unfinished, so the best prevention is to plan the rename as a migration from the start. The rebrand rollout tutorial linked above sets out the full sequence; this routine covers the habits that keep a fall from going unnoticed or unexplained.
Record a baseline for both names before launch. Note old-name searches, enquiries and sales by source, email engagement by provider and calls from listings, each from its own system, with the year-earlier figures beside them. A BaselineAn estimate of what a metric would have done without a given change, campaign or promotion, against which the effect is measured. taken in advance turns a feeling that things are quieter into a dated gap that a cause can be matched to.
Freeze other changes around launch. A rename that lands with new prices, a new web platform and a new agency leaves no way to tell which change cost the enquiries. Hold other structural changes for a period either side of launch, and log any exception with its date and expected effect.
Measure both names every month. Put old-name and new-name searches side by side with the old-name campaign's clicks. If the old name lingers, keep catching it; if the new name never climbs, look at recognition and awareness rather than the channels.
Run a clean-up pass after launch, and again later. Search for the former name, domain, phone number and logo file. Re-check listings, partner and supplier pages, review sites, templates and automated messages such as quotes, confirmations and invoices. Close every open row of the launch inventory, and bring the master record up to date so whoever handles the next change inherits a full list.
Write the fall and its causes into the report. Show enquiries and sales against the year-earlier period, with a note per cause found, its fix and whether it is verified. That note stops a later reader blaming the name for a gap the rollout caused.
Where people know the new name but still do not buy, see the diagnosis of brand awareness that does not turn into sales, and the marketing strategy troubleshooting hub routes other symptoms.
A staircase maker finds where its enquiries went after a rename (illustrative)
Tazmorin Staircases becomes Yskaborn
Tazmorin Staircases, an invented joinery firm making bespoke staircases, renamed itself Yskaborn (also invented) and moved to a new domain in the same week. Over the next 8 weeks the job book recorded 41 enquiries, against 74 in the same 8 weeks a year earlier, aligned by weekday. The rebuilt change log showed the analytics tag had been missing from the new contact page for the first 14 days, so the analytics figure of 19 enquiries understated the job book's 41; that part of the gap was measurement, and the comparison was restated from the job book alone.
Three real causes remained. A search for the old name showed a trade directory listing and a rival's ad above any page of the firm's. A block of 60 gallery pages, which had brought about a third of organic enquiries, redirected to the new homepage. And 12 directory listings still carried the old name and an old phone number. The firm mapped each gallery page to its new equivalent, ran an old-name search campaign at £120 a month to a page headed with both names, and corrected the listings at their source record first. By the end of the quarter the job book recorded 71 enquiries in 8 weeks against 74 in the same weeks a year earlier, close to the year-earlier level.
Common mistakes
- Blaming the name first. Judging the new name before checking the unfinished rollout tasks that can explain the fall.
- Trusting the analytics drop. Reading the fall from tracking that moved with the site instead of from the job book or order system.
- Comparing with the month before. Setting the post-launch weeks against the disrupted pre-launch weeks rather than the same weeks a year earlier.
- Redirecting everything to the homepage. Throwing away the rankings and links each old page had earned.
- Abandoning the old name. Leaving its searches to a directory or a rival from launch day.
- Changing every cue at once. Replacing name, colours, logo and sender on the same day, so returning customers recognise nothing.
