The short answer
A Webflow site is ready to launch when each check below has proof beside it, and no blocker is open. Proof means a result someone can look at: a crawl export, a form entry that arrived, or a Lighthouse run. "Looks fine to me" does not count.
Our website launch checklist is the full list for any platform, and it is worth copying. This chapter is the sign-off layer for a Webflow build: the table that ties the standards in this guide to a go or no-go decision. If the site replaces another one, the Site Move Playbook has the launch-day run sheet and the redirect work.
The sign-off table
Copy it into a shared sheet, and add a date and a link to the proof for each row.
| Area | Check | Proof | Owner | Severity |
|---|---|---|---|---|
| Brief | Scope is met: every agreed page exists | Page list compared with the sitemap | Project lead | Blocker |
| Brief | Forms send to the agreed places | A real entry from each form arrives, confirmed by a person | Project lead | Blocker |
| Build | Matches the design at each breakpoint | Side by side at desktop, tablet and phone sizes | Developer | Blocker on main pages |
| Classes | Chapter 2 review passes | Style list and Navigator read through | Second developer | Fix now if easy |
| Components | Long and missing content holds up | Test with awkward text, on a phone | Developer | Blocker on main pages |
| CMS | Templates work for every item type | Long, short and empty items checked | Developer | Blocker |
| CMS | Filters and load more work | Tested on the published site | Developer | Blocker if used |
| Motion | Hero visible right away | Slow network test, on a phone | Developer | Blocker |
| Motion | Reduced motion works | Device setting on, pages read through | Developer | Blocker |
| Speed | Core Web Vitals targets, and our Lighthouse target | Lighthouse on mobile per template | Developer | Fix or log |
| SEO | Unique titles and descriptions, one H1 | Crawl export | SEO owner | Blocker on main pages |
| SEO | Staging blocks are gone from live | Crawl for noindex, and read robots.txt | SEO owner | Blocker |
| SEO | Canonicals and sitemap agree | Crawl compared with the sitemap | SEO owner | Blocker |
| SEO | Schema is valid per template | Rich Results Test | SEO owner | Fix or log |
| Move | Every old URL has an answer | Whole old URL list tested | SEO owner | Blocker |
| Tracking | Events arrive after consent | Real-time or debug view | Project lead | Blocker if reported on |
| Access | Keyboard reaches every control | Tab through main pages | Developer | Fix or log |
| Access | Images have alt text, and text has contrast | Crawl export, and a contrast check | Developer | Fix or log |
| Content | No placeholder or test wording | Search of the built pages | Content owner | Blocker |
| Handover | Publish test passed | Editor publishes a real change | Project lead | Blocker |
Blocker, fix now, or log
Without a rule, the last week becomes a debate about every small thing. Agree this before the checks start.
| Severity | Means | Examples | What happens |
|---|---|---|---|
| Blocker | Loses leads, breaks main pages, hides the site, or tells a lie | A form that does not send. A noindex on live. Wrong prices. | No launch until it is fixed |
| Fix now | Visible, and quick to fix | A broken link. A cropped image. A class left with a default name. | Fix on the day it is found |
| Log | Real, small, and does not touch the main journey | A minor spacing issue on a rare screen width | Goes on a list, with an owner and a date |
Decision rule One person decides the severity when people disagree: the person named in the brief as signing off. Every logged item gets a date. A list with no dates is just a nicer way of forgetting.
Webflow traps to check by hand
These are the ones a general checklist tends to miss, because they come from how the tools work.
| Trap | Why it happens | Check |
|---|---|---|
| Attributes work only once published | Finsweet says they do not run in Design, Edit or Preview mode | Test every filter, search and load more on the published site |
| Interactions stop on loaded items | Items added by load more can miss interactions, according to Finsweet | Press load more, then hover and click the new items |
| Old cached items after API changes | Finsweet says loaded documents are cached until republish | Republish, or read the cache setting if your data comes in through the API |
| A global component edit reached too far | Unbound content changes everywhere | Read all pages that use a recently edited component |
| CMS template with thin data | The template looks good with the sample item | Open the emptiest item on the live template |
| Hidden elements still load | Something hidden on a breakpoint can still be in the page | Check what the phone downloads, not only what it shows |
| Staging settings carried over | Password or noindex settings stay on until someone changes them | Crawl the live domain, and check robots.txt on launch day |
| Custom code in the wrong scope | A script for one page is set site-wide | List each script, where it loads, and why |
Run it on the published site
Designer previews and the live site are not the same test. Run the final pass on a published staging address such as the webflow.io one, then again on the real domain, because forms, scripts and security rules can behave differently there.
- Publish to staging, with no cached session.
- Check the site on a real phone, on a mobile connection.
- Keep staging out of search results, and check the current docs for how to do this on your plan.
- Check
wwwand non-www, and that one sends cleanly to the other. - After launch, repeat the form, tracking and
noindexchecks on the real domain.
For search and answer engines, use our free tools for quick checks on key pages: the meta tags tool, the schema generator and the AEO score checker. For a deeper pass, see the Webflow SEO checklist, our schema guide and accessibility basics.
Two reviewers, for two kinds of blindness
The builder cannot see what they already know. Use a second pair of eyes, and split the job.
| Reviewer | Looks for | Works from |
|---|---|---|
| Second developer | Class names, components, code, breakpoints, speed | The Designer, a crawl and Lighthouse |
| Someone outside the build | Words, flow, wrong facts, buttons that surprise them | A phone, with no briefing |
Give the outside reviewer two tasks, such as "find what this costs" and "ask for a call". Watching someone try is more useful than a list of opinions. On smaller builds, one person can do both, as long as a little time has passed since building.
Sign off, and keep a record
Keep the record short. It answers the question "what did we check, and who said yes?" when something odd turns up in three months.
- The sign-off table, with dates and proof links.
- The list of logged items, with owners and dates.
- A dated export of titles, descriptions and URLs.
- The Lighthouse results by template, as a before picture for later.
- A note of which scripts run, where, and why.
- The name of the person who said go, and when.
Know how to restore an earlier version of the site before launch day. Check the current docs for how backups work on your plan, and make sure the person on call can do it.
The first days after launch
Launch day is the start of the watch. In the first week, send a real form again, read the Search Console reports as they fill in, look through the logged items, and ask your team to report anything odd. The Site Move Playbook has a full 30-day schedule if URLs changed.
If you would rather have someone else run this gate, it is part of how we handle Webflow development and Figma to Webflow projects. You can also see how the steps fit together on our process page.
Done when Every row has proof, no blocker is open, every logged item has a date, and one named person has said go.


