Webflow Website Audit Checklist: 20 Checks Before You Publish

Webflow gives you the markup. That is the whole appeal, and the whole problem. Nothing forces you to fill in alt text, bind a meta description, or size an image before you hit Publish, and a Collection template that is missing one binding publishes every item in that Collection with the same gap at the same moment. A Webflow site can look finished and still ship with fifty pages that share one title tag.

This is a practical Webflow website audit checklist you can run on a live, published site. It is organised into four areas with 20 concrete checks, the free tool to run each one, and the exact Designer panel or Site settings screen where the fix lives. Work through it top to bottom, or jump to the section you are worried about. For the platform overview first, see the free Webflow website audit page, and for the generic, platform-agnostic version, see the website audit checklist.

What should a Webflow website audit cover?

Four things, in order of how badly they go wrong. First, the per-page and per-template fields that Webflow leaves empty: titles, descriptions, Open Graph, alt text, headings. Second, the indexing layer: which copy of the site Google can see, what robots.txt says, where the canonicals point, and whether old URLs still resolve. Third, speed, which on Webflow is mostly images and interactions. Fourth, trust: the headers, certificates, and email records that sit outside the Designer. The table below maps the 20 checks to those four areas.

Area	Checks	Where the fixes live
Pages and CMS templates	1 to 6	Page settings, Collection page settings, the image element's Settings panel
Indexing and technical health	7 to 13	Site settings under SEO and Publishing
Speed	14 to 17	Assets panel, the image element's Load setting, Advanced publishing options
Trust and accessibility	18 to 20	Advanced publishing options, your DNS provider

Pages and CMS templates (checks 1 to 6)

Static pages and Collection templates fail differently. A static page fails one page at a time. A Collection template fails once and publishes the failure to every item.

1. A unique SEO title on every static page and Collection template. Static pages take their title in Page settings under SEO settings. A Collection template takes a pattern: open the template's settings from the Pages panel, click Add field in the SEO settings section, and bind the title to the item's Name or a dedicated SEO title field. Leave the pattern blank, or bind it to a field that repeats, and every item in the Collection publishes with the same title. Keep titles roughly 30 to 60 characters (the checker flags anything outside 20 to 70) and test one static page and one Collection item with the title tag checker.
2. A written meta description, bound on templates. Webflow does not invent a description for you, so a blank field is a blank tag. Set it per static page in Page settings, and on a Collection template bind it to a summary or excerpt field the same way as the title. Aim for roughly 120 to 160 characters (flagged outside 100 to 180) and verify with the meta description checker.
3. Exactly one real H1 per page. In Webflow a heading is whatever tag you set on the Heading element, and it is easy to style a paragraph to look like a title without ever making it an H1, or to leave a hero heading at H1 and then drop a second H1 into a section further down. Run the H1 checker on the homepage, one static page, and one Collection item, because each template can be broken on its own.
4. Alt text bound on CMS images. A static image takes its alt text in the Settings panel of the selected image element. A CMS image publishes with no alt text at all until you bind it: add a plain text field to the Collection for the description, then in the image element's settings choose that field as the alt text source. Multi-image fields take alt text per image from the ellipsis menu on each image, and images inside a Rich text field carry whatever alt text was set in that field. One unbound binding produces dozens of flagged images, which is why the alt text checker is worth running on a Collection item first. The bulk alt text audit guide covers doing the whole site at once.
5. Open Graph fields set per page and bound per template. A page with no Open Graph tags unfurls as a bare link. Static pages take Open Graph title, description, and image in Page settings. On a Collection template, pick an Image field from the Open Graph image dropdown in the template's settings and bind the title and description to fields; note that Webflow requires every Open Graph image in a Collection to share the same dimensions, and that a Collection with no Image field cannot set one at all. Confirm a Collection item unfurls with its own image, not the site default, using the Open Graph checker.
6. Structured data on the templates that earn rich results. Webflow adds no JSON-LD on its own. You can add it in Page settings in the Schema markup field, either by hand or generated by Webflow AI, and on a Collection template the generated block pulls in the item's dynamic fields, so one template covers every item. It needs a paid Site plan, and Reference, Multi-reference, and Multi-image fields cannot be used in it. Alternatively, paste a script block into the page's custom head code or a Code Embed element. Check one blog post or product template with the structured data checker.

Indexing and technical health (checks 7 to 13)

Webflow's defaults here are safe rather than complete. It generates a sitemap and forces HTTPS, but robots.txt, canonicals, and redirects are empty until you set them, and the staging subdomain is live from day one.

7. The webflow.io staging copy is not indexed. Every Webflow site publishes to a yoursite.webflow.io subdomain as well as your custom domain, and that copy is a full duplicate of the site. Turn on Disable Webflow subdomain indexing under Site settings > SEO (it needs a paid Site plan), which affects only the webflow.io copy, not your custom domain. This is the single most common way a Webflow site ends up competing with itself.
8. A global canonical tag pointing at the right domain. Set Global canonical tag URL under Site settings > SEO to your site's base URL. Include the protocol, match your default domain exactly (with www if that is the default), and leave off the trailing slash, or every canonical on the site gets a double slash. Any static page can override the global tag in its own Page settings. If another tool such as Tag Manager already injects a canonical, do not also set one here, because two canonicals on a page can cancel each other out. Read the tag on a page reached from a paginated Collection list, which Webflow serves at a URL ending in _page=2, and confirm it points at the base page. The canonical tags guide explains what to do when it does not.
9. robots.txt says what you mean. Webflow builds robots.txt from the rules you type under Site settings > SEO > Indexing, and adds the sitemap line for you. The Traffic control toggles in the same section write rules for whole categories of bots at once, which is convenient and blunt: if you want to allow the AI search agents while blocking the training crawlers, write the user-agent lines by hand rather than flipping a category. Check the live file with the robots.txt checker and confirm nothing is disallowing a folder you rely on. The AI crawler access guide lists which agents matter for AI answers.
10. The sitemap is auto-generated and lists what it should. Under Site settings > SEO, keep Auto-generate sitemap on so the file rebuilds on every publish. Pages you exclude with the page-level indexing toggle in Page settings drop out of the sitemap and gain a noindex tag at the same time, so use that toggle for thank-you and utility pages rather than the older site-search exclusion, which does not remove a page from search engines. Paginated Collection URLs are never included. Open /sitemap.xml on the live domain and confirm your Collection templates are there, then submit it in Search Console. The robots.txt and sitemap guide covers what a healthy pair looks like.
11. No broken links after a slug change or a deleted item. Renaming a page slug, deleting a Collection item, or retiring a static page leaves dead links in navigation, footers, and Rich text fields, and Webflow does not rewrite those for you. Scan several pages at once with the 404 checker. The 404 errors tutorial covers which ones actually matter.
12. Every old URL redirects once, to the right place. Redirects live under Site settings > Publishing > 301 redirects, and Webflow offers to create one automatically when you change a slug in Page settings, via the Permanently redirect the old URL to this new one checkbox. Two things catch people out: redirects only go live on a full-site publish, never a single-page publish, and Webflow evaluates them in the order they were added, so an old catch-all rule can swallow a newer specific one. Sites that have moved platforms or changed slugs more than once build chains. Collapse each to a single hop with the redirect chain checker.
13. Custom code is present where you expect it and absent where you do not. Site-wide head and footer code lives under Site settings > Custom code, per-page code in Page settings, and both need a paid Site plan; the limit is 50,000 characters per field. Audit it the way you would a plugin list: a tracking script from a retired vendor, a duplicate analytics tag, or a canonical injected by a tool you no longer use all sit here. Custom code is also where a schema block (check 6) or a manually written canonical (check 8) would be, so check it before assuming a page has neither.

Speed (checks 14 to 17)

Webflow sites are usually slow for two reasons: images uploaded at full size and rendered without variants, and interactions that move content after it paints. Both are fixable in the Designer.

14. Core Web Vitals in the green on a Collection page. LCP under 2.5 seconds, CLS under 0.1, INP under 200 milliseconds. Measure a Collection item and a static page with a hero, not just the homepage, because the templates carry the heaviest sections. Run the Core Web Vitals checker on each. The Core Web Vitals guide explains what each metric measures.
15. Images are compressed and served in modern formats. Webflow generates responsive variants for inline JPG, PNG, and WebP images automatically, but not for background images and not for images placed through a Rich text field, so a full-width hero set as a section background is served at upload size on every screen. Convert to AVIF or WebP with the image conversion tool in the Assets panel, or run Compress assets across an entire Collection from the Collections panel. The conversion is lossy and replaces the original, so download originals first. Check with the image optimisation checker.
16. Above-the-fold images load eagerly, the rest lazily. New images in Webflow default to lazy loading, which is right for everything below the fold and wrong for the hero, where a lazy image delays the largest paint. Select the hero image and set Load to Eager in its settings; leave everything else on Lazy. This only applies to inline images, so a background-image hero gets neither setting.
17. Interactions do not shift the layout, and the site is minified. An interaction that animates an element from zero height, or a slider that resizes as it loads, moves everything below it after the first paint and shows up as CLS. Reserve the space with explicit sizes and animate opacity or transforms instead of dimensions. The CLS guide walks through the pattern. Then open Site settings > Publishing > Advanced publishing options and turn on minify for HTML, CSS, and JS, plus per-page CSS if the site has grown a large style sheet.

Trust and accessibility (checks 18 to 20)

The last group sits partly outside Webflow, which is why it gets missed.

18. HTTPS is enforced and the certificate is valid. Webflow provisions the certificate and serves hosted sites over HTTPS by default, and it now sends an HSTS header on all non-Enterprise sites. What still goes wrong is a domain moved without re-pointing DNS, or a www and root pair where only one is the default and the other never redirects. Check with the HTTPS checker and the SSL certificate checker.
19. Security headers, and an honest note about what you cannot set. Webflow hosting does not let you add custom response headers unless you are on an Enterprise plan, so a Content Security Policy or X-Content-Type-Options header is out of reach for most sites. What you can do is turn on Use secure frame headers in Advanced publishing options to prevent clickjacking. Run the security headers checker so you know exactly which headers are missing, then treat the rest as a known platform limit rather than a to-do.
20. Email authentication for your sending domain. Webflow does not host your email, so SPF and DMARC live entirely at your DNS provider, and a marketing site often shares its domain with the company's mailboxes. Without those records, form notifications and outreach land in spam and the domain looks spoofable. Check with the SPF checker and the DMARC checker.

Which checks matter most?

Twenty checks is a lot, so if you are triaging, work in this order. First, anything that decides which copy of the site Google ranks: the indexed webflow.io subdomain (7), a wrong or missing global canonical (8), and a robots.txt rule blocking a folder you need (9). If any of those is wrong, nothing else on the list matters until it is fixed.

Next, the failures that hit a whole Collection at once: template titles and descriptions (1 and 2), alt text bindings (4), and Open Graph bindings (5). These are the highest-return fixes on almost every Webflow site, because binding one field repairs every item.

Then speed: an eager hero (16), converted images (15), and a Collection page that passes Core Web Vitals (14). Everything else, schema, redirect chains, custom code hygiene, and email records, is worth doing but rarely an emergency.

Common Webflow-specific gotchas

A few problems show up on Webflow far more than on other platforms:

• One template, every item. A Collection template with an unbound field does not fail on one page. It fails on all of them, at the moment you publish. Audit one item from every Collection, not just the blog.
• The staging copy is a full duplicate. The webflow.io subdomain is live and crawlable by default. The setting that stops it being indexed is off until you turn it on, and it needs a paid Site plan.
• Background images skip the optimisation pipeline. Responsive variants and lazy loading both apply only to inline image elements. A hero set as a section background gets the original file, at the original size, on every device.
• Redirects wait for a full publish. A slug change with the redirect checkbox ticked looks done in the Designer, but the redirect does not exist on the live site until the next full-site publish.
• Headings are whatever tag you chose. Webflow will happily publish a page whose visual title is a styled paragraph. The H1 checker sees the tag, not the font size.
• Custom code needs a plan. Schema, a manual canonical, and any third-party script all require a paid Site plan to publish, which trips up sites still on the free Starter tier.

Knowing these patterns means you can check for them deliberately rather than being surprised by them after rankings slip.

How do you run a Webflow audit in one pass?

Working through 20 checks by hand across every static page and Collection template is thorough but slow. To cover all of them at once, run a full free Webflow website audit: it crawls your published site with no embed or custom code, follows internal links into your Collection templates, runs all 40 checks across SEO, technical health, performance, and AI visibility, ranks the issues by estimated revenue impact, and writes the AI fix for your highest-impact issue, naming the exact Designer setting, Collection binding, or Site settings screen to change. The free tier scans all 40 checks in full detail with one AI fix; Pro adds an AI-written fix for every issue and a client-ready PDF report.

The advantage of an automated Webflow platform audit is not just speed, it is that it reads the published site rather than the Designer. A binding that looks set in the panel but publishes empty, a canonical overridden by custom code, or a hero that renders as a background image all show up in the crawl and nowhere else. If you would rather run individual checks as you go, the free targeted tools cover the big ones one at a time: the alt text checker, the Open Graph checker, and the 404 checker all run in seconds with no signup.

Make it a habit

The most important thing about a Webflow website audit is that you run it more than once. Every template edit, Collection import, slug change, or domain move can introduce a regression, and on Webflow a regression in a template is a regression on every page built from it. Re-running the checklist after each publish that touches a template, and monthly otherwise, is what keeps one unbound field from quietly becoming fifty untitled pages. Bookmark this page, or set up a recurring audit so the checklist runs itself.