Website Redesign / Domain Migration: How to Avoid Losing Rankings?
Chapter 2: Search Fundamentals · Question 33
Redesigning a website or changing its domain is one of the riskiest operations in SEO. Done well, rankings transition smoothly or even improve; done poorly, years of accumulated traffic can drop to zero overnight. This article breaks down the entire process clearly so you know what to expect.
Before the Redesign: A Complete Preparation Checklist
A redesign doesn't start on "launch day." Prepare the following at least 2-4 weeks in advance:
1. Fully crawl the old site
Use Screaming Frog or export all URLs from the Sitemap to generate a complete list. Key items to record:
- All pages with rankings (export via Baidu Webmaster Platform or 5118)
- All pages withbacklinkspointing to them (via Ahrefs or Baidu Webmaster Platform backlink analysis)
- All high-traffic pages (export via Baidu Analytics)
2. Create a URL mapping table
This is the core file of the entire migration. The format is simple:
| Old URL | New URL | Status |
|---|---|---|
| old.com/product/123 | new.com/product/123 | 301 configured |
| old.com/news/abc.html | new.com/blog/abc | 301 configured |
| old.com/about | new.com/about-us | 301 configured |
Principle: one-to-one mapping. Do not point multiple old pages to the same new page.
3. Pre-launch checks for the new site
- The new site's robots.txt do not accidentally block crawling
- The new site's sitemap generated and ready to submit
- The title, description, and H1 of new site pages retain the original optimized content
- The new site'sInternal linksstructure updated to the new URLs
301 Redirects: The Technical Core
301 A permanent redirect tells search engines "this page has moved permanently; please transfer the weight to the new address."
Configuration (Nginx example):
server {
server_name old-domain.com;
return 301 $scheme://new-domain.com$request_uri;
}
Common pitfalls:
- ✗ Using 302 temporary redirects instead of 301 (weight is not transferred)
- ✗ Redirect chains too long: A → B → C → D (each additional hop causes greater weight loss)
- ✗ Old pages return 404 directly without redirects
- ✗ All old pages point to the new site's homepage (this is effectively telling Baidu "all the old content is gone")
Baidu Search Resource Platform: Site Migration tool
Baidu provides a dedicated site migration tool. Path: Baidu Search Resource Platform → Site Support → Optimization & Maintenance → Site Migration.
Three migration methods are supported:
- Domain change migration: full-site migration from old.com to new.com
- Internal site migration (rules): URL structure changes, e.g. /article/123.html → /blog/123
- Internal site migration (mapping): submit old-to-new URL mappings one by one
Steps:
- Ensure all 301 redirects are live
- Add and verify the new site in Baidu Search Resource Platform
- Submit migration rules or URL mappings
- Submit the new site's sitemap
- Wait for Baidu review (processing typically begins in 1-2 weeks)
Expected migration timeline
Don't expect rankings to recover immediately after migration. The realistic timeline is:
- Weeks 1-2: noticeable ranking fluctuations; traffic may drop 20-50%
- Months 1-2: Baidu gradually recognizes the new URLs; rankings begin to recover
- Months 3-6: most pages return to pre-migration levels
- 6+ months: if the new site offers a better experience, rankings may surpass the old site
Note: The migration timeline above is areference estimate based on hands-on experience. Actual recovery speed varies with site size and scope of changes; these are not official statistics.
Key: Keep the old domain's 301 redirects for at least 1 year; do not shut them down early.
Monitoring priorities during migration
For the first 3 months after migration, check weekly:
- Baidu index volume changes (Site Owner Platform → Index Volume)
- Core keyword ranking fluctuations (5118 or manual monitoring)
- Crawling errors (Site Owner Platform → Crawling Exceptions)
- Whether 301 redirects are working properly (random spot checks on old URLs)
- Traffic recovery progress (Baidu Analytics comparison with same-period data)
If you find the index volume continuously declining for more than 4 weeks, immediately check whether any pages are missing redirects.
Practical recommendations
- Don't change the domain if you can avoid it: if you're only redesigning or changing the URL structure, try to keep the domain unchanged—the risk is much lower
- Roll out in batches: if the site has a large number of pages (10,000+), consider migrating in batches—migrate core channels first, and migrate the rest after observing stability
- Keep a backup of the old site: if something goes wrong, you need to be able to roll back quickly. Keep a complete database and static file backup of the old site for at least 3 months
Solve it with AI tools: preparation and monitoring before redesign/migration
Scenario 1: Scrape data from the old site to generate a "migration whitepaper"
I want to migrate my website from old.com to new.com. I have all the URLs of the old site (paste the URL list), the title and keywords of each page, and the traffic data exported from Baidu Analytics. Please help me: 1) generate a "migration whitepaper" listing high-traffic pages, pages with backlinks, and pages with core keywords; 2) mark the list of pages that must be prioritized for 301 redirects; 3) provide a complete migration preparation checklist (crawling → mapping → launch → monitoring).
Scenario 2: Batch-generate an old-to-new URL mapping table
The old site URL list is as follows (paste), and the new site uses [rule, e.g., domain changed to new.com, /news/abc.html changed to /blog/abc]. Please generate the corresponding new URL for each old URL and output a CSV (old URL, new URL), following these rules: one-to-one, no chains, and not all pointing to the homepage. Separately flag entries whose semantics don't match for me to confirm.
Scenario 3: Generate a migration monitoring checklist and automation script ideas
I'm executing a website migration next week. Please give me: 1) a weekly checklist for the first 4 weeks after migration (index volume, rankings, crawling errors, 301 effectiveness, traffic comparison, with how to check each item); 2) a script idea that can periodically check "whether old URLs' 301 redirects are effective" (can use Python/curl to check return codes and redirect targets).
Scenario 4: Write a site owner platform feedback statement related to the migration
I'm submitting a "website redesign" application on Baidu Site Owner Platform and need to write a statement. My situation is [migrating from an old domain to a new domain, changed the URL structure, 301 redirects already configured]. Please help me write a formal, clear redesign statement including: reason for the redesign, migration scope, 301 configuration status, and expected processing time. Keep the tone objective and professional.
Note: the boundaries of AI
- AI can only guess the migration mapping: the new URL correspondences it generates based on "semantic similarity" may point important pages to the wrong place—high-traffic/high-backlink pages must be confirmed manually one by one
- AI-generated scripts must be tested: run the monitoring script locally on a small scale first before putting it on the server—don't execute it for the first time in the production environment
- The redesign statement must be based on facts: it's fine for AI to help you polish the wording, but the specific details about your website (when it was changed, what was changed) must be filled in truthfully
