So proud to be announced as finalists in @webflow professional partner of the year award category.
This is for our first enterprise client @sisuclinic which we got chance to work with earlier this year.
Congratulations to the whole team 🎉🚀
#webflow#NoCode
Drumroll please 🥁
Now announcing this year's Webflow Awards finalists!
From customers, community members, and partners, here are some of the most imaginative projects and brilliant minds in web:
https://t.co/g3bx11wNZS
February against October, visits from Google went from 84 a month to 487.
Visits from AI assistants, mostly ChatGPT, went from pretty much nothing to 70 in September.
A few of the things we changed, which honestly any marketing team could look at on their own site:
→ We started tracking AI visits as their own channel. Before that they were mixed in with everything else and we couldn't really see them growing.
→ Pages answer first. Our comparison pages open with a two-sentence answer, and every section on our blogs starts with the answer in its first line.
→ Headings are written as the questions people actually search, not as clever labels.
→ Case studies say who it was and what changed right at the top. One of ours is now the second most visited page on the site from AI.
→ This month we started improving the ones already sitting on page one and two of Google, and merged the duplicates into one page.
If you're tracking AI visits on your own site, what are you actually seeing?
A marketing lead at a B2B company was waiting four weeks to get one page live, and it wasn't a redesign, just one page.
What she told me: "I'm not a developer, but I want more control."
Her developers weren't doing anything wrong, every change just queued behind product.
Earlier this year our site was ranking on Google for hundreds of question-style searches and getting barely any clicks from them. The answer was sitting right there on the results page, so nobody needed to visit.
Search Engine Roundtable had a piece last month saying AI Overviews now show up on over 80% of Google searches.
What started working for us was pages that answer first. Our comparison pages open with a two-sentence short answer before anything else, and those are where most of our AI visits land now, not the homepage.
The homepage is the page everyone spends the most time on in a redesign, and right now it's pretty much the one AI sends people to the least.
One site we built in 2021 went from fifteen pages to over a hundred, on the same build.
I would say the launch was the cheaper half of it, the pages since never really had a number on them because they turned up one at a time.
A marketing lead at a B2B company was waiting four weeks to get one page live, and it wasn't a redesign, just one page.
What she told me: "I'm not a developer, but I want more control."
Her developers weren't doing anything wrong, every change just queued behind product.
When a marketing team walks me through their WordPress site, what I hear about most is the list of things they've quietly stopped asking for.
The change itself is usually not hard, I think it's mostly that nobody wants to be the one who finds out what it breaks.
If your website sits with engineering, the landing page, the new logo and a typo on the pricing page all go in the same queue, behind the product roadmap.
Most teams stuck there didn't really pick it, it's just how the site was set up before they joined.
Earlier this year our site was ranking on Google for hundreds of question-style searches and getting barely any clicks from them. The answer was sitting right there on the results page, so nobody needed to visit.
Search Engine Roundtable had a piece last month saying AI Overviews now show up on over 80% of Google searches.
What started working for us was pages that answer first. Our comparison pages open with a two-sentence short answer before anything else, and those are where most of our AI visits land now, not the homepage.
The homepage is the page everyone spends the most time on in a redesign, and right now it's pretty much the one AI sends people to the least.
I ask on discovery calls what the website costs to run each month. Almost nobody can give me one number.
It kind of lives in four places, hosting, a developer retainer, plugin licenses nobody owns, and then the team's own hours, which don't show up anywhere at all.
When a marketing team walks me through their WordPress site, what I hear about most is the list of things they've quietly stopped asking for.
The change itself is usually not hard, I think it's mostly that nobody wants to be the one who finds out what it breaks.
When I ask a marketing lead who owns AI search on their side, I get one of two answers. The SEO agency has it, or nobody does.
Those are kind of the same answer. The SEO agency is measured on rankings, and this isn't rankings.
Who has it on your team?
One site we built in 2021 went from fifteen pages to over a hundred, on the same build.
I would say the launch was the cheaper half of it, the pages since never really had a number on them because they turned up one at a time.
I've started doing proper feedback calls with our retainer clients, and I push pretty hard for the negative stuff.
A few weeks ago I had one with a client we've worked with for almost five years. She leads design and owns their website, and she mostly couldn't come up with anything.
What she said instead: "It never feels like, oh no, that's not a capability we have. You're always like, you wanna do that? We'll figure out how to do it."
It goes both ways though. Her pixel-level QA notes over the years are a big part of how we run design on every other project now.
If your website sits with engineering, the landing page, the new logo and a typo on the pricing page all go in the same queue, behind the product roadmap.
Most teams stuck there didn't really pick it, it's just how the site was set up before they joined.
I don't think anyone is still on WordPress because they like WordPress.
Moving needs a date, a budget and somebody to own it, and staying doesn't really need any of that, so I guess it just stays.
I ask on discovery calls what the website costs to run each month. Almost nobody can give me one number.
It kind of lives in four places, hosting, a developer retainer, plugin licenses nobody owns, and then the team's own hours, which don't show up anywhere at all.
The website is usually the only line in the marketing budget that gets judged on whether people like looking at it.
So it ends up being the hardest one to defend when someone in the QBR asks what it actually returned.
When I ask a marketing lead who owns AI search on their side, I get one of two answers. The SEO agency has it, or nobody does.
Those are kind of the same answer. The SEO agency is measured on rankings, and this isn't rankings.
Who has it on your team?
I built an internal tool for my team with Claude Code, and I'm not an engineer. It runs our delivery now.
It's also been getting slower, and I honestly can't tell you which of my own changes did it.
When it slowed down I realized I had nobody to ask. I went back to the same chat that built it, which is kind of asking the thing that made the problem to find the problem.
Sites do this too, like a contact form that keeps saying thanks and stopped delivering anywhere months ago.
The first version is the cheap part now, for everyone, us included, and I think the expensive part is somebody properly owning it after it goes live.