Your website has one job. Most sites are doing six.
A site that tries to serve every audience at once converts none of them. How to decide what a page is for before designing it.
Ask ten business owners what their website is for and you will get ten versions of "to show what we do". Ask what it should cause a visitor to do and the answers get vaguer — which is usually visible in the homepage: a hero for investors, a section for recruitment, a blog nobody maintains, and somewhere below the fold, the thing the business actually sells.
Every page answers one question
The useful discipline is to assign each page a single question it exists to answer, and each section of that page one supporting question. A homepage answers "what do you do and is it for me?" A service page answers "can you solve my specific problem?" A case study answers "have you done this before, for someone like me?"
When a section cannot be tied to a question a real prospect asks, it is decoration. That does not make it worthless — but it should not be competing for attention with the part of the page that produces enquiries.
Competing calls to action cancel out
The common failure is not a weak call to action. It is five of them at once: book a call, download the guide, join the newsletter, follow on LinkedIn, view pricing. Each one is defensible. Together they hand the visitor a decision they did not come to make.
Pick one primary action per page and let everything else be secondary in size, colour and position. On our own site that is "Start a Project", with "View Our Work" as the softer path for people who are not ready.
How to audit your own site in an afternoon
- List every page and write the one question it answers. Pages you cannot fill in are candidates for deletion.
- Open each page on a phone and count the calls to action above the fold.
- Ask someone outside the business to describe what you sell after ten seconds on the homepage.
- Check which pages produced enquiries in the last quarter. Most sites earn from a handful.
The outcome is usually a smaller site. That is almost always an improvement.
Written by Code and Thrive. Get in touch if you want to talk through any of this for your own project.
Keep reading
- TechnologyWhen custom software is worth it — and when it isn'tBuilding is not automatically better than buying. A practical test for deciding which side of the line your workflow sits on.Read
- PerformanceSite speed is a revenue problem wearing an engineering costumeCore Web Vitals get treated as a technical scorecard. On a commercial site they are closer to a shopfront door that sticks.Read