No visibility
Few relevant impressions
The website appears rarely for useful searches or lacks pages for real intentions. Before conversion work, content, structure, authority and distribution need attention.
Guides
Traffic, message, trust, usability or technology: a practical diagnosis for deciding what to fix and when the homepage needs a redesign.
The short answer
A website can fail to generate enquiries for different reasons: it may not be found, attract the wrong people, explain its value poorly, provide insufficient evidence, create friction or lose the enquiry because of a technical failure. Before redesigning the homepage, separate visibility, understanding, trust and action. If relevant visits arrive but the journey does not persuade, redesign may be appropriate; if traffic is missing or the form is broken, changing the visual design alone will not solve the problem.
The same statement — “the website does not bring in customers” — can describe four completely different failures.
Impressions, clicks, visits and enquiries are not synonyms. Each step points to a different problem and intervention.
No visibility
The website appears rarely for useful searches or lacks pages for real intentions. Before conversion work, content, structure, authority and distribution need attention.
Visible but ignored
The title, description, brand or promise may not match the search. Check the page that is shown instead of automatically blaming the homepage.
Traffic without action
Message, audience, evidence, hierarchy or calls to action do not support the decision. The homepage and service pages become central here.
Action without outcome
The form may ask too much, fail technically, provide no confirmation or generate poorly qualified messages. End-to-end testing and a concrete definition of a valid enquiry are required.
First rule
Do not rebuild a website to compensate for data you do not have. Collect a meaningful period, test real journeys and record where people stop. The project starts with diagnosis, not personal taste.
Search Console describes visibility on Google; analytics describes what happens on the website. Neither tool alone explains why someone did not choose.
Two perspectives
In Search Console, examine queries, pages, impressions, clicks and CTR in context. A page can be shown for irrelevant searches and lower the rate without having a design problem.
In Plausible, define goals that match the commercial outcome: opening a contact route, a successful submission or a qualified enquiry. A button click is a step, not necessarily a conversion.
Which searches show the website? Which page appears? Are impressions growing? Do clicks come from needs that match the service?
Which pages do people enter through, which actions do they complete and where do they leave? Events must describe real steps rather than incidental interface movement.
Form totals are insufficient. You need to know whether enquiries concern the service, have plausible timing and budget, and can become useful conversations.
Compare equivalent periods and one change at a time. Without a before and after, attributing an outcome to the new title or homepage remains a hypothesis.
For choosing proportionate measurement, also read Plausible vs Google Analytics 4.
A new visitor does not know the company structure. They need to build an accurate model of what you offer quickly.
The audience recognises itself through situation, industry, objective or problem. “Solutions for everyone” avoids excluding anyone, but often persuades no one.
The heading should anticipate an understandable outcome or category. Creative language and slogans must not force visitors to decode what the business does.
Method, experience, specialisation, control, timing or terms must become observable differences, not adjectives such as quality, innovation and professionalism.
The page explains what someone can do now and what will happen afterwards. One clear request reduces uncertainty better than several equivalent buttons.
Trust does not come from random badges or context-free numbers. It comes from consistency between what you promise and what the website allows people to verify.
Cases and examples explain the problem, decision and scope. A gallery without context demonstrates taste, but not necessarily competence for the customer’s need.
Stages, point of contact, required materials and decision criteria make the service less abstract and show how the project is governed.
Saying what is not included, who the service does not suit and what affects cost or timing increases credibility. Transparency also filters incompatible requests.
Name, location or service area, contact details, experience and responsibility should be easy to find. An anonymous website asks for trust without exposing itself.
Consistency
Do not relegate every proof point to the bottom of the website. Prices, cases, process, assurances and limits belong where they resolve a specific uncertainty.
A button works when the action is understandable, proportionate to the decision and consistent with what the page has just demonstrated.
“Discuss the project”, “view packages” or “analyse your website” anticipate the outcome. “Learn more” may be too generic when the destination is not obvious.
Several actions can coexist, but one should lead. Buttons with equal weight and different destinations turn the choice into additional work.
Heading, button and next page should concern the same decision. Sending a specific request to a generic contact page interrupts the reasoning.
After submission, the website should show a persistent outcome, prevent duplicates and explain the next steps. A button changing colour does not prove that the enquiry arrived.
Micro-conversions and outcomes
Opening a menu, scrolling a section or clicking WhatsApp are signals. Define commercial conversion around the result that actually matters and compare it with the quality of enquiries received.
Even a relevant proposition can fail in the final stretch when the website asks too much, surprises the user or removes control.
It asks for information that is unnecessary at first contact or does not explain why it is needed. Every additional field should have a real purpose.
The journey forces people to search the footer, menu or unlabelled icons. The primary action should appear where the decision develops.
“Something went wrong” does not identify the field to correct and may not preserve valid data. Errors should be specific and recoverable.
Critical information appears only after contact. This increases unhelpful enquiries and abandonment when expectations are finally corrected.
Pop-ups, banners, chat and panels compete with content, cover controls or move focus. Every added layer should justify its cost.
Someone submits and does not know when a reply will arrive, from whom or what to prepare. Confirmation should close one uncertainty and open the next stage.
Performance, stability, mobile use, accessibility and form operation are conditions of conversion, not decorations to check at the end of the project.
The heading, proposition and primary action should not wait for sliders, fonts, trackers or script chains. The page should remain understandable when a secondary resource fails.
Images, fonts, banners and dynamic components must not move the button while someone reads or tries to use it. Stability protects continuity and control.
Text, menus, virtual keyboard, fields, errors and confirmation must be tested on real screen sizes. Shrinking the desktop layout is not mobile experience design.
Validation, anti-spam, submission, email, server response and confirmation must be tested together. A perfect interface with broken delivery produces no enquiries.
For an initial technical diagnosis use Analyse your website and explore the causes in Why your website is slow.
SEO and GEO should connect real needs with pages able to answer them. Sending generic visits to a generic homepage increases volume, not necessarily value.
A useful diagnosis does not end with “contact me”. It identifies a next step proportionate to the problem that was actually observed.
| Primary problem | What to verify | Relevant next step |
|---|---|---|
| The website is not being found | Queries, pages, content, indexing, links and authority | SEO and AI visibility guide |
| The website is slow or has technical problems | Mobile performance, indicative weight, WordPress and essential headers | Analyse your website |
| WordPress, plugins and dependencies constrain the project | Components, URLs, content, risks and SEO continuity | WordPress migration |
| A public website exists but the homepage no longer represents the business | Positioning, message, hierarchy, evidence and primary action | Page Zero |
| The website has not been built yet | Objectives, scope, content, package and necessary features | Services and packages |
| The requirement is already specific and mature | Requirements, integrations, constraints, timing and responsibilities | Contact |
The matrix provides direction but does not replace analysis. A website may have several problems at once; solve first the one that prevents you from observing the others.
The boundary is not the age of the visual design. It is whether the current architecture can express and verify the new strategy without accumulating compromises.
| Area | Targeted improvement | Redesign |
|---|---|---|
| Message | The proposition is correct but the heading and introduction are weak | The audience, offer or positioning has changed substantially |
| Evidence | It exists and can be added near the relevant objections | The website has no suitable space, hierarchy or content to support it |
| Journey | Calls to action, destinations and the form only need realignment | Navigation and pages follow a logic incompatible with the decision |
| Structure | HTML, responsive behaviour and components remain solid | Fragile layout, rigid content and accessibility require continuous patches |
| Platform | The system is governable and the change creates no new dependency | Themes, plugins or builders prevent reliable, durable intervention |
| Identity | Tone and visual language can evolve without contradicting the brand | Current perception repels the audience or misrepresents the real service level |
The economic criterion
Add the cost of corrections, the constraints that remain and the time during which the website will continue to misrepresent the business. Rebuilding everything is not always necessary; continuing to patch is not always cheaper.
Twelve observable checks to run on desktop, mobile, keyboard and the real submission journey.
Someone who fits the audience can see that the proposition concerns their situation without reading the entire website.
The heading and opening explain what is offered in concrete language rather than relying only on a slogan.
Method, experience or specialisation is connected to useful consequences for the customer.
The most important action is visible and clearly distinguished from secondary alternatives.
The button leads to the promised page, form or service without making the visitor start again.
Cases, work, process, prices or limits appear near the doubt they are intended to resolve.
Headings, paragraphs, lists and hierarchy make answers discoverable without reading every word.
Menu, text, actions, fields and errors work with a thumb and virtual keyboard on small screens.
Navigation, controls and the form are reachable in a logical order with a visible indicator.
Primary content arrives early and the layout does not move during reading and interaction.
Validation, anti-spam, server, email and confirmation have been tested end-to-end, including errors.
Goals distinguish opening, attempting, successful submission and commercial quality without collecting unnecessary data.
When a public website already exists but the homepage no longer represents the business, its value or service level, discussing colours alone is not enough.
Before deciding
Page Zero starts from the existing website and the information supplied to build a private, navigable proposition. It is not an automated template, a complete audit or a promise of results: it is a practical way to assess direction, hierarchy and positioning before commissioning the full project.
The sources explain measurement, structure, performance, forms and accessibility. Design decisions must then respond to the actual website context.
Logical organisation, useful content, titles, links and a structure that people and search engines can understand.
Queries, pages, clicks, impressions, CTR, top content and interpretation of changes over time.
Event and page goals, conversion rate, sources, funnels and journeys that lead to the action.
Perceived performance, stability and responsiveness as real experience, with responsibility shared across technology, content and business decisions.
Explicit association between labels and fields, understandable names and a useful clickable area that also supports assistive technologies.
Feedback about errors, warnings and success so that users can understand what happened and complete the journey.
Testable criteria for perceivable, operable, understandable and robust content, including focus, input, errors and interaction.
Sources checked on 10 August 2026. This guide does not promise a universal conversion rate: audience, offer, market, period and traffic quality all change the outcome.
Direct answers about traffic, conversions, redesign, forms, SEO, analytics and Page Zero.
Not automatically. First verify whether relevant traffic exists, whether people understand the proposition, whether they progress towards the action and whether the form works. Redesign is appropriate when message, structure and platform no longer allow reliable, coherent improvements.
There is no universal number. It depends on industry, source, seasonality, objective and the value of each enquiry. Use an equivalent period, separate traffic sources and do not conclude from a few sessions or a single day.
Visual quality can support understanding and trust, but does not replace a relevant proposition, credible evidence, a clear journey and a working form. Evaluate aesthetics by what they help people understand and do.
Not necessarily. Repeating the same action at relevant points may help; adding equal actions towards different destinations can increase uncertainty. One primary priority should remain obvious.
It should make the scope understandable and lead to relevant detail pages. Describing everything at equal depth creates a long page without hierarchy and weakens the primary proposition.
Search Console helps observe impressions, queries and clicks; analytics shows entry pages, journeys and goals. Few relevant visits point first to acquisition. Relevant visits without progress shift attention to message, trust and usability.
It can measure goals and events in a privacy-first configuration, but every implementation should be reviewed against transmitted data, custom properties, suppliers and real purposes. Measurement does not replace evaluating commercial quality.
No. It is an automated first diagnosis covering mobile performance, indicative weight, WordPress and selected security headers. It does not fully assess strategy, content, conversion, accessibility, SEO, GEO or code quality.
No. It starts from an existing public website to observe and rethink. Anyone creating a first website should define objectives, content, features and package on the Services page.
No. It shows one possible new homepage designed around the business and lets you assess direction and quality before the full project. No design can guarantee traffic, rankings or conversions independently of offer, market and management.
Next step
Page Zero lets you see a private, bespoke new homepage before deciding whether to commission the complete rebuild. I assess every request personally.