Webflow SEO: The Settings to Check on Every Site

The settings worth checking on every Webflow site are the per-page SEO title and meta description, the CMS Collection template's dynamic SEO pattern if you use the CMS, the global canonical tag, and — if you've moved a page — a 301 redirect. Webflow builds most of these as native fields in Page settings, not custom code you have to write yourself; the one that used to require custom code, schema markup, now has its own native field too. Here's exactly where each one lives, sourced from Webflow's help center.

Where do I set a page's SEO title and meta description?

Go to Pages panel > Page settings > SEO settings. Webflow's help center describes the two fields plainly: "Title tag — the text that typically displays as the page's title in search results. It's best practice to keep the title under 60 characters," and "Meta description — the text that typically appears below the page's title in search results... There's no character limit for meta descriptions, but search engines truncate long descriptions" (Webflow). You can write these manually, or click Generate to have Webflow AI draft them from the page's content — per the same page, you can add this metadata "if the site has a paid Site plan or is part of a paid Workspace." Webflow deliberately doesn't offer a site-wide title or description field: "Unique titles and descriptions for each page of your site lead to a better user experience and significantly improve SEO" (same source). After changing these, publish your site — then expect a wait: the help center says changes "can take days, weeks, or even months" to be indexed and show up in search results.

How do CMS Collection pages get their SEO fields?

The same Page settings > SEO settings panel exists on a Collection's template page, but instead of typing one static value, you build a pattern once and every item in that Collection generates its own title and description from it. Webflow's own example: "if you have a Collection of blog posts, you can use dynamic data in your SEO settings to use each blog post's title Collection field as the SEO title for each blog post" (Webflow). This dynamic-template approach isn't new — Webflow's own changelog dates the underlying feature to December 17, 2015, describing it as: "just create a template for your SEO tags and we'll automatically generate search engine-friendly titles, descriptions, and Open Graph content" (Webflow). It's a mature, stable feature, not a recent beta.

What about social previews — Open Graph settings?

Open Graph controls how a shared link looks on Facebook, LinkedIn, and X. Same location: Pages panel > Page settings > Open Graph settings. Webflow sets three fields — title, description, image — and warns that skipping this means "random content (or no content) will appear when your site is shared on social media" (Webflow). Reuse your SEO title/description via a checkbox under each OG field, or write unique copy, since OG content "works best when it's specific to the page being shared." Collection pages support the same dynamic pattern: click Add field to pull title, description or image from a Collection field, so every item gets a correct, unique preview automatically.

How do I set a canonical tag?

Two levels, both native. For the whole site: Site settings > SEO > Global canonical tag URL, where you enter your site's base URL (e.g. https://www.yourdomain.com); Webflow combines that with each page's slug to build every canonical tag automatically. Webflow flags specific formatting traps: "You must include the HTTP/HTTPS protocol... If your site's default domain is set to the www subdomain, you must also include the www URL prefix... You must exclude the trailing slash" (Webflow). For one static page that should defer elsewhere — a landing or campaign page — open its Page settings > SEO settings and enter a full URL in Page canonical URL, which overrides the global tag for that page only. Don't set both a global tag and an external tool's canonical injection (e.g. Google Tag Manager): Webflow warns this "will create multiple canonical tags on your pages, which search engines may ignore entirely" (same source).

Does Webflow generate a sitemap for me?

Yes, natively, with a toggle rather than a manual build. Go to Site settings > SEO tab > Sitemap section and switch Auto-generate sitemap to Yes; Webflow then builds sitemap.xml and "updates it each time you publish your site" (Webflow). Each URL entry includes a <lastmod> timestamp that updates on republish. If you turn auto-generation off, you get a text field to paste your own custom sitemap instead — useful for a reverse-proxy setup spanning multiple Webflow sites on one domain, though Webflow notes you can't delete the /sitemap.xml page once you've published one. Webflow adds the sitemap's address to your robots.txt automatically; removing that reference to substitute your own requires a paid Site plan.

How do I set robots.txt rules?

Go to Site settings > SEO > Indexing. Webflow's rules follow the standard User-agent / Allow / Disallow format, and the help center is explicit that this file is public: "Your site's robots.txt file is publicly visible — avoid relying on it to protect sensitive or private content" (Webflow). Not every bot respects it either: "Not all bots follow the rules specified in your robots.txt file, especially malicious or poorly configured ones... these bots may still access your site." The same panel also has a newer Content-Signal HTTP header, letting you tell AI crawlers separately whether content can be used for AI training, search indexing, or AI-generated responses (e.g. Content-Signal: ai-train=no, search=yes, ai-input=no) — Webflow flags it as experimental: "based on a proposed extension to RFC 9309 and is not yet an accepted standard" (same source).

How do I set up a 301 redirect?

Two routes. Automatic: rename a static page's slug in Page settings and check "Permanently redirect the old URL to this new one." Manual: go to Site settings > Publishing > 301 redirects, enter the old and new paths, and click Add redirect path. Webflow states that "to add 301 redirects, your site needs a paid Site plan, or it must be part of a Workspace with a paid Workspace plan." While there's no hard cap, Webflow recommends "1,000 maximum as best practice," since every rule adds to a manifest file every visitor's browser downloads (Webflow). Wildcard redirects with capture groups can redirect a whole folder at once; rules run in creation order, so add specific rules before broader wildcards. Publish the site for any redirect to take effect.

Can I add schema (structured data) markup without custom code now?

Yes — this changed from a custom-code-only workaround to a native field. Open the page, go to Pages panel > page settings > Schema markup section, and either click Generate schema markup to have Webflow AI draft it from the page's content, or paste your own JSON-LD. Webflow's help center: "Schema markup — also known as structured data — helps search engines and AI-powered tools understand the content and purpose of your pages," and it's available "if the site has a paid Site plan or is part of a paid Workspace" (Webflow). On Collection pages, generating schema with Webflow AI automatically binds relevant dynamic fields (name, price, image) so each item gets unique markup. If you already added schema through the older custom-code method, Webflow says it "will continue to work as expected" — no need to migrate it — but avoid using both at once, since duplicate structured data on one page is explicitly discouraged. Reference, multi-reference and multi-image Collection fields aren't supported here; use a plain text, image or similar supported field instead.

What still needs custom code instead of a native setting?

A few things: pinning exact Open Graph image dimensions (Webflow's own fix for missing Facebook previews is an <meta property="og:image:width">/og:image:height"> pair in Site settings > Custom code > Head code, or per-page if your images vary in size (Webflow)), plus anything the native panels above don't cover, like third-party verification meta tags.

What's automatic vs. what needs my input?

Where does Figment fit in?

Nowhere directly — Figment publishes a Figma file as a live site through its Figma plugin and isn't a CMS with Collection templates or a sitemap/robots.txt settings panel to compare against Webflow's. If your actual question is whether to stay on Webflow or rebuild the design elsewhere, using AI with your Webflow site and how to create a website from Figma are the more relevant reads; this post is about using Webflow's own SEO settings well.

Bottom line: Webflow has moved almost everything that used to require a custom-code workaround — schema markup, dynamic CMS SEO, Open Graph — into a native settings panel gated by a paid plan rather than by your ability to write JSON-LD by hand. The one manual habit that still matters most: set a canonical URL and a redirect the moment a page's address changes, because neither one back-fills itself.