What a visitor saw
A normal contact form with no obvious warning that its destination was outdated.
First-hand website repair · Worcester
How we repaired a broken website enquiry route without rebuilding the site
This is a transparent record of work on WellKept Digital’s own live website. It explains the visible problem, the checks behind the repair and the result we could actually verify.
Repair verified 29 June 2026 · Case study published 12 July 2026 · No invented client, ranking or traffic claim.
The problem
The form looked normal, but the enquiry route was stale
A visitor could complete the form, yet the website was still trying to send the message through an older domain. The live server also did not have the correct route in front of the website catch-all, so valid submissions could miss the form handler.
What the server did
The enquiry path could fall through to the website router instead of reaching the contact service.
Why this mattered
A silent contact failure can cost real enquiries while the rest of the website still appears healthy.
The diagnosis
We followed one test message from the page to the mailbox
Instead of replacing the whole website, we checked each hand-off in the existing enquiry path.
- The form destination shown in the live HTML
- The public response returned after a test submission
- The server rule responsible for sending contact requests to the form handler
- The field names the handler could accept from the live form
- The business setting that controlled the receiving mailbox
The repair
Four bounded changes, not a rebuild
1. Correct destination
The form was changed to use the website’s own contact endpoint rather than the retired domain.
2. Correct server route
Contact requests were routed to the form service before the general website catch-all.
3. Compatible form fields
The handler was adjusted to accept the real fields used by the live form instead of relying on one exact field name.
4. Managed recipient
The destination remained controlled by the business contact setting, not hard-coded into the page.
Verification
What the completed check proved
A labelled test submission returned the expected success redirect, the delivery system recorded the message as sent and the test arrived in the monitored mailbox.
What it does not prove
One successful controlled test does not promise that every future email will bypass spam filtering. It also does not prove a Google ranking, customer enquiry, sale or revenue result. Those are measured separately.
A useful check for any business
Do not judge a contact form only by how it looks
A proper form check should submit a clearly labelled test, confirm the public response, confirm the server recorded the delivery and confirm the message reached the intended inbox. That is much more useful than seeing a green success message on the page alone.
Start with evidence
Want us to check your website’s visible enquiry route?
Send the website address. The free review requires no login and is returned in writing.