How do you handle Arabic RTL?

Tested every commit, not at the end. Layout, typography, navigation gestures, form direction, date / number formatting all work natively in both directions. We use logical properties (margin-inline-start vs margin-left) so the same code serves LTR and RTL without duplicate stylesheets. Arabic typography uses Tajawal or your brand font with proper line-height tuned for Arabic glyphs (English line-height usually feels cramped for Arabic).

Do you handle SEO migration when we move from an old site?

Yes — that's the highest-risk part of any rebuild. We crawl your current site, generate a complete URL inventory, map old → new URLs with 301 redirects (in batch SQL or Next.js redirects() depending on platform), and monitor Search Console for the first 60 days post-launch to catch any rank drops early.

Can our marketing team actually edit pages without calling you?

On WordPress yes — that's the whole point of the platform; we ship a properly-trained editing workflow with a starter content kit and 2-3 training sessions. On Next.js, edits run through a CMS (Sanity / Contentful / Notion-as-CMS depending on team size); we configure it so non-technical editors can change copy and images without touching code, but structural changes still need a developer.

What about Lighthouse performance and Core Web Vitals?

We enforce performance budgets in CI: any commit that drops Lighthouse below 90 fails the build. For Core Web Vitals — LCP under 2.5s, INP under 200ms, CLS under 0.1 are minimum bars on every page. Mobile is the audited target, not desktop. This isn't optional; Google ranks on this and your mobile users will notice.

Web & WordPress

Professional websites, portals, and web applications — from institutional and corporate sites to complex applicant management systems, LMS platforms, and supplier directories.

Book a Free Consultation

What does Arabic-first web development mean?

Arabic-first web development means building a site so that its Arabic right-to-left version works from the first commit, rather than mirroring an English layout at the end. Mantiqi builds corporate sites, portals, applicant systems and Moodle learning platforms this way — on WordPress when marketing edits copy daily, on Next.js when performance and integrations matter more — and maps old URLs to new ones so a rebuild keeps its search rankings.

Typical timeline: Platform decision in week 1, design and build in weeks 2–8, content and launch in weeks 8–10.

Why this matters

Most Saudi corporate websites either look like 2014 (Bootstrap template, slow, broken Arabic RTL) or were rebuilt last year by an agency that delivered something pretty but uneditable — every tiny copy change becomes a support ticket. The right pattern depends on what you actually need: WordPress with a properly-built theme for content-heavy corporate sites where marketing needs to ship copy daily; Next.js for product / SaaS sites where performance and integration matter more than CMS flexibility; Moodle / custom LMS for education clients. Mantiqi builds in whichever the use case actually warrants — and ships Arabic RTL that works on day one, not as an afterthought.

What We Deliver

Corporate & Institutional Websites

WordPress Development & Customisation

LMS (Moodle) Setup & Configuration

Applicant & Enrollment Systems

Supplier & Directory Platforms

Arabic RTL Support

SEO & Performance Optimisation

How we deliver

01
Brief + platform decision
Week 1
We map the site's purpose (lead-gen, content marketing, applicant intake, e-commerce, internal portal), who edits content (marketing, IT, mixed), traffic expectations, and integrations needed. Output is a written platform recommendation with TCO estimate.
- Site-purpose + audience scorecard
- Platform recommendation with rationale
- Editor / content-ops workflow
- 3-year TCO estimate
02
Design + build
Weeks 2–8
Design shipped iteratively in Figma, reviewed in 2-week cycles. Build follows the locked design with proper accessibility (WCAG AA), Arabic RTL tested every commit (not at the end), and Lighthouse performance budgets enforced via CI.
- Design system + per-page mockups
- Production build (WordPress / Next.js / Moodle)
- Arabic RTL tested every release
- Lighthouse 90+ on all pages
03
Content + launch
Weeks 8–10
Content migration from existing site (preserving SEO juice via 301 mapping), DNS cutover with rollback plan, and post-launch monitoring against the previous baseline (traffic, rankings, Core Web Vitals).
- Content migration + 301 redirect map
- DNS cutover + rollback plan
- 30-day post-launch monitoring
- SEO baseline preservation report
04
Maintain + iterate
Ongoing
Monthly maintenance covers WordPress / plugin updates with regression-tested rollback, SSL / security patches, performance monitoring, and a small bucket of design tweaks per month. Larger feature requests scoped per sprint.
- Monthly platform + plugin updates
- Security + performance monitoring
- Small design / copy change bucket
- Quarterly Lighthouse + SEO review

Frequently asked questions

WordPress when marketing edits copy daily and the integration surface is mostly forms / blog / email — the editor experience is genuinely useful. Next.js (or similar React-based static / SSR) when performance, integration with custom backends, or design fidelity matters more than CMS flexibility. Moodle / Joomla rarely a good default unless there's a specific reason. Custom only when an off-the-shelf platform genuinely doesn't fit (rare for content sites, common for product UIs).

Still have questions?

Our team is ready to help. Reach out and we'll get back to you as soon as possible.

Book a Free Consultation View Services

Free offer

Free site + SEO audit

Send us your current site URL. We'll send back a written audit covering Lighthouse scores per top-10 page, Arabic RTL issues, technical SEO gaps, accessibility WCAG findings, and a phased rebuild / improvement plan with effort estimates.

Get the audit