Webflow SEO Audit Checklist 2026: 14 Checks for Webflow Sites

Webflow sites start from a better place than most. Hosting is fast, the HTML is clean, and the SEO settings are in one panel. That is why Webflow SEO problems are rarely technical disasters. They are small settings and empty CMS fields, repeated across every page a template generates.

This Webflow SEO audit checklist covers 14 checks specific to how Webflow builds and publishes sites. For checks that apply to every platform, use the main SEO audit checklist alongside it.

Why Webflow sites need a platform-specific audit

Three Webflow features cause most of its SEO issues.

The staging subdomain. Every Webflow project has a yoursite.webflow.io address. If it is crawlable, Google can find two copies of every page, and occasionally indexes the staging copy instead of the live one.

CMS templates. One Collection template generates every blog post, case study or product page. If the template binds the SEO title to a field that is sometimes empty, or uses the same meta description for every item, the problem is multiplied by the number of items.

Interactions. Webflow's animation system often sets elements to opacity: 0 and fades them in. If the main heading or hero image starts hidden, Largest Contentful Paint waits for the animation, and some crawlers see a page with invisible content.

How to audit a Webflow site in 6 steps

1. Open Site settings > SEO and confirm Staging indexing is off in the Indexing section, the global canonical URL is set, and the sitemap is enabled.
2. Search Google for site:yoursite.webflow.io to see whether staging pages are already indexed.
3. For each Collection template, open one item and check the bound SEO title, meta description, Open Graph image and the H1 field.
4. Crawl the live site and filter for URLs with _page= parameters from paginated collection lists.
5. Run PageSpeed Insights on the homepage and one CMS item, and note whether LCP is delayed by interactions.
6. List every image without alt text in the Assets panel and on CMS image fields.

The 14-point Webflow SEO audit checklist

1. Staging indexing off. In Site settings > SEO > Indexing, set Staging indexing to Off so search engines don't index the webflow.io subdomain, then republish.
2. Global canonical URL set to your live domain (for example https://www.example.com), so every page outputs a canonical to the custom domain.
3. One preferred host. Choose www or non-www as the default domain in Publishing settings; the other should redirect.
4. Auto-generated sitemap enabled and listed in robots.txt, or a custom sitemap kept up to date if you turned auto-generation off.
5. robots.txt reviewed. Webflow lets you edit it in SEO settings; make sure it does not disallow folders you want indexed, and decide which AI crawlers to allow.
6. Static page SEO settings complete: each page has its own title and meta description in Page settings, not the default page name.
7. Collection template SEO fields bound to fields that are always filled. Use a dedicated "SEO title" field with a fallback, rather than binding to a long post title.
8. One H1 per page. Webflow doesn't add an H1 for you, so pages built from sections can end up with none or several. Check the Navigator.
9. Collection list pagination handled. Paginated lists create URLs like ?3f5a2c_page=2. Keep them crawlable so older items are reachable, and make sure each item is also linked from somewhere stable.
10. Image alt text set in the Assets panel, and alt fields bound on CMS images. Decorative images should have empty alt text.
11. Interactions don't hide the hero. Avoid fading in the H1 or LCP image on page load; animate secondary elements instead.
12. 301 redirects added in Publishing settings for every renamed slug or deleted page.
13. Utility pages excluded: the site search results page and password pages should not be indexed.
14. Localization configured if you use Webflow Localization: each locale has its own URL and translated SEO fields, and hreflang appears in the source.

The webflow.io subdomain in detail

The staging subdomain is Webflow's most common SEO trap because it is invisible in day-to-day work. Designers publish to it constantly; nobody looks at it in search results.

Here is how to check and fix it properly:

• Check: search site:yoursite.webflow.io. Any results mean Google has indexed staging pages.
• Fix: set Staging indexing to Off in Site settings > SEO > Indexing and republish to both the staging and live domains, so the subdomain stops being indexed.
• Clean up: if staging pages are already indexed, the global canonical setting helps Google consolidate signals onto the live URLs. For stubborn cases, the Removals tool in Search Console (on a property verified for the subdomain) hides them temporarily while Google catches up.
• Prevent: add the check to your launch checklist for every new Webflow project, because the setting is per site.

The same logic applies to any staging environment: Vercel preview URLs, Netlify branch deploys and WordPress staging copies. If a copy of the site is public, it needs a block.

How Webflow compares with other platforms on SEO setup

The comparison explains why the checklists differ. On WordPress the risk is conflicting plugins; see the WordPress SEO audit checklist. On Shopify it is duplicate product URLs; see the Shopify SEO audit checklist. On Webflow it is templates and staging.

CMS template checks that save hours

Because one template drives many pages, a template-level audit is the highest-leverage hour you can spend on a Webflow site. For each Collection template:

• Title formula. Bind the SEO title to a field such as "SEO Title", and add a fallback in your content process so it is never empty. Keep the keyword near the start and the total under about 60 characters.
• Meta description. Bind to a summary field written per item. A shared description across 80 blog posts is a duplicate-content signal and a wasted snippet.
• H1. Bind the H1 to the item name, and check that no other element on the template is also an H1.
• Open Graph image. Bind to the main image field so shared links show the right picture.
• Rich text fields. Editors sometimes use Heading 1 inside rich text, creating a second H1; restrict it in your editorial guidance.
• Schema. Add JSON-LD in the template's custom code using field values (for example Article with headline and dateModified).

Run the checks on one item, fix the template, publish, and audit one more item to confirm.

Tools for a Webflow SEO audit

Webflow's SEO settings and the Audit panel in the Designer catch missing alt text and some structural issues. Search Console shows index status for the live domain; verify the domain property so all hosts are covered. PageSpeed Insights shows whether interactions delay LCP.

Seotific audits the published page from the outside, the way search engines see it, so it catches what the Designer can't: the canonical actually served, duplicate titles across Collection items, an H1 hidden by an interaction, and content missing from the raw HTML. A site crawl finds every _page= URL and every CMS item missing a description. The technical SEO audit checklist has the crawl-level checks that apply on Webflow too.

Frequently asked questions