FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 6 of 6

Pre-launch checks

The last gate. A table of checks, each with its proof, owner and severity, plus the Webflow traps worth testing by hand and a clear rule for when a problem blocks launch.

7 min readUpdated 2026-11-07
All chaptersChapter 6 of 6
  1. 01Brief and Figma handover
  2. 02Client-First, classes and variables
  3. 03Components and CMS model
  4. 04Interactions that stay fast
  5. 05Editor handover
  6. 06Pre-launch checks

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.

AreaCheckProofOwnerSeverity
BriefScope is met: every agreed page existsPage list compared with the sitemapProject leadBlocker
BriefForms send to the agreed placesA real entry from each form arrives, confirmed by a personProject leadBlocker
BuildMatches the design at each breakpointSide by side at desktop, tablet and phone sizesDeveloperBlocker on main pages
ClassesChapter 2 review passesStyle list and Navigator read throughSecond developerFix now if easy
ComponentsLong and missing content holds upTest with awkward text, on a phoneDeveloperBlocker on main pages
CMSTemplates work for every item typeLong, short and empty items checkedDeveloperBlocker
CMSFilters and load more workTested on the published siteDeveloperBlocker if used
MotionHero visible right awaySlow network test, on a phoneDeveloperBlocker
MotionReduced motion worksDevice setting on, pages read throughDeveloperBlocker
SpeedCore Web Vitals targets, and our Lighthouse targetLighthouse on mobile per templateDeveloperFix or log
SEOUnique titles and descriptions, one H1Crawl exportSEO ownerBlocker on main pages
SEOStaging blocks are gone from liveCrawl for noindex, and read robots.txtSEO ownerBlocker
SEOCanonicals and sitemap agreeCrawl compared with the sitemapSEO ownerBlocker
SEOSchema is valid per templateRich Results TestSEO ownerFix or log
MoveEvery old URL has an answerWhole old URL list testedSEO ownerBlocker
TrackingEvents arrive after consentReal-time or debug viewProject leadBlocker if reported on
AccessKeyboard reaches every controlTab through main pagesDeveloperFix or log
AccessImages have alt text, and text has contrastCrawl export, and a contrast checkDeveloperFix or log
ContentNo placeholder or test wordingSearch of the built pagesContent ownerBlocker
HandoverPublish test passedEditor publishes a real changeProject leadBlocker

Blocker, fix now, or log

Without a rule, the last week becomes a debate about every small thing. Agree this before the checks start.

SeverityMeansExamplesWhat happens
BlockerLoses leads, breaks main pages, hides the site, or tells a lieA form that does not send. A noindex on live. Wrong prices.No launch until it is fixed
Fix nowVisible, and quick to fixA broken link. A cropped image. A class left with a default name.Fix on the day it is found
LogReal, small, and does not touch the main journeyA minor spacing issue on a rare screen widthGoes 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.

TrapWhy it happensCheck
Attributes work only once publishedFinsweet says they do not run in Design, Edit or Preview modeTest every filter, search and load more on the published site
Interactions stop on loaded itemsItems added by load more can miss interactions, according to FinsweetPress load more, then hover and click the new items
Old cached items after API changesFinsweet says loaded documents are cached until republishRepublish, or read the cache setting if your data comes in through the API
A global component edit reached too farUnbound content changes everywhereRead all pages that use a recently edited component
CMS template with thin dataThe template looks good with the sample itemOpen the emptiest item on the live template
Hidden elements still loadSomething hidden on a breakpoint can still be in the pageCheck what the phone downloads, not only what it shows
Staging settings carried overPassword or noindex settings stay on until someone changes themCrawl the live domain, and check robots.txt on launch day
Custom code in the wrong scopeA script for one page is set site-wideList 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 www and non-www, and that one sends cleanly to the other.
  • After launch, repeat the form, tracking and noindex checks 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.

ReviewerLooks forWorks from
Second developerClass names, components, code, breakpoints, speedThe Designer, a crawl and Lighthouse
Someone outside the buildWords, flow, wrong facts, buttons that surprise themA 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.

Takeaways

What to remember from chapter 6.

  • Each check needs proof someone can look at. "Looks fine" is not a result.
  • Agree blocker, fix now and log before the checks start, with one person who decides.
  • Test Attributes, load more and interactions on the published site.
  • Run the final pass on staging, then repeat key checks on the real domain.
  • Keep a dated record of what was checked and who said go.

Keep a copy

Take the whole guide
as a PDF.

It all stays free to read here. If you want a copy for your team, leave your email and the download link shows up right away.

Nothing gets emailed to you, the link appears on this page. We do not send marketing email unless you ask. Privacy policy

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.