ContentsTap to jump to a section＋
- Low traffic and visits without inquiries are different problems.
- Test a submission through storage, notifications and staff visibility, not just the success message.
- Fix evidenced bottlenecks before assuming the whole website needs replacement.
Locate the break before redesigning
A polished website with no inquiries does not prove the visual design has failed. Buyers may not find it, visitors may be the wrong audience, or submissions may not reach the responsible team.
Separate four stages: visibility, relevant visits, submission and follow-up. These practical checks are not a sales guarantee; demand, pricing and sales capability also matter.
Appearance gets noticed. Clarity, reliable inquiries and follow-up need their own checks.
1. Search visibility for the right service
In Search Console, review the service page over a meaningful period. Impressions and clicks cover Google Search, not every traffic source.
For impressions without clicks, inspect queries, titles and descriptions. State the actual service and audience without unsupported price or ranking promises. For low visibility, check indexing eligibility, the canonical URL and discoverable links. An indexing request does not guarantee a ranking.
2. Visitor fit
Free-tool visitors may be valuable but have a different intent from businesses commissioning a website. Review inquiries by landing-page group instead of judging the entire site by total visits.
Answer purchasing questions such as page structure, quote preparation and when to redesign. Use descriptive links to the relevant service at the point where readers need the next step.
3. Specific services and credible evidence
Explain audience, scope, deliverables, process and buyer responsibilities. Generic claims about creativity do not establish project fit.
Place approved project evidence near the relevant claim. Define post-launch support rather than implying all future work is free. Ask an unfamiliar reader what the company does, who it serves and how to inquire. Difficulty answering is a content problem worth fixing before adding effects.
4. A clear inquiry path
Choose a primary action for each page and make its label match the destination. A quote button should not send visitors to an unrelated homepage.
Check the middle and end of the article as well as the hero. Mobile navigation, chat widgets and banners must not cover the action. Keep alternative contact methods available. Place calls to action after useful scope or evidence rather than after every paragraph.
5. End-to-end form delivery
Submit clearly marked test data and check four separate outcomes: UI success, stored record, delivered notification and staff visibility. A success message alone does not prove an email arrived.
A stored record without an email points to notification delivery; an email without a visible admin record requires checks of storage, filters, pagination or sync. Locate the gap before bulk re-entry or deletion.
Test invalid inputs and network failures. Preserve entered information and give clear corrective instructions. W3C recommends requesting only information necessary for the process.
- Use labelled test records, not fabricated customer identities.
- Match timestamps, record identifiers and recipients.
- Inspect spam folders, rules and the receiving account.
- Exclude tests from customer totals.
6. Real mobile usability
Use a physical phone and mobile data to follow the service-to-form journey. Check readability, menu overlays, keyboard behaviour and layout shifts.
Core Web Vitals describe loading, responsiveness and visual stability. PageSpeed Insights can identify issues, but lab scores do not represent every real user. Fix blocked actions and unstable layouts first; do not sacrifice useful information just for a score.
7. Ownership and follow-up
Assign responsibility for each inquiry type and an absence handover. Promise response times only when operations can support them.
Track receipt, reply, qualification and next steps. Separate duplicates and spam; multiple emails in one conversation are not multiple customers.
Record the date and nature of each change. On low-volume websites, one or two extra inquiries do not establish causality. Start with technical verification and observed problems before attempting split tests.
Repair or rebuild?
Fix specific content, buttons and delivery problems first when evidence points there. Consider a redesign when information structure, maintainability and multiple usability issues need broader change. Preserve valuable URLs and content during migration.
Share the site and the suspected bottleneck with Friday Works. A goal such as 'service readers rarely request quotes' defines a more useful scope than 'make it look better'.
FAQ
Frequently asked questions
Should a website with no inquiries be rebuilt immediately?
No. First distinguish low traffic, wrong-fit visitors, unclear content and delivery failures. Fix a specific bottleneck before commissioning a complete redesign.
Does a form success message prove an email arrived?
No. Verify storage, notification sending, recipient delivery and staff visibility separately.
Does more traffic guarantee more customers?
No. Traffic must fit the offer, the page must support a decision, and inquiries must reach staff. Measure qualified inquiries as well as visits.
References
Sources used in this guide
We prioritise official guidance and primary technical sources. Visit each source for full context and the latest updates.