Planning a website redesign? What to gather before you brief anyone
Most redesign requests I hear start with "the site looks dated". That's a fair reason, but it's not a brief. Small business redesigns usually slip, or end up costing more than expected, because the decisions that matter get made halfway through the build instead of before it.
None of what follows needs a designer or developer. It's an afternoon of homework, and it makes the conversation with whoever you hire (me or anyone else) much shorter and more useful.
Decide what the site is actually for
Write one or two sentences on what a visitor should do on your site. "Call us for a quote." "Book a consultation." "Buy from the online shop." "Check we're legitimate before they ring."
If you can't pick a main action, the design can't either, and you end up with a homepage that asks people to do six things at once. It's fine to have secondary actions. It's not fine to have no first one.
Find out what's working now
A redesign is a chance to break things that were quietly working. Before you change anything, note:
- Your most visited pages. Google Analytics or Search Console will show these. They're often not the homepage.
- Where enquiries come from. Which form, which phone link, which page people were on before they got in touch.
- What people search for to find you. Search Console's queries report is the honest version of this.
- What customers already tell you. "I couldn't find your prices" or "I didn't know you did X" is better design input than any trend list.
If you don't have analytics set up, that's worth fixing now so you can compare before and after.
Do a content inventory
List every page on the current site and mark each one: keep, rewrite, merge, or delete. A spreadsheet is plenty.
Then be honest about who's writing the new content. In my experience, the content is what holds a redesign up far more often than the design or the code. Layouts can't be finished properly around placeholder text, and "we'll write it later" tends to mean launching with the old copy in a new template.
Photos count too. If you want real photos of your team, premises or work, book that early. Stock photos are fine for some things, but they're rarely what makes a small business look trustworthy.
Protect the URLs that matter
If any page addresses will change (for example /our-services.html becoming /services), every old URL that gets traffic or has links pointing to it needs a permanent redirect to its new home. Google's own guidance on moving a site with URL changes recommends server-side 301 redirects and mapping old URLs to their new equivalents, not just pointing everything at the homepage.
Skipping this is one of the most common ways a nicer-looking site ends up with fewer enquiries. The redirect list comes straight out of your content inventory, so it's not much extra work if you do it there.
Sort out the practical bits
These aren't exciting, but they stall launches:
- Who controls the domain and the DNS? Find the login before you need it.
- Where is the site hosted, and is that changing?
- Email on the same domain. Changing DNS carelessly can interrupt email, so whoever touches it needs to know it's there.
- Integrations. Booking systems, payment gateways, newsletter sign-ups, CRM forms, Google Business Profile links. Make a list.
- Who signs off. One decision-maker, or a small group with a clear final say. Feedback from five people with equal votes is how projects drift.
Accessibility and speed are part of the design
It's much cheaper to get these right in the design than to retrofit them. Readable text sizes, enough colour contrast, forms that work with a keyboard, and buttons that are big enough on a phone are all design decisions. The current W3C standard, WCAG 2.2, is a useful reference even if you never read all of it.
Speed is the same. Huge hero videos, five web fonts and a slider on every page look fine in a mockup and feel slow on a phone in a car park. I've written more about what a slow website actually costs.
What to bring to the first conversation
- The site's main job, in a sentence or two
- Your current site's URL and access to its analytics, if you have them
- The content inventory, with keep/rewrite/merge/delete marked
- Two or three sites you like, and one sentence on why for each
- A realistic budget range and any hard deadline (a launch, a season, an event)
- Who signs off
With that, a designer or developer can tell you quickly what's realistic, what to do first, and what can wait for a second phase.
Where I fit in
I design and build websites for small businesses, and I'm happy to work from your existing content and branding or help shape them. If your redesign is a WordPress or WooCommerce site, I also fix and maintain those, so the new site keeps getting looked after once it's live.
If you're thinking about a redesign, send me a short note with your current site and what's prompting the change. I'll tell you what I'd look at first, including whether a full redesign is even needed.