I'll give you the number, because the number is the whole point. Over a recent stretch my own site pulled in more than 2,000 visitors and produced exactly zero new client conversations. Not a slow month. Zero.

My first instinct was the same one I talk business owners out of every week. I assumed it was a conversion problem. Maybe the call to action was weak. Maybe the contact form had too many fields. Maybe the page was slow on a phone. I have written before about all of those, and they are real, and they cost people leads every day.

But that wasn't it this time. The page worked. The form worked. People just had no reason to fill it out, because the people showing up were never going to hire me in the first place.

The number that should have bothered me sooner

Traffic and leads are not the same measurement, and treating them as one is how you end up congratulating yourself on a chart that means nothing. Two thousand visitors sounds like momentum. It feels like the thing is working. It is very easy to look at a line going up and assume the line going up is good news.

It isn't, on its own. A visitor count tells you how many people arrived. It tells you nothing about whether those people had a budget, a problem you solve, or any intention of hiring anyone. You can have a beautifully built site that knows its one job, a sharp value proposition, and a frictionless contact form, and still get nothing, if the room you filled is the wrong room.

That is the part the design conversation misses. Everyone wants to talk about the page itself: the layout, the copy, the colors, the speed. All of that matters. None of it matters if the audience standing in front of it was never your customer.

Where the traffic came from told me who it was

So I went and looked at where the visits were actually coming from, which is the step I should have taken first.

Most of my identifiable traffic came from two places: posts I had written on Bluesky and LinkedIn, plus a trickle from developer news aggregators like daily.dev. A couple of visits even came from ChatGPT citing one of my articles, which was genuinely encouraging and a story for another day.

Look at that list again. Bluesky's early crowd skews heavily toward developers and builders. daily.dev is a news feed for programmers, by definition. The articles those people were sharing and clicking were my technical pieces: framework opinions, architecture decisions, the deep-in-the-weeds stuff I love writing.

Here is the uncomfortable read. The people enjoying my best-performing content were my peers. Other developers. They were evaluating my technique, not my services. A developer admiring how I structured a Livewire component is not a small business owner who needs a website that books appointments. Those are two completely different humans, and I had built a content engine that spoke fluently to the first one and barely acknowledged the second.

No headline test fixes that. No new button color fixes that. I was throwing a great party for an audience that had no money to spend and no reason to spend it on me.

Audience-fit sits above conversion rate

There is a whole discipline around conversion-rate optimization, and it is useful. But it operates on the assumption that the traffic arriving is the traffic you want. CRO tunes the last few feet of the journey. It cannot save you if the journey started in the wrong city.

Audience-fit is the layer above all of it. Before you ask "why aren't these visitors converting," you have to ask "are these even the visitors I want." If the answer is no, conversion optimization is rearranging furniture in a house nobody who can afford it is walking into.

This is the trap that catches technical people especially hard, and I walked right into it. We write what we find interesting. What we find interesting is usually the craft. The craft impresses other practitioners. Other practitioners are not the buyer. So the better your technical content performs, the more confidently you can be reaching exactly the wrong people, with a metric that looks like success the entire time. That is the cruel part. Strong traffic numbers can actively hide an audience problem rather than reveal it.

What I'm changing

The fix is not to stop writing technical content. I am not going to pretend I don't enjoy it, and there is real value in being visible to peers: referrals, hiring, credibility, the occasional ChatGPT citation that puts you in front of someone new. That stays.

The fix is to protect a portion of the calendar for content written for the person who actually signs the contract. That means starting from their problem, not my solution. A business owner does not search for "TALL stack architecture." They search for some version of "my website doesn't get me customers." Those are different questions, and most of my catalog answered the first one beautifully and the second one almost by accident.

It also means watching the right number. Pageviews are a vanity metric the moment you stop checking who the views belong to. The number I care about now is whether the content is reaching people with a problem I can solve and a budget to solve it, and whether any of them raise their hand. One qualified conversation is worth more than another thousand admiring developers.

If you run a business and your site is busy but quiet, do this before you touch the design: open your analytics, find your top traffic sources, and ask one honest question about each one. Is this where my customers are, or is this just where I am comfortable talking? If you have never asked that question, the answer is probably worth more than any redesign. Figuring out who you are actually for, then building the site and content to reach them, is most of what we do.

The honest version

I diagnose this for clients constantly, and I still missed it on my own site for longer than I would like to admit, because the traffic was flattering and flattery is hard to audit. Traffic that goes up while leads stay flat is not a mystery and it is rarely a design failure. It is almost always a sign that you have gotten very good at reaching people who were never going to buy.

More visitors will not fix that. A new homepage will not fix that. The only thing that fixes it is deciding, on purpose, who you are actually talking to, and then writing like you mean it.