Webflow · WordPress to Webflow, rebuilds, domain cutover and 301 redirects
Moving a site to Webflow is never just a host move. Webflow has its own URL rules, its own CMS structure and its own way of handling canonicals and sitemaps, so URLs, templates and metadata all change at the same time.
That makes the URL map and the baseline crawl the two things that protect rankings. Map every old URL before you build, crawl the webflow.io build against the old site, and compare again after the domain switches.
Baseline crawl→Map URLs→Build and import→Crawl webflow.io→Switch domain→Crawl and compare
What can go wrong
The more the URL structure and templates change, the more the redirect map has to carry.
| Migration type | Risk level | What usually breaks |
|---|---|---|
| Webflow redesign, same site and URLs | Medium | New template drops SEO field bindings, headings change level, schema embeds removed |
| Webflow site restructured | Medium to high | Renamed collection URLs and page slugs without wildcard redirects |
| WordPress or another CMS to Webflow | High | Date and category URL patterns, tag and author archives, attachment pages and pagination all disappear, so every old pattern needs a rule |
| Platform move plus domain change | Highest | All of the above, plus cross-domain 301s and a Search Console change of address |
Old URL patterns Webflow does not reproduce
Nested foldersPaths like /services/seo/local/ on the old site, where Webflow CMS items sit one level under the collection URLFlattened URLs
Date and category paths/2024/05/post-name/ or /category/post-name/ permalinks from WordPressPattern redirects
Archives and attachmentsTag, author, date and media attachment pages with no Webflow equivalentRedirect or retire
Trailing slashes and parametersOld URLs ending in a slash or carrying ?page=2 style paginationTest every variant
Every old URL that earned links or traffic needs a planned destination. Webflow does not create redirects for URLs it never had.
Before migrating
- Crawl the old site and save the audit. This is the baseline: URL count, status codes, titles, meta descriptions, H1s, canonicals, word counts and schema per template.
- Build the old URL list. Combine the crawl, Search Console's top pages and backlink targets. Pages with no traffic and no links can be retired, but still deserve a redirect to the closest match.
- Design the Webflow URL structure first. Pick collection URLs before importing, because renaming them later moves every item.
- Write the redirect map. One row per old URL to its new Webflow URL. Turn repeated patterns into wildcard rules with capture groups, such as /blog/(.*) to /articles/%1, and test each rule against real old URLs.
- Import CMS content and check it. CSV imports generate slugs from names, so confirm slugs match the map. Carry over SEO titles and meta descriptions into dedicated fields, not just the body.
- Crawl the webflow.io build. Compare against the baseline for content parity: missing pages, dropped headings, shorter word counts, missing schema, empty SEO fields. Use redirect map validation to test the map before DNS changes.
- Lower DNS TTL a day or two before the cutover, so the switch to Webflow's hosting propagates faster.
After launch: what to check
Run these within the first hour after the custom domain points at Webflow, then crawl the full site and compare against the baseline in Audit Comparison.
| Check | Expected result |
|---|---|
| Old URL list | Every URL returns 200 (unchanged path) or a single 301 to its mapped page |
| Default domain | www or root chosen, the other returns a 301, HTTPS enforced |
| Canonical tags | Global canonical tag URL set, every page canonical on the production domain |
| yoursite.webflow.io | Indexing disabled, not competing with the new domain |
| robots.txt | Production rules, no leftover Disallow: / from the build phase |
| Indexable URL count | Close to the baseline, with every planned removal accounted for |
| Titles and descriptions | Match the baseline or planned values, no template defaults |
| Word count per template | No large drops on posts, services or case studies |
| Staging and old domain links | Zero links to the old host or webflow.io, via Custom Source Search |
| Tracking | GA4 and pixels fire once, via Tracking & Pixel Audit |
Downloadable checklistWebflow migration SEO checklist
0 of 20 done
How to identify the scope
Where the failures sit tells you what caused them.
Every URL fails the same wayDomain or site settingsWrong canonicals or noindex everywhere point to default domain, canonical or robots settings.
One URL pattern failsWildcard ruleAll old /2024/ or /category/ URLs 404: a pattern redirect is missing or wrong.
One collection failsTemplate or importPosts lost descriptions or headings: the template bindings or CSV fields are the cause.
Scattered URLs failMap gapsIndividual pages missing from the redirect map or imported with a different slug.
How to validate the fix
- Fix settings and redirect rules first, then publish to the custom domain.
- Recrawl the old URL list and confirm each returns a single 301 or a 200, with no chains through the old host.
- Recrawl the full site and compare against the pre-migration baseline.
- Target: every difference is one you planned in the URL map.
- Submit the new sitemap, use URL Inspection on your top pages, and file a change of address if the domain changed.
- Schedule weekly Scheduled SEO Audits for the first month and watch the Not found report in Search Console.
0Old URLs returning 404 without a planned reason
1Redirect hop from each old URL to its new page
4 weeksOf weekly audits and Search Console monitoring
Before and after example
Old WordPress site/2023/08/brand-audit/ → 200
/category/branding/ → 200
/tag/logo/ → 200
/category/branding/ → 200
/tag/logo/ → 200
→
Webflow launch/2023/08/brand-audit/ → 404
/blog/brand-audit → 200
/tag/logo/ → 404
/blog/brand-audit → 200
/tag/logo/ → 404
Fix: one wildcard 301 from the dated pattern to /blog/%1, category pages mapped to a Webflow category collection, and tag pages redirected to the closest category instead of the homepage.
Common mistakes
- Building the site first and mapping URLs afterwards. Collection URLs and slugs set during the build decide what the map has to do. Plan them together.
- Redirecting every old URL to the homepage. Google treats mass homepage redirects like 404s. Send each URL to its closest equivalent.
- Importing posts without their SEO titles and descriptions. The template falls back to the post name and a blank description on every item.
- Forgetting the webflow.io subdomain after launch. The build stays published there, so disable indexing before the custom domain goes live.
- Skipping trailing slash and parameter variants. Test old URLs exactly as they were linked, with and without the trailing slash.
- Dropping schema the old SEO plugin added. WordPress plugins often output Article, Breadcrumb and Organization schema. Rebuild it in Webflow custom code.
- Launching on a Friday and switching off the old host. Keep the old site available until DNS has fully moved and the redirect map is confirmed.
Related resources
Map first, then build
A Webflow migration is safe when every old URL has a destination and the crawl after launch matches the crawl before it, except for changes you planned. Save the baseline, design the URL structure with the map in hand, crawl the staging build, and compare again after the domain switches.