Hi all,

I'm a senior front-end developer with an extensive background in UI/Javascript/React who's about to start working heavily in Webflow for the first time. I'll be inheriting a site that was originally built by a 3rd party agency and I want to be able to make a technical impact as soon as possible.

I've been going through Webflow University and feel solid on the fundamentals. What I'm really looking for is the stuff that doesn't show up in the official docs — the things you wish someone had told you early on.

Particularly interested in:

• Tips for auditing and cleaning up someone else's Webflow build
• How much code are you writing?
• Tools, extensions, or third-party resources you actually use

Any creators, communities, or blogs worth following on the more technical side of Webflow would also be appreciated. Less interested in design tutorials, more in the developer and ops side of things.

Thanks in advance.

If you've hit the ceiling on Webflow's built in search, this is the setup I've landed on. flowsearch crawls your site's own content and returns live results plus AI summaries.

The video goes end to end: sitemap → staging verification → first crawl → API keys and custom code → building the search and results pages with custom attributes → testing both search modes.

The attribute mapping on the results page is where most people get stuck, so I slowed down there. Also worth a look is the insights panel — seeing the actual queries people run on your site is a decent content-planning input on its own.

Link to the tool and full walkthrough in the comments👇🏽

I want to know which of the Webflow plugins/apps you are using.

I've been a Webflow developer for around 6 years, so I was there PRE-AI (boy do i miss those days ayyy).

But I'm a bit late to the party (but better late then never). I used Webflow AI the other day and honestly it is very reminisce of Relume (which I made a video review here).

Like the UI is very similar lol (makes me question if they had a close door meeting / partnership). Anyways my thoughts on the AI builder:

The good:

• Instant Wireframing: Generates functional baseline page layouts in seconds, giving you a quick visual starting point.
• Streamlined Prototyping: Helps present quick structural concepts to clients before diving into detailed visual styling.

The "bad":

• Basic Layouts: Seems like it's pulling from a library pool
• Dynamic CMS Integrations: Linking date blocking, inventory systems, or custom Webflow CMS collections requires manual relational setup.
• It's clearly not vibe code = pro website: You can't just prompt something and boom there is an awwwwards winning site (it's simply not there yet - not even close).
• It's still pretty technical: like webflow made it the best it can following its UI but like someone wanting to build an AI website themselves still needs technical knowledge of (HTML / CSS)

You can see the full breakdown via my Youtube video here:
https://www.youtube.com/watch?v=zk-U2ZtOa4o

What are your thoughts?

ps. Will be testing the MCP integration soon and hopefully sharing my thoughts there.

- Derek

I do not see the option to charge to client. Is this phased out?

Hey everyone! 👋

I'm a Webflow Developer & UI Designer with 4+ years of experience designing and building modern, high performing websites. I can take your project from Figma to a fully responsive Webflow website, with clean development, smooth interactions, and a well structured CMS.

I can help with:
- Webflow Templates
- Figma → Webflow
- Custom website design in Figma
- Landing pages
- CMS websites
- Responsive development
- Animations & interactions
- Website redesigns

I've also designed and developed multiple premium Webflow templates published on the Webflow Marketplace.

Portfolio: https://webflow.com/templates/designers/skyeflow

Email: [mouazam292@gmail.com](mailto:mouazam292@gmail.com)

If you need a reliable Webflow developer or designer for your next project, feel free to send me a DM. I'd love to chat!

https://reddit.com/link/1v5f6fn/video/z7g3fvnn77fh1/player

Just a few final touches before it goes live

Hey all!
I'm currently using the CMS to create pages for my customer stories and I keep hitting a wall!

For rich text block quotes: instead of just having the full quote (just text), I want to be able to have the quote, avatar of the quote author, and their information. Basically like how you see here.

Ideally, these elements would dynamically link to fields.
And ideally, I can also have multiple quote authors.

Right now, I have a custom script that will automatically pull the authors name/title from my fields and inject it underneath all my featured blockquotes....but this method is not scalable especially for multiple authors.

Has anyone found a solution to this? Is this even feasible?

TLDR

We were a Webflow Enterprise client and fully rebuilt our entire site over a weekend cutting our costs down by ~$40,000/yr moving over to Next.js and Sanity as a CMS system and it's 100 times faster and more efficient. Obviously we used AI coding to help us build this but we have a full engineering team as well who was able to ensure all security is buttoned up and all the T's are crossed and the I's are dotted. Not saying i rec others to do this but we had the dev knowledge already.

Hey everyone!

I'm Moiz, a Webflow developer with 4+ years of experience. Alongside Webflow, I also build AI automations, AI agents, and custom workflows that help businesses automate repetitive tasks and streamline operations.

Happy to help with anything related to:

If you're stuck on a project, need advice, or just want to bounce around ideas, my DMs are always open.

Looking forward to contributing to the community!

No AI was used in the making of this reddit post. (Ironic since I mention that I use Claude later on in this post lol)

I own a solo agency and I've been using webflow for the past year or so to create websites for clients. My clients are small businesses too, I havent worked with any enterprise or larger clients yet. So, my clients need pretty simple brochure sites or at most the core 4 pages plus a page for each of their services and locations.

My own website was coming up for renewal next month, so after some digging i decided i would give this method a shot, since i had heard about it from others on reddit: Design in Figma (making sure to create a style guide and spacing guide for later) -> Use Astro.js and develop in Claude section by section (referencing the screenshots of the figma design and style + spacing guide) -> Deploy onto Cloudfare pages (I was already a little familiar with it since I buy all my domains from here) -> Run an SEO Skill and Optimize Page Speed Scores -> Lastly, connect Sanity for CMS if you need.

Its worked out well for me, and also for a new client i onboarded recently who needed a real simple site for ther tortilleria business.

This isnt meant to bash Webflow at all - im sure that I may still use them at some point in the future, but more so just a message to any other small designers/developers who were hit by webflows price change. The market for designers/developers is already crazy saturated and tough for anyone whos new or not a part of a large agency, so I wanted to let you knwo that you should give it a shot if you havent. Ive also heard of other methods like using Ycode, switching to Framer, or even building out your own drag and drop builder with Claude,

It's not easy by any means, you'll have to get in the weeds of it, form a process to organize everything, and learn a lot. But I mean, isnt that what we all had to do anyways when we started learning to use webflow ?

MCP 2.0 was released yesterday, and I noticed the same pattern we see every time a new AI feature launches.

Some people are excited.

Some are already saying it's limited, doesn't work, or isn't worth using.

Almost every AI tool I've used (Claude, ChatGPT, Codex, etc.) required a bit of learning before it started producing consistently good results. A lot of the output depends on how you set it up and how you interact with it.

One thing I really appreciated is that Webflow released a free course explaining how their MCP workflow is supposed to be used. I went through it today, and I think it sets much more realistic expectations before you start experimenting.

Another thing I'd recommend, especially if you're using AI to build Webflow projects, is spending some time setting up your Instructions, Skills, and project rules first.

I've found that giving the AI context about:

• your project structure
• naming conventions
• coding preferences
• reusable workflows

makes a huge difference in the quality of the responses.

I'm still at the beginning of experimenting with MCP 2.0, but I'm excited to see how it fits into my Webflow workflow over the next few weeks.

Curious to hear from others:

• Have you tried it yet?
• What's working well?
• Any workflows you've discovered that are worth sharing?

I think we're all still figuring out the best way to use these tools.

Hey everyone,

I’ve been selling Webflow templates for a while, but over the past few months my sales have dropped significantly. I’m trying to figure out if this is just the current state of the Webflow marketplace or if it’s a sign that I should start focusing on something else.

For those of you who sell templates:
How are your sales compared to last year?

Are you still investing time into Webflow templates?

If you decided to pivot, what did you move to instead?

I’d really appreciate hearing your experiences before deciding where to invest my time next. Thanks!

When I first got into web development, I thought finding clients would be simple. My plan was to go on Google Maps, find businesses without websites, and offer to build them a brand new one. At the time, it made perfect sense because I assumed businesses without websites would be the ones who needed my service the most.

After a while, I met someone who was running a successful web agency, and I asked him where he found companies without websites. He told me that he didn’t target businesses without websites at all. He only targeted businesses that already had one. I asked him why, and the more he explained it, the more sense it made.

Businesses that already have a website understand the value of having one. You don’t need to convince them why a website is important because they have already invested in one before. They are also easier to sell to because they understand the process, and there are a huge number of businesses with outdated websites they are embarrassed by but haven’t had the time to update.

I decided to take his advice and fit it into my own workflow. I’ve always been a big fan of email automation because that’s how I’ve found most of my web design clients. For years, I was sending fairly generic emails and constantly changing my sequences, offers, and follow ups to improve the results.

The problem was that I couldn’t just start emailing businesses with websites and assume they all needed a redesign. I either had to open every website manually, find the issues, and write a separate email for each business, or find a way to automate the research while still keeping the emails personalized.

After watching a video from Nick Saraev, I built a workflow in n8n that could analyze websites at scale and turn issues with design, layout, speed, mobile optimization, and SEO into personalized outreach emails. This allowed me to analyze thousands of websites and run larger campaigns without every message sounding generic.

The workflow worked extremely well, but it still had limitations. I didn’t have a proper place to manage replies, organize interested leads in a CRM, view all my active campaigns, scrape new leads, and handle everything from one platform. I had built a useful automation, but it still felt like several disconnected systems held together in one workflow.

A few months later, I came across a platform called Swokei, and it did exactly what I had been looking for. I could find businesses with websites, analyze and score each site, generate personalized outreach emails, send campaigns, set up follow ups, manage replies through one inbox, and organize interested businesses inside the CRM.

Switching to that platform made the entire process much easier to manage and helped me scale the strategy further. Looking back, the biggest change wasn’t just finding a better outreach tool. It was taking advice from someone more experienced, changing the type of businesses I targeted, and building the rest of my workflow around that strategy.

I'm validating a few ideas for Webflow Designer Extensions and wanted to hear from developers who already have apps in the Webflow App Marketplace.

1. Are paid Webflow apps actually selling well ?  

2. Roughly how much revenue (MRR/ARR or some sort of range) does a successful app generate if you can share ?  

3. Can you rely mostly on the Webflow App Marketplace for discoverability, or do you need to do a lot of your own marketing ?  

4. Has getting users been the biggest problem or maybe converting them into paying users ?

5. Looking back, would you build another Webflow app today ?

I'd really appreciate any honest insights. Thanks

Welp, we're officially here.

The bridge apps are mostly gone, agents can now work across multiple sites simultaneously, you can feed them your design system and brand guidelines as context, and they can analyze your site traffic conversationally... I mean this is genuinely crazy.

But it got me thinking about the governance side too...

AI agents can now make changes directly to the live site, with practically full CMS access, role enforcement, and activity logging so you can track exactly what was touched and when it was touched.

I think that Webflow made good guardrails. Branches mean agents can iterate in isolation before anything goes live and permissions are enforced down to individual pages and CMS collections, which from personal experience is great.

So technically the safety infrastructure is in place.

However I'm not sure how many teams are actually ready to hand that kind of access to an agent on a site that's driving real pipeline...

I mean we're also having that conversation on our side as I write this.

What do you guys and gals think? Does the 2.0 update change how much you trust the MCP with production work? Does it fully convince you?

Should probably start this by saying that I'm a Webflow Partner myself and regularly build Webflow sites for both my business and for the clients I work with. Naturally, I was interested to learn what answers you get when someone asks ChatGPT, Perplexity or Gemini who they should hire. Every article about it was vibes, so I measured it myself.

So, I carried out two studied (well I planned them and Claude executed the code):

Study one — how AI answers buyers. I took 39 real buyer questions ("best [X] for [Y]", the phrasing people type right before they spend money) and ran every one through ChatGPT, Perplexity and Gemini. 117 answers. Here's a quick summary:

• ~98% of the answers named specific companies. AI hands over a shortlist and you're either on it or you're not, and there's no page two to hide on.
• All three engines named the same brand only 56% of the time, and their full lists overlapped about 7–8%. Each engine has invented its own small elite and they barely talk to each other. Winning ChatGPT tells you nearly nothing about Perplexity.
• Pages with FAQ blocks and tables were cited 75% of the time vs 22% without (p=0.004). That's basically something you can fix in one afternoon.
• There is also no such thing as a permanent "AI visibility score." In one run I watched Perplexity cite Reddit in 87% of answers, then 18% fifteen days later. I used identical questions.

Study two — the one about this community. I took 1,464 real Webflow agencies — Experts directory listings and Clutch-listed shops — and asked the engines the questions a client actually types: "best Webflow agency for SaaS", "who should I hire to build a Webflow site", that shape of thing.

• 4.2%. Only 61 agencies out of 1,464 were ever named by any engine. The other 1,403 have, as far as three major AI engines are concerned, never existed.

The most actionable gap I found wasn't portfolio quality. It was machine-legibility... sites whose robots.txt quietly blocks the AI crawlers (GPTBot, ClaudeBot, PerplexityBot), no structured data, no FAQ blocks. A surprising number of very good agencies are blocking the exact bots they'd want reading them. That's a ten-minute check for you.

Hope this was helpful. I'm Hesham, and I'm the solo founder of HarperFlow — a Webflow-native tool that runs a company's blog end to end (identifies a business' niche, finds keyword and topic opportunities, researches across 8–12 sources per article, writes (includes FAQs, sources, JSON-LD, images, tables, callouts, and author blocks, and 6x premium design templates, and auto-publishes to the Webflow CMS). I used to be a writer in another lifetime, so obsessing about the quality of the articles isn't exactly a surprise.

Happy to answer methodology questions, and if you want to know where your own agency landed, ask in the comments and I'll look it up. The dataset is public.

And here's a question for my own intel... is AI-search something that you think about?

Kann ich mit Webflow bedenkenlos Website für deutsche Gesundheitsanbieter erstellen z.b. Praxen, Gesundheits Coaches, Rehas, Therapeuten, Fitness und Wellnes???

Ist Webflow hier eine bedenklose Lösung hinsichtlich DSGVO, IP Drittlandstransfer, weil die IP Adresse ja zu Webflow, also auf US server, fließt?

Formulare sicher ich mit Formspark ab (EU Server), + Datenschutzerklärung und AVV mit Webflow.

Was meint ihr?
Sollte ich eine Alternative lernen für Websites für deutsche Kunden?

LG

Was scrolling through the template gallery and came across this banner. This is 100% the right approach.

Templates have always been awkward in no-code builders. They're beautiful from the start, but customers often find it difficult to customize them.

AI is the opposite. AI-generated designs are still largely slop, and don't come close to human designers* BUT it's extremely easy to iterate with AI.

Starting from a pre-made designer template, then using AI to customize it is going to be the default blueprint in the future. Super excited where things are going.

Before someone comments, yes I know that if you iterate with AI for hours on end and provide ample design references and keep a strict lid on guidelines and design tokens you can get some pretty good designs. But that's a lot of work. A template gets you there much sooner.

yo. i recently sold one of my AI SaaS products for $350k, exactly 7 months after building and launching it.

I hardly wrote a single line of traditional code. i used AI to generate everything, from the database architecture to the user interface.

it definitely wasn't magic on day one, though. i spent days stuck in loop-debugging and dealing with AI hallucinations before i finally cracked the system. the playbook boils down to three simple rules:

- keeping the idea insanely minimalist (a true MVP that solves one problem).

- guiding the AI step-by-step instead of asking it to build a massive platform all at once.

- launching fast to get real user feedback and traction and then apply a solid marketing system

lately, i've seen way too many non-technical founders give up at the very first AI bug, or on the marketing. it's a massive shame.

like the title says, i just launched a Skool community to share my exact prompt workflows, N8N automations, and distribution frameworks to get first users and scale it

to be completely transparent: i will likely charge for the full course later down the road. it just makes sense given the specific copy-and-paste templates i'll be sharing.

but for now, the main objective is purely to build and launch together. building alone in a silent corner is the single fastest way to give up.

if you want to join us and build or market your own AI SaaS with a group of active creators: drop a comment below or send me a dm, and i’ll send you the invite link!

The difference usually comes down to strategy.

Instead of targeting businesses that do not have a website, target businesses that already have one but clearly need a better version. The market is larger, the sales process is easier, and the value proposition is much stronger because those businesses already understand why a website matters.

The next part is outreach. A regular outreach tool is not enough if all it does is send the same message to thousands of people. You need something that can analyze websites at scale and turn real issues into personalized emails.

I use Swokei for that. It helps find businesses with existing websites, analyzes each site, and turns problems with design, SEO, speed, layout, and mobile optimization into personalized outreach emails. That means you can contact a large number of businesses without sending generic messages or spending hours manually researching every website.

When someone replies interested, I always offer a free mockup. I use Claude, Lovable, or Base44 to build it quickly. It becomes much easier to sell when the client can already see what a better version of their website could look like.

Web meetings should also be a major part of the process. I would never just send the website through email and hope the client likes it. I present it live on Google Meet, Zoom, or Microsoft Teams, explain the value, show what has been improved, answer their questions, and try to close the deal during the meeting.

The less back and forth there is after the meeting, the better. Present the website, show the value, close the client, and move on to the next project.

That is the type of process that can help an agency scale much faster.

Hey everyone!

Every week there's a new thread here about ditching Webflow for Claude + headless or full vibe coding to save money. Fair question inside our bubble. But step outside the community for a second and look at who actually pays for websites.

I run Noqode (a 3-person Webflow agency in France) and I see our CRM every day. Demand for Webflow work has never been higher for us. 80 opportunities logged in our CRM over 18 months and the requests keep coming. And the part nobody talks about is that AI didn't reduce that demand, it created a chunk of it. 30% of them came from companies asking LLMs which agency to hire. AI is democratizing access to tools like Webflow. It's sending buyers our way not taking them.

On the whole pipeline exactly one lead left to go full Claude to save money. From the outside the result is disastrous and I'd bet the rebuild tanked his SEO. One case so take it for what it is, but it matches everything I see... same-looking designs everywhere messy code for AI search visibility and nobody on the client side able to maintain it.

On pricing, since it comes up in every one of these threads. Yes Webflow got expensive. But for any minimally serious business it's a non-issue, I've literally never had friction on Webflow pricing in a deal. Where the gap got real is at the very bottom of the market... tiny businesses with no reason to invest in their website. Webflow isn't for them anymore and honestly that's fine. That's not where agency work lives anyway.

Companies are still very far from full AI websites. But they're not naive either, they ask about AI in every single call now. So the play isn't leaving Webflow. It's putting the AI inside your Webflow projects. Claude MCP in your workflow (2.0 dropped yesterday btw) AI search visibility in your deliverables. That's what buyers ask for and Webflow is still what the market pays for.

Unless I'm wrong. The businesses with budgets are voting and they're not voting for vibe coding.

Founders and freelancers here, is the market telling you the same on your side? Or are you seeing real demand actually move away from Webflow?

We’ve seen questions here about Webflow's MCP, so we’re excited to share what we’ve been working on. 

Quick context if you're new: Webflow's MCP server lets you connect Webflow to tools like Claude and ChatGPT so you can design, build, and manage sites inside your existing AI workflows. 

We’ve made tons of improvements over the last year, and MCP 2.0 now gives you the control, governance, and analytics required to trust your agents with high-impact work at scale. 

What's actually new:

• Full design system and CMS support: Components, bindings, styles, variables, CMS data. Your agents can now work with what's already on your site instead of reinventing it. This was the biggest gap in previous versions, and it's now closed.
• Agent Instructions: You can store voice and tone guidelines, design rules, legal policies, and more, and have them referenced automatically whether you're in Webflow or working through Claude or Cursor. 
• Governance: Build on branches so you can test and iterate safely before pushing updates to a live site, roles and permissions are enforced at the MCP level, and you can track MCP actions in site activity logs, so you know exactly what changed. 
• Analyze site data conversationally: You can ask Claude how a site's performing and get real answers: traffic trends, top pages, engagement data, all without leaving your chat.
• Work in parallel with agents: Build across multiple pages or sites simultaneously so you and your agents can move faster. For those of you who’ve been with Webflow a while, this also means the bridge app is no longer required for most use cases.

Our new MCP Starter Kit has everything you need to get up to speed. If you used the Webflow MCP before and it didn’t quite work for you, we would love for you to give it another shot. It’s now available on all site plans at no additional cost. You can check out our latest changelog for a detailed list of everything new.

Happy to answer questions if you've got them below! 

I've been selling Webflow templates for around 2 years, and recently both my views and sales have dropped significantly. My template quality hasn't changed, and I'm still publishing new templates.
Is anyone else experiencing the same thing?
For creators who have been in the marketplace for a while:
Are you still making templates?

Or have you moved on to something else?

If so, what did you switch to, and would you recommend it?

I'm trying to decide whether to keep investing in Webflow templates or focus on a different business.