What should a proper trade website
include?

A homepage with one clear promise

The opening screen should identify the kind of business, the customer or work it serves and the next action. It does not need to explain every technical detail, but it must remove the first uncertainty quickly.

A generic line such as “quality solutions for all your needs” wastes the most valuable space. A customer should not need to inspect the footer to discover whether the company is a plumber, electrician or software supplier.

A page for each distinct commercial service

Important services deserve dedicated pages when the customer need, evidence and decision genuinely differ. An emergency repair, full installation and inspection are not interchangeable simply because the same trade performs them.

This does not justify hundreds of pages with one noun changed. A page should exist because it can answer a distinct intent with useful substance. Closely related questions can remain together on a strong pillar.

• What the service solves and when it is appropriate.
• The process, practical constraints and likely next step.
• Qualifications, standards or limitations that matter.
• Relevant photographs, projects and customer questions.
• A direct route to call, message or make a structured enquiry.

Real local relevance

Customers need to know whether the business genuinely serves them. A clear coverage page, project evidence, service-area knowledge and a consistent Google Business Profile can establish that relevance.

A list of every town in the county is not local expertise. Location pages are justified only when the business can provide distinct coverage facts, work, property context or customer information that changes the page meaningfully.

Proof that answers risk

The most persuasive proof depends on the service. Accreditations may matter for regulated work. Before-and-after photographs may matter for visual work. Clear process and project scope may matter for larger building work. Reviews matter across categories, but they should support rather than replace explanation.

Introduce the person or team honestly. State guarantees and response expectations carefully. Do not invent staff, premises, awards or customer outcomes to fill a visual gap.

A mobile enquiry route that respects the customer

Phone, form and messaging actions should be easy to reach without covering the page. The form should collect enough context to make the first response useful, use persistent validation and preserve the customer’s work if delivery fails.

After acceptance, the enquiry should enter an organised record with a unique reference. Analytics should record a genuine lead only after the server has accepted it—not when somebody merely focuses a form field.

Technical foundations customers rarely see

Descriptive titles, canonical URLs, semantic headings, internal links, crawlable content, a sitemap and appropriate structured data make the site easier to understand. Fast mobile delivery, adequate contrast, keyboard access and secure forms make it easier and safer to use.

Schema can clarify entities and page meaning, but it is not ranking dust. It must match visible content and cannot rescue a thin page.