CUSTOM WORDPRESS DEV

Custom WordPress Development for Qatar. Arabic and English, Built Properly From the Start.

Ignited Nepal builds custom WordPress websites for businesses and organisations in Qatar that need a bilingual Arabic and English presence built correctly. Arabic RTL requires a custom theme, not an Elementor RTL plugin that partially mirrors a left-to-right layout and produces inconsistent results. We build the RTL layout, the CMS architecture, the ACF field groups, and the Gutenberg block library from the ground up, in both languages, with Core Web Vitals optimised and Git version control throughout.

Request your WordPress Diagnostic → View the evidence →
Bilingual Arabic RTL and English WordPress builds · Custom theme, not an Elementor RTL plugin · ACF field groups and Gutenberg blocks in both languages · Core Web Vitals optimised
This is for you if

Who This Is For

Your WordPress site was built for an international audience and has never been fully localised for Arabic. You are missing a significant portion of your potential audience and sending a clear signal that the Arabic-speaking market is not a priority. You need a proper bilingual build, not a machine translation overlay.

Your current site uses Elementor with an RTL plugin and the Arabic version looks almost right. Almost. Certain elements still align incorrectly. Some components flip when they should not. The editorial team dreads touching the Arabic pages because unpredictable things happen. You need a custom theme where RTL is built in, not bolted on.

You have a functioning WordPress site for your home market and you want to reach Qatari customers with a localised presence. Your existing site was built for LTR content, English typography, and Western navigation conventions. Adapting it for Qatar means rebuilding the theme for RTL, adding Arabic as a first-class language, and restructuring the editorial workflow so your local team can publish in Arabic independently.

What's broken

What's Broken

Elementor RTL Plugins Do Not Produce Reliable Right-to-Left Layouts

Elementor was designed for left-to-right content. RTL plugins apply a CSS transformation to mirror the layout. This works for simple pages but breaks on complex components: navigation dropdowns, sliders, form fields, card grids, and modal overlays all behave unpredictably because the RTL transformation is applied after the component is rendered, not during its construction. A custom theme builds RTL as the primary layout mode for Arabic pages, not as a post-render modification.

Your Arabic Content Is an Afterthought in Your CMS

If your WordPress content model was built for English and Arabic content was added later, your editorial team in Qatar is working around a structure that was not designed for them. Field labels are in English. Post type descriptions assume English content. The editorial workflow assumes LTR composition. A properly built bilingual WordPress site treats Arabic content as structurally equal to English content, with Arabic-language editorial interfaces for staff who work in Arabic.

Your Typography Does Not Handle Arabic Script Correctly

Arabic typefaces have specific requirements: contextual letter forms, correct kashida extension, proper naskh or kufi rendering, and text direction that affects not just reading order but punctuation placement, number display, and list formatting. A theme that uses a generic web font stack for Arabic, without specifying an appropriate Arabic typeface and configuring it correctly, produces text that is legible but uncomfortable for native Arabic readers.

Your Site's Performance Suffers From Unoptimised Builds

Custom WordPress builds for Arabic-language sites often carry the same Core Web Vitals problems as English-language sites built on page builders, plus additional performance costs from unoptimised Arabic font loading. Large Arabic web font files without subsetting or display optimisation add significant weight to every page load and delay Largest Contentful Paint, particularly on mobile connections common across Qatar.

What we engineer

What We Do

Technical Specification

We document the full bilingual build before development begins. Custom post types, ACF field groups, Gutenberg block list, Arabic and English URL structure, language routing, font loading strategy for both Arabic and Latin typefaces, and hosting configuration. Both language versions are fully specified. You review and approve before any code is written.

Custom Theme With Native Arabic RTL

We build a custom WordPress theme where Arabic RTL is not a plugin modification of an LTR layout. Navigation, button placement, text alignment, form fields, card components, and typographic rhythm are all designed for RTL as the primary reading direction on Arabic pages. The same theme serves English pages in LTR without compromise. Neither language version is a modified version of the other.

Arabic and English Typography

We select and configure appropriate typefaces for both Arabic and English content. Arabic typefaces are loaded with subsetting and font-display optimisation to minimise render-blocking weight. Contextual letter forms, correct baseline alignment, and Arabic punctuation placement are all tested across browsers and devices before launch.

Custom Post Types and ACF in Both Languages

We configure custom post types and ACF field groups for your content model with Arabic-language field labels and editorial instructions for your Arabic-language editorial team. Team profiles, news articles, service descriptions, project portfolios, or whatever structured content your organisation publishes. Both language versions of each post type share a common structural model with language-linked entries.

Gutenberg Block Library for Arabic and English

We build a custom Gutenberg block library where every block functions correctly in both Arabic RTL and English LTR. Internal block alignment, icon placement, directional arrows, and form field labels all adapt to the active language. Editors working in Arabic see a block editor experience that is native to RTL, not a mirrored version of an LTR editor.

Core Web Vitals Optimisation

We optimise Core Web Vitals for both language versions. Arabic font loading is handled with subsetting and preload hints. Images are served in optimised formats with correct lazy loading. Critical CSS is inlined for above-the-fold content. Script loading is deferred where it does not affect interactivity. We target a pass on LCP, CLS, and INP for both Arabic and English pages, on both mobile and desktop.

Staging, Git, and Launch

We build on staging throughout, manage the codebase in Git with a documented deployment process, and launch to production after full QA in both languages. Editorial documentation is provided in Arabic for your Arabic-language editorial team and in English for your technical team.

Request your WordPress Diagnostic →
What changes

What Changes

Before
After
Before Elementor was designed for left-to-right content. RTL plugins apply a CSS transformation to mirror the layout. This works for simple pages but breaks on complex components: navigation dropdowns, sliders, form fields, card grids, and modal overlays all behave unpredictably because the RTL transformation is applied after the component is rendered, not during its construction. A custom theme builds RTL as the primary layout mode for Arabic pages, not as a post-render modification.
After A custom WordPress site with native Arabic RTL, correct Arabic typography, and an Arabic-first editorial experience communicates that your organisation takes the Arabic-speaking market seriously. The difference between a properly built RTL site and an Elementor RTL plugin site is visible to Arabic readers immediately.
Before If your WordPress content model was built for English and Arabic content was added later, your editorial team in Qatar is working around a structure that was not designed for them. Field labels are in English. Post type descriptions assume English content. The editorial workflow assumes LTR composition. A properly built bilingual WordPress site treats Arabic content as structurally equal to English content, with Arabic-language editorial interfaces for staff who work in Arabic.
After ACF field groups with Arabic labels, a Gutenberg block library that works correctly in RTL, and editorial documentation in Arabic give your local team a CMS they can use confidently. Content updates do not require escalation to a developer because the editorial interface was built for the people using it.
Before Arabic typefaces have specific requirements: contextual letter forms, correct kashida extension, proper naskh or kufi rendering, and text direction that affects not just reading order but punctuation placement, number display, and list formatting. A theme that uses a generic web font stack for Arabic, without specifying an appropriate Arabic typeface and configuring it correctly, produces text that is legible but uncomfortable for native Arabic readers.
After Arabic font loading is one of the most common causes of Core Web Vitals failures on bilingual Arabic WordPress sites. Addressing it at the build stage, with proper subsetting and loading strategy, removes a persistent performance deficit that affects search visibility and user experience on every Arabic-language page.
Before Custom WordPress builds for Arabic-language sites often carry the same Core Web Vitals problems as English-language sites built on page builders, plus additional performance costs from unoptimised Arabic font loading. Large Arabic web font files without subsetting or display optimisation add significant weight to every page load and delay Largest Contentful Paint, particularly on mobile connections common across Qatar.
After A custom theme where Arabic RTL is a first-class layout mode does not produce the broken components, misaligned dropdowns, and inconsistent alignment that characterise Elementor RTL plugin implementations. Every component is designed for RTL from the first line of CSS. The result is a site that behaves correctly in Arabic, consistently, across every page and every update.
How it works

Process

  1. 01

    Diagnostic

    We audit your current WordPress site or brief. We review your existing theme, RTL implementation if one exists, plugin stack, Core Web Vitals scores on both language versions, Arabic typography and font loading, editorial workflow, and content architecture. We deliver a written diagnostic report in English, with Arabic summaries where your team requires them. This takes one week.

  2. 02

    Technical Specification

    We write the full specification for the bilingual build: custom post types, ACF field groups with Arabic field labels, Gutenberg block list, language routing, font loading strategy for Arabic and Latin typefaces, and hosting configuration. You review and approve before development begins.

  3. 03

    Build

    We build the custom theme with native Arabic RTL and English LTR, configure bilingual content architecture, develop custom post types and ACF field groups in both languages, and build the Gutenberg block library for RTL and LTR operation. All work happens on staging. The codebase is in Git throughout.

  4. 04

    QA, Core Web Vitals, and Launch

    We test every page in Arabic and English, verify RTL layout at every breakpoint and across all custom blocks, check Arabic font rendering on multiple devices and browsers including those common in Qatar, and confirm Core Web Vitals scores for both language versions. We launch to production, monitor the first 48 hours, and deliver editorial documentation in Arabic and English.

Request your WordPress Diagnostic →
Common questions

Frequently asked questions about Custom WordPress Development

Why do Elementor RTL plugins not work reliably for Arabic WordPress sites?

Elementor RTL plugins work by applying a CSS direction transformation to the rendered output of an LTR page builder layout. This handles basic text direction but fails on complex components that have directional logic built into their structure: navigation dropdowns, card grids with directional arrows, sliders with left-right controls, and form fields with icon placement. A custom theme builds RTL as the primary rendering mode for Arabic pages, which means every component is constructed with the correct directional logic from the start rather than having it applied as a post-render override.

How do you implement bilingual Arabic and English on WordPress?

We evaluate the right multilingual approach for each build. WPML, Polylang, and custom post relationship approaches all have different tradeoffs for editorial workflow, content volume, and URL structure. We make a recommendation in the technical specification based on your team's content publishing workflow, the volume of content in each language, and whether translation is handled internally or externally. Arabic field labels and editorial instructions are included for whichever approach we use.

How do you handle Arabic typography and font loading without slowing the site?

Arabic typefaces are loaded using subsetting tools that extract only the character ranges present in your content, combined with font-display: swap to prevent the font from blocking initial render. We use preload hints for the primary Arabic typeface used above the fold. We also test the selected typeface for correct contextual letter forms, kashida rendering, and baseline alignment with Latin text on the same page. The goal is correct Arabic typography that does not impose a performance penalty.

Do you also handle sites that need to support other GCC markets beyond Qatar?

Yes. A bilingual WordPress site built for Qatar, with Arabic RTL, correct Arabic typography, and a well-structured content model, forms a strong foundation for expansion into Saudi Arabia, the UAE, Kuwait, Bahrain, and Oman. Market-specific URL structures, regional SEO configuration, and content localisation for different Arabic dialects can be added to the architecture we build for Qatar. We often plan for regional expansion in the technical specification even if the initial launch is Qatar-only.

Can you migrate our existing content from our current site into the new custom build?

Yes. Content migration is included in the build scope. We migrate posts, pages, custom post type entries, and media from the old site to the new WordPress structure, in both Arabic and English. Where the old content model does not map directly to the new architecture, we document the migration decisions and handle the transformation. We do not leave content migration as a manual post-launch task for your editorial team.

Start here

Arabic RTL on WordPress Requires a Custom Theme, Not a Plugin

Elementor RTL plugins produce sites that are almost right in Arabic. Almost is not good enough for an audience that navigates right-to-left by default. Ignited Nepal builds custom WordPress themes where Arabic RTL is a first-class layout mode, not a CSS transformation applied to an English-first page builder. Start with a diagnostic.

Request your WordPress Diagnostic →