“We Don’t Really Use the Website, It Doesn’t Do Anything For Us”

“We don’t really use the website, it doesn’t really do anything for us…”

I’ve heard some version of that sentence from lots of business owners. Said the way you’d talk about an old fax machine – technically still there, ignored, not worth the trouble.

While the noise merchants argue over which AI-powered framework they’re peddling is going to dethrone WordPress (which, for the record, runs nearly 50% of the entire internet) – the same frameworks that’ll likely be vaporware in a year faster than you can say “crypto” – the actual concern most small business owners face is that their website doesn’t actually do anything for them.

Truth is, as I’ve said to many young developers over the years – business owners simply do not care about which framework their site is built in. They only want it to work for them. Generate business. Generate leads. Make sales. Create inquiries. “Make the phone ring.”

I work almost exclusively B2B, so I think I have a pretty solid finger on the pulse of small business. I talk to my clients regularly, new and old. There are common trends in why they feel disconnected from their website, why it doesn’t work – and most of the time, it’s not their fault. Nobody told them what a website actually needs to do. The people who built it cheaply didn’t tell them. The hosting company didn’t tell them. AI never pushed back; their visitors never said a word… Nobody told them.

So let’s talk about why that is – and what to do about it.

What a Website Is Actually Supposed to Do

Before we get into why websites fail, it’s worth defining what “working” even means – because most business owners have never had that conversation. Not with their designer, not with their hosting company, not with anyone.

A website is not a digital brochure. It is not an online business card. It is not something you build because everyone says you’re supposed to have one.

A working website generates leads. It answers questions. It builds trust. It makes the phone ring. It collects form submissions, books appointments, and helps someone decide to contact you instead of your competitor. It’s doing all of that while you’re asleep, on vacation, at your kid’s game, or closed for the weekend.

If it isn’t doing those things, it isn’t “not being used.” It was never built to do them. Those are two very different problems – and only one of them is the owner’s fault.

“Did you market it?” “No.”

No one is coming to your website if you don’t tell them about it. It’s your greatest salesman – sitting out there working tirelessly, 24 hours a day, 365 days a year – but if you don’t direct people to visit, to explore, to inquire, no one is going to come.

Many clients tell me about the “good old days” when they’d drop an ad in the Pennysaver or the Yellow Pages and their phone would ring. When print stopped performing, those advertising dollars got pocketed instead of reinvested in digital strategies like Google Ads, LinkedIn advertising, or social campaigns. The phone stopped ringing and the website got the blame.

A website without marketing is a store built in the middle of the woods. The location isn’t bad. There’s no road to it. Something has to point people toward the site:

• Google Ads – paid placement at the exact moment someone searches for what you sell.
• Organic SEO – the slow-building asset that earns traffic without paying per click.
• Local directory listings – Google Business Profile, Apple Maps, Yelp, Bing – where local customers actually look.
• Email and referral campaigns – the customers you already have are the cheapest source of the next ones.
• Content marketing – articles that answer real questions and get found for years.

This is why the website doesn’t work.

“What did you pay for it?” “$200.”

Whether it was a family favor, a package deal, a budget freelancer, or “it was basically free” – what you’re actually paying for when you hire a web designer is labor. And that labor comes in the form of the experience, the thought, the strategy, and the time invested in deliverable outcomes.

A $200 website probably didn’t come with proper hierarchical content structure required to rank well on Google – or any of the other time-consuming technical requirements. It probably didn’t come with someone who spent time understanding the business, the customers, the goals, the intent – and tailored it to deliver results on those assumptions. More likely, the same template that went to every other client got a logo dropped on top of it and shipped.

What a budget build almost never includes:

• Content strategy and conversion planning
• Search engine optimization and schema markup
• Analytics configuration – so nobody even knows it’s failing
• Performance optimization and Core Web Vitals
• Competitor research and lead generation planning

Visitors pick up on this level of investment in a site – and it shapes how they perceive the business behind it. They may not be able to articulate it – but they know when something is off. A site that looks like it was thrown together signals to potential customers that quality might not be a priority – even when that couldn’t be further from the truth. The business is great. The website just isn’t telling that story. (I wrote a full breakdown of what websites actually cost and why – the short version is you’re paying for the parts you can’t see.)

This is why the website doesn’t work.

It’s built on cheap infrastructure.

“The hosting is only $5 a month though.”

(Sometimes worse – it’s $350 a month delivering the same quality as the $5 hosting. The price isn’t always the tell.)

Page load time is a significant ranking factor – still, yes, even in the age of AI. Slow servers deliver slow websites. Cheap infrastructure leaves a site exposed to security vulnerabilities, attack vectors, and general poor performance. On budget shared hosting, hundreds of sites share one server – and when the site next to yours gets hacked or hammered with traffic, yours pays the price too. (That’s the neighborhood effect, and it deserves its own read.)

No SSL? Visitors get a browser security warning before they even see the homepage. Poor load time? They close the tab and click the next result. The site is actively turning people away before they read a single word – and the business owner has no idea it’s happening.

Daily backups, uptime monitoring, managed updates, SSL – these aren’t upsells. They’re the baseline. Because when infrastructure fails, everything built on top of it fails with it.

This is why the website doesn’t work.

The content misses the mark.

It’s important that visitors know a business has been around since 1964 and is a third-generation family operation. But that’s about as far as most visitors want to go – because they’re primarily concerned with what the business can do for them.

Content that isn’t written for the audience – addressing their problems, their questions, their decisions – doesn’t connect. It needs to be authoritative, informative, helpful, and citable. It needs to meet E-E-A-T standards (Experience, Expertise, Authoritativeness, Trustworthiness – Google’s framework for evaluating content quality). It needs structure, hierarchy, and signals that tell search engines – and AI – that this source knows what it’s talking about.

No clear calls to action. No obvious next step. No reason for a visitor to do anything other than leave.

This is why the website doesn’t work.

There’s no SEO – and therefore no AISEO or GEO.

On-page SEO. Title tags. Header tags. Meta descriptions. Content blocks. Schema markup. Structured data. Image alt tags. URL structure. Internal linking. Proper heading hierarchy. Core Web Vitals.

All of it missing. All of it matters.

Search engines need formatting and structure to understand a site. Without it, the SERPs have nothing to place anywhere – so the site gets left out entirely.

Schema markup deserves special mention, because nobody outside this industry has ever heard of it. It’s structured data – a block of code visitors never see that tells Google, Bing, and every AI model reading their indexes exactly who the business is, what it does, where it operates, and how to reach it. Sites that have it get understood. Sites that don’t get guessed at.

And here’s what most people haven’t caught up to yet: if there’s no SEO, there’s no AISEO! No GEO – Generative Engine Optimization. Those AI summaries sitting at the top of every search result pull from authoritative, well-structured, properly cited sources. They’ll reference the businesses that follow best practices. The ones that don’t, simply don’t exist in that space.

87% of ChatGPT citations match Bing’s top search results. The fundamentals that get a site ranking on Google are the same fundamentals that get it cited in an AI response. The destination changed. The road didn’t.

That last part matters more every month. When someone asks an AI for a recommendation, the model assembles its answer from sources it already trusts – structured sites, consistent business listings, real citations. A site with no SEO foundation was invisible to Google. Now it’s invisible to the answer layer sitting on top of Google too. Same absence, twice the cost. (And no, AI didn’t kill search – Google is still growing year over year. You need both.)

This is why the website doesn’t work.

It wasn’t optimized.

A 17MB hero image that takes four seconds to load. The page expands to fill the space, the content jumps, the Cumulative Layout Shift score drops. Combined with uncompressed images, no browser caching, unminified CSS and JavaScript, no lazy loading – those small losses stack into a site that ranks poorly and performs worse. It’s death by a thousand cuts (or hours of time).

Speed is not a nice-to-have. Google has been saying this for years. Visitors figured it out the moment they hit the back button.

This is why the website doesn’t work.

AI built it. (This deserves its own article.)

This one is new – but it’s already showing up constantly.

A business owner spends an afternoon prompting an AI tool to build them a website. It looks reasonable at first glance. It has sections, some text, maybe a hero image. They publish it and consider it done.

The problem isn’t that AI was involved. The problem is that the person prompting it doesn’t know enough about design, development, or strategy to know when the output is wrong – and AI isn’t going to tell them. It’ll produce something that looks like a website the same way a child with a ruler can produce something that looks like architecture.

The prompts drive the output. If the person writing the prompts doesn’t understand information hierarchy, conversion flow, content strategy, heading structure, or why a call to action belongs above the fold – the AI doesn’t know to ask. It just builds what it’s told, confidently, without flagging that the foundation is wrong.

It doesn’t understand the business. It doesn’t understand the audience. It doesn’t understand the culture, the tone, the intent, or the competitive landscape. It doesn’t know that the hero copy should speak to the customer’s problem, not the business owner’s pride. It generates something generic because it was asked something generic – and generic doesn’t make the phone ring.

Then there’s the infrastructure underneath. AI-generated sites are frequently missing proper meta structure, schema markup, optimized images, correct heading hierarchy, SSL configuration, and half a dozen other things that don’t show up in a visual preview but absolutely show up in search rankings – and now in AI citations. They don’t know about these things, but google does!

I see these sites when they come in for repair. The visible layer is fine – sections, colors, a hero image. Underneath: no schema, no analytics, headings out of order, images at full camera resolution, forms that go nowhere. The owner did nothing wrong. They used a tool that promised a website and delivered a picture of one.

The person who built it can’t see what’s wrong because they don’t know what to look for. That’s not a criticism – it’s the nature of any tool used without the foundational knowledge to evaluate its output. You can’t proofread a language you don’t speak.

The barrier to entry got lower. The output got worse. And eventually, someone calls and says the website doesn’t do anything.

This is why the website doesn’t work.

It wasn’t *built* to actually do anything.

This is the one that ties all of this together.

It was built to “be a website.” And no one (aside from some web designers and developers) really care about websites. They care about what a website can do!

A website should generate leads. Book appointments. Drive phone calls. Close sales. Answer questions before they’re asked. Build trust before a visitor ever speaks to anyone. Work at 2am on a Sunday when nobody’s available. Be the best salesman, the most patient customer service rep, and the most consistent brand representative – all at once.

If it wasn’t built with any of that in mind, it won’t do any of it. Not because websites don’t work. Because this one was never designed to.

So what can you do about it?

None of this is meant as a criticism. Most business owners were never told any of this (feel free to forward this to someone you think should read it). The people who built the site cheaply didn’t mention it. The hosting company didn’t bring it up. The AI coding agent never pushed back. The customer didn’t leave any feedback when they just closed the window. It just… didn’t come up.

Start with a clear assessment – not of the design, but of the fundamentals.

If the answer to most of those is no – or “I don’t know” – the website isn’t broken. It was just never finished.

Most of these problems are fixable. And fixing them properly is exactly what turns a website that “doesn’t do anything” into one that makes the phone ring.

Need Help?

Not sure which of these is your problem? That’s a five-minute conversation, not a project. Send me your site and I’ll tell you straight what’s working, what isn’t, and what’s costing you calls – no pitch, no obligation. If it’s in good shape, I’ll tell you that too. Reach out anytime.

“The website isn’t broken. It was just never finished.”