Webflow SEO Checklist for 2026: Technical, On-Page and CMS Steps

Webflow gives you most of the SEO controls you need, but it does not set them up for you. A site can be beautifully designed and still miss titles, redirects, schema or a sensible CMS template. This Webflow SEO checklist is the order I use on client builds, from the technical base to the content.

I build Webflow sites every day, including the Northman law firm website and the Selhono interior design studio, so the steps below reflect how I check a site before launch. Use it for a new build or to audit one that already exists.

Key takeaways

• Fix the technical base first: indexing, sitemap, canonical URL, HTTPS and redirects.
• Every indexable page needs its own title, meta description and one H1.
• Set up CMS templates once, with dynamic SEO fields and schema, so every new item is optimised automatically.
• Page speed is part of SEO. Heavy images and third-party scripts are the usual culprits.
• Write answer-first content, then measure in Google Search Console.

What is a Webflow SEO checklist?

A Webflow SEO checklist is a list of settings and content checks that make a Webflow site easy for search engines to crawl, understand and rank. It covers site-level settings, page-level metadata, CMS templates, performance and measurement. Webflow also publishes its own SEO checklist, which is a good companion to this one.

Is Webflow good for SEO?

For most business websites, yes. Webflow produces clean markup, generates a sitemap automatically and lets you edit the settings that matter. Third-party reviews note some limits, such as restricted code access and extra effort on very large sites, so it is not magic. The platform is a good base. The result depends on how you use it.

Here is what is built in and what is still your job:

Which site-level settings should you check first?

Start with the settings that affect the whole site: your custom domain, indexing, sitemap, canonical URL and redirects. These are quick to set and cause the biggest problems when they are wrong. Webflow’s site-level SEO guidance covers the same ground.

1. Use one canonical domain. Pick www or non-www, set it as the default and make sure the other redirects to it. Check that HTTPS is on.
2. Set a global canonical tag. Webflow lets you set a global canonical tag and override it on a single static page. One catch from Webflow’s help article: if another tool such as Google Tag Manager already injects canonical tags, do not also set a global one in Webflow, or pages will carry two.
3. Keep the Webflow subdomain out of the index. Disable indexing of the .webflow.io subdomain in the SEO settings so it does not compete with your real domain.
4. Check the sitemap. Webflow generates it automatically and updates it when you publish. Open /sitemap.xml on your live domain and confirm the pages you want indexed are there.
5. Review robots.txt. Make sure it does not block pages or bots by mistake. If you want AI search tools to find you, see my AEO for Webflow guide.
6. Add 301 redirects for changed URLs. Webflow’s guidance says you can add redirects in the site settings, one by one or in bulk by CSV, and suggests keeping the total to roughly 1,000 or fewer. Publish the site afterwards so they take effect.

Menu names change between Webflow releases, so check the live dashboard if a label looks different from what I describe.

How do you optimise each page in Webflow?

Give every indexable page a unique title, a useful meta description, one H1 and a short, readable URL. In Webflow you set the title, description and Open Graph fields in the page settings under SEO. These are basic, but they are the items most often missing on live sites.

Page checklist:

• Title tag: 50–60 characters, with the main keyword near the start. Google may rewrite title links, and reports on its title sources show it can draw on several elements including the page heading and og:title, so keep those consistent.
• Meta description: 110–160 characters that promise what the page delivers. Google may use it as the snippet, but it can also pull text from the page.
• One H1 per page, then H2 and H3 in order. In the Designer, change the heading tag in settings rather than choosing a heading for its size.
• URL slug: short, lowercase, with the keyword and no dates or stop words.
• Images: descriptive alt text, sensible file names and no text baked into images.
• Internal links: link related pages with descriptive anchor text, not “click here”.
• One topic per page. Avoid targeting the same keyword on several pages, because they compete with each other.

How do you set up SEO for Webflow CMS templates?

Set the title, description and Open Graph fields on the CMS template page using dynamic fields, so every collection item gets its own metadata automatically. Add a plain-text SEO description field to the collection so editors write a proper one instead of leaving it blank.

For a blog or project collection I usually add:

• SEO title field (plain text) used in the template’s title setting, falling back to the item name.
• SEO description field (plain text) used for the meta description.
• Main image with an alt text field.
• Author and updated date fields, shown on the page and used in schema.
• Related items reference field to create internal links without manual work.

A note on duplicates: filtered collection lists, tag pages and pagination can create several URLs for similar content. Keep only the pages you want indexed in the sitemap, and use canonical tags where it makes sense.

How do you add schema markup in Webflow?

Add JSON-LD structured data as custom code. Webflow has no built-in schema editor, so use site settings for site-wide types such as Organization, the page settings for a single static page, and the CMS template page settings for schema generated from collection fields. Only mark up content that is visible on the page.

Practical rules:

• Use the standard types that fit: Organization or Person on the home page, BlogPosting on posts, FAQPage for real FAQ sections, BreadcrumbList for navigation.
• Keep schema fields plain text. A double quote or line break in a CMS field can break the JSON.
• Check how date fields print on the published page, and format them as 2026-10-26.
• Test every template with Google’s Rich Results Test and the Schema Markup Validator after publishing.

How does page speed affect Webflow SEO?

Page speed affects both rankings and conversions, so treat it as part of SEO. Google’s Core Web Vitals measure loading, responsiveness and visual stability. According to web.dev, a page is “good” when Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less and Cumulative Layout Shift is 0.1 or less, measured at the 75th percentile.

Webflow’s hosting and CDN give you a head start. The common problems are in what you add:

• Heavy images: upload at the size you display, use WebP or AVIF and lazy-load images below the fold.
• Third-party scripts: chat widgets, trackers and embeds are the usual cause of slow Webflow pages. Remove what you do not use.
• Layout shift: set width and height on images and reserve space for embeds.
• Animations: keep GSAP and interactions light, and never hide important content until an animation runs.

Run PageSpeed Insights on your key templates on mobile and desktop, and fix the biggest issues first.

How do you make your Webflow content rank?

Write content that answers a real question directly, then adds depth. Match the page type to the search intent: a guide for informational searches, a comparison for “vs” searches, a service page for commercial ones. Put a short answer under each question heading and support it with examples.

• Turn headings into the questions people ask.
• Write a 40–60 word answer under each, then detail.
• Use tables for comparisons and lists for steps.
• Link to sources for facts and statistics.
• Update pages only when you actually change them, and show honest dates.

This also makes the content easier for AI tools to quote. Google’s recent coverage around AI Mode describes AEO and GEO as still SEO, so one good page can serve both.

How do you measure Webflow SEO results?

Connect the site to Google Search Console, submit your sitemap and review the Pages and Performance reports every month. Search Console shows which pages are indexed, which queries bring impressions and clicks, and which URLs have errors. Pair it with your analytics tool to see what visitors do next.

A simple monthly routine:

1. Check the Pages report for new “not indexed” reasons.
2. Open Performance and sort by impressions to find pages ranking on page two.
3. Improve the titles and answers on those pages first.
4. Re-run PageSpeed Insights on your top templates.
5. Check for new broken links and add redirects where needed.

Common Webflow SEO mistakes

• Leaving the .webflow.io subdomain indexable.
• Forgetting 301 redirects after changing URLs or rebuilding a site.
• Setting a global canonical tag while another tool also adds one.
• Duplicate or empty titles and descriptions on CMS items.
• Several H1s, or headings chosen by size.
• Schema that does not match the visible page.
• Uncompressed images and unused third-party scripts.
• Publishing thin pages with no clear answer.

Final thoughts

Webflow SEO is mostly about doing the basics completely and consistently: a clean site setup, unique metadata, well-built CMS templates, fast pages and content that answers questions. Do those, measure monthly and improve what the data points to.

If you’d like help auditing or building a Webflow site that is set up for search from day one, get in touch and I’ll take a look.

Frequently Asked Questions