Know what is moving first
Inventory important pages, traffic, rankings, links, indexation, conversions and content roles—not just a URL export.
SEO website redesign and migration / a strategy to protect rankings
Your website can improvewithout losing the SEO signals it has earned.
A redesign, CMS change, URL change or domain move usually aims to improve speed, brand and user experience. Without an SEO migration plan, rankings, indexation, internal links and converting pages can lose their direction after launch. I connect URL inventory, mapping, 301 redirects, canonicals, hreflang, staging QA and post-launch monitoring into one migration plan.
URL mapping301 redirectsStaging QA30-day monitoring
Website migration search view / Hong KongProtecting ranking signals
SEO website migration
URLs / redirects / canonicalsQA before and after launch
Migration resultyourwebsite.com / SEO website migrationThe new site carries forward the old site’s search value
Use URL mapping, page-level redirects, canonicals, internal links and monitoring to reduce avoidable traffic gaps.
Before launchKnow which URLs cannot be lost
Baseline traffic, rankings, links, indexation and conversions before deciding where each old page goes.
After launchFind issues and recover quickly
Monitor 404s, redirect chains, canonicals, indexation, rankings and Search Console signals.
Post-migration SEO / ongoing observationAdjust from evidence
Migration is not the day you press publish.A real migration combines pre-launch baselines, launch-day controls and post-launch recovery.
1:1URL mapping first
301page-level redirects
6migration checks
30days of monitoring
10+years of SEO experience
01 / The real SEO migration problem
The new website is not the finish line.
It is a handover of search value.
Design, development and SEO each define success differently. A migration plan puts them on the same sheet: every important old URL needs a sensible new destination, and post-launch data must confirm that Google and users are receiving the new structure.
Map one-to-one instead of sending everything home
Map each old page to the most relevant new page; use 404 or 410 only when no useful replacement exists.
Keep staging problems in staging
Check noindex, robots, canonicals, sitemaps, internal links, structured data and templates so test settings do not reach production.
Do not redirect every old page to the homepage
The homepage rarely matches the old page’s topic, intent and user expectation, so a blanket redirect may not preserve the real relationship.
Launch day is not the acceptance test
Rehearse before launch, check in real time on launch day and review indexation, rankings, errors, traffic and conversions for the following weeks.
A redesign can change search intent
If new content, categories, titles or internal links change a page’s role, correct redirects alone do not automatically preserve relevance.
Old URL → new URLMap content, intent, traffic, links and the most relevant new destination page by page
301 / 404 / 410Choose the response by page relationship and content status instead of one rule for every URL
Canonicals / internal linksKeep self-referencing canonicals, navigation, anchor text and hierarchy consistent on the new site
GSC / Analytics / sitemapSet a pre-launch baseline and post-launch monitoring to separate technical issues from normal fluctuation
Before launch / baselineURL inventory, rankings, traffic, links, conversions, staging QA and the complete redirect map.
Launch day / control changeRelease redirects, canonicals, sitemap, robots, internal links and tracking; spot-check important pages one by one.
After launch / monitor and recoverReview 404s, redirect chains, indexation, rankings, traffic and conversions; fix by impact priority.
The real SEO migration deliverable is not a “live” status.
You should know which pages have been handed over, which signals still need watching, what could affect the business and who owns the next fix.
Map first, redirect secondAccept the work on staging firstRecover from post-launch data
02 / The SEO migration growth engine
From a risk list
to a safer handover.
Every URL has a destination.
I build an executable migration route around site size, platform, redesign scope, domain change, language versions and business priorities instead of waiting for traffic to fall before looking for the cause.
URL inventoryRedirect mapCanonicalsStaging QASitemapsLaunch monitoring
Explore the full SEO approach Primary objectiveSEO migration
+ safer handoverMigration control system in operation
+ safer handoverMigration control system in operation
Record important URLs, impressions, clicks, rankings, traffic, links, indexation and conversions for a meaningful post-launch baseline.
Pair old and new pages by content and intent, and clearly flag pages with no sensible destination.
Test 301s, redirect chains, loops, parameters, case, trailing slashes and final landing pages.
The new page should have its role explained consistently by the page, navigation, sitemap, canonical and language relationships.
Check noindex, robots, canonicals, test URLs, access controls and environment settings before repeating the check at release.
Use Search Console, Analytics, logs, crawlers and real-page checks to review 404s, indexation, traffic, rankings and conversions.
03 / After migration, return to business evidence
Migration is not only about preserving rankings.
It is about staying findable and chosen.
A redesign should be judged across search, user experience and conversion. These public results show the direction of previous projects, not a guarantee that every migration will reproduce them.
View all case studiesVOOPOOHomepage keywords
+68%Homepage keyword growth after site and content improvements.
3DMAKERPRO7 months
103%Built search demand and a conversion path from zero.
Technical signalsTechnical signals
300+A migration view spanning indexation, URLs, content and experience.
Global siteOrganic growth
14K+A public case grew organic traffic from under 5,000 to 15,700+.
Post-redesign search signals / from fluctuation to stabilityOngoing monitoring
04 / The SEO migration process
Plan the handover first,
then launch from evidence.
I place SEO inside the design, development and release rhythm so the team knows when to decide, test and respond to evidence.
- 01Set the baseline
Inventory the old site’s SEO assets
Record URLs, rankings, traffic, links, indexation, conversions, metadata, canonicals and language versions.
- 02Build the mapping
Give every important page a destination
Plan the new URL, redirect or content merge by topic, intent, user task and business value.
- 03Rehearse the release
Find issues on staging
Test templates, links, status codes, structured data, robots, noindex, speed and forms.
- 04Launch
Release from a checklist
Coordinate DNS, SSL, redirects, canonicals, sitemap, internal links, tracking and key-page spot checks.
- 05Verify immediately
Check the most important pages first
Check the homepage, service, product, category, popular content, conversion and long-tail pages.
- 06Recover and improve
Prioritize from 30 days of signals
Review indexation, 404s, redirects, rankings, traffic, enquiries and conversions; fix the highest-impact breaks first.
A redesign being complete does not mean migration is complete.
Search engines and users need time to understand the new site. Clear monitoring, ownership and recovery rhythm often matter more than a polished launch-day report.
SEO migration / public methodGoogle
Search resultlockelee.hk／website redesign SEOWeb engineering and search strategy have to work together
URLs, templates, content, experience and commercial pages make the migration together.
What makes migration work differentEvery change has a search consequence
It is not just moving old pages into a new template; it hands over page roles, signals and next steps.
The practical proofI work across SEO, web development and post-launch recovery.
MIGRATION05 / Why choose Locke
I do more than list the risks.
I turn the fixes into the website.
The common migration failure is separating the report from the live work. You need someone who understands CMS, templates, code, content, Search Console and business priorities, and can take part in the decisions and fixes.
01
SEO + web engineering ability
Connect redirects, canonicals, templates, content, speed, forms and tracking inside one redesign process.
02
Direct implementation, not reports alone
Work directly from baseline and mapping through testing and recovery, reducing distortion between strategy and development.
03
Prioritize by business impact
Prioritize services, products, categories, popular content and conversion pages rather than URL count alone.
04
Explain uncertainty clearly
No ranking guarantee, but clear probabilities, monitoring, ownership and next steps.
06 / What you will see in each migration cycle
Every risk
has a page and an owner.
You will see URL mapping, redirects, canonicals, indexation, important pages, errors and next fixes—not just a message saying the site is live.
SEO migration work view / current cycleHandover is trackable
Core areas being observed6
URLs, redirects, page signals, environment controls, indexation and post-launch results.
01
URL map and important pages
MappedKnow which old URLs should stay, merge, redirect or end.
02
301s, 404s and redirect chains
TestedCheck each important URL’s response, destination and unnecessary hops.
03
Canonicals, sitemap and hreflang
ConnectedKeep versions, page relationships, indexation hints and language settings consistent.
04
Post-launch recovery priority
Next stepChoose the next fix by traffic, rankings, conversions and technical impact.
07 / SEO website migration FAQs
Before we start,
let’s separate the risks.
The common mistake is treating the redesign release, URL change, SEO migration and post-launch monitoring as one day of work.
01Will a redesign always cause rankings to drop?＋
Not necessarily. Risk depends on how much URLs, content, templates, internal links, technical settings and site history change. Baselines, mapping, testing and monitoring reduce avoidable losses but cannot remove every fluctuation.
02Should every old URL be 301 redirected to the homepage?＋
Usually not. A 301 should send an old page to the most relevant new page. If there is no real replacement, assess a 404, 410 or retained page instead of hiding every difference behind the homepage.
03How should a staging site be kept out of the index?＋
Use environment-level access and noindex or robots controls, then recheck canonicals, sitemap, internal links and test URLs before production so staging settings are not released.
04How soon can you know whether a migration has problems?＋
Some technical issues can be found on launch day, such as redirects, 5xx errors, robots or forms. Indexation, rankings, traffic and conversions need days to weeks of observation. Start with a baseline and monitor by impact.
05What needs extra checking in a multilingual migration?＋
Beyond URLs and redirects, check each language version’s canonicals, hreflang, return links, language codes, sitemaps, internal links, content and local search intent.
06Can you guarantee that rankings will not change after migration?＋
No. Search results are affected by competition, algorithms, content, technology, user behavior and site history. I can reduce avoidable risks, establish monitoring and plan recovery, but cannot guarantee fixed rankings.
Start with your website
Planning a redesign or site move?
Find the SEO signals you cannot afford to lose.
Submit your website URL. I will review current URLs, important pages, search signals, language versions and likely migration breakpoints, then confirm whether mapping, technical checks or post-launch monitoring should come first.