By Khalid Namra18 min read
Why technical comes first
The best content in the world is worthless if robots cannot reach or read it. Technical SEO is not an extra optimization; it is the precondition that lets everything else appear. It is also the highest-leverage work: one fix can unlock hundreds of pages at once.
Crawling and crawl budget
Every site has a rough daily allowance of crawl requests, set by server speed and site importance. Wasting it on worthless URLs delays the important ones. The usual drains: infinite filter pages in shops, internal search results, duplicate URL parameters and empty tag pages.
- Block internal search results and filter pages in robots.txt.
- Reduce redirect chains: each extra hop costs a request and adds delay.
- Fix internal broken links before chasing external ones.
- Keep server response time under 500ms where possible.
Indexing and duplication
| Instrument | What it does | Common mistake |
|---|---|---|
| robots.txt | Blocks crawling, not necessarily indexing | Using it to hide a page, which can still appear without a description |
| noindex tag | Keeps the page out of results | Placing it on a robots-blocked page, so Google never sees it |
| canonical tag | Declares the main version among similar pages | Pointing it at a page with entirely different content |
| 301 redirect | A permanent move that carries most link equity | Redirecting every old page to the home page instead of its match |
| hreflang | Links language versions to each other | A one-way reference the other page never returns |
Core Web Vitals in practice
- LCP under 2.5s: compress the hero image, load it with priority, remove render-blocking scripts.
- INP under 200ms: cut third-party JavaScript and defer anything not needed for first render.
- CLS under 0.1: set width and height on every image and iframe, and reserve ad space up front.
- Arabic fonts are heavy: use woff2, load only the weights you use, and set font-display: swap.
Always measure on mobile over a slow network. Most Arabic traffic is from phones on imperfect connections, and testing on a fast desktop gives misleading numbers.
JavaScript and modern sites
Fully JavaScript-driven sites need an extra rendering stage before Google sees the content, and that stage can be delayed or fail. The fix is shipping ready HTML: server rendering or prerendered static pages. And do not rely on “Google will eventually render it” — generative crawlers are less patient and many execute no JavaScript at all.
A final technical checklist
- HTTPS enabled and every version redirects to one canonical host.
- A correct robots.txt that references the sitemap.
- An up-to-date sitemap containing only indexable URLs.
- Unique title and description per page, and a single H1.
- An explicit canonical on every page.
- Reciprocal hreflang between Arabic and English versions, plus x-default.
- Compressed images in a modern format with declared dimensions.
- No broken internal links and no long redirect chains.
- A custom 404 that returns the visitor to useful content.
- Valid structured data matching the visible content.
Frequently asked questions
What is the priority if my time is limited?
In this order: get your key pages indexed, then mobile speed, then duplication and canonicals, then structured data.
Is technical SEO a one-time job?
No. Every feature launch, theme change or migration can break something. Review the checklist after any major change and lightly each month.
Do I need a developer?
For deep speed work, server configuration and server rendering: usually yes. Tags, sitemaps and structured data can be handled from your CMS or an SEO plugin.
Related SADARA services
- Search Engine OptimizationWe build a clean technical foundation and content that deserves the top spot, then measure and refine weekly until you hold the lead.