Qodex Media
Website Design

Custom builds, conversion-focused architecture, and technical SEO setups.

Automation & AICore

AI workflows, CRM automation, and custom system integrations.

Paid Media

Google, Meta, and retargeting campaigns optimized for pipeline revenue.

Qodex Media Hospitality

Bespoke digital growth for safari operators, luxury lodges, and boutique hotels.

Qodex Media
Get in touch
SEO Migration Guide

A redesign should improve SEO, not wipe it out.

The SEO migration process for website redesigns: URL mapping, 301 redirects, content preservation, pre-launch checks, and the post-launch monitoring that catches problems early.

RedesignSEO MigrationRedirectsSearch Console

The horror story is common enough to be a cliché: a business launches its beautiful new website and watches organic traffic fall off a cliff, because years of accumulated rankings were attached to URLs and content that no longer exist. The tragedy is that it's entirely preventable with a process that takes days, not months.

Here is that process — the same one we run on every rebuild.

Inventory ranking URLs before design starts — that list is the contract

301 every changed URL to its page-level equivalent, never mass-redirect to home

Rankings belong to content: carry the substance over, not just the URLs

Watch Search Console weekly for six weeks post-launch; fix 404s as they appear

Before design starts: inventory what Google already gave you

Export every URL on the current site (a crawl tool, or Search Console's page list) and mark which ones matter: pages with rankings, traffic, or backlinks. Search Console's Performance report shows which pages earn clicks; even free Ahrefs/Semrush tiers show which have external links. This inventory is the contract the new site must honour — every URL on it either survives, or gets redirected to its closest equivalent.

This is also the moment to decide what dies deliberately. Old pages with zero traffic, zero links, and no purpose can 404 honestly — a redirect map is not a museum.

The redirect map is the project's most important document

For every old URL that changes, define its 301 (permanent) redirect to the new equivalent — ideally the same content at a new address, otherwise the closest relevant page. Avoid the lazy shortcut of redirecting everything to the homepage: Google treats mass homepage redirects as soft-404s and drops the old pages' equity anyway.

Match at the page level: old service page → new service page, old blog post → same post at its new URL. Chains (A→B→C) and loops are the classic failure mode when a site has been rebuilt before — test the map before launch, not after.

Preserve the substance, not just the addresses

Rankings belong to content. If the old page ranked because it thoroughly covered a topic, and the redesign replaces it with three elegant sentences, the 301 will not save the ranking. Carry over (or improve — never thin out) the copy, headings, and answers on every page with search value. The same applies to titles and meta descriptions that were earning clicks, and to image alt text.

Redesigns are the right moment to improve content — merge weak pages into strong ones, update stale facts — but improvement means more useful, not just prettier.

Launch day: the technical checklist

The launch itself is a sequence of small checks that each prevent a specific disaster.

  • Remove all noindex tags and crawl blocks from the new site (the #1 post-launch traffic killer — staging settings shipped to production)
  • Verify 301s live on a sample of the redirect map, checking for chains
  • Confirm every page has its title, meta description, and canonical tag
  • Submit the new sitemap in Search Console
  • Re-verify analytics and conversion tracking fire on the new pages
  • Spot-check mobile speed on key pages — a slower redesign is an SEO downgrade

After launch: watch for six weeks

Some ranking turbulence for a week or two is normal while Google recrawls. What's not normal — and what monitoring catches — is 404 errors piling up in Search Console (missed redirects: fix them as they appear), indexed pages dropping steadily, or rankings for money terms failing to recover after several weeks. Checked weekly, every one of these is correctable before it becomes permanent damage. Unwatched, they compound into exactly the traffic cliff this process exists to prevent.

Frequently asked questions

Will my website lose Google rankings during a redesign?

Not if URLs are preserved or properly 301-redirected and ranking content is carried over. Expect minor turbulence for a couple of weeks as Google recrawls. Redesigns lose rankings when URLs change without redirects, content gets thinned, or a staging noindex tag ships to production — all preventable.

How long do 301 redirects need to stay in place?

Effectively forever — or at least a year or two minimum. Google needs time to transfer equity, other sites keep linking to old URLs, and users keep old bookmarks. Redirects cost nothing to keep; removing them early is a pointless risk.

Can I change my domain name without losing SEO?

Yes, with the same discipline plus one extra step: page-level 301s from the old domain to the new, plus Google Search Console's Change of Address tool. Expect a somewhat longer settling period than a same-domain redesign. Keep the old domain registered and redirecting permanently.

My traffic dropped after a redesign — can it be recovered?

Usually, if you act within weeks rather than months. Diagnose in order: check Search Console for a noindex or coverage collapse, crawl the old URL list for 404s (missing redirects), and compare old page content against new for thinning. Fixing those recovers most redesign losses. The longer broken redirects sit, the more equity evaporates permanently.

Next step

Planning a redesign? Protect your rankings first.

Book a Strategy Call