Skip to content
Passionfruit
Book a call

Platforms: Webflow

Best SEO and GEO agency
for Webflow sites.

Webflow publishes fast, static pages, which is a strong start. What it leaves to you decides who gets recommended: schema, collection lists crawlers can read to the end, a CMS with real structure and pages that answer buyers’ questions. Passionfruit does that part.

How Webflow sites get found now

  1. Static HTML, until a script fills the list

    Webflow sends pages as static HTML, which suits crawlers. Collection items added by “load more” or a client-side filter are the exception: crawlers that skip JavaScript may never see them.

  2. Software shortlists start in a chat

    Buyers now ask ChatGPT or Google’s AI Overviews for the “best customer onboarding software for B2B SaaS” and get a short list of names back. Those names belong to companies whose pages answer that exact question in text.

  3. Design-led pages need words

    Many Webflow sites lead with motion and short lines of copy. Engines quote sentences, tables and FAQs, so a beautiful page with little text gives them little to cite.

What Webflow does for search, and what it leaves to you

Webflow puts many technical basics into its settings. These are the areas we check on every site: what Webflow covers, and what we add.

Titles and meta descriptions

Out of the box

Set per page, and on CMS templates bound to collection fields. Turning off a page’s sitemap indexing adds noindex and drops it from the sitemap.

What we add

Titles and descriptions written for the phrases buyers use, with CMS bindings that give every item its own rather than a shared one.

Canonicals

Out of the box

A global canonical base URL in site settings, combined with each page slug. Static pages can override it.

What we add

The base URL set once and checked in the live HTML, with any second canonical injected through Google Tag Manager removed.

CMS URLs

Out of the box

Collection items live at /collection/item, or under a static folder with CMS Folders.

What we add

Collection slugs that match how people search, folders and hub pages that give topics depth, and a 301 for every URL we change.

Sitemap

Out of the box

Generated for you. With Localization, only locales with publishing turned on are included.

What we add

A check that every page that should rank is in it, and that utility, thank-you and excluded pages are not.

robots.txt

Out of the box

Generated for you and editable in site settings.

What we add

Explicit rules for the AI search crawlers you want in, so search bots such as OAI-SearchBot stay allowed even if training bots like GPTBot are not.

Structured data

Out of the box

None by default. JSON-LD is added by hand in head code, through CMS field bindings on templates, or with an app.

What we add

Organization site-wide, plus Article, FAQ and SoftwareApplication JSON-LD bound to CMS fields, so every template ships complete markup.

International

Out of the box

With Localization, Webflow adds hreflang automatically, in page tags or in the sitemap.

What we add

Titles, descriptions and page copy written for how each market searches, rather than translated word for word.

AI crawlers and llms.txt

Out of the box

An llms.txt file can be uploaded in site settings. Webflow serves it from the root, keeps it out of the index and calls its benefit unclear.

What we add

An llms.txt as low-cost hygiene, and the work that matters more: crawler access checked in the live responses and collection lists every crawler can read to the end.

See where your Webflow site stands.

Book a call and we will check these on your own site, live.

Book a call

How AI engines read a Webflow site

An engine’s answer about your product is assembled from these five places. On Webflow, the first two come down to what the published page and its collection lists actually contain.

  1. Your published HTML

    Crawlers such as OAI-SearchBot and PerplexityBot read the page as Webflow serves it. Static pages arrive whole, so the part to check is anything a script adds after load. We make sure everything that matters is in the page as published.

  2. Your CMS collection lists

    A list that shows the first items and adds the rest with “load more” or a client-side filter hides most of the collection from bots that skip JavaScript. We give every item a crawlable link on a paginated or static list.

  3. Google’s index

    AI Overviews and AI Mode are built on Google’s own crawl, so classic Webflow SEO still feeds them. Blocking Google-Extended does not take you out of either; it only covers Gemini training and grounding.

  4. Review sites and comparisons

    G2, Capterra and “best tools for” roundups carry real weight when engines build a software shortlist. We watch how you appear there and work to get you into the roundups that get cited.

  5. Reddit and buyer communities

    Buyers ask Reddit, Slack groups and LinkedIn which tool to pick, and engines read those conversations too. We join them as your company, openly, and answer the questions your buyers are asking.

Search problems Webflow sites face

The issues we find on almost every Webflow site we audit, each with the fix.

  1. 01No schema anywhere

    Webflow adds none by default, so engines get no structured facts about the company, the product or its FAQs. We add Organization site-wide and bind Article, FAQ and SoftwareApplication JSON-LD to CMS templates.

  2. 02A missing or doubled canonical

    The global canonical URL was never set, or a tag manager injects a second one. We set it once in site settings and remove the injected tags.

  3. 03Design-led pages with little to quote

    Motion, imagery and short lines of copy leave engines little they can cite. We add answer-first sections, comparison tables and FAQs that sit inside the design rather than on top of it.

  4. 04Flat CMS URLs with no hierarchy

    Every item sits at /collection/item, so topics have no depth. We use CMS Folders, hub pages and dense internal links to show engines how the pieces connect.

  5. 05Collection lists crawlers cannot finish

    Client-side filters and “load more” buttons inject most items with JavaScript. We add paginated or static lists that link every item, so nothing depends on a script.

Find out which of these is costing you most.

Book a call and we will rank them by the revenue at stake on your own site.

Book a call

The tools you run, and where they stop

Webflow teams usually add a few of these to the stack. Every one fills a gap, and every one leaves a different gap open.

Webflow AEO

Their gap
Webflow’s own AEO product, currently for Enterprise sites, tracks AI citations and prompts, and its agents suggest and ship fixes on your Webflow pages. It is built around the pages you host there.
Your opening
We also work on what sits off the site, the Reddit threads, reviews and press engines cite, with a team that ships the work.

Schema apps

Their gap
They add JSON-LD templates to pages and CMS items, which fills Webflow’s biggest default gap. A template is only as complete as the fields behind it.
Your opening
We map every field engines read and check the live markup on each template.

Filter and load-more libraries

Their gap
They make long collection lists easy to browse by adding and filtering items in the browser. That can leave bots that skip JavaScript with the first page only.
Your opening
We keep the experience and give every item a crawlable link.

Google Tag Manager

Their gap
It lets marketers add scripts without a developer, SEO tags included. A canonical or schema block added there can contradict what Webflow already prints.
Your opening
We move SEO tags into Webflow and keep the tag manager for tracking.

The Webflow program, part by part

Each part of the program is built for how Webflow works: static pages, interactions, the CMS and its fixed collection URLs.

Content

Problem, solution and buyer’s guide articles in the blog collection, with question-style headings, direct answers and FAQs as real text in rich text fields. The blog sits on the same domain as your product pages, so an article that gets cited sends its authority, and its readers, to the pages that convert.

More on Content
01 / 10

Why Webflow teams work with Passionfruit

Webflow puts static pages, sitemaps and canonicals into settings your team can change. What is left is the work that decides who gets recommended, and it sits across the CMS, the copy, the schema and the rest of the web.

Passionfruit Intelligence tracks how your company shows up across ChatGPT, Gemini, Perplexity, Claude and Google’s AI answers, which competitors are named, and the pages and sources each answer leans on. Our team then ships the fixes: schema, crawlable collections, comparison and use-case pages, and the off-site work engines trust.

We work inside your Webflow project with your team’s approval, keep the design you built, and measure every change against pipeline, not just rankings.

What we measure

  • Signups and pipeline from organic search and AI referrals, by collection
  • Mentions in AI answers for category, comparison and alternatives prompts
  • CMS items crawlable and indexed versus published
  • Templates shipping complete, valid schema
Book a callHow Passionfruit connects to Webflow

Questions

Is Webflow good for SEO?

Yes, for the technical basics. Webflow serves static HTML and generates sitemaps, robots.txt and canonicals from your settings. What it leaves to you is schema, collection lists crawlers can read to the end, CMS structure and pages that answer buyers’ questions.

Does Webflow add schema markup?

Not by default. JSON-LD is added by hand in head code, bound to CMS fields on templates or added with an app. We add Organization site-wide and bind Article, FAQ and SoftwareApplication markup to CMS templates.

Can AI crawlers read Webflow CMS collection lists?

Webflow pages are static HTML, which suits crawlers. Collection items added by “load more” or a client-side filter are the exception, since crawlers that skip JavaScript may never see them. We give every item a crawlable link on a paginated or static list.

Can I change Webflow’s /collection/item URLs?

Partly. Items live at /collection/item, and the item slug is the only dynamic part. CMS Folders can nest a collection under a static folder, and we add hub pages and internal links to give topics depth.

Does Webflow support llms.txt?

Yes. You can upload an llms.txt in site settings, and Webflow serves it from the root. Webflow’s own help calls its benefit unclear, so we treat it as low-cost hygiene and spend the effort on crawler access and content.

How is Passionfruit different from Webflow AEO?

Webflow AEO, currently for Enterprise sites, tracks AI citations, and its agents suggest and ship fixes on your Webflow pages. Passionfruit also works on the sources off your site that engines cite, such as Reddit, reviews and press, and our team ships the work.

More platforms

Get found and chosen in AI answers.

Book a call and we will show you where Google and AI answers leave you out today, and what we would ship first to get you in.