I have a collection list with two conditions determining whether an item is displayed. When I apply each condition individually, the list of items displays as expected. Once I put both conditions on, everything gets wonky.

It is a list of names. When sorted in alphabetical order, the list only shows about 34 items. When sorted in reverse alphabetical order, the list shows about 41 names, but omits many of the names that had appeared the first time. Some names are appearing on both of the lists, so it's not like one scenario is excluding names the other is not. When I remove the sort completely, fewer names appear that what were there in either of the sort scenarios.

I have examined the spacing, overflow and any other filters and conditions and can't seem to find where I am going wrong. Any thoughts?

https://drive.google.com/file/d/1wTaZiGJbOfKG417yzPsHXxNb2KmvC0hc/view?usp=sharing

Could you please provide a digital copy of Webflow's current Form 6166 or an official address/tax certification document?

Thank you.

Every attempt fails with a generic "An internal error occurred", whether I'm creating a brand-new variable or updating an existing one, on both the production and beta MCP servers, and on multiple completely unrelated sites (so it doesn't seem to be project-specific). Reading a variable that already holds a custom value works fine — it's specifically writing one through the MCP that fails.

Has anyone else run into this? Curious whether it's a known issue, or if I'm missing something.

I'm subscribed to the Core workspace plan. When I want to build a new site I can't choose Webflow AI. All the settings are checked. Can anyone help?

Wesley

I recently paid for a Premium Site plan on Webflow. After payment, the project that was created was a blank site — and I can't find the AI Assistant anywhere on it. No icon in the right panel when I add a section, nothing in the sidebar either.

From what I've found, it seems the AI Assistant may currently only be available on sites created through the AI Site Builder flow, not blank sites, even if you're on a paid plan. If that's accurate, it wasn't made clear at the point of payment.

Appreciate support.

I'm hoping a Webflow staff member can help, since I haven't gotten anywhere through the standard channels.

The primary email on my account isn't mine — it was entered by mistake when the site was created, and I have no way to access or recover it. Because of that, I can't verify my email or reset my password through the normal flow, even though I'm still logged into my dashboard.

I've submitted a recovery request twice through the "Get Support" chat (each time it said "Your request has been submitted"), but nothing ever shows up under "My requests" and I've received no confirmation email. I also emailed info@webflow.com directly but I received an email saying this box isn't monitored.

I have an active paid Site plan and all the billing/verification details ready to share privately with support. Could someone from the Webflow team point me toward a working path to get this resolved, or confirm whether my email helped?

Thanks in advance — I really don't want to lose access to a site I've already paid for.

One thing clients ask for constantly that Webflow doesn't handle natively: live data tables they can update themselves.

They want their pricing table to reflect changes without contacting you. Their team directory to update when someone new joins. Their product list to sync from their inventory Sheet.

Every time, you either hardcode it or build a CMS workaround. Both break the moment the client touches anything.

Here's the third option I've been using:

1. Connect the client's Google Sheet to ZenTables

2. Style it to match their Webflow site

3. Drop one embed code into a Webflow Embed element

4. Walk away — client updates the Sheet, table updates automatically

Works for pricing tables, directories, listings, schedules — anything clients manage themselves.

If this fits your client workflow, ZenTables also has a partner program — 30% recurring commission on every client you refer. Details at zen-tables.com/partner

Free tier at zen-tables.com — worth trying on your next project.

What's your current workaround for live client data in Webflow? 👇

We’ve been building FormBridge (https://formbridge.ai) — a headless form platform designed for Webflow users who need more flexibility and power than traditional form builders.

Some of the features include:

• ✨ Conditional logic

• 🤖 AI-powered workflows

• 🔗 Webhooks & API integrations

• 📩 Advanced email notifications

• 📁 File uploads

• 🛡️ Spam protection

• ⚡ Fast, developer-friendly implementation

We’re looking for Webflow agencies, freelancers, and builders who’d like to try it and share honest feedback.

🎁 As a thank you, I’m happy to provide 3 months of FREE access to our Business Plan (all premium features included) for beta testers.

If you’re interested, just comment below or send me a DM, and I’ll get you set up.

We’re also open to feature requests and would love to build something that truly serves the Webflow community. Thanks in advance for your feedback! 💙

I am having trouble with some client quotes in a slideshow.

I would like to center the quotes vertically in the Container. For some reason, I can't figure out how to do that here. They stick to the top of the Container.

Thank you for reading my question, Webflow friends!

Michael

A solid discovery process saves time, reduces revisions, and helps everyone stay aligned throughout the project.

Here's the checklist we follow before starting any Webflow project.

1. Define the Primary Goal

Every website should have one clear objective.

Is it meant to:

• Generate leads?

• Sell products?

• Book consultations?

• Showcase a portfolio?

• Build brand credibility?

Without a clear goal, it's easy for the project to lose direction.

2. Understand the Target Audience

Before discussing layouts or animations, I always ask:

• Who is the ideal customer?

• What problems are they trying to solve?

• What information are they looking for?

• What action should they take on the website?

Understanding the audience influences every design and content decision.

3. Review Existing Assets

Before designing anything, I collect:

• Brand guidelines

• Logo files

• Color palette

• Typography

• Images and videos

• Marketing materials

• Existing website (if any)

Having everything ready upfront prevents delays later.

4. Create the Sitemap

One of the biggest mistakes I see is jumping straight into design.

Instead, I map out the site's structure first.

Typical pages include:

• Home

• About

• Services

• Case Studies

• Blog

• Careers

• Contact

A clear sitemap makes navigation much easier for users.

5. Plan the CMS Structure

Since Webflow's CMS is one of its biggest strengths, I define collections before building.

For example:

• Blog Posts

• Case Studies

• Team Members

• Testimonials

• Resources

• Careers

• FAQs

Planning this early avoids rebuilding sections later.

6. Discuss SEO Before Design

SEO shouldn't be added after launch.

At Appsrow, we define:

• Primary keywords

• Page hierarchy

• URL structure

• Meta titles

• Meta descriptions

• Heading structure

• Internal linking strategy

It's much easier to build with SEO in mind than retrofit it later.

7. Decide on Integrations

Before development starts, I confirm all required integrations.

Common ones include:

• HubSpot

• Salesforce

• Zapier

• Google Analytics

• Google Tag Manager

• Calendly

• Mailchimp

• Stripe

Knowing these requirements early prevents unexpected roadblocks.

8. Define the Design Direction

I ask clients to share websites they like and explain why.

Not to copy them, but to understand preferences around:

• Layout

• Colors

• Typography

• Animations

• Navigation

• Overall user experience

Visual references help avoid subjective feedback later.

9. Content Readiness

A great design can't compensate for missing content.

Before development begins, I check whether the client has:

• Website copy

• Images

• Team information

• Service descriptions

• Case studies

• Testimonials

• FAQs

If content isn't ready, we plan for it before moving too far into development.

10. Define Success Metrics

Finally, I ask one simple question:

How will we know this project is successful six months after launch?

The answer could be:

• More qualified leads

• Higher conversion rates

• Faster page speed

• Better SEO performance

• Increased organic traffic

• Improved brand perception

Having measurable goals keeps everyone focused on outcomes rather than opinions.

Final Thoughts

I've found that the best Webflow projects aren't necessarily the ones with the most impressive animations or interactions.

They're the ones that start with a clear plan.

At Appsrow, this checklist has helped us reduce revisions, improve communication, and deliver websites that align with our clients' business goals.

I'd love to hear how others approach new projects.

What's one question you always ask a client before starting a Webflow project?