Many business owners ask the same question before a redesign: once the website is changed, will the Baidu rankings be gone?
Let's start with the conclusion: a redesign itself does not necessarily cause ranking drops—what causes ranking drops is how the redesign process is handled. Some people see traffic transition smoothly after a redesign, while others see indexing wiped out within a week of launch. The difference isn't luck; it's whether a few things were thought through before the redesign.
First, distinguish whether you're "changing the skin" or "changing the skeleton"
There are two kinds of redesigns. One is visual and interaction adjustments, where the section structure, URLs, and body content basically stay the same; the other is a full rebuild that includes the technical architecture, section system, and page addresses.
The former carries very low risk; the latter is the source of ranking fluctuations.
Here's a specific scenario: a company in industrial equipment changes its old corporate website from static pages to a dynamic site with a backend management system. The original product page address was `product-12.html`, and the new site uses `products/12`. If it goes live directly without redirects, the hundreds of pages Baidu previously indexed all become 404s, and the rankings naturally can't be preserved.
The approach is simple: before launch, prepare a mapping table from old URLs to new URLs and map them one by one with 301 redirects. Section pages to section pages, detail pages to detail pages; for anything with no corresponding content, redirect to the most relevant parent section rather than sending everything to the homepage.
Pitfall to avoid: redirecting everything to the homepage looks convenient, but Baidu treats it as a soft 404, and link equity won't pass through.
Don't change content and titles on the same day as launch
The second common problem is "changing too much at once."
Some people rewrite the titles, descriptions, body content, internal links, and navigation all at once during a redesign, then find that rankings dropped but don't know which item caused it.
A more stable approach is to change in batches: first launch the structure and visuals, and observe indexing and ranking changes for two to four weeks; after things stabilize, adjust titles and body content. This way, if problems arise, you can pinpoint them quickly.
In addition, for pages that previously ranked well, don't delete entire core paragraphs in the body that have proven effective just to "write more beautifully." Search engines care about the match between content and intent, not the aesthetics of the copy.
Loading speed and mobile experience affect results more than visuals
A common mistake during redesigns is making the homepage a large image carousel with animations. It looks beautiful on PC, but takes five or six seconds to open on a phone.
Baidu's consideration of mobile experience is very real. Image compression, above-the-fold lazy loading, and reducing unnecessary scripts—these three things should be tested during the redesign acceptance stage, not patched after launch.
By the way, many teams are very performance-sensitive when doing mini program development, but become relaxed when building corporate websites, which isn't quite reasonable. Users on both sides have the same patience for speed.
Indexing submission and monitoring after launch
Launching the redesign is not the end.
Three things need to be done: submit the new sitemap on the Baidu Search Resource Platform; use crawl diagnostics to check whether several key pages can be crawled normally; and continuously observe index volume and keyword rankings for four weeks.
If you find indexing has dropped, first check whether robots.txt is mistakenly blocking, whether a large number of pages return 500, and whether redirects are working. Once these three items are ruled out, then consider content-level issues.
One reminder: do not change the domain name at the same time during a redesign. Stacking the two things together makes it almost impossible to attribute problems.
When it's appropriate to contact MIC Studio
If you're just changing a few images or adjusting colors, it can be done internally and doesn't require external involvement.
But in the following situations, working with a professional team will save time:
- The old site's tech stack is outdated, and the corporate website needs to be rebuilt while ensuring smooth URL migration
- The redesign also needs to connect to a backend management system, involving data structure and permission design
- After the redesign, a round of website security testing is needed to confirm there are no new injection or privilege escalation risks
- The business also requires supporting mini program development or App development, requiring unified accounts and data standards
MIC Studio does engineering work such as corporate website development, mini program development, and App development, and redesign migration falls within its regular scope. We don't promise rankings, but we will make controllable items such as redirects, indexing, and performance solid.
Three actionable recommendations
First, before the redesign, export the old site's URL list and the pages that had traffic in the past three months. These two datasets determine which pages must be protected with priority.
Second, launch in batches—structure first, content later. Leave an observation window between each batch; don't change everything at once.
Third, within four weeks after launch, check index volume and key term rankings once a week. If anomalies appear, check technical items first, then content items.
A redesign is something that requires restraint. Thinking it through before acting is much cheaper than firefighting after launch.