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!

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

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?

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?

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?

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.

I’ve been in contact with a lot of web agencies and web developers, and I personally haven’t found many people who run their agency in a more efficient way than I do. A lot of them have too many meetings, wait too long for client approval, don’t know how to price projects, and spend way too much time on each client instead of finishing the work and moving on to the next one.

I’ve been running my agency for four years, and after a lot of trial and error, I’ve managed to make the process as efficient as possible. I wanted to share some of the steps because I think they could be valuable for anyone just starting out.

Running a web agency alone or with a partner isn’t easy because there are a lot of things to take care of. When it comes to client acquisition, I recommend focusing on either cold calling or email automation. Which one you choose depends on whether you run the agency alone or with someone else.

If you have a partner, one person can handle sales while the other focuses on building websites, connecting domains, setting up emails, and taking care of the technical work. If you’re running the agency alone, or neither of you enjoys cold calling, I highly recommend email automation.

That’s what I’ve been doing for years. It’s powerful because you can send emails at scale, set up automatic follow ups, and wait for businesses interested in a new website to reply. While you’re working on one client, another opportunity can come in without you having to stop everything and search manually.

I don’t do regular email automation where I target businesses with no website. I do the opposite and target businesses that already have one.

I use a tool called Swokei to find businesses with websites, add them to campaigns, analyze each site, score it, and generate personalized outreach emails based on problems it finds with the design, layout, speed, SEO, and mobile optimization.I schedule the campaign, set up follow ups, and wait. 

I think this approach is much better for a few reasons. You’re targeting someone who already understands the value of having a website. You’re also not just asking whether they need a redesign. You’re pointing out real problems with their current site, which makes it clear that you actually took the time to look at it. Selling also becomes easier because they’ve already paid for a website before and understand the process.

Inside Swokei, you can choose the goal of the campaign. You can offer a free draft, try to book a meeting, or simply start a conversation. I always choose the free draft because that has worked best for me.

Once you’ve figured out how to get clients, the next part is building the website. I recommend using AI because it makes the process much faster. For anyone who still thinks AI can’t build great websites, I think they’re mistaken. You can use Claude, Base44, Lovable, or any other tool that works for you.

When someone replies interested, I call them and say, “Hey, I saw that you replied to my email. I’ve already built you a free draft of your website. Do you want to take a look?”

Then I invite them to a Google Meet.

At that point, it becomes much harder for them to reject the meeting because they already replied interested and now know you’ve built something for them. During the meeting, I present the website, explain why it’s better than their current one, stack the value, answer their questions, and try to close the deal.

These meetings usually go well because the client isn’t trying to imagine what the website might look like. They can already see a better version of their current site. They also took the time to join the meeting, so taking the next step becomes much easier.

I either take payment during the meeting or send them a contract to sign. Any changes and updates come after that, once we already have a deal in place.

Pricing depends on the business. I charge anywhere from $500 to $3,000 depending on the company, the size of the project, and how much value the website can bring them. I also charge a monthly retainer of around $50 for hosting, maintenance, support, SEO, and future changes.

That’s basically the entire process. Smaller steps, faster delivery, less wasted time, and more money made.

I enabled Microsoft Clarity's new AI Visibility feature on our website last week, and I'm surprised it's completely free.

To get the most out of it, I connected:

• Microsoft Clarity
• Cloudflare (AI Bot Activity)
• Webflow

Now I'm able to see things like:

• When our content is referenced in AI-generated answers
• Which pages AI platforms are discovering
• The prompts people are using to find our content
• Which AI bots are crawling the site and what they're accessing

We've been using Microsoft Clarity on our Webflow projects for years because it's free and provides great insights through heatmaps, session recordings, click tracking, and scroll depth.

The AI Visibility feature makes it even more interesting, especially if you're trying to understand how AI search engines interact with your website.

I'm planning to let it run for a few weeks to collect some meaningful data.

Has anyone else started using it yet?

I'm curious whether you've noticed anything surprising in the AI Visibility reports or if you're using a different tool to track AI traffic.

Hey all,

Trying to figure out the quickest way to build a Webflow site from scratch using AI. Not interested in templates or cloneables — I want an original build.

For those who've actually done this:

• Any AI tools that output actual Webflow-native stuff, or is it all mockups you end up rebuilding anyway?
• Anyone used UXMagic, Relume or Figma-to-Webflow in a real project? Was it actually faster or just more cleanup?
• Does AI help at all with CMS, interactions, or responsiveness — or just copy and layout ideas?

If you had to ship a custom Webflow site fast today, what would your exact workflow be? Real experiences > tool lists.

I’ve been doing Webflow work for 3+ years and I keep going back and forth on how much AI actually belongs in my process. I use it for some things (copy drafts, custom code snippets, debugging) and it genuinely saves time there. For actual building inside the Designer, I’m slower with it than without it.

Curious how experienced devs handle this. Do you trust it with client work? Where does it actually make you faster and where does it just create cleanup work? And what does your flow look like in practice, like do you generate custom code with it, plan CMS structures, write interactions?

Not looking for hot takes on whether AI will replace us. Just genuinely curious what’s working for people who’ve been doing this a while and if you managed to speed up your process without delivering AI slop to clients.

Hi all, Milos (SEO guy) from Broworks here. Need to vent a bit and also ask if anyone has actually solved this.

I've spent days literally on this. GSC keeps flagging some of our pages as "Page with redirect" in the coverage report. Nothing broken, checked everything I could think of, and every single tool I use (Screaming Frog, manual checks, you name it) says the page is fine. Even the Live Test inside GSC itself shows a green result.

So why is the coverage report still showing it as an issue?

I read a bunch of threads, watched videos, and tried different things, and honestly, most of the answers say "wait for Google to recrawl" or "check your redirects," which I already did. It's frustrating when you're doing everything right, and the tool still won't clear the flag.

We're on Webflow, so I'm going to double-check the canonical URL setup next, since I've heard GSC can misread the canonicals sometimes (but at this point I'm not even sure that's the real issue).

Has anyone actually fixed this, or found out why it happens? Is this just a GSC reporting delay thing, or is there something deeper I'm missing?

I'm trying to understand this properly instead of guessing, so wanted to ask people who've actually built and handed off sites.

For those of you who've built and handed off sites to non-technical teams:

• What's the difference, in practice, between a site a marketer can actually run themselves and one where they're stuck waiting on a dev for everything?
• Is it mostly a CMS/content-modeling thing, a components/class-structure thing, a permissions thing, or something else entirely?
• Have you ever handed off a site that you thought was well-built, only to find out later the client still couldn't do anything with it? What was actually missing?
• On the flip side — any handoffs that went really well? What did you do differently?
• Do clients ever ask for this upfront ("we need our team to be able to build pages themselves"), or is it always something that surfaces later as a complaint?

I'm trying to map out what separates a "looks good" build from a "the team can actually run this" build, from people who've seen it play out more than once.

Hallo ich brauche eure Hilfe. Ich entwickel ausschließlich mit Webflow. Einige Stellen konnte ich bereits von US Bezug trennen, wie Formulare und Analytics.

Was bleibt ist z.b. das IP Problem, die ins Drittland fließt. Wie könnte ich das lösen, wenn ich mit Webflow CMS Plänen arbeite und nicht mit teuren Enterprise Plänen ?

Ich bin kein Deeper Dev, um Setups zu bauen die Wartung und IT Erfahrung brauchen…

Beste Grüße

There is a new approach I started using in my web agency that completely changed my results. For years, I did what most people tell web designers to do. Go on Google Maps, find businesses without websites, and contact them.

What I started doing differently was targeting businesses that already had websites.

The reason is simple. If a business already has a website, it means they understand the value of having one. You do not need to convince them why a website matters because they have already paid for one before. The market for businesses with outdated, broken, slow, or poorly designed websites is also massive, and selling becomes much easier because they are already familiar with the process.

My biggest issue was figuring out how to send mass outreach to these businesses without sounding generic. I did not want to send thousands of emails saying, “Hey, your website needs a redesign,” and just assume that every business needed one. I wanted to send emails at scale while still telling each company exactly what was wrong with their website.

A little over a year ago, I watched a YouTube video from Nick Saraev where he built a workflow that analyzed business websites and turned issues with design, SEO, layout, speed, and mobile optimization into personalized outreach emails. Each company received a professional email that made it clear someone had actually taken a look at their website.

The idea was great, but building and maintaining the workflow took a lot of time. I still had to find the leads myself, the messages were not always consistent, and the automation kept breaking.

But it worked.

I was getting more clients than ever before, at one point around 10 websites a week, while my business partner focused on building the websites as quickly as possible.

I started searching online for a tool that could do everything in one place, and a few months later I found Swokei. It did exactly what I was looking for.

It lets you find businesses with websites, add them to campaigns, analyze and score each website, and set a quality threshold so websites that do not need fixing are automatically skipped. It then turns problems with design, layout, speed, mobile optimization, and SEO into personalized outreach emails.

You can also set up follow ups, manage replies through your own inbox, and organize leads inside the CRM without moving between five different tools.

I switched over and scaled even harder.

Sometimes the fastest way to grow your agency is not building every workflow from scratch. It is finding the right tools and using your time to focus on sales, clients, and growing the business.

Chekout one of our most selling Agency webflow template https://webflow.com/templates/html/minimaagenci-agency-website-template

Tried Shopify and honestly got overwhelmed pretty fasttt. For people who aren’t super technical, what are u using to build your ecommerce stores?

Is there anything simpler solution than shopify?

This community is specifically for webflow developers.

Whether you have any query or you are stuck in any issue, just share your problem and we'll help you figure out

Sonio is an AI-powered prenatal diagnostic platform, now part of the Samsung group. They needed to migrate away from WordPress urgently, 2 month deadline, strict corporate validation requirements, and zero tolerance for SEO drop or brand inconsistency.

The constraints were real: keep the existing design (no time for a full rebrand), clean up years of accumulated visual inconsistencies from WordPress, and protect every Google signal during the migration.

What we built: 100% component-based architecture in Webflow so their marketing team can build new pages without touching a developer. Full redirect mapping based on their existing impressions and backlinks. JSON-LD structured data for AI search engines (ChatGPT, Perplexity, Gemini). And a Webflow training session so they could manage the CMS themselves post-launch.

Result: 0% SEO loss, delivered in 60 days, for a Samsung subsidiary with enterprise-level validation requirements.

Happy to answer questions on the migration process 👀