What a car workshop website in Dubai needs

A car workshop website in Dubai needs one page per service a customer would search for, a contact route that ends in WhatsApp, reviews quoted from Google rather than written for the site, and search basics done properly: unique titles, structured data that describes the business honestly, and a Google Business Profile that matches the site. That is what I built for Creative Auto Services, an independent garage in Al Quoz, and handed over in October 2026.

This is a write-up of one project, not a template that suits every garage. I have left out what the client paid and anything about how the site is administered.

Which pages does a garage website need?

The live site has a homepage, a services hub, eight service pages, about, a workshop gallery, an FAQ, a contact page, a privacy policy and terms. The eight services are the ones the workshop wanted to be found for:

• Car service
• Engine repair
• AC repair
• Brake repair
• Car diagnostics
• Denting and painting
• Oil change
• Suspension repair

Each one has its own page with a local title, for example "Car AC Repair in Al Quoz, Dubai", and its own written content: the symptoms the workshop handles, the checks involved and how to book the car in. Across the eight that came to about 10,000 words, all written for this site. A single "Services" page with a bullet list cannot rank for eight different searches, and it gives a customer with a noisy AC nothing to read.

What should the contact page do?

Get the customer to the workshop with enough detail to quote. The contact page on creativeauto.ae is a repair estimate, not an address page. It asks four questions: what the car is doing, how urgent it is, whether it can still be driven, and a name and UAE mobile number. Then it sends the answers to the workshop on WhatsApp, and the workshop replies with a price. A "skip, just message the workshop" link sits beside it for people who would rather type.

I chose WhatsApp over an email form, because a form that emails an inbox nobody watches is worse than no form. The page also says what the number is used for: only to send that estimate, and nothing else.

Should the website show repair prices?

Only once the owner has approved them. The estimator was built to show price ranges, but every figure in it was a placeholder, so it shows no AED amounts until the workshop signs off its price bands. Publishing a number a workshop has not agreed to is how a customer turns up expecting a price the mechanic never quoted. The structured data leaves prices out for the same reason.

How should a garage use reviews on its site?

Quote real ones and link to where they live. I quoted four reviews word for word from Google, and the site links through to the Google reviews. I also took the review and rating markup out of the structured data. Google treats reviews a business publishes about itself on its own site as self-serving, and a rating typed into the code stops matching Google the moment a new review arrives.

What does the search setup include?

• A unique title of 60 characters or fewer and a description of 140 to 155 characters on every page, with the local terms first.
• Structured data that describes the business as an AutoRepair, which is a type of LocalBusiness on schema.org, with each service, the FAQ and the breadcrumbs marked up.
• A sitemap submitted to Google Search Console, with each page's last-modified date taken from when its content actually changed.
• A preview card per page for WhatsApp and social shares, so a link sent to a customer shows the right service.
• One address for the whole site. The www version redirects to the bare domain, and every internal link uses the same form.
• The Google Business Profile checked against the site, and the mismatches that were left went on the client's list.

None of that guarantees a ranking. It removes reasons for Google to misunderstand the site, and it makes every page a clean result when someone searches for a specific repair.

What about photos of customers' cars?

Blur the plates before they go up. I pixelated the readable number plates on the photos used on the site, and the workshop staff got a simple upload page for the gallery that includes a blur tool and asks them to confirm plates and faces are covered before a photo is published. A workshop takes more pictures than any web designer will, so the tool has to be in their hands.

What did I leave off on purpose?

• Prices the owner had not approved.
• A founding year that mixed two facts. The site says the owner has been in the trade since 1998 and, separately, that this Al Quoz workshop opened in 2020. Merged into one line, either reads as a claim nobody made.
• Facts the client had not confirmed yet, such as a full street address in the structured data. Those wait for the owner.

How fast should a garage website be?

Fast enough that a customer standing next to a broken car on mobile data gets the phone number straight away. The site is static, with no JavaScript needed for layout or navigation, and small scripts only where something moves, like the homepage slider and the estimate flow. I have written up a bigger speed rebuild separately if you want the detail.

What does the owner get at handover?

The hosting on the workshop's own account, Search Console access, the privacy policy and terms, a working email address for privacy requests and the photo upload page. I have written that list up as its own article, because it applies to any business, not just garages.