Search in Saudi Arabia happens in two languages, often from the same person on the same day. A site that handles only one is invisible for half the queries that matter to it.
Two languages, two sets of pages
The most common mistake is machine-translating an English site into Arabic and publishing it on the same URLs. Search engines need each language on its own URL, and users need Arabic that reads as though it was written in Arabic — because the phrases people search are not literal translations of the English ones.
Getting the technical side right means:
- A distinct URL per language, whether by subfolder or subdomain, used consistently.
- hreflang annotations linking the equivalents in both directions, plus x-default.
- The lang attribute and dir="rtl" set correctly, so the page renders and is parsed properly.
- A self-referencing canonical on each version, so the two are not read as duplicates.
Local intent beats national keywords
For a services business, "construction company Riyadh" is worth far more than a national term with ten times the volume, because the intent is closer to a purchase. Supporting that means:
- A complete, verified Google Business Profile with consistent name, address and phone.
- The same details in identical form everywhere they appear online — inconsistency dilutes the signal.
- Genuinely local content: the projects, districts and conditions you actually work in.
- LocalBusiness structured data giving search engines the facts directly rather than making them infer.
Write for the question, not the keyword
Search engines have been resolving questions rather than matching strings for years. The pages that earn traffic answer something specific that a buyer types when they have a problem — "how thick should an epoxy floor be", "why is my wall leaking" — and answer it properly.
That means headings that mirror the question, a direct answer near the top, and enough depth that the reader does not go back to the results page. Length is not the goal; not needing a second search is.
The technical baseline
None of the above survives a slow, badly structured site:
- Server-render content so it is in the HTML rather than assembled by JavaScript.
- One canonical URL per page.
- A sitemap that reflects what is actually published, and a robots policy that keeps thin pages like search results out of the index.
- Real heading structure and internal links between related pages.
Where BK IT fits
SEO and digital marketing sit alongside our web and software development, which matters because most SEO problems are engineering problems — rendering, canonicals, structure and speed — and are fixed in the codebase rather than in a report.
If you want an assessment of where your site stands, get in touch.