Technical SEO for Webflow: pre-launch checklist

We start at the smallest level: the single page. Each indexable page needs a unique title, meta description, a single H1, coherent canonical, ordered headings, useful image alt text and sensible internal links.

Where it is configured: static page titles and descriptions live in Page Settings; for CMS pages, compose them automatically from collection fields so every new item is born with correct metadata. The classic mistake we find: a CMS template serving the same title to a hundred pages.

A typical Webflow trap: H1s inside components. If the hero is a reused component, it is easy to end up with identical H1s on different pages, or two H1s on one page. Check page by page, not by sample.

And legal or utility pages? They can stay noindex — but then they must not appear in the sitemap.

Now one level up: the site as a whole. Robots.txt, XML sitemap, redirects, canonical domain, HTTPS and www/non-www variants must tell the same structure. In Webflow: the sitemap lives in the SEO settings, the Global Canonical Tag URL points to the production domain, 301 redirects live in the publishing settings.

One check that alone prevents real damage: make sure “Disable Webflow subdomain indexing” is on, so the .webflow.io version does not compete with the real domain. And at go-live, remove the indexing blocks used during development — the second most common mistake we see.

Bilingual site? Hreflang and canonical relationships must be reciprocal: each version points to the other, each canonicalises to itself. Errors here rarely block Google, but they create entirely avoidable ambiguity.

Third level: what the site weighs and what it declares. Oversized images, unnecessary scripts and unstable layout hurt experience and crawl quality. In Webflow: native responsive images, modern formats, lazy loading (but disable it above the fold) and a critical review of third-party scripts — that is where Core Web Vitals get lost, not in Webflow's own output.

The efficient way to check: run PageSpeed Insights on the template pages only — home, service, article. Fixing the template fixes every page derived from it.

On structured data, one rule: Organization, Service, BreadcrumbList, FAQPage or BlogPosting are used when they represent visible content, never to declare what the page does not show. In Webflow they are added as template embeds, composed from CMS fields; after launch, Search Console flags markup errors.

And here we are at launch day — the one we started from. In order: redirects loaded and tested (coming from another site? the migration checklist covers that part), canonical domain and HTTPS live, sitemap submitted to Search Console, robots.txt correct, no leftover noindex on important pages.

Then the best-spent hour of the project: the verification crawl on the production domain, confirming status codes, canonicals, unique titles and no redirect chains. One hour of checks worth weeks of rankings.

The two weeks after: monitor 404s and coverage in Search Console, confirm the main pages are indexed and historical queries respond again. Technical SEO does not end at launch — it ends when the data confirms everything responds as designed. Then, yes: the new site gets celebrated.