Before changing a URL or deleting a page, understand its role. Prepare page mappings, test redirects and check indexing after launch. A migration may cause temporary changes in search visibility.
What should you check before a website redesign?
Start with an inventory of existing pages and useful commercial journeys. In Search Console, review the pages and searches producing clicks. Include pages linked by partners, URLs printed in documents and destinations used in campaigns. A lightly visited page can still matter to a customer checking a specific reference.
Then classify pages as keep, improve, merge or remove. Record the service presented and the intended action for each. This map gives you concrete information for discussing the new structure. It prevents the project focusing entirely on a homepage while useful content quietly disappears.
- Export available URLs and search performance data.
- Identify service, project and contact pages.
- List French and English versions of each piece of content.
- Record external links and sales materials that need updating.
How do you organise existing URLs and redirects?
Keep useful URLs when practical. If a page moves, prepare a permanent redirect to the corresponding content. An old maintenance page, for example, should lead to the new description of that service. Redirecting every former address to the homepage may stop visitors finding the information they wanted.
Use a table containing the old URL, destination, editorial decision and expected status. Check redirect chains and missing destinations. Some removed pages have no sensible replacement: handle them explicitly rather than inventing a relationship. The migration plan should be reviewable before launch. These mappings belong among the website SEO checks to keep during the migration.
Which content should you keep or improve during a redesign?
Use the redesign to clarify your offer. A service page should explain the problem you address, how a project works and what information is needed to begin. Project examples add concrete context. Visitors should then be able to contact you from the page that answered their question.
Evaluate the new journey through scenarios: a prospect finds a service on their phone, views a project and requests a meeting. Test readability, navigation and required form fields. This keeps the design aligned with the commercial action the website should support.
How do you preserve French and English versions?
If you serve several markets, test each language as a complete journey. The English version should lead to the right contact information, examples and French counterpart. Hreflang links connect language variants; canonical URLs and internal links must also match the published versions.
On the staging site, check titles, descriptions, images and mobile behaviour. At launch, verify the intended indexing rules and sitemap addresses. Development access restrictions belong in the launch plan so public pages can be discovered when they are ready.
- Test old URLs and their destinations.
- Check language links and canonical URLs.
- Review which pages are allowed or excluded from indexing.
- Test contact and priority features on mobile.
What should you monitor after the new website launches?
After publication, watch navigation errors, discovered pages and search performance in Search Console. Compare suitable periods, accounting for seasonality and changes to your services. Google’s documentation explains that a migration may cause temporary fluctuations; a monitoring plan helps distinguish these from technical problems.
To prepare a redesign with OptiWebSolutions, bring the website address, available monitoring access and the pages you need to keep. Design, content and migration can then be scoped together. Work can be organised remotely with your teams in France or across Europe, using clearly assigned review stages. Our website development and redesign service describes the stages of this work.
