Webflow website redesign: how to migrate without losing your SEO
A Webflow website redesign depends less on the tool than on the scope, the content to carry over and the way you migrate without breaking what already works. A brochure site of a few pages can stay a small job. Add a blog, several languages or a CMS migration and it becomes a much bigger one.
- Three things move the quote before the page count: the templates to redesign, the volume of content to carry over, and whether a CMS cutover is involved.
- A partial redesign still makes sense as long as the site structure holds. You rebuild everything when the templates and the design system have drifted apart.
- The SEO risk sits in the cutover: a redirect plan prepared before go-live, then indexing QA URL by URL.
- On the fifteen-page Webflow sites we have delivered, classes named to a convention save around 2 to 3 days of rework at the end of production.
- A marketing team that runs its landing pages and campaign variations in a well-modelled CMS publishes without waiting in the dev team's ticket queue.
Which project to buy, and what we check before rebuilding the site
Before comparing quotes, you need to know what you are buying. The setup that holds up best is the one that stacks the fewest changes at once.
Six scenarios, and what drives the bill up
- Webflow landing page redesign: number of sections, campaign variants, content to write. For an acquisition page, little content, a short journey.
- Webflow brochure site redesign: number of templates, content carried over, forms to rewire. For a 5 to 10 page site to bring up to date.
- SaaS or startup site redesign with a blog or CMS: CMS modelling, editorial templates, volume of articles to carry over. For templates that need structuring and content that lives over time.
- Webflow e-commerce site redesign: catalogue size, product variants, checkout to rebuild. For a catalogue, product pages and buying journeys.
- Redesign with CMS migration: redirect plan, content mapping, indexing QA. When the site moves to a new editorial foundation.
- Redesign with multiple languages or localisation: number of languages, proofreading per version, localised URLs to manage. When the site has to ship in several languages.
Stack the fewest changes at once
A brochure site with no migration stays more predictable than a multilingual SaaS with a CMS, and a partial redesign keeps its value if the editorial foundation still holds. If you are starting from a WordPress site, a migration to Webflow sets the constraints early.
What we audit before rebuilding the site
Before any mock-up, we list what stays, what goes and what has to move. Pages to keep, content to merge, conversion tracking, forms, technical dependencies and SEO structure are the working base, especially if the site starts from an existing CMS. It is the same inventory as a Webflow SEO engagement, this time run before production rather than after. A redesign with migration adds the mapping of old URLs, the redirect plan and the indexing QA to the quote, and that is where preparation saves you from surprises later.
SEO checklist before a migration to Webflow
This list runs in order. The first four points happen before any mock-up, the next four before the cutover, the last two after.
- Export every indexable URL of the existing site, backed by the sitemap and a crawl.
- Attach traffic, rankings, backlinks and conversions to each URL.
- Decide page by page: keep, merge or remove, with the reason written down.
- Map each old URL to its new one, including merges and removals.
- Write the 301 redirects and have them reviewed before go-live, not after.
- Check canonical tags, robots.txt, the sitemap and metadata on staging.
- Crawl staging in full and fix the errors before opening to the public.
- Freeze content changes during the cutover window.
- Recrawl immediately after go-live: 404s, redirect chains, loops.
- Track indexing and queries in Search Console over the following weeks, and fix as you go.
Publish without depending on development, and keep classes clean
Webflow gives marketing teams editorial autonomy, which matters when they publish often, and it is one of the reasons companies call a Webflow agency rather than a traditional integrator. On Stockly, the CEO was able to edit and publish the content himself after delivery, without coming back to the studio. That way of working suits brochure sites and marketing pages that change often.
- Name classes according to a convention decided at the start.
- Reuse the same components when the same need comes up again.
- Limit template variants.
- Check the rework before final delivery.
- Let the CMS live at marketing's pace: a well-modelled CMS serves event pages, campaign variations and landing page creation without going back through production. A marketing team that runs this content gains several days per cycle, because it is not waiting in the dev team's ticket queue.
- UX and conversion: on a redesign, the journey comes before the visuals. On Acadomia, the work covered the design and experience of the enrolment site. That kind of project starts with the information hierarchy, the friction points and the quality of the forms, which is conversion optimisation work. On The Luxurist, we also handled the Webflow site with its CMS and the product pages, where the editorial structure counted as much as the styling.
Redesigns from branding to CMS
We have run redesigns where the stakes ranged from branding to CMS, with very different constraints from one project to the next. Here are a few we have delivered, from a brochure site built on a reworked template to projects with a regulator, WooCommerce or imposed components.
Stockly
Acadomia
Dulcolax, Sanofi group
The redesign method, from framing to go-live
Four phases, in this order. Framing sets the trade-offs, architecture rebuilds from what still earns its place, production goes template by template, and the cutover is prepared before go-live.
Set the objectives and the initial trade-offs
Framing sets the measurable objectives, the content to carry over and the sign-offs at each milestone. Without those trade-offs up front, the project grows with every round of design feedback, content adjustment and last-minute request. On a project like <a href="/en/work/stockly">Stockly</a>, this kind of framing kept the budget on the product rather than on the number of pages.
Deliverable: measurable objectives, list of content to carry over, sign-off milestones.
Rebuild the site structure, the templates and the design system
Rebuild the <a href="/en/blog/arborescence-site-web">site structure</a> from the pages that still earn their place. Define the recurring templates before the detailed mock-ups. Name classes with a stable convention. Build the reusable components in the design system, the core of the <a href="/en/webdesign-agency">web design</a> work on this kind of project.
Deliverable: target site structure, list of templates, class convention, design system components.
Build the site in Webflow without losing the content
The build goes template by template, carrying over the approved content and checking page states. This is the part that calls for a <a href="/developpeur-webflow">Webflow developer</a>, because a badly structured template costs you on every page that uses it. Naming classes to a convention cuts the rework at the end of production. The aim is a delivery that holds without heavy rework after go-live.
Deliverable: integrated templates, content carried over, page states checked.
Handle the sign-offs, the 301s and the cutover
The last stretch runs through sign-offs, 301 redirects, indexing QA and go-live. QA checks that the old URLs point to the right pages and that useful content stays findable. The <a href="https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes" target="_blank" rel="noopener">Google Search Central documentation on site moves with URL changes</a> sets out the expected order: map, redirect, then monitor indexing. On a CMS cutover, this is where a large part of the SEO risk plays out.
Deliverable: 301 redirect plan reviewed, indexing QA, go-live.
Partial, full, migration: what settles it
A partial redesign is enough when the site structure holds, the useful content is already there and the site can be brought up to date without a heavy migration. A full redesign becomes the better option if the templates, the design system and the content logic are too fragmented. When the source CMS stands in the way, the migration matters as much as the new site itself.
The right level of redesign
- Partial redesign: the site structure holds, only the design has aged, the useful content is already there
- Full redesign: the UX and the architecture need rethinking, the templates and the design system are too fragmented
- Migration: the CMS blocks changes, and the site moves to a new editorial foundation
- In every case, pages that already carry traffic call for an SEO audit first
When it is not a Webflow redesign you should be pricing
- If the need goes beyond what a visual CMS can carry, what you should be pricing is a custom-built site, not a redesign
- Two columns of the grid ticked at the same time are not a contradiction: they are the signal to split the project into two phases rather than handle everything at once
- After the cutover, any usability problems that remain are a job for a UI and UX design engagement in its own right, not for a second pass at the redesign
After go-live, we check indexing, the 301s, the forms, 404 errors, internal linking and GA4 tracking. If the site comes from another CMS, the migration aims to limit the loss of organic visibility, and to measure that loss rather than promise there will be none. Post-delivery follow-up is there to fix what breaks along the way, then to stabilise the site.
Partial, full or migration: the decision grid
This grid reads line by line: as soon as a situation applies to you, it pushes the project towards the matching column.
| Your situation | Partial redesign | Full redesign | Migration |
|---|---|---|---|
| The site structure is still relevant | Suitable | Rarely necessary | Not applicable |
| Only the design has aged | Suitable | More than needed | Not applicable |
| The UX and the architecture need rethinking | Insufficient | Suitable | To assess |
| The CMS blocks changes | Insufficient | To assess | Suitable |
| Many pages already carry traffic | Caution | Caution | SEO audit required first |
| URLs will change on a large scale | Redirect plan | Redirect plan | Redirect plan and QA |
Two columns ticked at the same time are not a contradiction: they are the signal to split the project into two phases rather than handle everything at once.
What drives the bill up by type of redesign
The budget varies mostly with the page count, whether there is a blog or a CMS, migration and multiple languages. The ranges by project type are in our article on the price of a Webflow website. On Stockly, a professional Webflow template under $150 served as the base, given a full art-direction pass, and the site shipped for under €10,000: tight framing changes the cost line. At the other end, the studio's engagements run from €10,000 to over €500,000 depending on scope, with three billing models: fixed price, specific quote or retainer. The item-by-item breakdown is in our article on the price of a website.
| Type of redesign | What drives the bill up | Why |
|---|---|---|
| Webflow landing page | Number of sections, level of content, marketing variants | Each variant adds a design pass and a review |
| Webflow brochure site | Page count and quality of the content carried over | Unsorted content costs you in back-and-forth before the build |
| SaaS or startup site with a blog or CMS | Editorial templates, blog, recurring components | The CMS has to be modelled before it is filled |
| Webflow e-commerce site | Catalogue, product pages and buying journey | Product variants and order states multiply the screens |
| CMS migration | Redirects, content carried over, indexing QA | QA is done URL by URL and cannot be fully automated |
| Multiple languages or localisation | Languages delivered and per-version checks | Each language adds a full proofread and a set of URLs to check |
A quote that does not explain the "why" column sells an amount, not a scope.
Partial redesign, full redesign or migration?
Three questions to place the project. The answer depends on what still holds in your site, not on the urge to redo everything.
When the templates, the design system and the content logic are too fragmented, rebuilding everything costs less than patching it up.
The project starts with the inventory: pages to keep, content to merge, forms, conversion tracking. The CMS is modelled before it is filled, classes are named to a convention, and the redirect plan is ready before go-live.
Testimonials
The migration went through without losing traffic. Redirects, metadata, everything was checked before go-live. No surprises.
The Webflow design system they delivered let us produce campaign pages at scale. We now turn out in two days what used to take us two weeks.
We were looking for someone who understood Webflow and SEO at the same time. The CMS templates were restructured for search, and the marketing team can finally publish without breaking the tags.
What we hear before a redesign
"We are redoing everything, we might as well start from scratch"
A partial redesign still makes sense as long as the site structure holds. You rebuild everything when the templates and the design system have drifted apart, not because the site is old. If two columns of the grid are ticked at the same time, we split the work into two phases rather than handle everything at once.
"The price depends on the number of pages"
Three things move the quote well before the headline page count: the templates to redesign, the volume of content to carry over, and whether a CMS cutover is involved. Unsorted content costs you in back-and-forth before the build.
"We will deal with the redirects after go-live"
The SEO risk sits in the cutover. The 301 redirect plan is written and reviewed before go-live, not after, and indexing QA is done URL by URL. A well-run migration aims to limit the loss of rankings, not to promise there will be none.
"What we are buying is a go-live"
On delivery, the client team should walk away with a system, documentation and access: the design system in Webflow, the CMS collections modelled, the redirect plan applied, full access in the client's name and a written handover. A quote that says nothing about these deliverables sells a go-live, not a redesign you keep control of.
Frequently asked questions
About the author
Related pages
To go further, here are the most useful pages depending on your project.
Talk about your redesign
A short call is enough to place the project between partial, full and migration, and to list what has to be audited before any mock-up.