Why Your Hull Website Gets No Enquiries

Why is a live Hull website still quiet?

Live is not the same as working. A site can look finished on a desktop and still produce a quiet week. The homepage loads. The logo sits in the corner. Nobody calls. Owners often blame Google first. Sometimes that is fair. Often the problem is closer: the next step is hard to find, the form fails on a phone, or the number is buried under a footer nobody scrolls to.

Quiet enquiry inboxes do not appear as a line on a spreadsheet. They show up as a Tuesday that should have been busier.

I have watched a contact form fail on a mid-range Android while the same page looked fine on a desktop monitor. Fields dropped. The send button sat under the keyboard. The success message never arrived. The owner had been blaming “the algorithm” for months. The algorithm was not the villain. The machinery was.

The buried phone number

You know your number. Your customers do not. If it sits in a tiny footer, or only as an image that cannot be tapped, or behind a “contact us” maze, people leave. On a phone between jobs, nobody wants to pinch-zoom a PNG of a landline.

I put the number where a thumb finds it. Header. Tap-to-call. Repeated near the service you just described. Same number everywhere a stranger will check. Hard to miss.

Same problem with the address when someone wants to know you are local. Say it as text. Not only as a map widget that fails to load.

A number that only appears after a long scroll of slogans is a number that does not exist for the visitor who had thirty seconds. Repeat it. Make it a link. Do not hide it in an image of a business card.

Forms that die on mobile

Desktop tests lie. A form that works on your office monitor can drop fields, hide the send button, or choke on autofill when someone uses a device in a car park. Spam traps that block real people are another classic. Captchas that punish older customers. Success pages that never arrive, so the visitor assumes nothing happened and does not try again.

When I build a form, I test it on a phone. Messages land in an inbox you check. You get a clear confirmation on screen. If the form dies later, you still have a person who wrote it on the other end of the email. A working enquiry path belongs in the build from day one, not as an afterthought.

Short helps. Their name, a number they answer, a line on the job, a notes box. Twenty fields for a boiler leak is how you lose the leak. Required fields should be the ones you will actually use when you ring back.

If submissions land in an inbox nobody opens, the page can be perfect and the week still stays quiet. Check the inbox. Check the junk folder. Send yourself a test from a different device after every change.

No clear next step

Some sites explain the business for three screens and never ask for anything. No call button. No short form. No “request a quote”. Visitors are not mind-readers. If you want a booked job or a clinic enquiry, say so near the service they came to read about.

A next step is a sentence and a control. “Call for a survey slot.” “Book a table.” “Ask about availability.” Soft endings - “get in touch if you would like to know more” - read as optional. Optional is easy to skip.

Put the ask on the home page and again on the service the visitor just finished reading. One place is a hope. Two places is a path.

Vague headlines that could belong to anyone

“Quality solutions for discerning clients” tells nobody whether you fix boilers in Hull. Name the job. Boiler service. Dental implants. Sunday lunch bookings. Concrete words match how people search and how they decide.

The first heading is a promise. If it could sit on a solicitor’s site and a café’s site without changing a word, it is not doing the job. Rewrite it as the sentence you would say if someone stopped you in the street and asked what you do.

Service pages that hide the work in a blob of six trades are the same problem at page length. Someone searching for a specific job needs a page that speaks to that job. Not a novel. A clear title, what you do, where you cover, and how to enquire.

Quiet traffic versus broken conversion

Sometimes Search Console shows people arriving and the inbox stays empty. That is a different problem from zero visits. Zero visits points at findability - titles, the listing, the usual local work. Visits without replies point at the page itself: the visitor found you, then bounced, got lost, or tried to enquire and failed.

Before you spend on ads, spend twenty minutes as a stranger. Open the site on your phone with Wi-Fi off. Can you find the number in one glance? Does the form submit? Does the success message appear? Does the homepage say what you do in the first screen, or only after a scroll of slogans?

A page that crawls on a weak signal will lose the call before any of this matters. A listing that still points at an old URL will lose the click before the page gets a chance. A homepage of library handshakes will lose trust before the form is even tried. Those are each a clause, not the diagnosis. The diagnosis on a quiet-but-visited site is usually the number, the form, the ask, or the headline.

Old domains without redirects are another quiet leak. You moved. Memory did not. Bookmarks and search land nowhere useful. Cutover belongs in going live.

What I look at first

I do not promise a flood of leads on day one. I do look at the machinery that stops enquiries from happening.

Clear tap-to-call. A form tested on a device. Pages that name the work and the place. Titles written for the search people actually type. The live URL matching what Maps sends. Redirects from anything you used to own.

One contact for design, build and the inbox afterwards. Tweaks after launch get priced in writing first. I stay reachable; I do not disappear the week the site goes live.

A café needs different proof than a trade covering half the city. I ask what you want the site to win, then build towards that, not towards a template that looked fine on someone else’s phone.

Site live but the week stays quiet? Call 07900 141 380 with the URL and what you expected - calls, form fills, or neither - or write that to info@shaunallen.co.uk; the quote form works if typing is easier. I will mark what looks broken before anyone talks packages.