Technical SEO Consultant, Oman

Supplier sites built from PDFs

Companies that sell to energy operators, ports, utilities and government-linked bodies in Oman often publish much of their substance as documents: company profiles, product brochures, technical datasheets, quality certificates and prequalification packs. Procurement teams do download these, so they have a role. The problem comes when the documents replace web pages instead of supporting them.

The technical symptoms are consistent:

• Search results show a PDF rather than the service page, so a buyer lands in a document with no navigation and no contact button.
• Scanned brochures contain images of text rather than text, so search engines and AI tools see almost nothing.
• Several versions of the same brochure are live under different file names, with the old one still ranking.
• Arabic documents with no embedded text layer, or with characters stored in a way that extracts as nonsense.
• Large files linked from every page, slowing nothing on the page itself but wasting crawl attention on duplicates.

My review lists every document the crawler and Search Console can find, checks whether it has extractable text, and recommends one of three outcomes: keep it as a supporting download linked from a proper HTML page, replace it with an HTML page and redirect the old file, or remove it. The audit framework is described on my technical SEO audit page.

Legacy CMS faults and duplicate versions

Older websites accumulate small inconsistencies that add up. A site moved to secure hosting years ago may still answer on the insecure address. Both the www and bare domain may serve pages. Folder names from an earlier design may still work alongside the new ones. Each variation is another address for the same content, and search engines have to guess which one to keep.

On Omani sites I check for:

• Secure and insecure versions both returning pages instead of one redirecting to the other.
• www and non-www versions both live, sometimes with different content because one was forgotten.
• Removed pages returning a normal status with an empty template rather than a proper not-found or gone response.
• Abandoned sections, such as an old Arabic site in its own folder that nobody maintains but that is still indexed.
• Plugins and modules no longer updated, which can add security risk as well as broken markup.

Sometimes the honest recommendation is that repair costs more than a rebuild. I set out both paths with their trade-offs, so the decision is made on evidence rather than habit. If a rebuild wins, the work becomes a migration, covered further down this page. If repair wins, the fixes are written as tickets in order of impact. The broader technical approach is on my technical SEO page.

Garbled Arabic, right-to-left layout and fonts

Arabic text that once displayed correctly can turn into question marks or strings of odd symbols after a hosting move or database upgrade. This happens when content stored in an older Arabic encoding is read as if it were Unicode, or the other way round. Visitors see broken pages, and search engines index gibberish or nothing at all. Because it often affects only older content, or only text pulled from one database table, it can go unnoticed for a long time.

I check a sample of Arabic pages, titles, metadata and PDF text for these faults, identify which source is affected and specify the conversion. The fix usually belongs to the developer or hosting provider, but it needs to be described precisely.

Layout and fonts come next. Arabic pages should declare right-to-left direction and the Arabic language on the page, mirror navigation and forms correctly, and keep embedded English terms, numbers and phone numbers in the right order. Fonts are the most common speed cost on bilingual sites: complete Arabic and Latin families in several weights, loaded on every page, with text invisible until they arrive. Subsetting, limiting weights and choosing a loading strategy that shows text immediately reduces that cost. URLs need a decision too: Arabic, transliterated or English slugs for Arabic pages, chosen before new pages are generated. Questions of country versions and other markets belong to the Oman international SEO page.

Speed beyond Muscat and where the site lives

Omani buyers and customers are spread from Musandam to Dhofar, and many browse on phones. A page that loads comfortably on a fast office line in Muscat can feel slow on a phone in a port area, a highway service town or an industrial estate. Core Web Vitals field data captures that reality where enough Omani visits exist; where it does not, I run lab tests set up to imitate mid-range phones and slower connections rather than a desktop on fiber.

Typical causes on Omani sites include:

• Project photos uploaded straight from cameras, several megabytes each, with no resizing or modern formats.
• Homepage sliders and background videos that load before the main text.
• Chat widgets, social feeds and several analytics tags all starting at once.
• Shared hosting with slow server response and no caching.

Hosting location matters as well. A server on another continent with no CDN adds delay before anything appears. Some organizations, particularly those dealing with government entities or personal data, may be expected to host certain data in Oman; that is a question for your legal or compliance advisor, given Oman's personal data protection law. I assess the speed and crawling implications of each hosting option so the choice is informed on both sides. Consent banners deserve a look too: the legal approach is for your advisor, but a banner that shifts the page on load is a fixable technical fault. The diagnostic method is on the Core Web Vitals consulting page.

Branch markup, rebuilds and remote collaboration

Many Omani businesses operate from several places: headquarters in Muscat, a workshop in an industrial area, a branch in Sohar or Salalah, a site office near Duqm. Structured data should describe one organization with several real locations, not a set of unrelated businesses. I plan Organization markup defined once, LocalBusiness markup on genuine branch pages with Arabic and English names that match signage, and addresses written in the way locations are actually found, which often relies on area, building and landmark. The model follows my schema markup consulting method.

When a legacy site is replaced, the redirect map is the most important document in the project. It draws on crawl exports, Search Console, analytics landing pages and link data, including those PDFs and old folders that still bring visits, test it on staging and on production, and monitor indexing and errors after launch. The process is detailed on the SEO migration consulting page.

I work with your in-house developer or web agency, remotely and in Oman business hours, with shared issue registers and short review calls. Your developers keep ownership of the code. If the website also needs to connect to your CRM or ERP, the Oman digital transformation page covers that wider plan, and the Oman overview lists my other services.