Saudi construction lead-generation website

Emtidad Riyadh: a construction company website case study

Emtidad Riyadh is an Arabic website for a contractor covering construction, renovation, finishing, structural work, and maintenance in Riyadh. The journey helps a property owner understand the right service, review relevant work and delivery stages, then send location and project details through a structured WhatsApp request.

Project goal

Help someone searching for a contractor understand the service, share project and location details, and start a useful WhatsApp conversation.

Visit the live website Review the related service

People and decisions

How visitors move through this project

A useful case study starts with the people, the decision they need to make, and the information that helps them take the next step.

The visitor journey

A property owner opens the home page or the local service page that matches the job.
They review the scope, project stages, examples, and service-specific answers.
They submit an inspection enquiry or use phone and WhatsApp actions from their mobile.

Who this example is for

Contractors and renovation firms serving a defined city or region.
Businesses that need to inspect a job before preparing a quote.
Local service teams that need fast pages without a heavy CMS.
Teams that want project details delivered to WhatsApp in a usable format.

The challenge

What the website needed to solve

Searching for a contractor carries high intent and high uncertainty around scope, price, delays, and accountability. A generic company page does little to reduce that uncertainty. The site needed focused local service pages, trust at the right moments, and a mobile site-visit request that did not force the customer into a long phone call or a closed email form.

The solution

How the delivery was structured

The site was built with Astro as a fast Arabic static experience. Separate pages cover extensions, renovation, villa finishing, structural work, and building maintenance. A site-visit form collects service, district, and project details before opening WhatsApp with a prepared message. Project examples, process content, FAQs, mobile contact actions, and GeneralContractor and FAQPage data support the decision journey.

Implementation

Core parts of the project

Local service architecture

A homepage focused on general contracting in Riyadh
Separate routes for extensions, renovation, villa finishing, and structural work
Building maintenance, projects, and contact paths
Service content connected to local customer questions

Structured site-visit request

Fields for name, phone, service, district, and project description
A prepared WhatsApp message carrying the request context
Clear price, call, and WhatsApp actions
Persistent mobile contact access at the decision point

Trust before quotation

Content addressing common concerns before construction starts
Services, process, project, and FAQ evidence
Clear explanation that an estimate depends on site condition and scope
Actions tied to an inspection or useful project details

Astro and technical search foundations

Static HTML pages with optimized imagery and a local Arabic font
Page-specific titles, descriptions, and canonical links
WebSite, WebPage, GeneralContractor, and FAQPage structured data
Intentional noindex on the preview domain until a production domain is approved

AstroTypeScriptStatic Site GenerationCSSJavaScriptArabic RTLSchema.org

Architecture and trade-offs

Why the project took this approach

Key implementation decisions

Use Astro and static pages because the local marketing site does not need a database to explain and sell the service.
Create separate service pages rather than placing every construction term on one page.
Turn the form into a structured WhatsApp message that carries service, neighbourhood, and project details into the conversation.
Keep the Cloudflare Pages preview out of search until the production domain and business details are approved.

Constraints to account for

Closely related services need distinct pages and intent to avoid near-duplicate content.
A useful estimate depends on area, site condition, and finish level, not a generic headline price.
Visitors often use a phone and need a fast contact route that preserves the context of the request.
The current Pages address is a preview environment, not the final indexed production domain.

Delivery ownership

Responsibilities and ownership after delivery

Plan page intent and service content.
Design the Arabic interface and mobile enquiry path.
Develop the Astro site and service pages.
Connect the inspection form to WhatsApp and prepare metadata and structured data.
Set up the preview deployment with the appropriate indexing controls.
The current public Pages address is a noindex, nofollow preview, not the final production domain.
Indexing should begin only after the production domain and business information are reviewed.
The case study does not claim customer, advertising, or sales figures.

Planning a similar platform

What to prepare before a similar build

The actual service list and areas served.
Approved images and descriptions of completed work.
The business phone, WhatsApp number, and final production domain.
The qualification questions needed before an inspection or quotation.

Key lessons

Lessons from this delivery

Local service websites should make the service scope and next step clear before relying on slogans.
Sending the neighbourhood, service type, and job description in the first enquiry saves a round of questions.
Local service pages need different answers and useful content, not just a swapped service name.
Keep a preview environment out of search until the final domain and business information are ready.

The live preview demonstrates the service pages and WhatsApp inspection path; it is explicitly identified as a noindex preview rather than a final indexed site.

Delivered outcome

What changed through the project

Multiple contracting services separated into routes customers can understand and reach directly
Less pre-contact friction through a WhatsApp message containing the essential project details
A practical mobile journey for property owners in Riyadh
Local service pages and structured data prepared for a final production domain
Preview and future production indexing kept separate to avoid duplicate search versions

Handover scope

Project deliverables

Arabic Astro construction company website
Dedicated local service pages
Projects and contact routes
Site-visit request connected to WhatsApp
Mobile call and WhatsApp actions
FAQ, process, and trust content
Metadata, canonical links, and structured data
Cloudflare Pages preview configured as noindex

Related scope

Planning a project with similar requirements?

Share the goal, content, languages, integrations, timeline, and ownership requirements for a specific recommendation.

Send the project brief Read the Arabic case study