The Ultimate Guide to Website Redesign with Webflow

How to redesign a website with Webflow

Run the redesign in three phases. Spend the 60 days before launch on a URL inventory, a ranking baseline, a conversion baseline, an integration map, a content audit and a validated 301 redirect map. Spend the launch window on staging QA, DNS cutover, redirect activation, sitemap resubmission and first-hour verification. Spend the 30 days after on crawl health, ranking comparison, conversion delta and integration checks.

Skip any of the three and you find out what broke in the wrong order, usually from a panicked revenue lead at 11pm.

The risk is the handoff, not the platform

A redesign that moves platforms is like transferring a patient between hospitals. The old hospital works. The new one works. The risk sits in the ride and the handoff at the receiving door. Most agencies sell you the destination. The discipline that decides the outcome is in the transfer - the redirects, the data parity, the moment the old system shuts down and the new one comes up.

Get the transfer right and the platform is nearly a footnote. Get it wrong and the best CMS available will not save your rankings.

When a redesign is actually worth doing

Redesign when the site is costing you something you can name. Three signals are worth acting on.

• Campaigns wait on a dev queue. If a landing page takes six weeks and a test gets blocked by a CMS limitation, the cost is not design taste. It is go-to-market speed.
• The site fails on mobile. Analysis of HTTP Archive Web Almanac data from July 2025 found only 48% of mobile websites pass all Core Web Vitals. Google and SOASTA research from 2017 found mobile bounce probability rises 123% as load time goes from 1 to 10 seconds.
• Small speed gains move the funnel. Google and Deloitte, in Milliseconds Make Millions (2020), found a 0.1-second mobile speed gain brought 21.6% more users to the form submission step.

If none of those apply, you may need a content refresh and a performance pass rather than a rebuild. Price that work first, before you budget for a new site.

The 60 days before launch

The work that decides whether a redesign goes smoothly happens before anyone touches the new platform.

Inventory every URL Google has indexed

Not just the sitemap. Pull the Pages report from Search Console, the top pages report from your rank tool, and a fresh crawl. De-duplicate, then tag each URL with current traffic, current rank for its primary keyword, backlink count and a target URL on the new site. That list becomes your redirect map.

Pages with no traffic and no links can be merged or dropped. Everything else needs a direct, intentional destination. A sitewide fallback to the homepage is the most common first-migration mistake.

Lock a ranking baseline

Capture daily rank snapshots for your top 100 organic keywords starting 30 days before launch. Without the baseline you cannot tell whether a post-launch move is redesign damage or ordinary volatility.

Document conversion rates path by path

Record current conversion rates for every key path - form submissions, demo requests, downloads, trial sign-ups - at the page level. A half-point drop on a high-traffic page is real revenue, and you need to be able to see it.

Map every integration

List every third-party tool talking to the current site. Marketing automation forms, scheduling embeds, chat widgets, tag containers, de-anonymization tools, video hosts, custom webhooks. Each needs a tested integration on the new site before launch. Miss one and leads route silently to nowhere on day one.

Audit the content while you have the chance

Decide before launch what carries over, what gets rewritten, what gets cut and what gets archived with a 410 instead of a 301. Cutting thin pages is part of the redesign, not a separate project.

Build and validate the 301 map

Source URL, destination URL, notes. Then check that every destination actually exists on the new site. The most common launch-day failure is redirecting traffic to a 404. Validating the map before cutover prevents weeks of lost rankings. Platform-specific steps are in our WordPress to Webflow migration guide.

The launch window

Launch day is a sequence, not a moment. The shorter you make it, the less risk you carry.

1. Final staging QA. Walk every page. Submit every form with a real address. Confirm every integration fires. Fix on staging, never on production.
2. DNS cutover. Schedule it for low-traffic hours and drop your DNS TTL to five minutes a full 24 hours ahead, so propagation does not drag and your team can tell which site a visitor is hitting.
3. Redirect activation. Push the whole 301 map at cutover, not piecemeal afterwards. Then spot-check 20 redirects across the map with a status checker.
4. Sitemap resubmission. New sitemap into Search Console within an hour. Remove the old one pointing at legacy URLs.
5. First-hour verification. Homepage loads. Top five traffic pages load with correct redirects. Forms submit and reach the CRM. Analytics fires. No server errors. A teammate on a different network confirms what you are seeing. The first hour catches most launch-day issues if someone is looking.

The 30 days after launch

This is when a redesign proves itself or unravels. Watch four things.

• Crawl health. Check the Search Console Pages report daily for the first 14 days. Spikes in "not found" or redirect errors are missed rows in your map. Fix them within 24 hours.
• Ranking comparison. Expect a short dip in the first week or two, then recovery. A key term still down past day 21 usually means a redirect chain, a canonical mismatch or content that did not carry over.
• Conversion delta. Compare week over week against your baseline. A temporary dip is normal while users adjust. A persistent, large drop is usually a form integration failing quietly or a call to action that moved below the fold.
• Integration health. Every Monday for four weeks, test your top three integrations end to end. The ones that break silently are the ones that cost pipeline.

Keep your on-page work consistent through all of this using our Webflow SEO guide.

What changes for the marketing team after launch

The point of moving to Webflow is not a nicer homepage. It is who can ship.

We migrated M13 off Contentful - 438 pages in 21 days. Their marketing now moves 10x faster, and work that took three weeks takes 24 hours or less. We moved Bigeye off Contentful and Gatsby in under 30 days and saved them thousands of dollars in development costs. We rebuilt Uniqode, a site with 200,000+ monthly visitors, moving over 74 pages and 400 blog articles. For ColorStack, the redesign delivered a 300% increase in conversions, and those conversions were online summit sign-ups.

Across client work, Ammo's own results are a 30% decrease in bounce rates and a 10x increase in time to market, with 200+ B2B high-growth clients shipped. Our web design and development service is where that work sits.

What a Webflow redesign costs

Published Ammo pricing, which is subject to change:

• Landing pages start around $10K.
• Full builds run $70K-150K+.
• Growth Support, for companies under 100 employees, starts at $4,800 / quarter on a fixed scope with a 90-day usage window.
• Growth Partner, for companies with 100+ employees, starts at $5,200 / month.
• Growth Partner+, for enterprise scale, starts at $15,000 / month.

Plans are month to month, and new client onboarding is limited to 8 per month across all plans.

Set that against the cost of standing still. In the Forrester TEI study commissioned by Webflow, the composite organization modeled 332% ROI over three years, $2.12M net present value and payback in under six months. Those are Forrester's modeled figures for a composite organization, not a prediction of your result. Our audit model risk-adjusts benefits down 15% and caps modeled ROI at 332% for that reason. For a framework you can run yourself, see how to determine ROI with a website.

How to choose a redesign partner

Judge agencies on the transfer, not the renders.

• Ask for a migration they shipped with numbers. Page counts, timelines, what happened to rankings in the 30 days after. Portfolio screenshots do not tell you whether the redirects held.
• Ask who owns the 301 map. If the answer is vague, you will own it.
• Ask what they cut. A partner who ports every page unchanged is doing a port, not a redesign.
• Ask what happens after launch. Monitoring, fixes and who answers at 11pm on cutover night.
• Watch the small signals. Reply speed, a tidy proposal and a clean scope document predict how launch week will feel.

The one thing most teams skip

Most agencies treat a redesign as a port - same content, new platform. The redesign is the rare moment when you can fix what has been wrong for years.

In the M13, Bigeye and Uniqode projects, the pattern was the same. We ran an aggressive content audit inside the migration window. We cut thin pages, consolidated duplicates and rewrote the weak ones rather than rebuilding what was there. Leaner, stronger content sets recover faster, because there is less low-value material competing for crawl attention.

Want the numbers for your own site before you commit to anything? Run the free GTM audit and see what your current platform is costing you.

Frequently asked questions

How long does a Webflow redesign take

It depends on page count and integration complexity. For reference, M13 moved 438 pages in 21 days and Bigeye moved a complex data platform site in under 30 days. Plan 60 days of audit work before the build window regardless of size.

Will we lose our search rankings

Rankings usually dip for the first 7 to 14 days and then recover, provided every indexed URL has a direct 301 to a live destination. Persistent losses past day 21 almost always trace to a redirect chain, a canonical mismatch or content that did not carry over.

Should we keep our existing URL structure

Keep it wherever it is sensible. Changing URLs means every backlink and bookmark depends on your redirect map being complete. When you do change them, document each change and validate that the destination exists before cutover.

How much does a website redesign cost

Ammo's published pricing puts landing pages at around $10K and full builds at $70K-150K+, with retainers from $4,800 / quarter for teams under 100 employees. Pricing is subject to change. The more useful comparison is the cost of doing nothing for another year.

What happens to our forms and other integrations

Every integration gets mapped before the build and tested on staging before cutover, then re-tested weekly for the first month. Integrations that fail quietly are the single most expensive post-launch problem, because leads disappear without an error.

Can our marketing team edit the site without developers

Yes, that is the main reason teams move. After their migration, M13's marketing moves 10x faster, with work that took three weeks shipping in 24 hours or less.

Is a redesign the right move if our site is only a few years old

Not always. If the site is fast, converts well and your team can ship pages without a dev queue, a content refresh and a performance pass cost far less. Redesign when you can name the thing the current site is costing you.