301 redirect

last updated

May 15, 2026

category

reading time

2 min

Table of contents

    Definition

    A 301 redirect is a permanent instruction that tells search engines and browsers a page has moved and passes its SEO authority to the new URL.

    What is a 301 redirect and when should you use it?

    A 301 redirect is a permanent instruction that tells search engines and browsers: "This page has moved. Update your records and go here instead." It passes the majority of a page's SEO authority (its "link equity") to the new URL.In a Webflow migration, 301 redirects are how you prevent traffic loss when URLs change.

    If your old site had /services/web-design and your new Webflow site uses /what-we-do/design, every search engine and external link pointing to the old URL needs a 301 redirect to the new one. Missing redirects mean Google treats the new pages as brand new - with no history, no authority, and no rankings. Traffic drops follow.

    Webflow has a built-in redirect manager in the project settings. For large sites, redirects are typically managed as a CSV import. Either way, the redirect map needs to be complete and tested before launch.

    Go deeper: How to migrate to Webflow without losing SEO?

    Frequently Asked Questions

    How long does it take Google to process redirects after a migration?

    Most redirects are processed within a few weeks of launch, but full recrawling of a large site can take 4-8 weeks. During this period you may see ranking fluctuations that normalise once Google has fully processed the new structure. Submitting an updated sitemap in Google Search Console immediately after launch speeds this up and gives you cleaner data in the coverage reports.

    What's the difference between a 301 and a 302 redirect?

    A 301 is permanent: it tells Google to update its index and transfer link authority to the new URL. A 302 is temporary: it routes traffic elsewhere but tells Google to keep the original URL in its index. In a migration, you almost always want 301s. Using 302s by mistake prevents SEO authority from transferring and can cause old URLs to remain indexed alongside the new ones.

    How do we handle 301 redirects during a Webflow migration?

    Build a redirect map before the migration starts - a spreadsheet with every old URL and its new destination. Once the Webflow site is built, upload the redirects via Webflow's redirect manager (Project Settings > SEO > Redirects). Test every redirect before launch using a tool like Screaming Frog or a redirect-checker extension. Pay particular attention to your highest-traffic and most-linked pages - those are the redirects where an error costs the most.

    Ready to improve your AI visibility?

    Get your visibility score and actionable reccomendations in minutes.