I’ve been working on Upwork for several years and have completed around **200–300 web design projects**.

A good portion of those were concepts, personal projects, or templates that I created myself, so I own the rights to them. 

They include:  
Figma website designs  
Webflow websites  
Fully coded HTML/CSS/JS sites  
Landing pages and etc

Instead of letting them sit on my hard drive, I’d like to sell them to other designers, developers, agencies, or startup founders who could reuse or customize them.

Does anyone know:  
Are there marketplaces where I can sell these?  
Has anyone done something similar?  
Any advice on pricing or where buyers usually look?

I’d appreciate any recommendations or experiences. Thanks!

Solo dev here, mostly B2B SaaS websites on Webflow for clients. Lately I’ve noticed something, locking in a new client has gotten insanely hard. Haven’t felt this kind of struggle in the last 6-7 years.

Portfolio’s solid, case studies are there, I’m doing daily outreach, writing cover letters, sending DMs, all of it. Still not closing.

Is this because of the AI proposal flood everywhere now? Are budgets just tighter across the board? Or am I missing something on my end?

If you’ve been actively hunting for clients this past year, is your experience the same? Or are you still closing deals without this much friction?

Most AEO content recycles the same advice. Some of it is legit: direct answer at the top of the page, short snippet-ready paragraphs, FAQs on questions people actually ask. Some of it is theater, llms.txt being the poster child, sold as THE magic file when to this day almost no model demonstrably consumes it. But even the good advice on that list has a ceiling: it's a prerequisite, not a differentiator. I've seen technically flawless pages never get cited, and average pages get cited constantly. The difference sits somewhere else.

Here's the breakdown. Lever 1 makes you eligible. The other five are the actual game, and they're all facets of the same thing: becoming an entity the model recognizes in your niche.

1. Technical readability. An LLM bot is blind, it reads your code, not your design. Short sentences, clean HTML, structured data, sourced stats, light code. This makes your page readable and retrievable. It doesn't make it cited. If you're on Webflow, a decent chunk of this lever is handled for you, the generated HTML is clean and semantic out of the box. Which is exactly why technical readability alone won't set you apart: your competitors on the same stack have it too.

2. The humans behind the brand. A model is wary of a faceless brand. About pages with the actual team, author pages linked to real profiles, an active Google Business listing, real-life events relayed on your site. You signal a real entity instead of a ghost site. Heavily underrated.

3. Hyper-specialization. A site that talks about everything is a reference on nothing. Models cite sources they clearly associate with a topic. Being the recognized reference on one precise angle beats being the 50th generalist. This is the keystone, and the slowest to build.

4. Multichannel repurposing. One pillar piece turned into an article, a post, a video, a short. When a model runs into your name across several sources on the same topic, the repetition becomes an authority signal. You're not chasing one perfect page, you're building a consistent, repeated presence.

5. Comparison content. Models pull heavily from listicles and "best X" rankings to answer recommendation queries. Absent from that format, you're invisible across a whole category of prompts. And yes, a lot of those rankings are produced by players who place themselves well, worth knowing when you read them.

6. The sources models weight heavily. Some platforms are overrepresented in what LLMs cite: Reddit, YouTube, niche-specific media. Showing up there with real value often outweighs a classic backlink. Target media in your actual topic, not some off-subject outlet.

The through-line: technical makes you eligible, authority makes you cited. Most people overinvest in lever 1 and skip the other five, when the real game is becoming a recognized entity in your niche.

Curious how people actually working on this see it. Same hierarchy, or would you flip some of the levers?

I've spent the last 6 months running AEO experiments with Flozi. The goal wasn't to chase AI "hacks" but to understand what consistently helps Webflow pages get surfaced in Google AI, ChatGPT, and other answer engines.

Here are my observations and learnings:

1. SEO fundamentals matter more than ever but mostly as a prerequisite

Technical SEO isn't what gets you cited by AI, but it determines whether your content is even eligible.

If Google or Bing hasn't indexed your page, AI systems usually can't retrieve it through web search.

A simple test:

• Publish a page that isn't indexed.
• Ask ChatGPT (with web search enabled) about information only available on that page.
• In most cases, it won't find it.

2. Intent alignment mattered more than content formatting

One thing I kept checking was what Google actually thought each page was about.

For example, if I wrote a comparison page but Google classified it more like a "how-to" page (visible in GSC through the queries the page ranks for), I either waited for Google to re-evaluate it or adjusted the content so it better matched the intended search intent.

The better the intent matched, the easier it became for the page to gain visibility.

3. Competition still wins

This was probably the biggest lesson.

For one Webflow + Bing Webmaster topic, there was very little competition. After publishing, the page started appearing in Google AI and ChatGPT within about a week.

For broader AEO topics with dozens of established competitors, I've had far less success despite using the same writing process.

The opportunity wasn't "AI optimization."

It was finding topics where there was still room to become a strong source.

So what actually worked?

• Strong technical SEO so pages get indexed.
• Understanding what Google already recognizes each page for.
• Finding low-competition topical gaps.
• Building clusters around those gaps.
• Publishing genuinely useful content.

What didn't consistently move the needle

I tested most of the common AEO advice:

• Putting the answer in the first paragraph.
• Adding FAQ schema.
• Adding lots of tables.
• Breaking everything into small chunks.
• Writing every heading as a question.

None of these consistently helped on their own.

They can improve readability, but they didn't compensate for weak topical coverage or poor intent alignment.

Curious if others building Webflow sites have seen the same patterns, or if you've found something completely different.

We built a scraper that watches 12 freelance platforms simultaneously and tagged every Webflow job posted in last 1 month.

Most Webflow freelancers are competing on one platform when the work is spread across 12. Upwork has the most volume - but also the most competition by a wide margin.

The most interesting number in the table: FlowRemote. It's a Webflow-specific job board. Jobs posted there averaged 2 - 4 competing proposals. Same quality of client, same budgets - but almost no one is watching it.

Job type breakdown:

• Landing pages and marketing sites: ~38% of all jobs
• CMS builds: ~24%
• Webflow + Figma to Webflow: ~18%
• E-commerce (Webflow Commerce): ~11%
• Maintenance and updates: ~9%

Landing pages dominate on Freelancer[.]com and Fiverr. CMS and complex builds skew heavily toward Upwork, Contra, and the Partner channel. If you specialise in CMS or e-commerce, Upwork and Contra are genuinely the right pools - but the competition data still applies.

Where the best budgets actually are:

The highest average budgets weren't on Upwork. They came from two places most freelancers ignore: LinkedIn contract posts and Webflow Certified Partner leads.

Both channels have minimal competition for a simple reason - they require more effort to access and aren't surfaced in a feed most people check. But the clients posting there tend to know what they want, have allocated real budget, and aren't shopping for the cheapest option.

The speed problem:

This is the part that changed how we think about this. We timestamped every job and every close. The pattern across every platform:

Jobs posted in the morning filled faster than afternoon posts. The first proposal submitted within 30 minutes of posting had a materially better response rate than proposals submitted after 2 hours - even when the later proposal was objectively stronger.

On Upwork the cliff is steeper: once a job hit 20 proposals, response rate dropped sharply regardless of quality. The client is overwhelmed and starts defaulting to whoever showed up first or whoever is cheapest.

The implication: platform breadth matters less if you're always late. The freelancers winning consistently are the ones who see jobs fast across multiple platforms, not the ones with the best proposals.

Full data below. We ran this for 30 days in June 2026 across 12 platforms.

Sharing because we couldn't find this data anywhere else and figured the community would find it useful.

Three things we'd change if we were freelancing in Webflow right now:

First, add Contra and FlowRemote to your daily check. They have real budgets, real clients, and a fraction of the competition. There is no good reason these aren't in everyone's rotation already.

Second, get on the Webflow Partner program. The lead volume is small but the quality is unlike anything else on this list.

Third, stop optimising proposals on Upwork after the first hour. The data is pretty clear that hour one is the only hour that moves the needle there. If you missed it, move on.

Methodology:

Scraper checks each platform every 15 minutes. Jobs tagged "Webflow" as primary skill. Both fixed-price and hourly included. Budget ranges self-reported by clients so treat averages as directional. Proposal counts pulled at the 1-hour, 6-hour and 24-hour mark per job. Time-to-close defined as first hire confirmed or job removed.

This is one month of data so treat it as directional rather than definitive. We'll run it again next month and compare.

Not selling anything - we're building a tool in this space and this is the research we did for ourselves.

Happy to answer questions about the methodology.

Hi everyone

I am having this issue when open the website on iphone

Do you know how to get rid of it?

https://lumia-studio.webflow.io/

Own and run a video production agency, mainly into corporate films and Monthly content for Restaurants, I have a website on a webflow platform. Looking for someone who can develop the current website and automate lead generation. Please help!

I'm currently working on a project and I'm having issues figuring out how to make a component work.

The idea is that a back button only appears on the "news" page if you came from the "about" page. The goal would be that people who entered the news page from an external link do not see a back button, unless they used the "go to news page" from the about page.

Here's an example site: https://preview.webflow.com/preview/dynamic-button-example-dae24a?preview=0a3bc168c37d66cc58499b38b00ddcfb&workflow=preview

The back button only needs to go to the "about" page, not necessarily the browser history. Thank you for your help.

I wanted to share a few technical walls we ran into and the exact solutions we found. Not complaints. Just honest documentation of edge cases that took us longer than expected to solve.

1. No native range input

Webflow has no <input type="range"> element. If you want a slider, you're stuck with third-party libraries or workarounds.

Our fix: take a Custom Element, set its tag to input, add type="range" as a custom attribute, then target it with a data attribute from an HTML Embed script. Works perfectly — and since Webflow's style panel doesn't expose ::webkit-slider-thumb or ::webkit-slider-runnable-track, you style it in a <style> block inside the same embed.

input[type="range"][data-calculator-slider]::-webkit-slider-thumb {
  -webkit-appearance: none;
  width: 1.5rem;
  height: 1.rem;
  border-radius: 50%;
  background: #8e2ffa;
  border: 2px solid white;
  box-shadow: 0 0 0.5rem rgba(142, 47, 250, 0.5);
  cursor: pointer;
}

2. display: flex on a Rich Text breaks the layout with unexpected top/bottom spacing

When you put a Rich Text element in display: flex, you get a mysterious padding-like space at the top and bottom that you didn't add anywhere.

The reason: block elements inside Rich Text (<p>, <h2>, etc.) have default browser margins. In normal flow, those margins collapse between siblings. The moment you switch to display: flex, margin collapsing is disabled — the margins from the first and last children no longer get absorbed by the container, so they become visible as extra space.

Fix: target the first and last children of the Rich Text with custom CSS:

.your-rich-text > *:first-child { margin-top: 0; }
.your-rich-text > *:last-child  { margin-bottom: 0; }

None of these are Webflow dealbreakers — they all have clean solutions. But they're the kind of things that can cost you a few hours if you hit them blind.

— Rayane, Noqode

Client came in with a functional site that didn't match their product.

We rebuilt this from scratch in a month.

Added a custom Lottie hero + white-to-dark mode on scroll. Built in Webflow.

https://reddit.com/link/1ulknfx/video/da8dvwuaztah1/player

Feedback appreciated! :)

If someone is available today, I am stuck and need this project out the door. Will pay for your time.

Issue - I have built a modal following the very helpful Creative Designs Youtube video. 

This is the second time I’m doing it. The first was a success, so I copied that modal into a new page, created new combo classes, and edited the content and style.

When I click the button or image to open the modal, it opens at the middle of the page, much higher than the button, out of the screen view. All I get is the dark overlay, can’t see the form until I scroll up. The whole section is a centred flex box, and it look slike the popup is centred to the whole page, not opening in the screen view.

Can someone help me get the modal to open in the section, or at least in the view of the screen when clicking to open it. 

Designer link https://preview.webflow.com/preview/rewiring-aus?utm_medium=preview_link&utm_source=designer&utm_content=rewiring-aus&preview=dda8cfc1fffeefb685cb046f8f136e99&pageId=6a4332abba810b354321124c&locale=en&workflow=preview

Staging preview. https://rewiring-aus.webflow.io/get-involved/community-electrification-handbook

Context: a client asked me why ChatGPT never mentions their brand, even when they're clearly the best fit for the query. I didn't have a great answer, so I dug in.

Turns out ranking well on Google doesn't mean much to how AI engines decide what to cite. They crawl differently and evaluate trust signals separately — schema, crawler access, author/org info, content structure. A page can rank fine on Google and still never get cited by ChatGPT or Perplexity.

So I built a checker: paste a URL, get a score out of 100 across 5 areas —

• Crawlable — robots.txt, AI crawler access (GPTBot, ClaudeBot, PerplexityBot, etc.), sitemap
• Citable — content depth, FAQ structure, freshness
• Structured — schema markup, heading hierarchy, alt text
• Authoritative — internal/external linking, entity schema, llms.txt
• Verifiable — author identity, About/Contact pages, E-E-A-T signals

It also tells you exactly what's failing and how to fix it, not just a score.

I'm still actively finding edge cases and fixing them, so if you run it and something looks wrong or missing, I'd genuinely appreciate the feedback — happy to fix it.

https://www.thecssagency.com/tool/aeo-analyzer

I've agreed to help a friend do 4 pages on a Webflow project he has and I have spend hours stuck on just the first section of the first page, 1 of which I'm trying to figure out how to set up a gradient over an image.

Am I this stupid or is there a big learning curve? I'm a frontend developer for 5-6 years now and I thought these no code solutions would come easier to me because of it.

A little over a year ago I posted here about CartGenie when we were first launching. So I figured I’d share a quick update because we’ve crossed off a lot of those long-requested features recently!

For anyone who hasn't seen us before: CartGenie is a Webflow-native ecommerce/checkout platform. If you've ever hit the ceiling on what Webflow Ecommerce can actually do or gotten tired of stitching together third-party plugins via Shopify to cover the gaps... that's the itch we're scratching: End-to-end native Webflow stores!

We've had a big few months and wanted to share some of the bigger things that just landed:

Automatic Discounts — Discounts that apply on their own when a cart qualifies, no coupon code needed. Great for volume/bulk pricing, order thresholds, and B2B. If a customer does enter a code, that one wins. This was one of our most-requested features for ages.

Product Bundles — A real bundle product type. Group multiple catalog items into one listing with its own page, title, and price, while inventory, tax, and shipping still get handled per product underneath. Nice for "buy these three and save" without hacking it together on the front end.

https://preview.redd.it/utcr3i47wmah1.jpg?width=1500&format=pjpg&auto=webp&s=3725b78c5cba9839367f4b6d232e12a9b6d27a4f

Subscription upgrades — A lot here: a new order per renewal, different upfront vs. renewal pricing, variable intervals (every 3 weeks), expiration dates (monthly for 6 months), and more.

Swatches on CMS Lists – Since Webflow recently increased their nested CMS list limits, you can now feature all 3 option sets as swatches / buttons on your store pages!

https://preview.redd.it/9vvb3t5uwmah1.jpg?width=1200&format=pjpg&auto=webp&s=90b60667c4cee3d75a9e0d90c80a57a25a47331f

Pre-Orders — Accept orders before inventory lands. Clearly tagged front and back end, with shipping-timeline notifications. And if an order mixes pre-order and in-stock items, you can ship the ready stuff now.

Partial Fulfillment — Ship available items immediately and keep the rest open until they're ready. Customers get notified which items shipped, with per-package tracking. Pairs really well with the pre-order stuff.

https://preview.redd.it/35zflnh1xmah1.jpg?width=1500&format=pjpg&auto=webp&s=7e4c5bc43fb7138ad8a2604b85deb463f6b67b8c

Offline & Custom Payment Methods — Accept payments outside the standard card flow: bank transfers, checks, invoicing, cash on delivery, or whatever custom method you need. Orders come through with the right status so you can reconcile once payment clears.

Upsells (coming soon) — pick which products to offer as upsells across product pages, cart, checkout, and confirmation, triggered automatically when someone views a specific product.

Worth pointing out: none of this exists in Webflow Ecommerce today, and on Shopify most of it means bolting on paid third-party apps.

Happy to answer questions if anyone's curious how any of it works!

Start selling for free at CartGenie.com

https://preview.redd.it/rgzibv0z4fah1.png?width=452&format=png&auto=webp&s=76aaa7903681283dc173a8e5046ad324de03538d

Hello everyone!
Just got hired on a new project. The website is fairly big, 100+ static pages, 50 collections etc.....
I just saw it this funny class nomenclature, inspired to tailwind. Perhaps I'm wrong but I'd imagine eg. changing the k-px-0 for k-px-20, firstly removing all the classes then putting them back.... or should I keep a spreadsheet 😆
There's no style guide in place. I'm wondering what would do somebody else in this case:
1- Reverse engineering the approach used (800 classes) and basically learn/adopt it?
2- Hybrid approach (eg introducing Client-First for the structure)?
3- Propose a full refactoring?
4- Add another design system (Webflow native).

Share your experience please!