Website launch checklist
Webflow launch checklist for agencies
A Webflow site is built on its webflow.io staging subdomain and goes live when it is published to the client's custom domain. Before handoff, check the Site settings that decide which domain search engines see, where form notifications go and what visitors meet on the live site. Use the full website launch checklist for everything that is not specific to Webflow.
Last reviewed
← Full website launch checklist
Domains and search visibility
The webflow.io subdomain is kept out of search
Manual
Go to Site settings > SEO > Indexing section, set Staging indexing to off, then save and publish the site. It needs a Site plan or paid Workspace.
Why it matters: Webflow then publishes a robots.txt only on the subdomain that tells search engines to ignore it.
The client's domain is the default domain
Manual
In Site settings > Publishing > Production, click Make default next to the client's domain, then publish the site to it.
Why it matters: Traffic from the other connected domains redirects to the default, which Webflow says helps avoid SEO penalties due to duplicate content.
The global canonical URL matches the default domain
Manual
In Site settings > SEO > Global canonical tag URL, enter the base URL with https://, with www if the default domain uses it and without a trailing slash. Save and publish.
Why it matters: Webflow combines this URL with each page's slug to fill every page's canonical tag.
Source: Webflow Help Center: Set canonical tags to improve SEO
robots.txt rules allow the live site
Manual
In Site settings > SEO > Indexing, read the robots.txt rules and remove any rule written to block crawlers during the build. Save and publish.
Why it matters: “User-agent: *” with “Disallow: /” blocks all bots from the entire site.
Key pages have Sitemap indexing on
Manual
On each key page, open Page settings > SEO settings and check that Sitemap indexing is on. For CMS items, check the toggle in Item details.
Why it matters: Turning it off adds a noindex robots meta tag to the page and removes the page from the sitemap.
Redirects
Old URLs have 301 redirects
Manual
In Site settings > Publishing > 301 redirects, enter each Old path and its Redirect to path, click Add redirect path, publish, and open each old URL to test it.
Why it matters: Without a redirect, anyone who visits an old URL from search results, a bookmark or printed material lands on a 404 page.
Source: Webflow Help Center: How do I set up redirects in Webflow?
Forms
Form notifications go to the client
Manual
Select each form, open the Settings panel and, under Send to, click Email Notifications. Replace the recipients with the client's addresses and click Apply.
Why it matters: By default, Webflow sends form notifications to the email address associated with the account, which may be the account that built the site.
A test submission arrives
Manual
Submit each form on the published site and check that the entry appears in Site settings > Forms. If a form uses a custom form action, confirm where that service delivers it.
Why it matters: With a custom form action, submissions are not sent to Webflow, and Webflow sends no notification emails for them.
Source: Webflow Help Center: Why am I not receiving form notification emails?
Before handoff
The site password is off
Manual
In Site settings > General tab > Website password, toggle Password protection off and publish. Set pages and folders that should be open to Public under Access control > Restrict access.
Why it matters: A site-wide password is required on all of the site's domains while it is on.
Source: Webflow Help Center: Password protect your site or web pages
The “Made in Webflow” badge is agreed
Manual
In Site settings > General tab > Webflow branding, set Display “Made in Webflow” badge as agreed with the client, then save and publish.
Why it matters: While the setting is on, the badge appears on both the staging subdomain and the custom domain. Hiding it needs a paid site plan or a Growth, Agency or Enterprise Workspace.
Favicon and webclip are uploaded
Manual
In Site settings > General > Icons, click Upload icon, upload one square image, select the icons to update, click Apply and publish.
Why it matters: Browsers show the favicon in tabs and bookmarks, and the webclip appears when the site is saved to a phone's home screen.
What a Launch Ready scan covers on Webflow
A Launch Ready scan reads the published pages of a Webflow site with the same rules as any other site (see How we scan). A Launch Ready scan does not log in to the Webflow admin and does not read platform settings. So every item above is Manual. Where a setting leaves a result on the published pages, the scan sees the result, not the setting:
- A page with Sitemap indexing turned off carries a noindex robots meta tag, and the scan reports it. See A noindex tag left on.
- On a project set to Production, a robots.txt on the scanned domain that disallows the whole site for all crawlers is reported. See robots.txt still blocking the site.
- A form whose action points at localhost is reported, and on a project set to Production, so is one that points at a webflow.io address or another staging-style host. See A form still posting to staging.
- On a project set to Production, links and canonical tags that point at the site's webflow.io subdomain are reported when the subdomain carries the site's name or a staging word. See Staging and localhost links left in.
- On paid plans, when the crawled pages show a Webflow site, an advisory check that does not change the score flags a production scan of a webflow.io address, and links or canonical tags on the custom domain that point at any webflow.io address, unless a general check already reports the same link or canonical tag.
- The Staging indexing setting changes robots.txt on the webflow.io subdomain only, which a scan of the live domain does not read.
- The scan does not check the favicon or the “Made in Webflow” badge.
Everything else
The items above cover Webflow settings only. For everything else, use the free 72-item website launch checklist.
Related launch mistakes
Check your next client site before handoff
Add the staging or live URL, read the fix list, and send the client a report when it is ready.