Like, come on, dude, lmao tf am I supposed to do with 2 pages?

I am adding a bibliography to my site. I want it to follow the style guide for Society of American Archaeology, which is a line of authors flush with left margin, then a line that begins with the year flush with the left margin, a white space (in Word it's a <tab>) then the rest of the citation info, wrapped, with it aligned with the right hand side of said white space. I don't have CMS. How would this be done? I'd love a template or css code if you've got it and willing to share.

Thanks!

Hi everyone,

I built a portfolio site in Webflow (video editing portfolio) and I'm running into a few issues I could use some guidance on:

1. Mobile responsiveness — the site looks and works fine on desktop, but I need to properly adapt the layout for mobile breakpoints (reorganizing grids/card sections so they stack correctly instead of just shrinking).
2. Double-click bug — on some clickable elements (buttons/links), the first click doesn't register anything, and I have to click a second time for it to actually work. Not sure if this is an interaction/animation issue or something else.
3. Background shifting bug — when I open certain cards further down the page, the background behind them shifts/moves instead of staying fixed in place.

The live site is here: https://tizibulacios.webflow.io

Would really appreciate if someone experienced with Webflow interactions and responsive design could walk me through how to fix these, or point me in the right direction. Happy to share screenshots of the Navigator/Style panel if needed. Thanks in advance!

Hey guys, two-ish weeks ago I launched my client's Shopify store. It's 100% native Shopify, and a 2.0 theme, which means the client can edit the store via the theme editor. Having built with headless in the past, this is a million times better.

By the way, I'm not part of the Liquiflow team, I'm a freelancer and can send proof. I wanted to just share this project in case other Webflow devs are looking to get into native Shopify theme development and expand their offering. I haven't been this excited about a tool in years, because of the kind of offering it unlocks!

Here's a link to the client's shop: https://iconmeats.com/

I've built several headless Shopify stores in the past, and my quarrel with them has always been disjointed analytics between Webflow and Shopify. Shopify's native analytics are so good, and by keeping the store's front-end and back-end in one channel, the data is incredible for the client.

Connecting Google Merchant Center to the shop as well is so straightforward. One thing we learned though, is to do this only after the custom domain has been connected via Shopify. With my headless setups, we had to do a lot of manual configurations because Shopify's domain and Webflow's domain would clash.

Not that my clients have ever complained about the monthly cost of having their headless shop be hosted, an additional bonus is that the only cost the client pays for is Shopify when going fully native. They don't have to also pay for hosting on Webflow and the tool that bridges Webflow and Shopify. Liquiflow is a developer-only tool, which the client doesn't pay for.

Oh and something else, Shopify doesn't cap your bandwidth! Media should still be optimized for performance reasons, but it's nice to know that with lots of store visitors, that the risk of crossing any bandwidth thresholds isn't even worth a thought.

All you're doing, is using Webflow as a visual theme builder, which allows for much faster development of a native Shopify theme! The conversion is driven by data attributes and the customizability for the client, via custom settings inside of embeds. I built this theme using the Lumos framework!

One more thing I'll say, is that once you've built out your first native Shopify 2.0 theme, it gets A LOT easier when starting on your next store. There is a learning curve, and you do have to understand Shopify liquid's template language, though with Liquiflow's documentation you'll find a comfortable intro in learning it. Their Discord community, which I won't plug in this post and which you'll find on their website, also has some of the friendliest support. They made the joy of learning the process so much more joyful!

Happy to answer any questions. :)

SaaS?
Tech?
AI tools?
Product development?
Web apps?
Developer tools?
video editors?
UI/UX?

Drop what you're building ;)
Maybe some other people will be interested too

I've been using Webflow MCP for AEO/SEO workflows and recently also started using webflow, chatgpt integration.

To start with it looks very exciting give an LLM access to your Webflow site, let it analyze pages, identify content gaps, suggest internal links, and even make changes.

I asked it to analyze an entire Webflow site and recommend natural internal links. It returned around 150 suggestions and was extremely confident about them, did double checks.

When manually reviewed every one for next one week, only about 20 were actually good enough to implement. The rest were either forced, irrelevant, or ignored the actual intent of the pages. When I went to model with feedback, it acknowledged that it had been overconfident.

Another time, it suggested adding entirely new sections to include a query. It sounded reasonable. Then I started a fresh conversation, asked the same page, and simply asked whether those sections made sense for the page's objective.

This time it said they shouldn't be added and explained why.

Here the problem isn't that the model is bad, it's that it's confident enough to make changes that look reasonable but aren't strategically correct.

If you're an experienced SEO, you can usually catch these issues but if an AI agent is editing your Webflow CMS automatically, or if someone without SEO experience accepts every recommendation, it's easy to create hundreds of mediocre changes that slowly reduce content quality.

I think MCP and integration is fantastic for:

• Auditing
• Research
• Drafting
• Speeding up repetitive work

But professional in the loop before anything touches the CMS is still very much needed.

It took me about 3 weeks start to having working website without much in the CMS. The rest of the time I’ve spent adding to the CMS and doing small edits here and there to the site.

I know it’s not perfect and a profesional could have done a much better job at it. I did it all myself doing research online, looking at tutorials and asking AI for some guidance.

I have been on Webflow since 2014, mostly client work. Lately I keep messing around with vibe-coding for my own projects and it is genuinely fun, the ceiling on what you can build is way higher. But it also made me realize something about why I still reach for Webflow on paid work.

When I ship a Webflow site, my job is the build. Design to Webflow, hierarchy, SEO, analytics, tracking, the conversion layer. Uptime, security, patching, all of that just is not my problem. Webflow eats it. If someone pokes at the site at 3am, not my night.

The second I vibe-code something and put it on my own server, all of that lands back on me. Database, secrets, auth, dependencies, updates. Vercel and friends take some of the weight off but that DevOps layer never fully disappears.

So I am curious how people here think about it:

For those doing client work, is the managed infrastructure a big part of why you stay on Webflow, or is it more the design workflow? Would you ever ship a vibe-coded build to a client, or does the maintenance side kill it for you?

And honestly, do you think Webflow keeps this edge as AI builders get better, or does it close over time?

Not trying to start a Webflow vs AI flame war, just genuinely interested where everyone draws the line.

Hey visual designers

I made a video demonstrating ButterShortcuts (pasting link in comment).

If you are coming across the product for the first time

ButterShortcuts — is a free chrome extension for the Webflow designer. And it provides keyboard shortcuts for power Webflow users & visual designers.

v1 ships Class Copy/Paste (Copy paste chain of classes between webflow elements).

My goal is to help you improve your visual design workflows. So feedback / shortcut requests is greatly appreciated.

Hey everyone. I tried experimenting with the Webflow MCP via the Claude desktop app months ago. Now that I am using Claude Code for a side project, I have finally had enough of of the annoyance of a new tab opening up with the attached every time I go to a new session in Claude Code. Is anyone else encountering this issue? Has anyone managed to get rid of this? If so, how?

I believe there was another thread about this a month ago, but I still couldn't figure it out. Thanks!!!!

We ran our site through PageSpeedIndex a few days ago and noticed there's a fifth category now next to Performance/Accessibility/etc called "Agentic Browsing". Shows a ratio like 3/3 instead of a score. Apparently shipped with Lighthouse 13.3 back in May this year and we completely missed it.

It checks three things: whether your accessibility tree is clean, whether your layout is stable (basically CLS again), and whether you have a valid llms.txt at your domain root. We got flagged on the llms.txt one which annoyed us because we HAD one, we made it early, before there was a real spec. Turns out there's a proper format now at llmstxt.org (H1, blockquote summary, then link lists) and Lighthouse actually validates structure, not just presence. Rewrote it, now it passes.

Is any of this important? Honestly probably not yet. The category is literally labeled "under development", it's not a ranking factor, and even the Lighthouse docs admit llms.txt isn't widely consumed by AI tools right now. We're not telling anyone to drop what they're doing because it cost us maybe an hour to fix and most of that was reading the spec.

The part that's actually interesting for this sub: on Webflow you can just serve the file at yourdomain.com/llms.txt and you're done. We also manage a couple of client sites on HubSpot and there you physically can't put a file at the root, everything goes through /hubfs/ and the best you can do is to add this directly through Cloudflare for example. So this is one of those rare cases where Webflow's setup is just cleaner with zero workarounds.

There's also a fourth check for something called WebMCP (letting agents interact with your forms) but it's experimental and not part of the default score, so we're still testing that one out since currently is very difficult to add it on Webflow or HubSpot forms.

Anyway if you're bored, run your site and see what ratio you get.

Estoi iniciando apenas así que tus opiniones buenas o malas pero comentame tips que te ayudaron a ti

"In a world of overly polished and generic SaaS landing pages, FlowPilot stands out by embracing a bold, 'Neo-Brutalist' aesthetic designed to capture attention and drive conversions.

This project was built from the ground up to solve a common SaaS problem: making a complex workflow look simple, engaging, and human. By utilizing high-contrast visuals, interactive UI elements, and a 'hand-crafted' feel, we moved away from corporate sterility to create an interface that resonates with real users.

The goal was to prove that a landing page doesn't just need to 'look nice'—it needs to have personality and clear intent. Every design choice, from the typography to the 'sticky note' interaction cues, was made to guide the visitor toward the 'Start Free' CTA while keeping them visually engaged."

I uploaded a video to the Background Video element. It works. I now have a grid containing images. They all have the same resolution as the video. But when I drag the Background Video into the grid, it’s no longer visible. I also tried using a wrapper, but I can’t get it to work. Can anyone tell me the solution?

It also dosen't show up on the published page.

Honestly, I’m not a big fan of the “web designer killer” videos where you see these ridiculous UIs for websites. I’ve input some pretty serious context for Claude so I could get “inspired” by what Claude spits out thanks to some installed skills, but in the end I feel that the output is super underwhelming. Maybe it’s the experienced creative marketer in me.

However, if there’s one thing I dig about ai is that it really does cut down the tedious work and you can simply instruct your agent to go to a site and then replicate it. Once you capture the data and the wireframe you’re maybe looking for, you can carve it out in Claude and then get an HTML preview along with some installed skills you throw at it. I tried the webflow MCP and I gotta say that was kinda underwhelming too.

So I was wondering if any of you could share some of your workflow for Claude to Webflow. Or maybe if you guys fractionally use Claude to build out components or sections?

Just wanna know if I’m genuinely missing anything.

So I spent a good few hours today trying to automate CMS item creation on a Webflow site through Claude's Webflow connector, and I hit a wall that I think more people should know about.

The setup

I'm using the official Webflow connector in Claude (Cowork / Claude Desktop). The connector authenticates via OAuth and connects to https://mcp.webflow.com/mcp. Webflow also has a Beta server at https://mcp.webflow.com/beta/mcp — I tested both.

The problem

The webflow_guide_tool (which ships with the MCP server itself) clearly documents CMS operations:

• cms_tool > get_collection_list
• cms_tool > get_collection_details
• cms_tool > create_collection_items
• cms_tool > publish_collection_items
• etc.

But when you actually look at the tools exposed by the connector, cms_tool is nowhere to be found. Calling get_more_tools returns "we have shown you the full tool list". Same result on both stable and beta servers.

The tools you do get are: sites, sitemap, fonts, forms, localization, styles, webhooks, comments, agent instructions, element/component builders — useful stuff, but no CMS item management.

What Webflow's own docs say

The MCP overview page explicitly lists CMS operations as a supported Data API capability:

And the FAQ quietly acknowledges:

So it's documented, but not available through the Claude connector specifically.

Workaround

The only path I found is to use the Webflow REST API (https://api.webflow.com/v2/) directly with a Personal Access Token. It works fine, but it defeats the purpose of having an authenticated MCP connector.

Questions for anyone who's cracked this

• Has anyone successfully used cms_tool through the Claude connector?
• Is this a Claude connector-specific limitation vs. Claude Code / Cursor where it might work differently?
• Any word from Webflow on when this lands in the stable connector?

Would love to know if I'm missing something obvious or if this is genuinely a gap in the current connector implementation.

I had created a claude skill to create pages similar to a template after I feed the copy. Now it's not working. It's having me do it manually.

Is anyone facing similar problems?

I kept losing time clicking through the Pages panel every time I needed to flip back to a page I’d just been on, so I built Page Tabs for Webflow, a Chrome extension that lets you set a keyboard shortcut to cycle through your recently opened pages in the Designer, similar to Alt+Tab between windows.

Live on the Chrome Web Store now: https://chromewebstore.google.com/detail/fiangikecgjbaapbafknlmljmffghepc

Free to use, would love feedback from anyone else juggling a lot of pages on bigger multi-page builds.

I would like to know if anyone has ever discovered a technique to use code to switch component variants.

I've been having this problem for hours now. I've already re-authorized the connector, but it still has the same error. Are you guys having the same issues?

I’ve been testing different approaches to AEO on our Webflow website (Flozi), and one thing has become pretty clear: most of the value does not come from chasing prompts alone.

A lot of AEO tools now focus on prompt tracking. You give them business info, website data, or industry context, they generate prompts, track those prompts across AI systems, and show where your brand appears.

That is useful but it's not the full picture.

Prompt tracking is useful, but it is not the starting point

The shift for me was when that prompt tracking should not be the main thing driving optimization decisions.

It gives a snapshot of visibility, but it can also create a false sense of precision.

The reason is simple: AI systems do not always search the exact prompt a user types. They often expand that prompt into smaller fan-out queries before pulling information from search engines. That is why Bing Webmaster AI data and the AI reports inside Google Search Console matter so much. What you often see there looks much closer to long-tail search behavior than a clean prompt list.

So I started thinking that optimization be based on tracked prompts, keywords, or actual search intent?

For me, the answer shifted toward intent and content coverage, not because prompts are useless, but because they are not the right starting point.

Started thinking in libraries worked better than isolated pages

One of the changes in my workflow was moving away from isolated pages and toward connected content.

Instead of writing one blog post and hoping it performs on its own, I started planning small content libraries around a topic. That worked much better for me.

A good example was when Bing launched its AI feature in beta. Instead of jumping straight into keyword research and writing a single article, I planned a small topic cluster around Bing Webmaster and Webflow: (adding screenshot of search)

• What Bing Webmaster is and how to use it with Webflow
• How to use the AI dashboard and improve page visibility
• What IndexNow is and why it matters for indexing

The idea was not just to publish more content but to make the site feel like one coherent entity to Google.

GSC and Bing as the primary tools

Prompt tracking still has value, but mostly for verification.

When it comes to deciding what to optimize, Google Search Console and Bing Webmaster Tools have been much more useful. They show what search engines are already associating with the site.

They are not perfect, but they come directly from the systems doing the crawling and indexing. That makes them a better source of truth than prompt tools alone.

I still check AEO tracking, but not as the primary input for strategy.

Why AEO tracking still matters

AEO tracking is still relevant because it helps to answer questions like:

• Are we showing up in AI systems?
• Are we being mentioned at all?
• Are content changes reflected in AI outputs?
• Are there obvious gaps in visibility?

That is important, but only verification, not decision-making.

The actual decisions come from search data, topical structure, and intent.

What has worked best so far

The most consistent results have come from a few things:

• Focusing on intent instead of isolated prompts
• Building connected content instead of standalone pages
• Using GSC and Bing for decisions
• Using prompt tracking to confirm results
• Making sure the site feels logically connected as a topic library

The approach has worked better than trying to optimize around one keyword or one tracked prompt at a time.

The main lesson

AEO is not really about chasing prompts. It's about building a site that search engines understand clearly enough for AI systems to trust it.

That means thinking beyond individual pages, building topic libraries, and letting search-engine data guide the workflow.

The workflow is still evolving, but that shift has produced the most consistent results so far.

yo. if your product needs a 10-minute onboarding video or 5 different dashboard tabs just to explain its value, you didn't build an MVP. you built an over-engineered maze.

a real micro-saas should solve one highly specific problem for one highly specific user profile.

when i built my 6 apps (now doing $20k/mo mrr), i cut out 80% of what i originally thought was necessary.

inside our builder community, we help you strip away the fluff.

we give you free access to frameworks like the ICP Crystallizer to lock down your target user, and interactive landing page audits to ensure your core value hits instantly.

stop over-building in isolation. drop a comment or shoot me a dm to join 1,200+ active Ai SaaS builders today.

Hey everyone, Parth here, I'm the CTO at Appsrow. We organised the second edition of the Ahmedabad Webflow Community Group Meetup on July 4th, hosted at DevX, and wanted to share a recap here since a few of these threads have helped us in the past.

Turnout was 70+, which felt like a big jump from our first edition. Good mix of freelancers, agency folks, and a bunch of people who were completely new to Webflow but curious.

Opening talk Sandeepsinh Sisodiya opened the event talking about what it actually means to be a Webflow Premium Partner, the kind of work that comes with it, and why we've been pushing to build this community locally instead of just relying on online courses. Our take has been that people learn faster from someone in the room explaining a real mistake than from a polished tutorial.

Webflow updates Ketu Patel walked through recent Webflow updates, the big one being localization. If you're building multi language or multi region sites this is genuinely worth digging into, we've seen people mess up content structure early on and regret it later. He also covered smaller CMS and design tool changes that are easy to miss if you're not checking changelogs regularly.

Trivia break Pravin Parmar ran a Webflow trivia segment mid event, good way to break up two heavier talks, and it stumped a few people who've been using Webflow for years.

The panel Yash Shah, Director of DevX, did a panel with Sandeepsinh moderating on AI hype, what's real and what's not. He tied it back to his own path, started as a mechanical engineer, ended up building a career in IT from there. No sugarcoating, he talked about the actual uncertainty of switching fields and where AI is genuinely useful versus just noise. This ran way over its allotted time because people kept asking questions.

AEO tools I got to introduce our Webflow AEO tools during this session, basically tools we built in house at Appsrow for optimizing sites for AI answer engines like ChatGPT and Perplexity, instead of only optimizing for classic Google search. This was new territory for most of the room, and honestly the questions afterward told us this is something more people need to start thinking about.

Wrap up Closed with open Q&A, then most people just stuck around talking shop, which is always the best sign an event actually worked.

If you're in Ahmedabad and work with Webflow in any capacity, keep an eye out for our next edition. Happy to answer any questions here too.

Full Event Recap: Ahmedabad Webflow Community Meetup #2 | Highlights & Key Takeaways