Technical SEO is the set of fixes that let Google crawl, index, and rank your site without friction. If any one of those three steps breaks, the best content on earth stays invisible. In Morocco, where most visits arrive on a phone over Inwi, Orange, or Maroc Telecom networks (usually 4G, sometimes 3G), speed and a clean technical base are not a luxury: they are the entry ticket.
The good news: roughly 80 % of technical problems fit into a short, checkable list you can audit in an afternoon with free tools. This guide gives you the exact thresholds, the tools, and a prioritization table so you know what to fix first. It is deliberately the opposite of a sales pitch: it is the resource we wish we had found when we started.
Crawl, index, rank: what actually happens?
Picture Google as a hurried librarian. It sends a robot (Googlebot) that follows links from page to page: that is the crawl. For each readable page, it decides whether to store it in the library: that is indexing. Then, when someone searches, it pulls the most relevant pages and orders them: that is ranking.
Three classic failure points, in order of severity:
- Blocked at crawl. A misconfigured
robots.txt, a page behind a login, or a site so slow that Googlebot gives up. The page is never seen. - Crawled but not indexed. The page is read but judged thin, duplicated, or marked
noindex. It exists for Google but appears in no search. - Indexed but poorly ranked. Here the problem is usually content or signals (links, authority), not pure technique.
Technical SEO tackles the first two failures. Until they are fixed, investing in content is like filling a leaky bucket.
How do you check what Google sees?
Open Google Search Console (free, essential) and use the URL Inspection tool. Paste one of your key pages. Search Console tells you whether it is indexed, when it was last crawled, and flags any blockers. Also type site:yourdomain.ma into Google: the result count gives a rough estimate of pages actually indexed. A large gap between your published pages and that number is a warning sign.
What are Core Web Vitals and which thresholds matter?
Core Web Vitals are three measures Google uses to judge the real experience of a page. They have been ranking factors since 2021, and their weight is rising. The "good" thresholds to aim for:
- LCP (Largest Contentful Paint) under 2.5s: time until the largest visible element (often an image or heading) renders.
- INP (Interaction to Next Paint) under 200ms: responsiveness when the user clicks or types. INP replaced FID in 2024 and is stricter.
- CLS (Cumulative Layout Shift) under 0.1: visual stability, meaning nothing jumps during load (an ad pushing the text down, for example).
Why does this matter so much in Morocco? Because a site tested on fibre wifi in Casablanca can feel fast while it crawls on degraded 4G in Tanger or 3G in a rural area. Google measures the experience of real users (Chrome field data), not your desktop test. A slow site drives visitors away AND costs rankings. We detail this double cost in our guide on the slow website killing your growth.
What do you measure Core Web Vitals with?
PageSpeed Insights (free, from Google) gives all three metrics in field and lab data, with ranked recommendations. The Core Web Vitals report in Search Console shows the site-wide trend. For live diagnosis, the Lighthouse tab in Chrome DevTools simulates a phone on a slow network: precisely the Moroccan scenario.
Why is mobile-first decisive in Morocco?
Since 2023, Google indexes the mobile version of your site, not the desktop one (mobile-first indexing). In plain terms: if your mobile site hides content, loads fewer images, or is broken, that degraded version is the one Google scores.
In Morocco the stakes are amplified by three local realities. First, mobile traffic far exceeds desktop for most consumer-facing sectors. Second, data plans remain a watched budget: a 5 MB page is not neutral for the user. Third, network quality varies sharply: excellent on 4G+ in central Casablanca or Rabat, more temperamental elsewhere. Optimizing for the slow mobile case is not an edge case, it is the average case.
Three reflexes that change everything: compress and serve images in WebP, lazy-load anything below the fold, and limit third-party scripts (every widget, chat, or tracker adds milliseconds of INP).
How do you technically audit your site?
The reference tool for a full audit is Screaming Frog SEO Spider: free up to 500 URLs, which covers most Moroccan SME sites comfortably. It behaves like Googlebot and lists problems page by page.
What Screaming Frog reveals in one pass
Run it on your domain and prioritize these:
- 404 codes and redirect chains. Broken links waste crawl budget and frustrate visitors.
- Title and meta description tags that are missing, duplicated, or too long.
- Canonical tags that are absent or pointing to the wrong page.
- Pages set to
noindexby mistake (a classic after going live from a staging environment). - Click depth: a page more than four clicks from the homepage is crawled poorly.
- Hreflang wrongly declared on an EN/FR/AR site.
Always cross-check this data with Search Console: Screaming Frog shows what exists, Search Console shows what Google actually does with it.
The technical pillars you must never neglect
Beyond speed, a few fundamentals determine correct indexing.
The XML sitemap lists your important pages and submits them to Google. Generate it automatically, keep only indexable pages in it (no 404s, no noindex pages), and declare it in Search Console.
The robots.txt file tells Googlebot where it may go. A single misplaced line (Disallow: /) can deindex an entire site. Check it after every rebuild.
Canonical URLs resolve duplication. If the same page exists with and without www, with and without a trailing slash, or with tracking parameters, the rel="canonical" tag indicates which one counts. Without it, Google dilutes your signals across several URLs.
Hreflang is crucial in Morocco, where a serious site is often trilingual (French, Arabic, English). A correct hreflang declaration stops Google from serving the English version to a French-speaking searcher, or penalizing your pages as duplicates. It is subtle to wire: each page must point to its equivalents in the other languages, reciprocally.
HTTPS is no longer negotiable. A plain HTTP site shows a "Not secure" warning in the browser and loses trust. The SSL certificate is free (Let's Encrypt) and at most Moroccan hosts it activates in one click.
Structured data (schema.org) helps Google, and now AI engines, understand your content. A correctly placed Organization, Article, or FAQPage schema raises your odds of appearing as a rich result and being cited by generative AI.
Which technical fixes come first?
Not everything has the same return on effort. Here is a prioritization table, from highest payoff to finest tuning, with the impact and the fix method.
| Technical problem | SEO impact | How to fix |
| --- | --- | --- |
| robots.txt blocks the site | Critical: zero indexing | Remove Disallow: /, retest in Search Console |
| noindex left after go-live | Critical: pages absent | Inspect with Screaming Frog, remove the tag, request reindexing |
| No HTTPS / SSL | High: trust and rank loss | Enable Let's Encrypt, force a 301 redirect to HTTPS |
| LCP above 2.5s | High: Core Web Vitals + mobile drop-off | Compress images to WebP, enable caching, cut JS |
| Missing or dirty XML sitemap | Medium: incomplete crawl | Generate a clean sitemap, submit to Search Console |
| Missing / duplicate canonical | Medium: diluted signals | Set rel="canonical" on each URL variant |
| 404 links and redirect chains | Medium: wasted crawl budget | Fix or redirect with a direct 301 |
| INP above 200ms | Medium: mobile responsiveness | Lighten third-party scripts, defer non-critical JS |
| Incorrect FR/AR/EN hreflang | Medium on multilingual sites | Declare reciprocal pairs, validate no errors |
| CLS above 0.1 | Low to medium: visual comfort | Reserve dimensions for images and embeds |
Work the table top to bottom: fix what blocks indexing first, then what slows things down, then the polish.
When the technical meets the strategic
Technical SEO is not an end in itself: it is the foundation that lets your content perform. A fast, clean, properly indexed site gives every published article a fair chance to rank and, now, to be cited by ChatGPT, Claude, or Google's AI Overviews. That is exactly the Authority Engine logic: a healthy technical base plus genuinely useful content creates an asset that works for you for years. On our own site, a single content cluster drives roughly 56 % of impressions and 97 % of clicks, precisely because the technical base lets the content breathe.
The riskiest moment for technical health is a redesign or platform switch: that is where rankings are lost by accident. If you are weighing a rebuild, first spot the signs you need a website redesign so you do not break what already works. And if you want a technical base built from day one for speed and indexing, our custom development team bakes Core Web Vitals into the wireframe. To see how we turn that base into a stream of leads, explore our Authority Engine method.
FAQ
How long does it take for a page to get indexed in Morocco?
It depends on your domain authority and crawl frequency. A page on an established site can be indexed within hours to a few days. On a brand-new site, expect a few days to two or three weeks. To speed it up, submit the page via Search Console's URL Inspection tool and make sure it is linked from your menu or an existing article.
Are Core Web Vitals enough to rank well?
No. They are one factor among hundreds. An ultra-fast site with no relevant content will not rank. Conversely, at comparable content and authority, the site that respects LCP under 2.5s, INP under 200ms, and CLS under 0.1 takes the edge, especially on mobile. Treat them as a necessary condition, not a sufficient one.
Is the free version of Screaming Frog enough for an SME?
Yes, in the vast majority of cases. The free version crawls up to 500 URLs, which covers most small brochure and e-commerce sites in Morocco. Beyond that, or for advanced features (Search Console integration, scheduled crawls), the paid license is justified, but start with the free one.
Do you need a developer to fix these problems?
Not always. Enabling HTTPS, generating a sitemap, or compressing images can often be done from your CMS or host's interface. On the other hand, multilingual hreflang, fine INP tuning, or restructuring a site tree need technical skill. The rule: fix the critical blockers yourself (robots.txt, noindex, SSL), delegate the rest when the return justifies it.
Does mobile-first also apply to a B2B site in Morocco?
Yes. Even in B2B, your prospects run a first search from their phone, often on the move or between meetings. Since Google indexes the mobile version, a B2B site neglected on mobile underperforms for everyone. The rule holds whatever the sector.