Webflow SEO Settings You Are Probably Ignoring: Canonical Tags, Robots.txt, and Sitemap.

What Webflow SEO Settings Do Most People Skip?

Webflow gives you more native SEO control than almost any other visual website builder. Custom meta titles and descriptions on every page, automatic sitemaps, 301 redirects, canonical URLs, clean semantic HTML, and custom code injection for schema markup. But most Webflow site owners only use the basics: title tags and meta descriptions. The technical SEO settings that significantly impact search performance go untouched.

I audit Webflow sites regularly for clients and the same gaps appear on nearly every site. Missing canonical tags that create duplicate content issues. Robots.txt settings that accidentally block AI crawlers. Sitemap configurations that exclude important pages. Open Graph tags that produce ugly social media previews. These are not advanced settings. They are foundational configurations that take 15 minutes to set up and produce lasting SEO benefits.

Here is a walkthrough of every Webflow SEO setting you should configure, where to find each one, and what to set it to.

How Do Canonical Tags Work in Webflow?

A canonical tag tells search engines which version of a page is the "original" when similar or identical content exists at multiple URLs. Without canonical tags, search engines may split ranking authority between duplicate URLs, weakening the performance of both. In Webflow, every page and CMS item has a canonical URL field in its SEO settings.

For most pages, the canonical URL should be the page's own URL. Webflow sets this automatically, but verify that each page's canonical URL matches its actual URL, including the correct protocol (https, not http) and domain format (with or without www, matching your primary domain setting).

Canonical tags become critical when you have pages with similar content. If your site has both /services/webflow-development and /webflow-development pointing to similar content, set the canonical on the secondary page to point to the primary page. This tells Google to consolidate ranking authority on the page you want to rank.

For CMS items, Webflow handles canonical URLs automatically based on the collection page template URL structure. Verify this by inspecting the page source of a published CMS item and confirming the canonical tag matches the expected URL.

What Should Your Robots.txt File Look Like?

Webflow auto-generates a robots.txt file that allows all crawlers to access your site. You can customize it in Site Settings under the SEO tab. The default setting works for most sites, but there are important additions to consider.

For AI crawler access, ensure your robots.txt does not block AI crawl bots. Some Webflow sites have inherited restrictive robots.txt rules that block GPTBot (ChatGPT's crawler), ClaudeBot (Anthropic's crawler), or PerplexityBot. If you want AI systems to crawl and potentially cite your content, these bots need access. Verify by checking your published robots.txt at yourdomain.com/robots.txt.

Block pages you do not want indexed: staging subdomains, thank-you pages (which should not rank in search), utility pages, and any pages with thin or duplicate content. Add Disallow directives for these specific paths rather than blocking entire directories.

Reference your sitemap in robots.txt with a Sitemap directive pointing to yourdomain.com/sitemap.xml. This helps crawlers discover your sitemap quickly without relying solely on Google Search Console submission.

How Do You Customize Webflow's Automatic Sitemap?

Webflow generates a sitemap automatically at yourdomain.com/sitemap.xml that includes all published pages and CMS items. You cannot edit this sitemap directly (Webflow generates it), but you can control which pages appear by using the "Exclude from sitemap" option in individual page settings.

Exclude pages that should not appear in search results: thank-you pages, password-protected pages, utility pages, and test pages. Including these dilutes your sitemap with low-value pages that waste crawl budget. A clean sitemap containing only your important, indexable pages helps search engines prioritize crawling the content that matters.

After publishing any changes to your site structure (adding or removing pages), verify your sitemap by visiting it directly and checking that all important pages are listed. Submit the sitemap through Google Search Console under the Sitemaps section. Webflow updates the sitemap automatically when you publish, but Search Console submission prompts faster recrawling.

How Do Open Graph Tags Affect Your Traffic?

Open Graph (OG) tags control how your pages appear when shared on social media platforms, messaging apps, and some AI systems. A properly configured OG image, title, and description produce an attractive, clickable preview that drives more shares and referral traffic. Missing or misconfigured OG tags produce ugly, text-only previews that people do not click.

Webflow lets you set OG title, description, and image on every page and CMS item through the page's Open Graph Settings. The OG title can differ from the SEO title, which is useful when the SEO title is keyword-optimized but the social title needs to be more engaging. The OG description should be concise and compelling, not a copy of the meta description.

The OG image is the most impactful field. Create a template image (1200x630 pixels is the standard dimension) with your brand colors, your headline text, and your logo. Use this template consistently across all pages. Webflow does not auto-generate OG images, so each page needs a manually uploaded image or a CMS-driven image from a featured image field.

For CMS items (blog posts, case studies), bind the OG image to the featured image field and the OG title to the post title. This ensures every CMS item has proper social sharing metadata without manual configuration per item.

What About Webflow's Indexing Settings?

Each Webflow page has indexing controls in its SEO settings. The "Exclude this page from search results" toggle adds a noindex meta tag that tells search engines not to index the page. Use this for pages that should exist on your site but not appear in search results: thank-you confirmation pages, landing pages for paid campaigns (if you want to track them separately), and internal utility pages.

Never noindex your important pages accidentally. I have seen Webflow sites where the homepage or a key service page was inadvertently set to noindex during development and never switched back before launch. Check every page's indexing status before publishing, and audit your site through Google Search Console's Coverage report to catch any accidentally excluded pages.

For staging sites on Webflow's webflow.io subdomain, Webflow automatically adds noindex to prevent staging content from being indexed. This protection only applies to the staging subdomain, not to your custom domain. Always verify that your published custom domain pages are set to allow indexing.

How Do You Configure Webflow's 301 Redirects?

301 redirects in Webflow are configured in Site Settings under the Publishing tab. Add the old URL path and the new URL path, and Webflow will permanently redirect any traffic from the old URL to the new one. This is essential when you change page slugs, restructure your site, or migrate from another platform.

Set up redirects for every URL change, no matter how small. Changing a blog post slug from /blog/old-title to /blog/new-title without a redirect creates a 404 error for any existing links, bookmarks, or search engine references to the old URL. The redirect preserves the ranking authority and backlinks associated with the original URL.

For sites migrated from WordPress or another platform, create a comprehensive redirect map covering every old URL. I covered this process in detail in my WordPress to Webflow migration guide, but the principle applies to any URL structure change: every old URL that received traffic or has backlinks needs a 301 redirect to its new equivalent.

How to Audit Your Webflow SEO Settings This Week

Open your Webflow site in the Designer. Check Site Settings for robots.txt (verify no important crawlers are blocked), sitemap settings (verify all important pages are included), and global head code (verify Organization schema is present). Then check each of your top 5 pages for proper canonical URLs, OG tags with images, and correct indexing status.

Visit yourdomain.com/robots.txt and yourdomain.com/sitemap.xml directly to verify the published versions match your intended configuration. Submit your sitemap through Google Search Console if you have not done so recently.

For the schema markup that goes in your site-wide and page-specific head code, my guide on 8 schema markup types every Webflow site needs covers the implementation. For the broader SEO checklist that includes these technical settings, my complete SEO checklist for launching a website covers every requirement. And for the AI crawler access that robots.txt controls, my article on fixing Cloudflare blocking AI crawlers covers the access configuration.

These settings take 15 minutes to configure correctly and produce permanent SEO benefits. Every day they remain misconfigured is a day you are leaving search visibility on the table. If you want help auditing your Webflow site's technical SEO settings, I am happy to take a look. Let's chat.