To migrate a website without losing your SEO, you must build a complete inventory of existing URLs, create a 301 redirect map (old URL to new URL), preserve the titles and content that already perform, and watch Search Console for eight weeks after launch. Everything else (the new design, the new tech stack, the shiny new CMS) is secondary. A botched migration does not show up on launch day. It shows up three weeks later, when impressions collapse in Search Console and nobody understands why.
In Morocco, I have watched gorgeous redesigns destroy 60% of organic traffic over a single weekend, simply because the agency changed the URL structure without setting up a single redirect. The site looked better. It stopped selling. Here is the method to avoid that very expensive mistake.
Why does a redesign so often tank traffic?
Google has indexed your site exactly as it exists today: every URL, every title, every internal link is a known address. On migration day, you change those addresses. If you do not tell Google where the content moved, it lands on hundreds of 404 pages. The signal is brutal: "this site lost all its useful content." Rankings follow.
The trap is that the drop is not immediate. Google takes one to three weeks to recrawl the whole site. During that delay everything looks fine, the client congratulates the agency, and then traffic starts melting. By the time the alarm goes off, the damage is done, and every day of delay makes the loss worse.
The causes are almost always the same, and they are all avoidable: forgotten redirects, changed URL structure with no mapping, a staging environment left blocked to crawlers after go-live, content trimmed or deleted during the "cleanup," and broken hreflang on multilingual sites. In the Moroccan market, where many sites juggle French, Arabic, and sometimes English, that last point causes real carnage.
How do you run the pre-migration audit and URL inventory?
Before you touch anything, you need to know exactly what you have. This is the most neglected and most decisive phase.
Build the complete URL inventory
Pull the list of all your indexed URLs from three sources, then merge them:
- The Search Console export ("Pages" and "Performance" reports, to get the URLs that actually generate impressions and clicks).
- A full site crawl with a tool like Screaming Frog (the free version covers up to 500 URLs, enough for most Moroccan brochure and service sites).
- Your current sitemap.xml and, if possible, the server logs.
For every URL, record three critical things: its organic traffic (clicks over 90 days), any backlinks, and its intent (product page, blog article, service page). A "web agency Casablanca" service page that brings 40 clicks a month is an asset. You protect it first.
Decide what deserves to be kept
Not all pages are equal. Sort them: keep as is, merge, or delete. A frequent mistake in Morocco is to bulk-delete "ugly old" blog posts without checking whether they capture traffic. On ClaroDigi's own site, a single content cluster drives roughly 56% of search impressions and 97% of clicks: deleting the wrong pages would be sawing off the branch the entire traffic sits on. Before you delete anything, always look at the data.
How do you build the 301 redirect map?
A 301 redirect is a permanent instruction: "this page moved for good to this new address." It passes most of the old URL's SEO authority to the new one. It is the heart of a successful migration.
Your redirect map is a simple two-column table: old URL, new URL. Every URL in the inventory needs a destination. Golden rules:
- One page to one relevant page. Never redirect everything to the homepage. An old "/services/web-design" page should point to the new web-design page, not to "/". A redirect to the homepage is treated by Google as a "soft 404" and loses the SEO value.
- Avoid redirect chains. If A redirects to B which redirects to C, you dilute authority and slow the site down. Redirect A straight to C.
- Keep HTTPS and a single canonical domain. Force www or non-www, never both.
Technically, these redirects live in the .htaccess file (Apache), in the Nginx config, or through your framework's native redirects. For a bespoke build, the team handling your custom development bakes the redirect table directly into the deployment, which removes manual oversights.
Preserving titles, content, and internal links
The design can change, but three invisible elements must survive the migration, or rankings drop even with perfect redirects.
Title tags and meta descriptions: copy across the ones from pages that perform. A title like "Web Agency Casablanca | ClaroDigi" that ranks well does not get rewritten "for freshness." If you change it, you reset Google's test clock to zero.
Body content: the temptation during a redesign is to "modernize" by cutting text. But Google ranks the text, not the design. A 1,500-word page that ranks must not become a "cleaner" 300-word page. Keep the volume and depth of the pages that bring traffic.
Internal linking: your internal links pass authority from page to page. If the redesign breaks half the internal links, you redistribute the SEO "juice" badly. Rebuild the linking structure and check every link after go-live. For the technical foundations (speed, indexing, markup), our guide on technical SEO in Morocco details the checks to run.
Handling hreflang for an FR / AR / EN site
This is the point that specifically hurts Moroccan sites. If your site exists in French, Arabic, and sometimes English, every language version of a page must declare the others through hreflang tags. A classic error: the new URL structure changes (for example /fr/services becomes /services and /ar/services becomes /ar-ma/services) and the hreflang markup keeps pointing to the old addresses, now 404.
The result: Google no longer understands which version to show a Casablanca user searching in French on google.co.ma, and it may serve the Arabic version to a French speaker, or worse, deduplicate your pages as duplicate content. After migration, verify that each hreflang tag points to a URL returning 200, and that the language codes are correct (fr, ar, en, or regionalized fr-ma, ar-ma). A poorly tagged bilingual site loses half its potential in both languages at once.
The step-by-step migration checklist
Here is the full sequence, organized by phase, with the risk you run if you skip the step. Print this table and tick every line on launch day.
| Phase | Action | Risk if skipped | |-------|--------|-----------------| | Pre-migration | Full URL inventory (Search Console + crawl + sitemap) | You redirect blind, traffic pages vanish | | Pre-migration | Sort each page (keep / merge / delete) | Deleting pages that bring real traffic | | Pre-migration | Full backup (files + database) | No rollback if the launch fails | | Build | 301 redirect map (old to new) | Mass 404s, 30 to 60% traffic drop | | Build | Carry over titles, meta, and performing content | Ranking reset, lost positions | | Build | Rebuild internal linking | Authority redistributed badly | | Build | Staging blocked to crawlers (noindex / robots.txt) | Google indexes staging, duplicate content | | Go-live | Remove the crawler block on production | The new site stays invisible (deindexed) | | Go-live | Check HTTPS, canonical domain, hreflang | Duplicate content, wrong version served | | Go-live | Submit the new sitemap.xml to Search Console | Slow recrawl, delayed indexing | | Post-migration | Watch impressions, coverage, and errors (8 weeks) | Drops go unnoticed until irreversible | | Post-migration | Fix residual 404s found in the logs | Backlinks and traffic lost for good |
The most dangerous error in this whole table is invisible: forgetting to remove the noindex from staging at go-live. The site is live, it is beautiful, it works, but a single line in robots.txt tells Google not to index it. Traffic does not dip, it disappears. Check that line first.
Post-migration monitoring in Search Console
The migration does not end at launch. The first two weeks are decisive. Watch three reports in Search Console:
- Performance: are impressions falling? Mild fluctuation in the first days is normal. A drop of more than 20% that persists past ten days signals a redirect or indexing problem.
- Page indexing (coverage): how many pages are indexed versus excluded? Watch the rise of "404 not found" and "excluded by noindex tag."
- Sitemaps: is your new sitemap being read correctly, and how many URLs were discovered?
Compare the numbers week by week. A well-migrated site recovers its impression level in four to eight weeks, sometimes with a gain, because a redesign often improves speed and the mobile experience. If after eight weeks you are still 30% down, that is not "Google settling," it is a broken migration that needs auditing line by line.
Conclusion: migration is an SEO project, not a design project
Remember this: a successful migration is invisible to your visitors and transparent to Google. The new design is the easy part. The part that protects your revenue is the redirects, the preserved titles, the correct hreflang, and the disciplined eight-week monitoring that follows. This is exactly the logic of ClaroDigi's Authority Engine: a digital asset is built slowly and protected methodically, never sacrificed for a fresh coat of paint.
If you are planning a redesign and want to protect hard-won traffic, see how our SEO and GEO method turns your site into a source of qualified leads on the ClaroDigi Authority Engine page. And if you are still unsure about launching the redesign, read the signs you need a website redesign in Morocco first to confirm the project is worth it.
FAQ
How long does it take to recover traffic after a migration?
A correctly migrated site recovers its impression level in four to eight weeks, the time Google needs to recrawl everything. If after eight weeks you are still clearly below (more than a 20 to 30% persistent drop), the migration has a technical flaw (missing redirects, forgotten noindex, lost content) that must be audited and fixed immediately.
Should you keep exactly the same URL structure during a redesign?
It is the safest option. If you can keep the existing URLs, you avoid almost all of the SEO risk. When a structure change is unavoidable (new CMS, new architecture), the 301 redirect map becomes mandatory and each old URL must point to its most relevant equivalent, never to the homepage.
Does a 301 redirect lose SEO authority?
A clean 301 redirect passes most of the old page's authority to the new one. The real loss comes from mistakes: redirect chains (A to B to C), redirects to irrelevant pages, or mass redirects to the homepage. A single direct, relevant redirect keeps almost all the value.
How much does a safe SEO migration cost in Morocco?
The migration SEO work (audit, mapping, redirects, hreflang, monitoring) typically runs between 8,000 and 30,000 MAD depending on site size, on top of the redesign cost itself. It is insurance: an undetected traffic drop costs far more in lost customers and in ad spend wasted to compensate.
What should I do if my site is bilingual French-Arabic?
Treat hreflang as an absolute priority. After migration, verify that each version (French and Arabic) correctly declares the other, that language codes are valid, and that every hreflang tag points to a URL returning 200. Broken markup loses traffic in both languages at once, and it is the most common error on multilingual Moroccan sites.