Technical SEO Consultant, Qatar

Arabic versions that search engines cannot see

Many Qatari sites offer Arabic, but not always in a form search engines can index. Translation plugins and page builders sometimes switch language with a script or a cookie while the address stays the same. To a visitor that looks fine. To a crawler there is only one page, usually the English one, and the Arabic text never reaches the index.

Other variations cause similar trouble:

• Arabic pages exist on their own URLs but carry English titles, descriptions and structured data because those fields were never translated.
• The Arabic section is linked only from a flag icon in the header, with no internal links between Arabic pages, so crawlers find it late or not at all.
• The language attribute says English on every page, including Arabic ones, because it was set once in the theme.
• The language switcher always leads to the other homepage rather than the matching page.

I check each of these with a crawl, a comparison of raw and rendered HTML and the URL Inspection tool, then write a specification for your developer: separate crawlable Arabic URLs, translated metadata, correct direction and language attributes, internal links within the Arabic section, and a switcher that links equivalent pages. The method follows my technical SEO audit, scaled to a smaller site where every page gets individual attention.

Booking engines, portals and other domains

Hotels, restaurants, clinics, schools and property developers in Qatar often rely on third-party systems for the action that matters: a reservation engine, an appointment tool, a property listing portal or an online application form. These usually live on another domain or a subdomain run by the vendor. That brings several technical questions that rarely get asked when the system is chosen.

• Which domain holds the content? If room, unit or course descriptions only exist inside the booking or portal system, your own site may be thin while the vendor's pages compete with it.
• Is the vendor domain indexable? Booking steps and session-based pages should normally stay out of the index, while useful descriptive pages should sit on your domain.
• Are descriptions duplicated? The same text on your site, the portal and several listing sites makes it hard for search engines to choose the original.
• Does tracking survive the hop? Without cross-domain measurement, every booking looks like it came from your own site rather than from organic search.

I map these flows, recommend which pages belong where, and specify canonical, robots and tracking settings. Where the vendor platform limits what can be changed, I note the limitation and suggest a workaround rather than a fix that cannot be implemented.

Numerals, phone formats and structured data

Arabic pages in Qatar may display prices, phone numbers and dates in Eastern Arabic numerals, Western digits or a mix of both, sometimes on the same page. Readers handle that easily. Machines are less forgiving. Structured data, click-to-call links, WhatsApp links and analytics events expect consistent machine-readable values, and a phone number written in a different numeral system or with right-to-left reordering can produce a broken link or a mismatch between markup and page.

I check that:

• Telephone links and WhatsApp links use a standard international format regardless of how the number is displayed.
• Prices in markup are plain numeric values with the riyal currency code, even when the page shows them in Arabic numerals.
• Opening hours in markup match the hours shown, including different schedules during Ramadan where you publish them.
• Mixed-direction text, such as an English brand name inside Arabic copy, is wrapped so it displays correctly.

Beyond formats, the markup itself should reflect what you are: Hotel, Restaurant, MedicalClinic, School or a general LocalBusiness type, plus a single Organization entity that ties branches and brands together, with Arabic and English names recognized as the same organization. I plan this by template with the method on my schema markup consulting page, and your developer implements it.

Hosting, page builders and speed on phones

Many Qatari sites are built with visual page builders on shared hosting chosen at launch and never revisited. The result is often a heavy page: multiple slider libraries, animation scripts, several font families for two scripts, large unoptimized project photos and a growing stack of tags for ads, chat and analytics. Phones then struggle to render and respond, which shows up in Core Web Vitals field data even when lab tests look acceptable.

My review covers:

• Which templates fail which metric on mobile, from field data where Qatar traffic is sufficient, otherwise from lab tests run under realistic conditions.
• Arabic font loading: how many weights, whether files are subset and whether text stays invisible while fonts load.
• Third-party scripts, who owns each one and whether it needs to load on every page.
• Consent banners that appear late and push content. The consent approach belongs with your legal advisor, given Qatar's data protection law; the rendering is a developer fix.
• Hosting location, server response time, caching and whether a CDN edge close to the Gulf would help.

Some organizations, especially those working with government entities, may have requirements about where data is hosted. That question is for your legal or compliance advisor; I assess the performance and crawl side of the options. The diagnostic method is set out on my Core Web Vitals consulting page.

Redesigns, agencies and who owns the accounts

Qatari businesses often refresh their websites around a rebrand, a new project portfolio or a change of agency. Each rebuild is a migration risk. Project and service URLs change, Arabic pages are rebuilt later than the English ones or not at all, and old campaign pages that still earn links are forgotten. I prepare the redirect map, check the new build on staging, verify redirects and tags on launch day, and monitor indexing afterward, following the approach on my SEO migration consulting page.

Account ownership is a quieter technical issue. It is common for the agency that built a site to have created the Search Console property, the analytics account, the tag manager container and the hosting account in its own name. When the relationship ends, the business can lose access to its own history. Part of my work is an access audit: confirming that the company owns each account, that agency users are added as users rather than owners, and that server log access is available when needed.

I work with your agency rather than around it, giving them specifications, answering questions and checking results. The work is remote, with calls during Qatari business hours. Where the site has to connect with CRM and ERP, see digital transformation in Qatar, and the Qatar international SEO page covers sites that serve visitors from abroad.