Most of the sites we take over are not badly designed. They are badly structured, which is why nobody can change them without filing a ticket. The rebuild is mostly a structure exercise.
Start with the content model
Before any design, identify the pages that repeat: services, locations, team, case studies, posts. Each one becomes a CMS Collection with typed fields, plus reference or multi-reference fields where they relate to each other. A case study references the service it belongs to. A team member references an office. Each Collection gets a single Collection page template.
Get this right and the tenth service page is a form entry. Get it wrong and somebody is hand-building pages again within six months.
Check the site plan before designing around any of this. Collection and item counts are capped per plan, and Basic has no CMS at all, so what the site is currently paying for decides what the content model can be.
Then the style system
Classes get defined once and reused rather than styled per element. Repeating interface gets built as components, so changing the card or the CTA block changes it everywhere instead of in twenty places. This is the part that determines whether the site still looks like itself after a year of other people editing it.
Migration is mostly redirects
Moving the content is usually scripted or exported straight into the CMS. The part that damages search is the URL map. Every old URL needs either the same path or a 301 to its closest equivalent, set up under Site settings > Publishing > 301 redirects before launch, with no chains. Skipping this is the most common reason traffic falls after a redesign.
One constraint to plan around: Webflow writes every redirect rule into the site's manifest, and treats roughly a thousand rules as the practical maximum. A 1:1 map off a large old site can exceed that, so pattern-based wildcard rules usually have to do the bulk of the work and the hand-written ones get reserved for pages that earned links.
A few things have to be carried across by hand, because nothing moves them for you: title tags and meta descriptions, canonical rules, the sitemap submission in Search Console, and any structured data. Schema goes in as custom code rather than through a plugin, either in page-level head code or as an embed in the body, and on Collection templates it can bind to CMS field values so it generates per item.
What the setup looks like afterwards
Hosting, SSL and the CDN come with the site plan.
The legacy Editor was retired in August 2026. Editing now runs through Workspace roles: Marketer for building pages from existing components and templates, Content editor for text, images and CMS records, Reviewer for comments only. Somebody in marketing can work on content without being able to restructure the page underneath it.
The thing to check early is seat count, not seat cost. Client seats come included with the Workspace plan, a limited number per site, and additional ones cannot currently be bought. So the question to answer before launch is how many people actually need to edit, because that number is capped.
Where it is the wrong tool
A large ecommerce catalog. Anything needing real server-side logic. A product application with accounts and state. Webflow can sit in front of those, but it should not be the whole stack, and we will say so rather than take the build.
If you want someone to look at yours
We design and build on Webflow, and we take over sites that were built once and then left alone. Book a call and we will look at what you have.
Marketing that gets a reaction.