Are We Building Websites for Algorithms Instead of People?

I catch myself falling into this trap all the time.

I will be building a website, checking the page speed, looking at the SEO score, running audits, tweaking headings, compressing images, adjusting spacing, moving sections around, and somewhere in the middle of all that I have to stop and ask myself a very simple question:

Is this actually better for the person using the website?

Because it is easy to forget that part.

It is easy to get pulled into the numbers. Page speed scores. SEO scores. Core Web Vitals. Keyword density. Green lights in plugins. Accessibility checks. Technical audits. Schema markup. Meta descriptions. Heading structures. Internal links. Image alt text.

None of those things are bad.

In fact, I care about them a lot. A website should load quickly. It should be structured properly. It should be easy for search engines to understand. It should work well on mobile. It should be technically sound.

But I do think there is a point where we start building websites for the tools instead of the people.

And that is where things get a bit strange.

A website can pass a performance test and still feel cold. It can have a perfect SEO score and still say very little. It can be technically correct and still be difficult for a real visitor to understand.

That is the part I think about more and more.

Clients Often Come With the Checklist First

A lot of clients come to me with a list of things they have been told their website needs.

They want it to be fast.
They want it to rank.
They want it to be SEO optimized.
They want it to score well on Google.
They want it to have the right keywords.
They want the page speed to be as high as possible.
They want the structure to be “correct.”

And to be fair, those are all reasonable things to care about.

I would never tell a client that SEO does not matter. I would never say performance is unimportant. I would never build something slow and messy just because it looks nice.

But what I often notice is that people come in thinking about what Google might want before they think about what their actual customers need.

They think about the algorithm before the visitor.

They think about the audit before the experience.

They think about the score before the person who is landing on the homepage, trying to work out whether this business can help them.

That is usually where the better conversation starts.

Because yes, the website should be technically strong. But it also needs to be clear. It needs to feel trustworthy. It needs to answer real questions. It needs to show the visitor where to go next. It needs to make sense to someone who has never heard of the business before.

That is not always the same thing as chasing the highest possible score.

I Understand Why It Happens

I do not think people do this because they do not care about users.

I think it happens because numbers feel safer.

A page speed score gives you something clear. An SEO plugin gives you a green or red light. A tool tells you what is wrong. A checklist tells you what to fix.

User experience is harder to measure.

You cannot always put a simple number on whether a website feels trustworthy. You cannot always measure whether the tone sounds natural. You cannot always see from a plugin whether the homepage makes sense to a first-time visitor.

So we end up focusing on what is easiest to check.

I do this too.

I can spend too long trying to squeeze a few extra points out of a performance score, even when the site already feels fast. I can overthink whether a heading is optimized enough, then realize the more important question is whether the heading actually helps the visitor understand the page.

That is the trap.

The tools are useful, but they are not the audience.

The Website Score Trap

It is very easy to start chasing scores.

If a performance tool says the site is 96 out of 100, it is tempting to try and get it to 100. If an SEO plugin says the page needs the keyphrase in one more place, it is tempting to add it, even if the sentence becomes worse. If an audit says an image could be smaller, it is tempting to remove or compress it to the point where the page technically improves but visually loses something.

Sometimes that work is genuinely useful.

Other times, it is just score-chasing.

That is where I try to be more careful now. A better score is only valuable if it creates a better website.

If improving page speed makes the site feel smoother, that is good. If improving SEO makes the content clearer and easier to find, that is good. If improving accessibility makes the website easier for more people to use, that is very good.

But if a change only makes a tool happier while making the page less helpful, less human, or less clear, then I have to question it.

A website is not there to impress an audit report.

It is there to help a person understand something, trust something, buy something, book something, or make a decision.

SEO Should Not Make the Website Sound Robotic

SEO is one of the biggest places this shows up.

Everyone wants their website to rank, and understandably so. There is no point building a great website if nobody can find it.

But sometimes SEO turns good writing into strange writing.

You can feel it when a page has been written mainly for search engines. The same phrase appears too many times. The headings sound unnatural. The location name is squeezed into places where no person would actually say it. The content is long, but not necessarily useful.

It might technically be “optimized,” but it does not feel helpful.

This is something I try to avoid in my own work.

I want pages to be found by search engines, but I also want them to make sense when a real person reads them. I want the keywords to be there, but naturally. I want the structure to be clear, but not stiff. I want the page to answer what people are actually wondering, not just what a tool says is missing.

Good SEO should make a website clearer.

It should not make it sound like it was assembled from a keyword list.

Page Speed Matters, But It Is Not Everything

I care a lot about website speed.

A slow website is frustrating. It makes a bad first impression. It can damage trust. It can hurt conversions. It can make people leave before they even see what the business offers.

So yes, page speed matters.

But page speed is not the whole user experience.

Sometimes a useful website needs real images, project photos, product galleries, videos, testimonials, maps, forms, and other elements that add value. Those things need to be optimized properly, but they should not always be removed just to make a score look cleaner.

A website that loads instantly but does not say anything useful is not a good website.

A website that is technically lightweight but gives no proof, no personality, no clear next step, and no reason to trust the business is not doing its job.

The aim should not be to make every page as empty as possible.

The aim should be to make the site fast enough that it feels smooth, while still giving visitors what they need to make a decision.

That balance is where good web development actually happens.

The User Does Not Care About the Same Things We Do

This is something I have to remind myself of often.

Most users do not land on a website thinking about Core Web Vitals, heading hierarchy, schema markup, plugin bloat, or whether the homepage has been perfectly optimized for a keyphrase.

They are thinking about themselves.

Can this business help me?
Do I trust them?
Do they understand my problem?
Have they done this before?
How much does it cost?
Where are they based?
What happens next?
How do I contact them?

That is what the website needs to answer.

If those questions are not answered clearly, the technical side will not save it.

A visitor can leave a technically excellent website because they could not find the information they needed. They can leave because the copy felt vague. They can leave because the site looked generic. They can leave because they did not feel confident enough to enquire.

Those are user experience problems, even if the audit score looks good.

A Website Should Feel Like It Was Built for Someone

The websites I like most feel like they were built with a real person in mind.

They are not always the flashiest. They are not always the most technically perfect. They are not always chasing every trend.

But they make sense.

The language feels natural. The pages are easy to follow. The design supports the content. The images feel relevant. The calls to action are clear. The site gives the visitor enough information to feel confident, but not so much that they feel overwhelmed.

That is what I try to build towards.

Not just a website that scores well.

A website that feels useful.

A website that understands the person using it.

The Algorithm Still Matters

I do not want this to sound like I am dismissing SEO or technical optimization.

I am not.

The algorithm matters. Search visibility matters. Website speed matters. Technical structure matters. Accessibility matters.

A website still needs solid foundations.

But I think those things should support the user experience, not replace it.

SEO should help people find useful pages. Page speed should make the experience smoother. Technical structure should make the site easier to understand and maintain. Accessibility should make the website usable for more people.

These things are important because they help the user.

That is the part worth remembering.

The Better Order of Priorities

When I am building a website, I try to think about the order of priorities.

First, who is the website for?

Then, what do they need to understand?

Then, what questions are they likely to have?

Then, what action should they be able to take?

Then, how do we make that experience clear, fast, trustworthy, and easy to use?

After that, the technical optimization can support the structure.

That order matters.

If you start with the algorithm, you can end up with a website that technically checks the boxes but does not really connect with anyone.

If you start with the user, the SEO and performance work has something meaningful to support.

Final Thoughts

I think a lot of us are guilty of building for algorithms sometimes.

I definitely am.

It is easy to get caught in the scores, plugins, audits, and best-practice checklists. It feels productive. It feels measurable. It feels like progress.

But the real test of a website is not just whether a tool approves of it.

The real test is whether the person using it understands what they need to understand, trusts what they see, and knows what to do next.

That is what clients often need more than another perfect score.

A fast website is good.
An SEO-friendly website is good.
A technically clean website is good.

But a website that actually helps people is better.

The best websites should do both.

They should be technically strong enough to perform well, but human enough to make sense to the people they are meant for.

That is the balance I keep trying to come back to.