Website redesign checklist that prevents rework.

If your current site is “fine on desktop” but awkward on a phone, you are already paying for it - fewer calls, fewer form fills, more drop-offs. A redesign is usually triggered by one of three problems: the site is slow, it is hard to use on mobile, or it does not convert reliably. This website redesign checklist is built to stop the usual failure mode: a nice-looking rebuild that ships late, loses rankings, and still generates the same weak leads.

Before you design anything: lock scope and success

A redesign without a definition of “done” turns into endless opinion. Decide what the site must achieve in plain outcomes: enquiries, bookings, quote requests, phone calls, or store visits. Pick one primary conversion action per page type (home, service, contact) and treat everything else as supporting content.

Set constraints early. If you need the site live before a busy season, say so. If you have internal staff who must update content, that is a platform decision, not a preference. Also decide what is staying: domain, brand name, core services, service areas. Redesign is not rebranding unless you choose it.

KPI and measurement decisions

If you cannot measure it, you cannot fix it. Define the baseline now (current traffic, current enquiry rate, top landing pages, top conversion pages). Then define what “better” means - for example faster load time on mobile, more calls from service pages, or a lower bounce rate for local search visitors.

Inventory what you already have (and what you should delete)

Most sites fail because they carry old content forward without checking whether it works. Do a quick inventory of:

• Top pages by traffic (these are your SEO assets)
• Top pages by conversions (these are your money pages)
• Pages that exist “because they always have” (these are often dead weight)
• Downloads, PDFs, images, and forms (these create hidden maintenance)

If a page has no traffic, no conversions, and no strategic purpose, retire it. That decision reduces build time and makes navigation cleaner.

Decide your content ownership

Confirm who writes and who approves. If you do not have internal capacity to write, do not leave it until the end. Content is not decoration. It controls structure, page count, and how the site is indexed.

Information architecture: make navigation do less

You want fewer choices, not more. For a Bay of Plenty service business, the common pattern is: clear services, clear service areas (if relevant), proof, and a contact path that works on mobile.

Avoid mega menus unless you have a genuine catalogue. Keep the main navigation tight and predictable. If users cannot find pricing signals, service scope, and next steps within seconds, they will bounce and call your competitor.

Page templates and repeatable blocks

Decide which page types exist and what blocks they contain. For example: hero with one call-to-action, service summary, proof (testimonials, logos, case studies), FAQs only where they reduce sales friction, and a final contact block.

Build repeatability in from the start. It keeps design consistent and reduces long-term maintenance.

Design for mobile first (because that is where the traffic is)

Mobile-first is not a slogan. It is a constraint. You need:

• Tap targets that are easy to hit
• Short forms that do not punish thumbs
• Phone number and address that are clickable
• Sticky or obvious calls-to-action where it makes sense

Also check your content length. On mobile, users scan. That does not mean “thin content”. It means headings that carry meaning and paragraphs that are not walls of text.

Accessibility is part of usability

You do not need enterprise-level compliance theatre. You do need basics: readable contrast, proper heading structure, labels on form fields, and keyboard navigation that does not break. Accessibility improvements usually improve conversion because they reduce friction for everyone.

SEO: protect what already works

Redesigns often drop rankings because URLs change, content is rewritten without intent, or metadata is forgotten. Treat SEO like a migration, not a refresh.

Keep or map every URL

Create a list of all current indexable URLs. For each one, decide: keep it, merge it, or remove it. If a URL changes, you must set up a 301 redirect from the old to the new. Do not redirect everything to the home page. That throws away relevance.

Preserve search intent

If a page ranks for “builder Tauranga” or “physio Papamoa”, do not replace it with vague marketing copy. Keep the core service language, location context where appropriate, and the proof that helps users decide.

On-page basics that get missed

Check every template supports:

• Unique page titles and meta descriptions
• One clear H1 per page
• Logical H2/H3 structure
• Image alt text where it adds meaning
• Internal links between related services

Also confirm you are not accidentally blocking indexing via robots settings during development.

Performance: treat speed as a feature

A fast site converts better and costs less to run. Performance is not just a hosting problem. It is design, build, and content discipline.

Decide your performance budget

Set targets you can test against: mobile load times, image sizes, and maximum script weight. If a design choice breaks the budget, you change the design.

Common performance killers

Large hero images, autoplay video, too many fonts, and plugin-heavy Wordpress installs are the usual offenders. Optimise images properly, use modern formats where supported, and do not ship three tracking tools that all do the same job.

If your stack includes Cloudflare caching and sensible server provisioning, you can usually hit strong results without drama, but only if the front end is not bloated.

Platform and maintenance: choose what you can support

A redesign is also a support plan. If the site will be updated monthly, you need a workflow for updates, backups, uptime monitoring, and security hardening.

Wordpress is fine when it is managed properly. OctoberCMS is a good fit for more bespoke builds that still need a clean admin experience. The key question is not which platform is “best”. It is which one matches your content editing needs, integration requirements, and appetite for ongoing maintenance.

Forms, spam, and deliverability

Treat forms as a system, not a widget. Decide where submissions go (email, CRM, job management software) and how you will handle spam. Confirm your domain email setup supports reliable delivery so leads do not disappear into junk folders.

Tracking and compliance: set it up before launch

If you care about leads, you need consistent tracking. Decide what counts as a conversion: phone click, email click, form submit, booking completion. Configure it and test it.

Also handle privacy sensibly. If you use cookies for analytics or advertising, you need clear disclosure and a consent approach that fits your tools. Do not add banners that break the site or block basic functionality.

Content production: build the pages that matter first

Do not start with the About page. Start with:

• Home (positioning and routing)
• Core service pages (what you sell)
• Contact (how you get paid)

Then build proof: testimonials, case studies, accreditations, team bios if they help trust. Local businesses win on clarity and confidence, not hype.

Images and brand assets

Use real project photos and team photos where possible. Stock is sometimes necessary, but it reduces trust fast if it looks generic. Make sure you have rights to use every image and logo. Keep file sizes under control.

QA: test like a customer, not a developer

QA is where a redesign either becomes professional or becomes a weekly headache.

Test on real devices: iPhone and Android, not just a resized browser window. Check different browsers. Then test user journeys: find a service, understand price expectations, contact you, complete a booking.

Checklist for functional QA

You are looking for boring reliability:

• All forms submit and send to the right inbox
• Thank-you pages or success messages appear
• Phone and email links work on mobile
• 404s are handled and redirected where appropriate
• Analytics events fire once (not twice)
• Page speed is acceptable on mobile data

If anything is flaky, fix it before launch. You will not “get to it later”. Later is when you are busy.

Launch: treat it as a controlled change

Pick a launch window when you can watch the site for a few hours afterwards. Freeze content changes right before launch so you are not trying to sync edits across two environments.

Have a rollback plan. Even a simple one: a full backup and a clear path to revert DNS changes if needed.

Post-launch checks in the first 72 hours

Watch Search Console for indexing issues and crawl errors. Check redirects. Confirm forms are coming through. Check key pages on mobile again. If you run ads, confirm landing pages and tracking still work.

Ongoing support: avoid the “set and forget” trap

A redesign is not the finish line. Plugins, themes, and dependencies change. Hosting needs updates. Security threats evolve. The businesses that get consistent results treat maintenance as routine, not as an emergency.

If you want a local team to build and maintain a fast, mobile-first site with a practical support setup, Responsive is set up for exactly that.

Keep one habit after launch: once a month, review what pages people land on, what they click, and where they drop off. Small fixes made regularly beat big redesigns every few years.