Check four things on every Webflow site: 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 a 301 redirect for any page you move. Webflow offers native fields for each of these in Page settings and Site settings. Schema markup, which used to need custom code, now has a native field too. Each section below gives the menu path, 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: "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).
Write them 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 has no 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). Publish the site after changing them. 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?
They get them from a pattern you build once on the Collection's template page. The same Page settings > SEO settings panel exists there, but instead of one static value, every item in the Collection generates its own title and description from the pattern. Webflow's 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 is a mature feature. Webflow's changelog dates it 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).
How do I set Open Graph settings for social previews?
Go to Pages panel > Page settings > Open Graph settings. Open Graph controls how a shared link looks on Facebook, LinkedIn and X. Webflow sets three fields (title, description, image) and warns that skipping them means "random content (or no content) will appear when your site is shared on social media" (Webflow).
Reuse your SEO title and description with the checkbox under each Open Graph field, or write unique copy, since Open Graph content "works best when it's specific to the page being shared." Collection pages support the same dynamic pattern. Click Add field to pull the title, description or image from a Collection field, so every item gets its own preview.
How do I set a canonical tag?
Set it at two levels, both native.
- Whole site: go to Site settings > SEO > Global canonical tag URL and enter your site's base URL (for example
https://www.yourdomain.com). Webflow combines it with each page's slug to build every canonical tag. Webflow flags 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). - One static page that should defer elsewhere, such as a landing or campaign page: open its Page settings > SEO settings and enter a full URL in Page canonical URL. This overrides the global tag for that page only.
Do not set both a global tag and an external tool's canonical injection (for example 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. 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 sitemap. That suits a reverse-proxy setup that spans several Webflow sites on one domain. Webflow notes you cannot delete the /sitemap.xml page once you have 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.
For page-exclusion rules and Google submission steps, see the Webflow sitemap guide. For a site in more than one language, see the Webflow Localization guide for translated URL structure and locale-specific SEO.
How do I set robots.txt rules?
Go to Site settings > SEO > Indexing. Webflow's rules use the standard User-agent / Allow / Disallow format. The help center says the 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 obeys 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 has a newer Content-Signal HTTP header. It lets you tell AI crawlers separately whether content can be used for AI training, search indexing, or AI-generated responses (for example 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?
Use one of 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." There is no hard cap, but 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 markup without custom code?
Yes, with 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 says: "Schema markup — also known as structured data — helps search engines and AI-powered tools understand the content and purpose of your pages," and it is 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 binds relevant dynamic fields (name, price, image) so each item gets unique markup. Schema you added earlier through custom code "will continue to work as expected," so you do not need to migrate it. Avoid using both on one page, since duplicate structured data is discouraged. Reference, multi-reference and multi-image Collection fields are not supported here. Use a plain text, image or similar supported field instead.
What still needs custom code?
Two things: pinning exact Open Graph image dimensions, and anything the native panels do not cover, such as third-party verification meta tags. Webflow's own fix for missing Facebook previews is an <meta property="og:image:width"> and og:image:height"> pair in Site settings > Custom code > Head code, or per page if your images vary in size (Webflow).
What does Webflow handle, and what do I fill in?
| Handled by a native toggle or panel | Needs you to fill it in |
|---|---|
| Sitemap generation and its robots.txt reference | Per-page SEO title and meta description |
| Redirect creation on a slug rename (if you check the box) | Manual 301s for deleted pages, restructured folders, or domain moves |
| Canonical tag population once you set the global URL | The global canonical URL itself, and any per-page override |
| Schema markup generation (Webflow AI, on paid plans) | Reviewing AI-generated schema for accuracy, or writing manual JSON-LD |
Set a canonical URL and a redirect the moment a page's address changes, because neither one back-fills itself.