Redirect & HTTP Status Checker for Webflow Designers

Why Webflow Designers need this

You rebuilt a client's old site in Webflow, pasted a few hundred 301 rows into Site settings, published, and the launch call ended with everyone happy. Then the first crawl report arrives: old product URLs land on the homepage, a few bounce through two redirects, and the webflow.io staging address is still answering as if it were a second copy of the site. Webflow does not tell you what a visitor or crawler actually experiences after publishing; the redirect table only shows what you typed. The Redirect & HTTP Status Checker fills that gap by requesting a URL and following every Location header, up to 10 hops, until something answers. For each hop you see the status code, whether it is permanent or temporary, and where it points, followed by the final URL and its final status. Run it on a handful of old URLs after each publish, and on the plain http:// and non-www versions of the domain. It reports what the server answers, not whether the destination is the page you meant, so keep the old sitemap or crawl export beside you and compare the Final URL by eye.

Webflow Designers specific guidance

Start with the old URLs, not the new ones

Open Site settings, then Publishing, then 301 redirects in Webflow and copy five old paths from the table: one blog post, one CMS collection item, one category or archive path, one deep service page, and the old homepage variant. Paste each into the checker as a full address such as https://www.oldclient.com/blog/seo-tips-2019, one per run, because the tool takes a single URL at a time. If you type a bare domain it is tested as http://, which also shows you the HTTP to HTTPS step. Ten minutes is enough for this pass. What it does not prove: a clean result for five URLs says nothing about the other 295 rows, and it does not read your redirect table, only what the live server returns after you publish.

Reading the summary and the chain checks

Look at the Final URL and its status first. Final status is 200 OK passes; a 404 or 410 means the rule points at a page that is gone or was mistyped, often because a CMS item slug changed after the rule was written. Then check the hop count: the Short redirect chain row warns at three or more hops, which tends to happen when an old rule points at a URL that is itself redirected. Final URL uses HTTPS should pass. Finally read the Redirect Path and confirm a permanent move shows 301 or 308 rather than 302 or 307. The result does not prove the destination is the right page: an old product URL that redirects to the homepage still ends in 200 OK.

What to fix first in Webflow

Fix the failures first: change the destination under Site settings, Publishing, 301 redirects, publish, and re-run the same URL, since nothing changes on the live site until you publish. Next collapse chains by pointing the first old path straight at the final page. After that, deal with the homepage dumps by mapping each old path to its closest equivalent. Leave the webflow.io address for last and treat it separately: the checker shows whether it answers or redirects, but it cannot tell you whether Google indexed it. Switch off subdomain indexing in the SEO tab of Site settings, and remember that robots.txt controls crawling, not removal of pages already indexed.

Example scenarios

Common mistakes

• Only testing the homepage. The homepage redirect is usually the one rule everyone gets right, while deep CMS items and archive paths are where the typos live. Sample at least one URL from every section of the old site.
• Trusting the redirect table without publishing. Rules saved in Site settings do not affect the live domain until the site is published. Run the checker after publishing, not after saving.
• Sending every old URL to the homepage. A bulk catch-all ends in a clean 200 OK, so the report looks healthy while visitors land on a page that has nothing to do with what they clicked. Map each path to its closest equivalent.
• Leaving temporary redirects from the old host. A rule at the previous host or a CDN may still answer 302 or 307 for a move that is permanent. Read the type label on each hop in the Redirect Path.
• Treating robots.txt as the fix for webflow.io. Blocking crawling does not remove staging pages that Google already knows about, and the checker does not read robots.txt. Disable subdomain indexing in Site settings and verify in Search Console.

Frequently asked questions

Is Webflow good for SEO when I migrate an old site with hundreds of URLs?

Webflow handles redirects well enough for most migrations, as long as you map them yourself. Rules live in Site settings, Publishing, 301 redirects, and they only take effect after you publish. Very large CMS sites with thousands of pages are harder, because you manage rules by hand and have limited access to underlying code. Sample old URLs from each section with the checker, confirm each ends in 200 OK within two hops, and keep a spreadsheet of old and new paths for the rest.

How do I disable webflow.io subdomain indexing and check it?

In Site settings, open the SEO tab, switch on the option that disables indexing of the webflow.io subdomain, then publish. The redirect checker cannot confirm indexing status or read robots.txt, so use it only to see how the staging address answers, for example whether it returns 200 or redirects to your custom domain. Blocking crawling is not the same as removing pages already in Google, so check Search Console separately for staging URLs that were already picked up.

Should a Webflow 301 redirect point to the homepage when a page is gone?

Only when the homepage really is the closest equivalent. Sending hundreds of unrelated old URLs to the homepage tends to look like a soft failure to search engines, even though the checker will show a 301 followed by 200 OK and call it healthy. Map each old path to the most relevant new page, and for content with no equivalent let it return a 404 or 410. The tool reports status codes, not relevance, so compare the Final URL with what you intended.

Why does my Webflow site redirect twice from http to www?

A typical chain is http://example.com going to https://example.com and then to https://www.example.com, ending in a 200. Usually these jumps come from HTTPS enforcement plus whichever domain you chose as the default. Run the plain http:// address in the checker and read the Redirect Path. Two hops is within the Short redirect chain check, while three or more triggers a warning. If you add an old 301 rule on top, point it straight at the final https address.

Does a 301 in Webflow replace the canonical tag or schema markup?

No. A redirect sends visitors and crawlers from an old address to a new one, while a canonical tag only suggests a preferred version of a page that still loads. Webflow also has no built-in schema feature, so JSON-LD is custom code you add yourself, and a redirect will not carry it over. After a migration, trace the old URL with the checker, then open the final page separately to confirm the canonical and structured data are present, since the checker reads neither.

Reference: The guide titled Webflow SEO: How to Fully Optimize Your Webflow Site explains that the default webflow.io staging domain can cause duplicate content if indexed, and that robots.txt controls crawling, not indexing.