How to Choose a Web Development Agency in Riyadh
- Ask who writes Arabic, who designs RTL, and who owns hosting, analytics and the CMS after launch.
- A Riyadh agency should show live bilingual sites, not only English mockups.
- Scope the first release: pages, languages, integrations, and who publishes content later.
- Do not sign a build that leaves ad accounts, Search Console or the domain registrar in the vendor's name.
Choosing a web development agency in Riyadh is less about the slideshow and more about who can ship an Arabic-and-English site that a Saudi team can run after the agency leaves. Many proposals look the same: a stack, a timeline, a homepage animation. The differences that matter are language, ownership, and what “done” includes. This guide is a buying checklist, not a catalogue of frameworks.
What the site has to do in Saudi Arabia
Most commercial sites here have to work in Arabic, often in English as well, on a phone first, with a path to enquire that someone on your team actually answers. They also have to be findable: titles, a sitemap, analytics, and Search Console in your accounts. A pretty export that you cannot edit, cannot measure, and cannot show in Arabic is not a business website.
Google’s SEO starter guide is the floor for the technical side. For two languages, add the multilingual rules: separate URLs, self-canonicals, hreflang. Eclipse’s notes on bilingual SEO in Saudi Arabia cover that layer. The agency you hire should already work that way, not discover it at launch.
Questions that separate a studio from a template shop
- Who designs RTL? Ask to see Arabic pages they have launched — navigation, forms, numerals, mixed English brand names inside Arabic sentences. A mirrored English layout is not RTL design.
- Who writes the Arabic? Developer-translated strings read like developer-translated strings. Copy should be written in Arabic, then implemented.
- What can your team edit on day 31? If every comma requires a change request, you bought a hostage, not a site.
- Where does the site live? Domain registrar, DNS, hosting, and TLS certificates should be in your company’s name, with the agency as an invited operator.
- Where does measurement live? Google Analytics, Tag Manager, Search Console, and any pixels: your accounts, their access. Same rule as ads.
- What happens to environments? Staging URL, backups, and a documented deploy path. “We upload from a laptop” is not a process.
- Which integrations are in the first release? Forms, CRM, payments (mada, Apple Pay, Tabby/Tamara only if you actually need them), booking, ZATCA invoicing — each one is a project. List them, do not nod at “and APIs.”
Scope a first release you can launch
Write a one-page brief before you take proposals:
- Languages and who owns each.
- Page list for version one (not the five-year information architecture).
- The primary conversion (form, email, WhatsApp — whichever you staff).
- Must-have integrations versus later.
- Who will publish news, jobs, and case studies after launch.
- Examples of sites you respect, and why (speed, Arabic type, enquiry path — be specific).
Ask each agency to quote that brief, not a generic “corporate website” package. Compare apples. A lower fee that omits Arabic, SEO essentials, or training is not cheaper.
Technical quality you can test before signing
| Test | What to look for on their live work |
|---|---|
| View-source / disable JS | Main copy still present. A blank shell is a crawl risk. |
| Mobile | Tap targets, Arabic line length, no horizontal scroll. |
| Title tags | Unique, not “Home” on every URL. |
| Language | html lang matches the page; Arabic URLs are not English with a flag icon. |
| Forms | A submission you can complete on a phone, with a confirmation that is not “mailto: only.” |
| Performance | Hero images sized for the screen; no four unused sliders. |
You do not need to be an engineer to run these. Open three of their launched sites as a customer would.
Contracts and handover
- Deliverables: page list, languages, components, and integrations in writing.
- Source: repositories or exportable theme files, not only a page builder login the vendor keeps.
- Licences: fonts, stock, plugins — transferred or listed with renewal dates.
- Warranty window for bugs after launch, and an hourly rate after that, so you are not surprised.
- Handover session recorded, with admin users in your domain emails.
If the agency insists the only login is theirs, stop. That is not a partnership; it is a lock-in.
Content, SEO and the build must share a sitemap
A development project that treats SEO as a phase after launch usually ships with duplicate titles, missing H1s, and a sitemap that still lists test URLs. Put the URL list in the same brief as the page designs. For every URL in version one, name the language, the primary query in that language, and the page it should not compete with. The developers then implement canonicals, hreflang and robots as part of the build, not as a marketing ticket in month four.
If you already have a WordPress or static export, ask the agency to inventory it before they propose a new stack. Migrations that change every URL without 301s throw away years of Search Console data. Eclipse has seen that cost on more than one Saudi rebuild; it is cheaper to map old paths first.
Accessibility and forms are not extras
Arabic sites fail in the same places English sites fail, plus a few more: labels that are not tied to inputs, error messages only in English, and buttons that cannot be used with a keyboard. You can test this without a lab: tab through the form on a laptop, submit it empty, and try it on a mid-range Android phone on cellular. If the agency cannot sit with you while you do that on a staging URL, they are not ready to launch.
The enquiry path is the product. A site that looks expensive and cannot send a brief to marketing@yourdomain is not done. Decide before kickoff whether the form hits an API, a CRM, or email, and who is on call when it fails. Do not leave mailto: as the only production path unless you have accepted that most mobile visitors will bounce.
How this relates to marketing
A site that cannot rank or convert makes Ads and SEO more expensive. The development brief should name the queries and campaigns the pages will support. Conversely, do not ask a media team to “do SEO” on a site they cannot change. Eclipse builds sites as website development in Saudi Arabia and runs the marketing on the same measurement. If you already have a site, the useful first step is often a technical and content inventory, not a full rebuild.
Bring the brief, three competitor or peer URLs, and who on your side will own content. Do not bring a 40-page feature list for version one.
Frequently asked questions
Should we hire a local Riyadh agency or an overseas studio?
Either can build. What you cannot outsource blindly is Arabic copy, RTL design review, and someone in your timezone who can fix a form on a business day. Ask where those three sit.
Is a website builder cheaper than custom development?
It can be, if the builder can do bilingual RTL, your integrations, and handover in your accounts. Compare the brief, not the tool logo.
When is a rebuild justified?
When you cannot edit, measure, or add an Arabic page without the vendor, or when Core templates block the enquiry path. If the site is merely dated, a content and SEO pass is usually first.
Sources: developers.google.com · developers.google.com