Contact path checklist · published July 31, 2026
When Customers Can't Call or Message You From Your Site
Your site is up. The phone number is right there at the top. The form loads. And the phone is not ringing the way it used to.
By Christopher Buchner, founder of PruneQ
The first instinct is usually to buy something. More traffic, more ads, a redesign. Before spending on any of that, it is worth checking whether the path between wanting to contact you and actually contacting you still works. It is free to check, it takes about ten minutes, and it fails more often than most owners expect.
What I checked, and what I found
On July 30, 2026, I checked 14 small business websites, all heating and cooling contractors, against their live pages. Real companies, real pages, loaded that day. I was looking for one thing: something on the page a customer would notice, and could confirm for themselves in ten seconds.
Twelve of the 14 still had one. Three of the twelve contradicted themselves on a basic fact a customer checks before getting in touch: which phone number, which town, which service area. Two different phone numbers on one page. An address in one town with a sentence below it saying the business is located in a different town. One service area at the top of the homepage and a different one further down.
The rest were unfinished pages and copy errors sitting on the routes customers use. Website builder placeholder text still showing on a service page. Buttons across a homepage still carrying the builder's default label instead of saying what they do. A sentence directly above a contact form with a word missing from it.
Here is what that number is not. It is not a survey. Those 14 sites were not random, they came from a list I had already collected because I suspected something was wrong with them. So the right way to read it is that on a set of sites picked because they looked shaky, most of them were, and the problems were sitting in plain sight rather than buried in the code. Nothing about the count tells you what share of all websites have these problems, and I am not going to pretend otherwise.
None of these sites were broken in the technical sense. Every page loaded. The phone numbers were clickable. The forms submitted. The problems were all in the layer above that, where a person is deciding whether to bother.
No business is named here, and nothing distinctive enough to identify one is quoted. The point is the pattern, not the companies.
The contact path is a chain, not a button
Most people picture the contact path as one thing, the form or the phone number. It is actually four things in a row, and a customer only gets through if all four hold.
Can they find it
The route to contacting you has to be visible on the page they landed on, not only on a contact page they have to go looking for.
Can they use it
On a phone, the number has to be tappable, the form has to be operable, and the fields have to be labelled.
Can they tell which answer is real
If your site gives two phone numbers, two addresses, or two service areas, the customer has to guess. Some of them will guess by leaving.
Does it reach you
A form that submits and goes nowhere looks identical to a form that works, from the customer's side and from yours.
Fix them in that order. There is no point testing form delivery on a form nobody can find.
Eight checks you can run yourself
Run all of these on a phone, not a laptop. Most of what fails, fails on phones.
Check 01
Tap the phone number
Open your homepage on your phone and tap the number where it appears at the top of the page. It should start a call. If it only selects the text, it is not a link, it is a picture of a number or plain text.
Test it: Tap it. That is the whole test.
Check 02
Count the phone numbers
Read your homepage top to bottom and write down every phone number on it. Then do the same on your contact page and in the footer. They should all match. Old numbers survive in footers and on service pages for years after everyone has stopped using them.
Test it: If the list has more than one number on it, that is today's fix.
Check 03
Check that the address and the service area agree
Read only the address lines and only the service area lines, on the homepage and the contact page. A customer deciding whether you come to them needs one answer, not two.
Test it: Say your service area out loud, then find the sentence on the site that says it. If you cannot find one sentence that says it, that is the gap.
Check 04
Look for unfinished text on the routes customers use
Website builders leave placeholder text behind, and it lands on the pages nobody revisits. Service pages, gallery pages, and testimonial blocks are where it hides. Words that describe a page element, like a bare label reading Button or a heading reading Title or Question, mean a section was never finished.
Test it: Open every page linked from your main menu and skim for words that describe a page element instead of your business.
Check 05
Submit your own form from an outside address
Not from your own email, and not from the same device you built the site on. Use a personal address on a different provider.
Test it: Submit it, then wait ten minutes and check your inbox and your spam folder. If nothing arrives in either, the form is not reaching you, and it may not have been for a while.
Check 06
Read the confirmation the sender sees
After submitting, what does the page say? A bare thank you with no further information leaves the customer wondering whether it went through. It should say the message was received and roughly when they will hear back.
Test it: Read it as if you had never seen the site before. Would you know it worked?
Check 07
Check who is watching the inbox
Forms often deliver to an address somebody set up once and nobody checks. The same goes for the voicemail box on a number that was forwarded twice.
Test it: Find out who opened that inbox last, and when. If nobody knows, that is your answer.
Check 08
Check the same path on a slow connection
Turn off wifi and load your homepage on mobile data. Contact sections that depend on a script or an embedded widget can fail quietly when the page loads slowly, and the rest of the page looks fine.
Test it: Load it, wait, and confirm the number and the form are both actually there.
A sensible repair order
- Fix anything that stops a customer reaching the contact route at all.
- Fix contradictions. Pick one number, one address, one service area.
- Fix unfinished text on the pages your menu links to.
- Fix the confirmation message, and confirm somebody is watching the inbox.
- Write down what you changed and the date. You will want that later.
That order handles access before appearance, and truth before polish.
What this does not tell you
A clean contact path does not mean the phone will ring. It removes reasons it would not. Those are different claims and it matters that they stay separate.
I also cannot tell you how many customers any of these problems cost a business, and neither can anyone else, because nobody can see the people who left. What can be said is what is on the page, and whether it is still there tomorrow. That is the part worth being precise about.
If you want the longer version of this for a consultant or advisory site, the website cleanup checklist for consultants covers buyer clarity, crawlability, identity, and measurement alongside the contact path. If you would rather someone else ran the checks, that is what PruneQ does.