
.webp)
%201.png)
%201.png)
.webp)
Most redesign projects are sold on how the new site looks. The ones that fail are almost never ugly. They are invisible.
Six weeks after launch, organic traffic is down 40%, the pages that used to convert are gone, and nobody can say exactly which decision caused it. The design was approved by everyone. The problem was never the design.
Here is what we run before touching a single page.
Every page that had a ranking and no longer resolves is a ranking you gave back. This is the most common cause and the easiest to prevent.
Someone decides the old service page was too long and trims it to a paragraph. That page was long because it answered eleven questions people were actually searching. Now it answers one.
The new navigation is cleaner, which usually means shallower. Pages that used to receive links from six places now receive none, and search engines read that as a demotion.
Titles and descriptions that took years to tune are replaced by whatever the new template auto-fills.
Notice that three of the four are content and structure decisions, not code. That is why a redesign run purely as a design project loses traffic even when the build is flawless.
Before any wireframe, pull every URL with impressions in the last twelve months from Search Console. Not the last month. Twelve, so seasonal pages show up.
For each URL, record impressions, clicks, average position, and the queries it ranks for. Then sort by impressions and draw a line. Everything above the line is an asset you are contractually obligated to protect. Everything below is a candidate for consolidation or deletion.
Most sites are surprised by this list. It usually contains at least three pages nobody on the marketing team thinks about, and it almost never matches the sitemap the agency was handed.
A redesign is the only cheap moment to remove pages. Thin pages, duplicate service pages in two languages, template detail pages nobody meant to publish, old campaign landers.
Deleting them is good. Deleting them silently is not. Every removed URL needs a 301 to the closest surviving equivalent, or a deliberate 410 if there is genuinely nothing equivalent and you want it out of the index.
The failure mode here is redirecting everything to the homepage. Search engines treat a mass redirect to the root as a soft 404 and the equity evaporates. Redirect to the closest match or do not redirect at all.
Write the map as a two-column sheet: old URL, new URL. Fill it while the new information architecture is being decided, because that is when the answers are cheap to change.
Two details that catch people in Webflow specifically:
If you change a collection slug, every item URL under it changes. One slug edit can move 200 URLs.
A hand-written link with a typo will get crawled and indexed as its own URL, and you will find it in Search Console months later wondering where it came from. Use dynamic links inside Collection Lists so the CMS builds the path for you.
Export current titles and descriptions. Treat them as copy that already passed a test, because it did: it earned the impressions you are trying to keep.
Improve them where the data says to, which usually means where impressions are high and click-through is near zero. Do not rewrite the ones that are working just because the new brand voice is different.
Rankings move for two to four weeks after a structural change. Judging a redesign in week one tells you nothing except whether the site is up.
What to watch, in order: coverage errors in Search Console, then impressions by page against your pre-launch baseline, then position for your top twenty queries. If impressions on a protected page drop more than 20% and stay there past week three, something in the map is wrong and it is still fixable.
If nobody on the project owns the redirect map, the redesign will lose traffic. Not might. The map is the difference between a redesign and a restart, and it costs a day.
We rebuild sites in Webflow without giving back the rankings the old one earned. If you are planning a redesign and want the migration handled as carefully as the design, see how we approach it or look at what we have shipped.
.webp)
Stop letting technical debt limit your revenue. Get a 30-minute strategic diagnostic of your digital infrastructure. No fluff, just strategy.

%201.png)

.webp)
%201.png)


%201.png)


%201.png)
