.png)
.png)
.png)
How to Organise Problem-Led Navigation Without Hiding Core Services
By Blackbird Marketing
Problem-led navigation should support a trades website’s core services, not replace them. Keep a clear Services route in the main navigation, then add a smaller set of problem-led pathways for visitors who know what has gone wrong but do not know the technical name of the work required.
In short: Organise the site around two valid starting points: the service a visitor already knows they need and the problem they are trying to resolve. Both routes should lead to clear, relevant service information without creating a separate page for every symptom.
What should the main navigation contain?
The main navigation should make the business’s actual services visible at the first sensible level. A visitor who already knows the service they want should not have to choose between a series of symptoms before reaching it.
For most trades websites, a simple structure might include:
Services: the genuine areas of work the business provides.
Problems or advice: a limited set of recognisable customer situations.
About: relevant business information.
Areas covered: only where the trading area is accurate and useful.
Contact: a consistent route for an enquiry.
The labels and order will depend on the business. The important decision is that the core service structure remains understandable without forcing visitors to solve a problem-led puzzle first.
Why use problem-led routes on a trades website?
Customers often describe an outcome rather than a service. They may say that power keeps tripping, water is appearing where it should not, or a room needs changing, without knowing whether the answer involves a repair, replacement, installation or further investigation.
A problem-led route gives that visitor a useful starting point. It can explain what information matters, outline the possible categories of work and direct them towards the service that is relevant to the situation.
It must not present a remote diagnosis as fact. The purpose is to help someone understand the next step, not to confirm the cause of a property problem without the necessary checks.
How should services and problems work together?
Use a two-layer structure rather than two competing menus. The first layer names the business’s core services. The second presents selected problems that naturally lead into those services.
For example, a website might show its main service categories in the primary menu and then include problem-led links within the relevant service section. A visitor who starts with a problem can follow that route, while someone who already knows the service can go straight to the service page.
On a smaller site, the problem routes may not need their own top-level menu item. Short sections or clearly labelled links on the relevant service pages may be enough. The decision should be based on the number of genuine customer questions, not on a desire to create more navigation items.
Use customer language without making an unconfirmed diagnosis
Navigation labels should be understandable to a householder or property manager. A phrase such as “power keeps tripping” may be a more useful entry point than a technical term, provided the page then explains that several causes are possible and that the actual work may need checking.
Technical terminology can be introduced on the destination page. This lets the business explain the relevant service accurately without making the first click dependent on the visitor already knowing trade language.
When does a problem deserve its own page?
Create a separate problem-led page only when it represents a distinct customer question and can lead to a suitable service or enquiry route. A different heading alone is not enough.
Before adding a page, ask:
Does this problem describe a meaningful decision for the customer?
Will the page provide information that is not simply copied from an existing service page?
Does the business genuinely want enquiries about this situation?
Is there a clear service destination or next step?
Will a visitor understand why this page exists?
If the answer is no, improve the relevant service page instead. Several related problems can often be handled by one well-structured page, with short sections that answer the different starting questions.
For a separate view on deciding the appropriate number of service pages, see How Many Service Pages Should a Trade Website Have?.
What should each problem-led page explain?
A problem-led page should move the visitor towards a sensible decision rather than act as a dead-end article. It should connect the customer’s description with the business’s relevant service, while being clear about what cannot be confirmed from the information available.
Where appropriate, include:
The situation covered: describe the problem in plain language.
Possible categories of work: explain why the answer may vary.
Information that may matter: such as when the issue began, what has changed and whether access is available.
Relevant service information: explain why the linked service may relate to the problem.
Safety boundaries: avoid encouraging a visitor to carry out work that requires a qualified professional.
The next enquiry step: make it clear what the visitor can ask or provide when making contact.
Use cautious wording where the cause is uncertain. “This may have several causes and needs checking” is more useful and credible than stating that a particular repair is definitely required.
How do you stop problem-led navigation hiding services?
Keep service names visible in the primary menu, page headings and relevant links. Problem pages should signpost the service they relate to instead of making the visitor return to the homepage or search through a general list.
Do not rely on icons, images or vague labels to communicate the offer. A visible text link is easier to understand, and it remains clear when a mobile menu collapses or a visitor is using a keyboard.
Check that:
Every core service has a clear home.
A visitor can reach a service without first selecting a problem.
Problem labels describe recognisable situations rather than internal business categories.
Each problem route leads to a relevant destination.
Menus do not contain several near-identical categories.
Contact options do not cover labels or interrupt the information a visitor needs.
A problem-led route is successful when it gives uncertain visitors another way in without making the direct route harder for people who already know what they need.
How should the structure be tested?
Test the navigation from different starting points, not only from the homepage. Ask someone to find a known service, then ask them to find the right starting point for a problem without using the site search.
Look for hesitation, repeated backtracking, similar labels and pages that lead to the same destination without explaining the difference. Test the menu on a narrow screen as well as with a keyboard, because a structure that works in a desktop mock-up may be harder to use when the menu is condensed.
After launch, review the questions arriving through enquiries and the routes that appear to stop without a useful next step. That does not mean changing the navigation constantly. It means checking whether the labels, page relationships and service destinations still reflect genuine customer decisions.
When should the navigation be reviewed as part of a wider redesign?
A small site may only need clearer service labels, a few useful problem links and the removal of duplicated pages. A wider review is more important where the site has overlapping pages, an awkward mobile menu, outdated services or a redesign that could affect established page addresses.
Blackbird Marketing’s published website design service describes a review, plan, build and launch-or-improve approach. That is relevant when navigation needs to be considered alongside the structure of service pages and the practical work of maintaining the site.
When deciding whether that type of support is appropriate, review the published website design service and ask which proposed changes relate specifically to navigation, service pages, mobile use and any existing page addresses.
A final check before publishing
Write down the business’s core services and compare them with the proposed menu. Every service should have a clear home. Every problem route should have a clear reason to exist, a relevant destination and an honest explanation of what the visitor can establish from the page.
Then test three journeys: someone who knows the service name, someone who only knows the problem and someone who is unsure whether the business is suitable. If each person can understand what to do next without guessing, the navigation is supporting both discovery and conversion.
Ready to review your website structure? If problem-led routes are making core services harder to find, a structured website review can identify what should be simplified or connected. Discuss your website design requirements with Blackbird Marketing.
