Engineering Consultancy Website: Projects, Team, Trust
Plan an engineering consultancy website in Egypt: service pages, project case studies, named engineers, credentials and a short brief form, in Arabic and English.
An engineering consultancy website has an unusual job. Nobody buys design, supervision or technical review from a homepage. The visitor is a developer, a contractor or a property owner who is deciding whether your judgement can be trusted with a building, a plant or a budget. They cannot inspect that judgement directly, so they look for evidence of it: who the engineers are, what you have actually delivered and how you talk about problems. A good site makes that evidence easy to find and honest to read.
In short: organise the site around services, project case studies and the named engineers behind them. Show credentials as issued, describe projects with scope and your role, avoid unverifiable claims, and end every page with a short way to send a brief. Write Arabic and English separately if you work with both local and international clients.
Who reads a consultancy website, and what they want
Three readers arrive at a consultancy site, and they want different things.
- The owner or developer wants to know whether you have handled something like their project and who would handle it.
- The contractor or main consultant is looking for a specialist to add to a team and wants discipline, capacity and references.
- The procurement or tender reviewer checks that the company exists, is properly registered and can show relevant experience.
All three skim. They read headings, project titles and names before they read paragraphs. Google's guidance on helpful, reliable content emphasises showing who is behind the content and their real experience, which is exactly what these readers are checking.
The pages an engineering consultancy website needs
| Page | Purpose | What to include | What to avoid |
|---|---|---|---|
| Home | Say what you do and for whom | Disciplines in plain words, two or three featured projects, contact button | Slogans such as "excellence in engineering" with nothing behind them |
| Services (one page per discipline) | Match the visitor's need | Structural, MEP, infrastructure, supervision, review: scope, deliverables, typical stages | One long page listing everything in one paragraph |
| Projects | Provide proof | Name or type of project, location, your role, scope, year | Projects you only touched briefly, presented as yours |
| Team | Put names to judgement | Engineers with discipline, years of practice, memberships as issued | Anonymous "our experts" |
| Credentials and registrations | Reassure procurement | Company registration, professional memberships, quality certificates as issued | Logos of bodies you are not actually registered with |
| Insights | Show how you think | Short signed technical notes, dated | Copied standards text or generic advice |
| Contact | Receive a brief | Office address, phone, short brief form | A form that demands full project documents up front |
Small offices often skip the team page because they feel too few to list. That is a mistake. A consultancy sells people, and three named engineers with real backgrounds are more persuasive than a corporate paragraph.
Write project pages that prove something
The project page is the heart of the site. Each one should tell a short, specific story rather than hang a photo gallery on a title.
- The brief. What the client needed, in a sentence or two.
- Your scope. Design, supervision, review, studies or a combination; and which stages you covered.
- The challenge. One technical or practical difficulty, such as a tight site, a soil condition or a phasing constraint.
- What you did about it. Describe the approach in terms a non-engineer owner can follow.
- The outcome. What was delivered, stated factually. If you cannot quote a number, do not invent one.
Always ask the client before publishing a project that is not public, and respect confidentiality clauses. A safe pattern is to describe the type, location at city level and your role, without naming the client when you do not have permission. Do not publish drawings or details that clients consider proprietary.
Credentials: show them as issued
Procurement teams look for registrations and professional memberships. List them exactly as issued, with the holder's name where it is personal rather than company-wide, and check which details the relevant bodies actually require or allow you to display. Never display a logo or a number you cannot document. A short, accurate list is stronger than a wall of badges, and an inaccurate claim on a public website can end a tender conversation.
Two languages for two sets of clients
Many Egyptian consultancies serve local developers in Arabic and regional or international clients in English. Write the two versions separately. The Arabic version often leads with relationships, project types and local regulatory experience; the English one with disciplines, standards you work to and the languages your team handles. Our guide to company profile websites covers how a corporate profile differs from a marketing page, and the earlier notes on contractor company websites show how the contractor's view complements yours.
Make it fast, readable and easy to cite
Engineers read on large screens at the office, but owners often open links on a phone from a message. Test both. Compress project images, keep tables readable on narrow screens and give each service and project its own address so that people can share the exact page. Google's Core Web Vitals explain the loading and stability measures worth meeting.
For search, a few habits matter more than tricks:
- One page per discipline and per notable project, each with its own title and description.
- Plain terms in headings. Use the words clients use before the words the standards use.
- Structured data for the company, such as the ProfessionalService type on schema.org.
Nobody can promise a ranking. Measure instead how many briefs arrive and from which pages.
How WorldSite helps consultancies
WorldSite is a no-code website platform with 13 templates, including designs suited to companies and professional services, and pages that run in Arabic and English with correct right-to-left layout. You can build a page per discipline and per project, publish dated technical notes on the built-in bilingual blog, and receive briefs in your dashboard instead of a shared inbox. The Pro plan adds a custom domain, analytics and SEO tools, and team members with roles, so a project coordinator can add a case study without access to everything else.
WorldSite is a website platform. It does not manage proposals, drawings or project files, so keep those in the systems your office already uses. To plan the overall site, start with our guide to website design in Egypt, and for keeping it current our notes on website maintenance.
A launch check for a consultancy site
Read the site as a procurement reviewer. Is the legal company name and address on every page footer? Can you find three relevant projects in two clicks? Do the team pages name people and not just titles? Does each credential match a document you could produce on request? Then read it as a prospective client: can you send a brief in under a minute from your phone? Fix what fails, and set a quarterly reminder to add the latest finished project, because a portfolio that stops in an earlier year signals a firm that has gone quiet.
FAQ
What pages does an engineering consultancy website need?
A home page, one page per discipline, a projects section with individual case studies, a team page with named engineers, a credentials page, short technical notes and a contact page with a brief form.
How do I show projects without breaking client confidentiality?
Ask permission first. If you cannot name the client, describe the project type, the city, your role and the scope. Do not publish drawings, values or details that the client treats as private.
Should a consultancy website show prices?
Usually not. Consulting fees depend on scope, so explain how you scope and quote, list what a typical engagement includes, and invite a brief rather than publishing figures that will be wrong for most projects.
Do I need Arabic and English versions?
If you work with both local developers and international or regional clients, yes, written separately for each. If you serve one market, start with its language and add the other when you have the time to do it properly.
Can WorldSite manage my project files and proposals?
No. WorldSite is a website platform and does not handle proposals, drawings or project documents. Use it to present your firm and receive briefs, and keep project work in your existing systems.
By Mahmoud Fathy, Web-Builder Solutions Lead at WorldSite.
Show your judgement through named engineers and honest projects: build your consultancy website on WorldSite.
Planning your consultancy website? Ask us
Tell us your disciplines, clients and languages, and we will reply with the practical next step.