A redesigned website may look clearer, but visitors can still lose access to a service if existing links stop working. Redesign planning should include the transfer of pages, content and enquiry routes as well as visual changes. The goal is to keep established journeys usable.
1. Inventory the existing pages
List services, products, articles, documents and contact pages. Consider advertising links and older addresses shared elsewhere. Decide whether each page stays, changes or merges with another. Avoid removing useful content without a plan simply because it no longer fits the new menu.
2. Map addresses when URLs change
Identify the most relevant new destination for each old address. Sending everything to the homepage can lose the visitor’s intent. Google recommends planning URL mapping and appropriate redirects when addresses change. Validate the implementation with sample links before launch.
3. Preserve meaning and useful connections
The new destination should clearly represent the original subject and service. Review images, downloadable documents and internal links. Check Turkish and English versions separately. When combining pages, ensure that information answering a specific visitor need does not disappear in a general summary.
4. Test enquiries before launch
Validate essential phone links, forms, WhatsApp links or checkout flows in a suitable test environment. Check mobile navigation and the route from key pages to contact information. Prevent unnecessary messages or real payments during testing. Assign launch ownership and agree a recovery plan.
5. Monitor after publication
Check important old links, form operation and changes in search performance. Search rankings can fluctuate temporarily during a move, so avoid definite conclusions from one day’s data. Record issues with the relevant address and reproducible steps. Redesign is not a guarantee that rankings will remain unchanged.
Define the redesign scope early
Review existing pages and enquiry routes with BE Soft to plan design, content migration and launch checks together. Technical reference: Google Search Central site migration guidance.
