Fazley RabbiA website redesign should start with three questions, not with colours or a new template: what the site must do better, which of your current pages are worth keeping, and what must not break during the switch. Write the answers down first and the design work becomes faster, cheaper and far less risky. This guide covers the goals, the content audit and a checklist you can use before you talk to any developer.
Redesign, refresh or just a fix?
Not every tired-looking website needs a full redesign. It helps to name what you actually need.
| What you need | When it fits | Example |
|---|---|---|
| A fix | One clear problem: slow pages, a broken form, a menu that fails on phones | A coaching centre whose admission form stopped sending emails |
| A refresh | The structure works, but the look and some content are dated | New photos, updated details, cleaner fonts |
| A redesign | The site no longer matches the business, or it is hard to use and hard to update | A shop that now sells online, but whose site was built as a brochure |
If the main problem is that the site breaks on phones, a focused rebuild may be the better path; see a mobile-first website redesign.
Start with goals you can check later
"Make it modern" is a wish, not a goal. A useful redesign goal describes a change in what visitors do or what your team can do. For example:
- More enquiries through the website form or WhatsApp button, not only phone calls.
- Visitors on mobile data can open the main pages without a long wait.
- Staff can update prices, products or notices without calling the developer.
- People who search in Bangla land on a Bangla page that answers them.
- Foreign buyers find the certificates, capacity and contact details they look for.
Pick the two or three that matter most. For each one, write down how you will tell whether it improved (form submissions, calls that mention the website, time staff spend on updates) and where you stand today. Without a starting point, you cannot judge the redesign afterwards.
Also write down who the site is for. A pharmacy in Bogura, for example, serves nearby families who want opening hours and a phone number quickly. An exporter serves a buyer abroad who is comparing several suppliers. The same "modern design" serves those two very differently.
Do a content audit before any design
A content audit is a list of every page you have, with a decision about each one. A spreadsheet is enough. For each page, record:
- The page address (URL) and title.
- What the page is for, and whether its information is still accurate.
- Whether people visit it or find it on Google (Google Search Console and your analytics show this).
- Whether other websites or your Facebook posts link to it.
- A decision: keep, update, merge with another page, or remove.
This is usually where the real problems show up: three pages saying almost the same thing, a services page listing work you stopped doing long ago, a team page with former staff, or no page at all for the service customers ask about most. Fixing these often matters more than the new look.
The audit also tells you what must be written for the new site. Content that is not ready on time is one of the most common reasons redesigns stall, so give each new or rewritten page to a named person with a deadline.
Protect what already works
A redesign can quietly undo the search visibility your site has built up. Pages that bring visitors from Google today should keep their content, or move to a new address with a permanent (301) redirect from the old one. Before launch, map every old URL to its new home. Keep your business name, address and phone number identical to what appears on your Google Business Profile and Facebook page.
If you are changing host or platform at the same time, the risks add up. Moving to a new website without losing rankings covers that process in detail.
Other things that break without anyone noticing: email on your domain, ad tracking codes, payment gateway settings and forms connected to other tools. List them in the audit as well.
A practical redesign checklist
- Write two or three goals and how you will measure each one.
- Describe your main visitors and what they need from the site.
- List every current page and decide: keep, update, merge or remove.
- Note which pages bring traffic and which have links pointing to them.
- Plan the new page list and menu, then draft the content.
- Map old URLs to new ones and plan the redirects.
- List integrations: email, forms, payments, analytics, ad pixels.
- Confirm that the domain, hosting and all accounts are in the business's name.
- Test on real phones over mobile data before launch.
- Watch Search Console and enquiries for a few weeks after launch.
Before you contact a developer
Bring your goals, the audit spreadsheet and a few websites you like, with a note on why. That turns "we want a new website" into a brief a developer can plan and price properly; how to write a website brief shows what to include. If you want a second pair of eyes on your plan, my web development service starts with exactly this kind of review.