CELORA /
Website redesign: improve the experience and preserve the route to an enquiry
Your website looks dated, mobile pages are difficult to read and the services have changed. A new design seems like the obvious answer. Yet an existing website also has useful addresses, search landing pages and contact routes that customers already know.
Start with two questions: what should become easier for the customer, and what already works? This helps you commission a useful change rather than replace every screen for its appearance alone.
In this article
A smaller change may be enough
If customers find the right service but cannot understand the price or spot the booking option, review that page first. Clearer scope, genuine work and a simpler form may address the problem without a complete rebuild.
A broader redesign makes sense when the structure itself gets in the way: several services share one long section, updates are difficult or mobile visitors cannot comfortably make contact. The website’s age alone does not decide this.
Record what you need to preserve
Create a short inventory: URL, customer task, available traffic data and contact route. Mark pages linked from advertising, business listings and partners. Before removing a page, understand the job it serves; useful content may belong in the new structure.
Also record integrations, enquiry recipients and available source files. Agree on secure access handover separately rather than putting passwords in a general project brief.
Test receipt, not just the button
A “sent” message does not by itself confirm that your team received the email. Test the complete journey: entering details, the spam check, submission, receipt and the ability to reply.
Repeat the check on a phone. Is the contact field easy to use? Is an error understandable? Can the customer recover their description after a failure? If an operator must confirm a booking, explain that before submission.
Plan changed URLs
A new visual design does not automatically require new addresses. When URLs change, map each old page to its appropriate replacement. Google’s migration guidance covers permanent redirects, internal links, canonical URLs and sitemaps. See the official migration guide.
Treat this as part of the project scope, with someone responsible for checks after launch. Keeping every previous ranking cannot be guaranteed.
Compare deliverables in the estimate
One proposal may cover mockups; another may include development and publication. Ask which pages and copy will change, whether mobile design and forms are included, how URLs are handled, what is checked before launch and which sources you receive.
Separate publication from ongoing support. A useful first stage can be one key service, its enquiry form and navigation, with further changes justified by what you learn.
Questions before commissioning
Must we change the CMS? No. Choose based on editing needs, current limitations and maintenance costs. A new platform does not replace a clear offer.
Can we work in stages? Yes, when stage boundaries are agreed and changes do not break neighbouring sections. Start with a problem you can check.
When do we assess results? Verify technical operation and actual enquiry receipt at launch. Assess visitor behaviour and search performance once comparable data is available.
Send your website and one problem
Contact CELORA with a concrete concern: a hidden mobile booking option, nowhere to put new services, or a visual refresh that should preserve useful pages. Mikhail will review the structure and discuss a practical scope. The studio is based in Saint Petersburg and works remotely with businesses in other cities and countries.
Discuss your redesign · Explore the service · Our live Aventin project