What a Construction Company Website Needs to Win Enquiries
By Ali Sedighi, MBA · Last reviewed November 2026
A construction company website needs to do five jobs: say clearly what you build and for whom, prove it with documented projects, show the credentials that reduce a client's risk, make it easy to enquire from a phone, and load quickly. Design taste matters far less than those five. Most visitors arrive with a single question, which is whether this firm has done a project like theirs, and they decide within a minute. This guide sets out the pages a construction site should have, what belongs on the homepage and project pages, how to design the enquiry form, the technical standards to hold a developer to, and how to tell whether the site is earning its keep.
Key points
- Visitors want proof of similar completed projects, so the portfolio is the most important part of the site.
- State project types, sectors and service area on the homepage before any slogan or mission statement.
- Show licences, insurance, safety programme and warranty details where a cautious client can find them fast.
- Design for a phone first, with a tap-to-call number and a short, sensible enquiry form.
- Own your domain, hosting, content and analytics accounts outright, whoever builds the site.
In this guide
- Who visits a construction website, and what are they checking?
- The pages every construction site should have
- What belongs at the top of the homepage?
- How should projects be presented?
- Enquiry forms and calls: making contact easy
- Technical standards to hold your developer to
- How to set it up: a build sequence that avoids rework
- Measuring whether the website is working, with Canadian notes
- Common mistakes
- Frequently asked questions
Who visits a construction website, and what are they checking?
Four kinds of visitor matter. Prospective clients want evidence of similar work and a sense of how you operate. Architects, designers and consultants want to know whether you are a credible name to recommend. Lenders, insurers and procurement staff verify that the company is real and established. Job applicants and subcontractors judge whether you are worth working for. A good site serves all four without confusing any of them.
This is why a construction site cannot be a brochure with a slideshow. Each visitor is doing due diligence. They scan for project types, look for names and faces, check how recent the latest work is, and search for anything that signals risk. A site that has not been updated in years quietly says the company may be winding down, even when the yard is full.
The pages every construction site should have
Plan the site map before any design work begins. Each service and each sector you serve deserves its own page, because clients search and think in those terms. The projects section needs an index that can be filtered by type, and an individual page for each significant job. The about page should introduce the people who run projects, not only the founder's story.
Add the pages that support trust and recruitment: a process page that explains how a job runs from first call to warranty, a safety and credentials page, a careers page with current openings, and a contact page with a real address, a map and business hours. A subcontractor or supplier registration page is useful for larger firms and keeps those enquiries out of the client inbox.
- Homepage with services, sectors, area and featured projects
- One page per service and one per sector served
- Project index with filters and individual project pages
- About and team page with names, roles and photos
- Process, safety and credentials pages for cautious buyers
- Careers page and a separate subcontractor enquiry route
- Contact page with address, phone, hours and form
What belongs at the top of the homepage?
The first screen should answer three questions without scrolling: what do you build, for whom, and where. A plain statement such as commercial and light industrial general contractor serving the region, with a strong project photograph behind it, does more than any clever tagline. Put the phone number and an enquiry button in the header so they stay visible on every page.
Directly below, show routes into the site by client type or project type, then three or four featured projects, then proof: years operating, association memberships, safety certification and a few genuine client comments with permission. Avoid auto-playing video with sound, sliders that rotate before anyone can read them, and large blocks of text about values. Visitors came to see buildings.
How should projects be presented?
Treat each project page as a short record of the job. Lead with the finished photograph, then give the facts in a consistent panel: building type, scope of work, delivery method, duration and your role. Follow with a few paragraphs on the challenge and how the team handled it, then a sequence of progress and completion photos. Consistency across pages lets a visitor compare projects at a glance.
Quality beats quantity. Ten well-documented projects persuade more than sixty thumbnails with no explanation. Retire older work that no longer reflects the kind of contract you want to win. Get written permission before naming clients or showing identifiable interiors, and remove anything a client asks you to take down. Where confidentiality applies, describe the project by type and scale without naming it.
- Hero photograph of the completed project
- Fact panel: type, scope, delivery method, duration, role
- Short narrative of the main challenge and the solution
- Progress and completion photos with captions
- Related service link and an enquiry prompt at the end
Enquiry forms and calls: making contact easy
Many construction enquiries start on a phone, often from a parked truck or a site office. The phone number must be tappable. The form must be usable with a thumb. Ask only what an estimator needs to return the call prepared: name, contact details, project type, location, expected start and a description. Allow file uploads for drawings where your system supports it safely.
After submission, show a confirmation page that says when and how you will respond, and send the enquiry to more than one person so it cannot sit in a single inbox. Offer separate routes for careers and supplier contact so sales staff are not sorting through unrelated messages. Protect forms against spam with a quiet method that does not frustrate real visitors.
Technical standards to hold your developer to
Write the technical requirements into the project brief, because they are hard to add afterwards. Pages should load quickly on mobile data, which mainly means disciplined image handling. The site must be secure, backed up and kept updated. It should meet accessibility standards so that people using screen readers or keyboard controls can use it, which is also a requirement for some public sector clients.
Insist on a content system your own staff can use to add a project without calling the developer. Every page needs an editable title, description and heading. Structured data for the organisation and services should be in place at launch. When replacing an old site, map every old address to its new equivalent with redirects so you do not lose the search visibility you already have.
- Fast mobile load with compressed, correctly sized images
- Secure hosting, regular backups and software updates
- Accessible colour contrast, headings, alt text and keyboard use
- Staff can add projects and edit pages without code
- Redirect map from every old URL to the new one
How to set it up: a build sequence that avoids rework
Start with content, not design. Choose the ten to fifteen projects you will feature, gather photos and facts for each, and write the service and sector pages in draft. Only then brief a designer, because a layout built around real content will not need to be torn apart later. Agree the site map, the form fields and the tracking plan in writing before development starts.
During the build, review on a phone at every stage. Before launch, test each form, each phone link and each redirect, and confirm that analytics and call tracking are recording. After launch, assign one person to add a new project each month and to check enquiries are arriving. A site is finished the way a building is finished: it then needs maintenance.
- Select projects and gather photos, facts and permissions
- Draft service, sector and about page text
- Approve site map, form fields and tracking plan
- Design, build and review on mobile throughout
- Test forms, calls and redirects, then launch
- Schedule monthly project additions and checks
Measuring whether the website is working, with Canadian notes
Set up analytics with form submissions and phone calls recorded as conversions, and review them monthly. Look at which pages people land on, which projects they view before enquiring, and where they leave. Then go beyond the site: log each enquiry, whether it was qualified, whether an estimate was booked and whether the job was won. Divide the annual cost of the site and its upkeep by jobs won through it.
For Canadian firms, a few points apply. State provincial licences, warranty enrolment and workers' compensation standing accurately, since these vary by province. In Quebec and other bilingual markets, provide properly translated French pages. Publish a privacy policy that explains what the forms collect and why, and only add people to marketing lists with their consent. Refresh seasonal content before the building season opens each spring.
Common mistakes
- Opening the homepage with a vague slogan while hiding what the company builds three clicks deep.
- Uploading huge unedited camera files that make every project page slow to open on a phone.
- Letting the web developer register the domain and hosting in their own name, leaving you without control.
- Showing dozens of project thumbnails with no description of the scope, your role or the outcome.
- Launching a redesign without redirects from old addresses, which wipes out existing search visibility almost overnight.
Frequently asked questions
Should we use a template or a custom design?
A well-chosen template on a mainstream platform is fine for most small and mid-sized contractors, provided the structure, content and photography are right. Custom design makes sense when you need unusual functions such as a filterable project database or bid portal. Spend first on content and photos. A custom design filled with weak content will not persuade anyone.
How many projects should the portfolio show?
Enough to cover each service and sector you want to win, with at least two or three examples of each. For many firms that means ten to twenty detailed project pages. Remove old or off-strategy work as you add new jobs. A visitor should find a project resembling theirs within a couple of clicks.
Do we need to show prices on the website?
Most construction work is too variable for a price list, but silence on cost frustrates visitors. Explain what drives the cost of your typical projects, such as size, site conditions, finishes, structural changes and permitting, and describe how you prepare an estimate. This helps serious clients self-qualify and reduces enquiries from people whose expectations are far from reality.
How often should a construction website be updated?
Add a project whenever a notable job completes, and aim for at least one a month. Review service pages, team listings and credentials twice a year. Check forms and phone links monthly. A full redesign is only needed when the structure no longer fits the business or the technology is out of date, not on a fixed schedule.
What should we own when the website is finished?
You should hold the domain registration, the hosting account, the content system login with full administrator rights, the analytics and search console properties, and the original design and image files. Have this written into the contract before work begins. If the relationship with the developer ends, you must be able to move the site without starting again.