In short: a redesign should never begin with the deletion of the old site. It starts with an inventory of URLs, content, links, performance and conversions. The new experiment is then built with a correspondence plan and tested redirects.
Refusing a site can improve its image, speed and ability to convert. It is also a migration: known addresses of engines, Internet users and other sites will be modified or replaced. If this dimension is ignored, useful pages may disappear from the index and external links may lead to errors.
The realistic objective is not to promise "zero variation". It is to preserve legitimate assets, to limit breaks and to precisely measure the period after the changeover.
Start with data, not with the new model
The initial audit brings together several sources: site crawl, sitemap, indexing data, input pages, queries, known external links and conversions. It also identifies current errors, because a redesign should not reproduce historical problems.
Each URL is classified: to be kept, improved, merged, redirected or removed. A little visited page is not automatically useless; it can answer a rare but decisive question. Conversely, a highly explored URL may not generate any value.
Build a usable inventory
For each page, enter at least:
-
its URL and HTTP status;
-
its title, its main intention and its distinctive content;
-
the internal links it receives and issues;
-
its destination in the new tree;
-
the expected action and, if available, its contribution to conversions;
-
the decision to keep, merge or delete.
This inventory serves as a migration contract. It avoids discovering after the launch that a service page, an image or a document often consulted has been forgotten.
Redesign the architecture without erasing the existing request
A new site structure should improve clarity. It should not change all URLs only to make them "prettier". A stable, descriptive and properly indexed URL can remain in place even if the design changes completely.
When several weak pages cover the same intention, a merger may be relevant. The new page must then include the really useful information, and the old URLs must point directly to it. Avoid chain redirects and systematic referrals to the home page.
Our guide to creation of a website explains how to link architecture, content and paths before development.
Prepare a unique redirection plan
The redirect map associates each old address with the best new destination. A permanent 301 or 308 redirection is used when the movement is sustainable. The destination must deal with the same need; otherwise the visitor and the engine lose the context.
Before the changeover, check:
-
that no destination itself refers to another URL;
-
that the URLs with parameters actually used are taken into account;
-
that the HTTP, HTTPS versions, with or without
wwwconverge to the canonical domain; -
that important files, images and PDFs are not forgotten;
-
that the internal links of the new site point directly to the final URLs.
Keep what makes the page credible
A redesign often fails on the content: historical texts are replaced by shorter slogans, but precise answers, service details and evidence disappear. The page becomes more spectacular and less useful.
Design must prioritize information, not arbitrarily reduce it. Keep the elements that respond to the objections, describe the method, specify the scope or demonstrate a real experience. Achievements and frequently asked questions can reinforce this journey provided they remain factual.
Process technical signals before the acceptance testing
Pre-production must reproduce the essential conditions of the target without being indexed. We check for title tags, descriptions, canonicals, robot directives, possible alternates, structured data and social metadata.
The final sitemap contains only indexable canonical URLs. Technical pages, duplicates and temporary environments are excluded. The pages that must be found have normal HTML links from other pages of the site.
The technical SEO audit before going online provides a more detailed checklist for this phase.
Test the journeys and the actual performance
An SEO migration is also a UX migration. Forms, menus, filters, payments and consents must work on mobile, on the keyboard and in case of error. The main content should not depend on a fragile interaction or a blocked third-party script.
Compare the most important templates before and after the redesign. Laboratory measurements help with diagnosis; field data, collected after sufficient traffic, indicate the experience lived. Images, fonts and marketing scripts are frequent points of vigilance.
Organize the rocker and the back
On launch day, freeze editorial changes for the time of synchronization. Save the necessary files, database and configuration. Deploy the redirects with the new site, then test a representative sample of old URLs.
A return procedure must specify what can be restored, in what order and by whom. Without it, an urgent mistake turns into improvisation.
Monitor the following weeks
After the switchover, check daily at the beginning, then at regular intervals:
-
404 and 5xx errors;
-
the evolution of indexed and excluded pages;
-
priority requests and entry pages;
-
conversions, not just sessions;
-
abnormally requested redirections;
-
the availability and performance of key journeys.
An isolated decrease or increase is not enough to conclude. Seasonality, campaigns, competition and the time required for the new crawl must be taken into account.
When to entrust the redesign to an agency
Support becomes particularly useful when the site has a lot of URLs, several languages, a catalog, integrations or a significant share of organic acquisition. The value then comes from the coordination between strategy, UX, content, development and operation.
BlackStone Digital supports the creation and redesign of custom sites as well as their referencing. To prepare a diagnosis, transmit the domain, objectives, available access and constraints via the contact page.
