After a redesign, URL changes, or a new design system, Google traffic can drop for weeks — even if the site “looks better.” That is almost never random: it is a SEO signal problem (canonicals, redirects, sitemap, duplicate pages).

At Soft Seven Art (Casablanca), we treat technical SEO like infrastructure: without it, design and content underperform. Here is the concrete plan we run after every website refresh / redesign or WordPress migration.

What Google actually needs (2026)

Google does not index “a website.” It indexes URLs. For each search intent, it picks one preferred URL. If you have:

  • multiple paths for the same page (/article/ vs /blog/, /projet/ vs /portfolio/)
  • conflicting www / non-www canonicals
  • an empty or outdated sitemap
  • thank-you pages, filtered listings, and RSS feeds that are indexable

…then Search Console fills up with “duplicate without user-selected canonical,” “page with redirect,” “crawled — currently not indexed.” That is a diagnosis, not a punishment.

The 7 technical SEO levers that protect traffic

1. One clear canonical host (apex, no trailing slash)

Pick one form (e.g. https://softsevenart.com/… without www) and enforce it everywhere: rel="canonical", 301s, sitemap, internal links. Two hostnames = two sites in Google’s eyes.

2. 301s, not 302s

Old URLs (legacy CMS, old slugs, /expertises, /article/…) must return a permanent 301 to the new page. Temporary 302s or soft-404s that bounce to a listing dilute SEO equity.

3. A living, submitted sitemap

sitemap.xml must list real published pages: services, solutions, blog, projects, landings. Submit it in Google Search Console on the correct property (non-www if that is canonical). A 6-URL sitemap after a redesign invites invisibility.

4. Hreflang that points to the right page

In multilingual setups, each alternate must target the equivalent page (same article, same project), not the listing. Broken hreflang creates cross-language duplicates.

5. Noindex what should not rank

Thank-you pages, ?category= filters, RSS feeds, preview environments: noindex,follow. Otherwise Google wastes crawl budget on junk.

6. Core Web Vitals and mobile

A heavy redesign (uncompressed images, scripts, fonts) can tank LCP / INP. On mobile, that often hurts conversion and rankings first.

7. Intent-aligned content + proof

Technical SEO opens the door. Content that ranks in 2026 is factual, dated, clear, with useful H2s and proof (method, cases, numbers). That also prepares GEO — visibility inside AI answers.

Search Console checklist (after redesign)

  1. Correct canonical property (apex or domain)
  2. Sitemap submitted and “Success”
  3. URL Inspection on 5 money pages (home, 2 services, 1 article, 1 project)
  4. Pages report: indexed up, duplicates down
  5. Validate fix on duplicate reports once 301s are live

Classic mistakes that cost 3 months of traffic

  • Changing every URL “for cleanliness” with no redirect map
  • Leaving old and new URLs both returning 200
  • Submitting the sitemap on the wrong property (www vs non-www)
  • Indexing 6 languages with thin identical content
  • Confusing Google Analytics with SEO (measurement ≠ indexing)

How long to recover?

Often 2 to 8 weeks after technical fixes + sitemap, depending on domain authority and how many legacy URLs exist. Patience is not an excuse to wait before fixing: every day without 301s reinforces the wrong URLs.

FAQ

Traffic dropped after redesign — does Google “hate” the new design?
Rarely. It is almost always technical (URLs, canonicals, crawl) or diluted content.

Do I need an expensive SEO suite?
Search Console + a clean sitemap + correct 301s deliver ~80% of post-redesign recovery.

Does local SEO (Casablanca / Morocco) change the basics?
It matters for market pages and consistent NAP — but the technical foundations stay the same.

Need a technical SEO audit after a redesign?
→ SEO & SEA · Refresh without breaking SEO · Send your Search Console / URL

Web design agency — brochure, corporate, ecommerce.

Explore our web services · Request a quote