Building a Website Whose Job Is Enquiries

Start from the query list, not the homepage

Before choosing a layout, group your researched queries into the distinct jobs people are trying to get done. Each genuine group earns one page. If two groups would produce near-identical content, they are one page. This is how you avoid both a thin site and a bloated one.

A structure that holds up

• Home. What the site does, who it serves, the single main action.
• Service hub. The overview page that owns the core commercial term and links to every specific service page.
• Service pages. One per real job, each with scope, process, price logic, timeframe and its own enquiry path.
• Pricing. The most-read page on most service sites. Explain ranges and what changes them rather than hiding behind “contact us”.
• Coverage. Honest description of the area served — only as many area pages as you have real content for.
• Problem guides. Informational pages that capture earlier searches and link inward.
• Contact. Every way someone can reach you, with expected response time.

URL and internal linking

Keep URLs short, lowercase and descriptive, mirroring the hierarchy. Link the hub to each service page and back again, link guides to the relevant service page in context, and avoid orphan pages entirely. Internal links are both how visitors navigate and how crawlers understand what each page is for.

Page anatomy that converts

Lead with the specific outcome, not a slogan. State scope and price logic early. Answer the three objections every visitor has — cost, timing, trust — on the page itself. Put a form or call path within reach at the top and repeat it after the content. Keep one primary action per page.

Forms done properly

Ask for the minimum the recipient needs to respond. Use real labels rather than placeholder-only fields, keep everything keyboard-reachable, mark required fields clearly, validate on the server as well as in the browser, and show honest success and failure states. Never show a success message unless the submission was actually stored or sent.

Explain at the point of collection who receives the details and why. Keep marketing consent as a separate, unticked option — bundling it into the enquiry is both bad practice and, in many jurisdictions, not valid consent.

Technical requirements

Pages must render meaningful HTML, return correct status codes, carry one self-referencing canonical each, load quickly on a mid-range phone, and appear in a sitemap that lists only real indexable pages. A missing page must return a genuine 404, not a 200 homepage. Run a launch QA pass and fix what it finds before submitting anything for indexing.

What to leave out

No fabricated reviews, invented certifications, fake “as featured in” logos, countdown timers or stock photos presented as your own work. These convert slightly better for a short while and destroy the asset’s value permanently.