Webflow SEO: what to switch on first

Searches to plan around

Query patterns and the intent behind them. We don’t quote search volumes: check your own Search Console for the ones you already appear for.

• “[problem] software”, “tool to [job]”

  Category discovery

  Use-case pages written in the buyer's words. Software sites on Webflow often have a page per product area and none per job.

• “[competitor] alternatives”, “[A] vs [B]”

  Switching

  A comparison collection with real fields (price, limits, integrations, date last checked) keeps pages distinct. A Collection list shows 100 items at most, so paginate big sets (Webflow).

• “[your tool] [other tool] integration”

  Evaluation

  One CMS item per integration you really support: what syncs, the setup steps and the limits.

• “[service] agency for [industry]”, “[agency] case study”

  Hire

  Studios and agencies on Webflow win on case studies written as text, not a gallery of mockups.

• “[job] template”, “[topic] checklist”

  Resources

  Free templates and checklists in a resources collection earn links and rank for queries a pricing page can't.

• “[your brand] pricing”, “[your brand] reviews”

  Brand check

  Put prices and plan limits in text on the page, and set the title tag and Open Graph on it. Webflow has no site-wide default for either.

Page families that work

• Use-case and audience pages

  /use-cases/approval-workflows

  Static pages, one job each, with their own title, description and Open Graph image. Each static page has a Sitemap indexing toggle and can carry its own canonical (Webflow).

• Integration pages (CMS)

  /integrations/hubspot

  A collection with fields for what syncs, in which direction, setup steps, limits and a docs link. Bind the template's title and description to fields so every item has its own.

• Comparison and alternatives (CMS)

  /compare/you-vs-incumbent

  Fields for price, limits, integrations and the date you last checked, plus a plain section on who should pick the competitor. Dated facts are what keep these pages honest.

• Blog and guides (CMS)

  /blog/seo-checklist

  A blog collection with an author reference, a rich-text body and a summary. The item URL is /<collection URL>/<item slug>, and the collection part can't be removed (Webflow).

• Customer stories (CMS)

  /customers/acme

  The problem, what the customer did and the result, with their permission. These rank for the niche problem queries a feature page doesn't cover.

• Resources and templates (CMS)

  /templates/quarterly-okr-sheet

  One item per template or checklist, with a description, a preview and how to use it. Things people can use before signing up earn links and bookmarks.

Risky page types

• Template pages with one field changed

  A CMS template makes it easy to publish hundreds of pages that differ by one word. Google's scaled content abuse and doorway policies describe that pattern. Set a minimum bar: items below it stay draft, or get the item-level Sitemap indexing toggle switched off, which adds noindex and removes them from the sitemap (Webflow).

• City or industry pages for places and sectors you don't serve

  Pages that exist only to catch a search, with the same body text, are the doorway pattern. The safe method is here.

• AI-written posts published in bulk

  Google's guidance on generative AI content says using AI to produce many pages without adding value for users may breach its scaled content abuse policy. It applies whether the items are typed into the Webflow CMS or sent in through its API.

Technical pitfalls

1. 1

   The staging site can be indexed

   If you publish to yoursite.webflow.io as well as your custom domain, search engines can index both unless Staging indexing is off in Site settings > SEO > Indexing. That setting needs a Site plan or a paid Workspace, and it publishes a robots.txt on the subdomain only (Webflow's indexing guide, staging subdomain). If you've connected more than one custom domain, set a default domain so the others redirect to it (Webflow).

2. 2

   Canonical tags come from the global URL

   Set the Global canonical tag URL in Site settings > SEO and Webflow adds a self-referencing canonical to every page, combining your base URL with each page's slug. Include https, include www if that is your default domain, leave off the trailing slash and don't also inject canonicals from another tool. Static pages can override it with a page-level canonical (Webflow, site-level SEO). Google treats a canonical tag as a strong signal, not a command.

3. 3

   SEO settings are per page: bind the CMS templates

   There are no site-wide title or description settings and no global Open Graph tags. Each page sets its own, and with none set “random content (or no content)” appears when a link is shared (Webflow, Open Graph). On a Collection page use Add field to build the title and description from collection fields, and do the same for Open Graph. Webflow suggests titles under 60 characters and sets no meta description limit; the Open Graph image picker lists JPG and PNG assets only.

4. 4

   CMS URLs: the collection slug stays

   A CMS item URL is /<collection URL>/<item slug>. You can change the collection URL or put it inside a folder, but you can't remove it (Webflow). Rename it after publishing and you need a redirect: one wildcard rule covers every item (Webflow). A locale subdirectory that matches a folder, page or collection slug wins, and your page returns a 404 (Webflow).

5. 5

   Sitemap: auto or custom, and the indexing toggle

   Switch on Auto-generate sitemap in Site settings > SEO and Webflow rebuilds it at every publish, with a lastmod date and, with Localize, hreflang. A custom sitemap means you update it by hand, and you can't delete /sitemap.xml once it exists. Turning off a page's Sitemap indexing toggle adds noindex and removes the page from the sitemap; a robots.txt rule or your own noindex code doesn't remove it from the auto sitemap (Webflow, indexing). Item-level toggles for CMS items need a paid Site plan.

6. 6

   robots.txt needs a paid plan and can't be removed

   Rules go in Site settings > SEO > Indexing and need a Site plan or a paid Workspace. Once the file exists you can only replace it, for example with an allow-all rule (Webflow, indexing). Don't use Disallow to deindex a page: Google has to crawl it to see a noindex tag (Google).

7. 7

   Structured data is yours to add

   Webflow's guidance is to add JSON-LD as custom code in Page settings (each code area holds up to 50,000 characters), or on a Collection template where field values fill the properties (Webflow, custom code). It is easy to let markup drift from the page, so update it when the page changes and test it in the Rich Results Test. Google stopped showing FAQ rich results in May 2026 (Google).

8. 8

   Redirects: paid plan, order and limits

   Add 301s in Site settings > Publishing. They need a paid Site plan or Workspace. Webflow recommends keeping them under 1,000 rules and using wildcards such as /old/(.*) to /new/%1. Rules run in the order they were added, so put specific ones before a wildcard. To redirect an existing page you must first delete it, draft it or change its slug, and ticking “Permanently redirect the old URL to this new one” when you change a slug creates the 301 for you. Redirects don't cover localized subdirectories (Webflow).

9. 9

   Images, speed and list limits

   Webflow builds responsive variants (srcset) for images uploaded in the Designer or a CMS image field, not for images added by CSV import or the API. A conversion tool turns JPG and PNG assets into WebP or AVIF, though AVIF is poorly supported for Open Graph images (Webflow, conversion tool). A Collection list shows up to 100 items and a page can hold 40 lists, so paginate big archives (Webflow, Google).

10. 10

    CMS plan limits

    Webflow's May 2026 plan update merges the CMS and Business plans into one Premium plan with 20,000 CMS items, and lifts the CMS plan's limit from 20 to 40 collections (Webflow). Check your plan's item and collection limits before you design a family of thousands of pages.

11. 11

    Localize: an add-on, subdirectories and 302 routing

    A second locale needs a Localize add-on. Each locale publishes in a subdirectory, with hreflang tags in the page head and in the auto-generated sitemap and per-locale titles and descriptions. Visitor routing uses 302 redirects you can't override, and Localize doesn't work with Webflow Ecommerce plan features (Webflow, SEO and routing, overview).

How AI assistants answer questions in this category

Webflow's traffic controls in Site settings > SEO > Indexing write robots.txt rules for two groups of bots, both allowed by default. The search-engine group lists Googlebot, Bingbot and OAI-SearchBot among others; the AI group lists GPTBot, ClaudeBot, ChatGPT-User, Claude-User and PerplexityBot among others (Webflow). Perplexity documents PerplexityBot as the crawler that surfaces sites in its search results (Perplexity), so switching off the whole AI group blocks that crawler too, not only the training crawlers; write custom rules if you want to separate them. A Content-Signal header can also state your ai-train, search and ai-input preferences (Webflow). You can upload an llms.txt to your custom domain (Site settings > SEO > LLMs.txt, UTF-8, under 100 KB), which Webflow itself calls experimental (Webflow); Google says its Search ignores that file (Google). Webflow AEO analytics need a Team or Enterprise plan plus the Analyze add-on (Webflow).

What tends to earn a citation

• Pricing, plan limits and integration lists in text on the page, not only in images.
• Comparison items with dated, specific facts: what each tool does, its limits and price, and when you last checked.
• Customer stories with a named problem, approach and result.
• JSON-LD on collection templates that matches the visible fields.

Check whether the AI crawlers you want can reach your site with our AI crawler checker.

Where links come from

• Partner and integration pages

  Tools you integrate with often run a marketplace or partner list. A listing there is relevant and brings referral visits; give them the exact page that describes the integration.

• Free tools, templates and data

  A resources collection (calculators, checklists, templates) earns links from pages that would never link to a pricing page.

• Startup and product directories

  Pick maintained startup directories and review sites, and skip any that sell links.

• Customers who publish the story

  A customer who posts your case study on their own site gives a relevant link and a quotable proof point.

A 90-day plan

1. Days 1–30

   Switch the right things on

   • –Turn Staging indexing off, set the default domain and set the global canonical URL.
   • –Switch on the auto-generated sitemap, submit it in Search Console and review any robots.txt rules.
   • –Set the title, description and Open Graph image on every static page, and bind each CMS template's SEO fields to collection fields.
   • –Add 301s for old URLs, using wildcards, and test them with a redirect checker.

2. Days 31–60

   Build the collections

   • –Pick one or two page families (integrations, comparisons, customer stories) and write down the fields every item must have.
   • –Publish only the items that meet that bar. Keep the rest as drafts or switch their Sitemap indexing off.
   • –Add JSON-LD to each template using field values, and validate it.
   • –Link items to hubs and to each other with reference fields.

3. Days 61–90

   Publish steadily and run the loop

   • –Add blog items to a collection at a steady pace, by hand or through Autopilot, and publish the site when you use staged items, which go live at the next site-wide publish.
   • –Rewrite titles by hand in Page settings on pages at positions 5–20.
   • –Decide on llms.txt and the bot traffic controls on purpose, then check them with the AI crawler checker.
   • –Review the Page indexing report by URL prefix (/integrations/, /blog/) and Search Console's Generative AI performance report.

What to watch in Search Console

The Performance report gives clicks, impressions, CTR and average position by query, page, country, device and date. Clicks from Google's AI features are counted there too, under the Web search type (Google), and since August 31, 2026 the Generative AI performance report shows which pages get impressions in AI Overviews and AI Mode.

Indexed against published, per collection

Filter the Page indexing report by URL prefix. A collection with many “Crawled – currently not indexed” items is telling you the pages look alike: fix it or leave it.

webflow.io pages in Google's index

Search for site:yoursite.webflow.io, or add the subdomain as its own Search Console property. Pages that show up mean the staging site is indexed: turn Staging indexing off, then check again in a few weeks.

“Duplicate, Google chose different canonical than user”

This Page indexing reason shows where Google isn't following your canonical. Check the global URL for an http, https or www mismatch with your default domain (Webflow).

Pages at positions 5–20 with few clicks

The cheapest wins. Rewrite the title and description in Page settings, or in the template's dynamic fields if the whole collection is affected.

Impressions in Google's AI features

Search Console's Generative AI performance report counts impressions in AI Overviews and AI Mode. Webflow's own AEO analytics need a Team or Enterprise plan and the Analyze add-on. Autopilot tracks ChatGPT, Perplexity, Gemini and Claude, not Google's AI Overviews.

Frequently asked questions

Sources

Checked on October 8, 2026. Search patterns and page advice are our own judgement from running this playbook; we don’t quote search volumes or third-party statistics.

1. Webflow Help Center: Dynamic content limits
2. Webflow Help Center: Set canonical tags to improve SEO
3. The Webflow Way: CMS Collections
4. Google Search Central: Spam policies for Google web search
5. Webflow Help Center: Disable search engine indexing
6. Google Search Central: Guidance on using generative AI content
7. Webflow Help Center: Webflow staging subdomain
8. Webflow Help Center: Set a default domain
9. The Webflow Way: Site-level SEO
10. Google Search Central: How to specify a canonical URL
11. Webflow Help Center: Add SEO title and meta description
12. Webflow Help Center: Control the look of social shares with Open Graph
13. Webflow Help Center: Manage CMS Collections
14. Webflow Help Center: Manage your site's locales
15. Webflow Help Center: Create a sitemap in Webflow
16. Webflow Help Center: Set robots.txt rules
17. Google Search Central: Block Search indexing with noindex
18. The Webflow Way: Page-level SEO
19. Webflow Help Center: Custom code in head and body tags
20. Google Search Central: Latest documentation updates
21. Webflow Help Center: How do I set up redirects in Webflow?
22. Webflow Help Center: Responsive images
23. Webflow Help Center: Image conversion tool
24. Google Search Central: Pagination best practices for Google
25. Webflow Help Center: Updated pricing and simplified plans for May 2026
26. Webflow Help Center: Localized SEO and locale routing
27. Webflow Help Center: Webflow Localize overview
28. Perplexity: Perplexity crawlers
29. Webflow Help Center: Upload an llms.txt file to your site
30. Google Search Central: Optimizing your website for generative AI features on Google Search
31. Webflow Help Center: Webflow AEO overview
32. Webflow Developers: Publishing with the CMS API
33. Search Console Help: Page indexing report
34. Search Console Help: Generative AI performance report (Search)
35. Google Search Central: AI features and your website
36. Search Console Help: Performance report