Website Redesign Checklist

Do not redesign blindly

A redesign should not begin with make it modern and nothing else. Modern is not a strategy. Before replacing the old website, identify what is still useful, what is confusing customers, and what the business now needs the site to support. This protects the parts that work and stops the new design from becoming a prettier version of the same problem.

Start by naming the reason for the redesign. Is the current site slow, dated, hard to update, weak on mobile, poor at explaining services, or disconnected from the way the business now operates? Each reason leads to a different kind of work. A visual refresh may fix trust issues, but it will not fix a broken enquiry flow. A new page layout may help scanning, but it will not replace missing service detail. The brief should say what must improve, not only what must change.

• It keeps useful existing content, rankings, and customer pathways from being lost during the redesign.
• It separates visual taste from real performance, usability, and business problems.
• It gives the redesign team proof, assets, URLs, access, and priorities before work starts.
• It makes stakeholder review easier because decisions are documented instead of scattered.
• It turns a redesign from a cosmetic refresh into a stronger operating asset.

Audit the current site before removing anything

List the current pages, the enquiries they generate, the services they explain, and any pages that already rank in search. If a page is useful, it may need rewriting or restructuring rather than removal. If a page is outdated, decide whether it should be updated, merged, redirected, or retired. This small audit can prevent accidental damage to search visibility and customer trust.

Check your analytics if you have access. Look for pages with steady visits, pages where people leave quickly, and pages that appear before contact form submissions. Also review customer emails and phone calls. If people keep asking the same question, the new website should answer it more clearly. A redesign is a chance to remove friction, not just move sections around.

Collect the right assets early

Good redesigns move faster when the raw material is ready. Gather logo files, brand colours, fonts if you use them, professional photos, service descriptions, testimonials, frequently asked questions, team bios, location details, and links to competitors or references you like. Do not worry if the content is rough. Rough content is still better than empty placeholders.

• Current website login, domain, and hosting access
• Important forms, booking links, payment links, or embedded tools
• Analytics or search data if available
• Reviews, case studies, project photos, and trust proof

Images deserve special attention. If the old site used generic stock photos, consider replacing them with real photos of the team, place, products, or work. Real images usually improve trust because visitors can see the business behind the claim. When real photos are not available, choose images that support the page without pretending to be your staff or customers.

Separate visual issues from business issues

A dated layout is a visual issue. Poor mobile behaviour is a usability issue. Weak service descriptions are a messaging issue. Missing calls to action are a conversion issue. Slow loading may be a technical issue. Treating all of these as design makes the project vague. Naming the real problem helps the redesign solve it properly.

For example, if visitors ask the same basic questions before contacting you, the site may need stronger service pages and FAQs. If people visit but do not enquire, it may need clearer calls to action and better proof. If customers cannot find where to book or request a quote, the navigation and page hierarchy need work. The more precise the diagnosis, the easier it is to judge whether the new site is actually better.

Plan redirects before launch

Redesigns often change page URLs. If old URLs disappear without redirects, visitors can hit broken pages and search engines can lose useful signals. Make a simple redirect list before launch: old URL, new URL, and status. It does not need to be fancy. It just needs to exist before the site goes live.

Redirect planning is especially important for service pages, guide articles, local landing pages, pricing pages, and any page linked from social media or email campaigns. If a page has no direct replacement, send visitors to the closest relevant page rather than the home page by default. Good redirects feel invisible to users, which is exactly the point.

Review the new site like a customer

Before approval, test the site on mobile, click every main action, read the pages out loud, check the contact flow, and confirm the strongest proof is easy to find. A redesign is successful when visitors can understand the business faster and act with more confidence. Ask someone outside the project to complete a simple task, such as finding a service, checking price guidance, or sending an enquiry. Their hesitation will show you where the site still needs work.

Prepare handover and future updates

A redesigned website should not become stale the week after launch. Decide who can request edits, where new content should be stored, and how guides or resource updates should be handled. Keep a list of image sources, page titles, redirects, key logins, and tracking tools. If the site will keep growing, treat handover as part of the redesign, not an afterthought. The best redesign gives the business a stronger foundation for the next year, not only a nicer launch day.

After launch, compare the new site against the goals in the redesign brief. Are visitors finding the right services faster? Are enquiries more relevant? Are staff sending fewer clarification emails? A redesign should be judged by practical improvements, not only by whether the pages look newer. Keep a short list of post-launch observations so the next round of improvements is based on real use instead of guesses.

Keep the brief visible during review. When opinions differ, return to the agreed goals and decide which option best supports the customer journey.

That keeps the redesign grounded in evidence instead of last-minute preference.

How Excelin Web and ExcelinWeb Portal help you use it

Excelin Web helps turn this guidance into a cleaner website, safer setup, and more organised business workflow. ExcelinWeb Portal keeps the practical side visible, so requests, notes, content, approvals, and next actions do not disappear into scattered messages.

The bigger lesson is that business setup is not just preparation. Every guide should help the owner understand what customers need to trust, what the team needs to repeat, and what information should be saved for the next decision.

• Use ExcelinWeb Portal to keep this article's next action visible until it is genuinely finished.
• Attach notes, links, content, images, or decisions where your team can find them.
• Use Excelin Web for website structure, business email, launch support, SEO, and custom workflow planning.
• Keep ExcelinWeb Portal, a product of Excelin Web Limited, as the connected place where setup tasks turn into real business workflows.
• Connect the task to website, bookings, customers, finance, analytics, or team handoff when it affects those areas.
• Move from this guide into the next practical step while momentum is high.