Pre-Launch Checklist for Webflow: What Mazette.co Always Verifies

Why a pre-launch checklist is never a waste of time

Pushing a site to production without checking it first is a bit like signing a contract without reading it. It usually works out. Until the day it doesn't.

At Mazette.co, we never publish a site just "because the design's been approved." We publish once a precise list of technical, SEO, and editorial points has been ticked off. This rigor isn't paranoia: it's what prevents 404s discovered three weeks after launch, contact forms that silently fail, or worse, a site that's invisible on Google because indexing was accidentally blocked.

In 2026, with generative engines now firmly embedded in search habits, going live isn't just about "does it work" anymore. It's also about "can an AI actually read, parse, and cite this content." This article gathers our complete checklist, the one we literally follow on every single delivery.

The technical checks you can't skip

Does the site actually work across every browser and device?

Yes, but only if you've tested it. Chrome, Safari, Firefox, Edge, and mobile above all: a flawless render on your designer's screen guarantees nothing on an entry-level iPhone or an Android tablet.

• Test the site on at least 3 desktop browsers and 2 mobile browsers
• Check intermediate breakpoints (tablet portrait/landscape), not just desktop and mobile
• Verify keyboard and touch interactions, not just mouse behavior
• Review animations on a slow connection: a janky transition makes the whole site feel cheap

Are all links and forms actually working?

A broken link happens to everyone. A broken link that goes undetected before launch has no excuse.

• Crawl the entire site with Screaming Frog SEO Spider to catch 404s, redirect loops, and broken links
• Test every form end-to-end, including actual email delivery (not just the on-screen confirmation message)
• Check third-party integrations: CRM, newsletter, chat, payment
• Confirm external links open in a new tab when appropriate

Is performance where it needs to be?

A slow site loses visitors before they've even seen it. Google's Core Web Vitals remain a ranking factor, and users are getting less patient by the day.

• Check image weight and format (WebP or AVIF rather than heavy JPEGs)
• Verify lazy loading is active on below-the-fold images
• Trim non-essential third-party scripts that drag down load time
• Test PageSpeed scores on both mobile AND desktop, not just one

To go further on this specific topic, our article on animations and their impact on perceived performance explains how to balance visual smoothness with fast loading times.

Technical SEO: the part you can't easily fix after the fact

Is the site actually ready to be indexed?

This is THE critical checkpoint. A staging site protected from indexing that keeps that block live in production becomes an invisible site on Google, sometimes for weeks before anyone notices.

• Confirm the "Enable indexing" setting is switched on in Webflow (Site Settings > SEO)
• Check the robots.txt file: no leftover "Disallow" rule from the testing phase
• Generate and submit the sitemap.xml in Google Search Console
• Make sure no noindex tag is lingering on pages that need to be visible

Are the metadata optimized page by page?

A generic title ("Home | My Site") or one duplicated across several pages is a missed opportunity every time. Every page should clearly tell both humans and search engines what it's about.

• Confirm every page has a unique title tag, under 60 characters, with the primary keyword
• Check meta descriptions: unique, compelling, under 155-160 characters
• Run the SEO title generator on your most strategic pages if you're still unsure
• Check the Hn hierarchy: a single H1 per page, with a logical structure underneath

Is structured data in place?

In 2026, structured schemas aren't just for Google's rich snippets anymore. They've become the main gateway for generative AI to understand and correctly cite your content.

• Confirm the Organization schema is present on the homepage
• Add an Article or BlogPosting schema to blog content
• Validate all your schemas with Schema Validator before publishing
• Run the Detailed SEO Extension page by page for a quick one-click audit

Our dedicated article on SEO best practices on Webflow covers each of these technical points in more depth.

AEO: preparing the site for generative AI answers

Can ChatGPT, Perplexity, and AI Overviews actually read your content?

The answer comes down to one simple question: if an AI had to summarize your page in three sentences, would it have enough clear material to do so? Confusing text, no heading structure, no direct answer at the top of a section, and these tools simply skip right past it.

• Make sure each section opens with a clear answer before going into detail
• Check that H2/H3 headings frame specific questions or topics, not vague wordplay
• Make sure factual information (pricing, timelines, contact details) is written as real text, never locked inside an image only

Have you connected your AI analytics tools?

There's no way to know if your site is being cited by generative AI without the right tracking tools in place. It's a project of its own, but it starts at launch: the sooner tracking is set up, the sooner you'll have usable data.

We cover this in detail in our article on Webflow Analytics opening up to Claude and Gemini, a shift that genuinely changes how you measure AI visibility in 2026.

Content, translation, and editorial consistency

Has the content been proofread by someone other than its author?

Writing fatigue makes you miss the most obvious mistakes. A second, fresh pair of eyes always catches them.

• Full spelling and grammar proofread, page by page
• Check tone consistency across the entire site
• Review legal notices, terms of sale, and privacy policy
• Confirm CTAs are consistent with where the link actually leads

If the site is multilingual, is the translation complete and clean?

A multilingual site with untranslated chunks left over is the most visible sign of a rushed launch. It's spotted immediately, and it undermines credibility for everything else.

• Check each language with Weglot page by page, including navigation and footer elements
• Confirm translated URLs are clean and consistent with local SEO
• Check hreflang tags to avoid any conflict between language versions

The final checklist, right before you hit "Publish"

What should you check in the very last few minutes?

These are the details that are easy to forget, precisely because they come right at the end of the project.

• The favicon and Open Graph images are properly set up for social sharing
• The domain name and DNS are correctly pointed
• The SSL certificate is active (that little padlock in the address bar)
• 301 redirects are in place if the site is replacing an older version
• Analytics tools (Google Analytics, ad pixels) are installed and tested
• A backup of the Webflow project is made before any final changes

Why handing this step to an agency changes everything

This checklist adds up to dozens of checkpoints. Each one, taken on its own, seems simple. Put together, they demand a methodical rigor that many in-house teams simply don't have the time, or the habit, to apply with the same thoroughness on every single project.

That's exactly what Mazette.co brings to the table: a method tested across dozens of launches, where every validation step is documented and systematic. Our Webflow expertise and our SEO expertise come together precisely at this pivotal moment in the project, the one where a single overlooked detail can cost weeks of lost visibility.

Getting ready for launch and want a second pair of eyes before you publish? Let's talk, this is exactly the kind of moment we love, when everything needs to be perfectly locked in.