A small business website redesign should do more than make an old site look newer. It should make the business easier to understand, help the right visitors take action, improve mobile usability, and protect the search visibility the company has already earned.
That matters in a market where small businesses account for most Canadian employer businesses. A redesign can support growth, but an unplanned rebuild can also create broken links, lost enquiries, confusing navigation, and avoidable SEO setbacks.
This checklist explains what to review before hiring a designer or developer, what to protect during the project, and what to verify before the redesigned site goes live.
1. Define the business problem before discussing design
Start with the reason the website needs to change. “It looks dated” may be true, but it is not specific enough to guide a successful project.
Common redesign goals include:
- generating more qualified enquiries
- explaining services more clearly
- improving mobile usability
- making the site faster
- supporting a new market or service
- simplifying client updates
- strengthening trust and credibility
- improving online sales or bookings
Choose one primary goal and two or three supporting goals. Then attach a measurable outcome to each one. A professional-service firm might track consultation requests, while a retailer might focus on product discovery and completed checkouts.
If you are still deciding whether a redesign is justified, review these warning signs that a website may be costing you customers.
2. Record the current website baseline
You cannot judge whether the redesign worked unless you know how the current site performs.
Before changing anything, record:
- monthly organic traffic
- enquiries, purchases, bookings, or other conversions
- top landing pages
- pages with valuable backlinks
- rankings for commercially important searches
- current Core Web Vitals
- mobile and desktop conversion rates
- common user journeys
- form completion and abandonment
Also save a full crawl of the current site, analytics annotations, Search Console exports, and a reliable backup. This baseline becomes a reference if traffic, tracking, or functionality changes after launch.
3. Inventory every useful URL
Create a spreadsheet containing every indexable URL and decide what will happen to it.
Each existing page should be marked as:
- keep and improve
- merge with another page
- replace with a new page
- redirect to the closest relevant alternative
- remove because it has no useful replacement
Do not delete a page simply because it looks old. It may still attract search traffic, earn links, or support a customer journey. When a URL must change, map the old address to the most relevant new address with a permanent server-side redirect.
Google’s guidance for site moves recommends preparing a URL map, updating internal links, checking canonical signals, and submitting the new sitemap. Redirecting every old page to the homepage is not a suitable substitute for a page-to-page mapping.
4. Clarify the audience and priority journeys
A redesign becomes unfocused when it tries to give every visitor equal priority.
Identify the audiences most likely to become good customers. For each audience, document:
- the problem they need to solve
- the information they need before contacting you
- the concerns that may delay a decision
- the proof that reduces risk
- the action you want them to take
Then map the shortest sensible route from landing page to conversion. A visitor arriving on a service page should not need to search the entire site to find relevant proof, pricing guidance, or the contact form.
For most small business websites, clearer hierarchy and stronger service pages create more value than adding animation or decorative effects.
5. Build the content structure before the visual design
Wireframes should begin with content priorities, not placeholder text.
For each important page, define:
- the main promise
- the primary audience
- the questions the page must answer
- the evidence required
- the main call to action
- supporting internal links
This makes design decisions more objective. It also prevents the common situation where a polished layout leaves too little room for useful explanations, case studies, FAQs, or conversion content.
A service page should usually explain the problem, the approach, expected deliverables, who the service suits, relevant work, and the next step. Nexxen Studio’s WordPress website design service is the natural destination for businesses planning a custom WordPress rebuild.
6. Plan accessibility from the beginning
Accessibility is easier to build into the system than to add after launch.
The redesign should include:
- sufficient colour contrast
- keyboard-accessible navigation and controls
- visible focus states
- descriptive form labels and error messages
- useful alternative text for informative images
- logical heading order
- readable text sizes and line lengths
- controls that do not rely only on colour
- support for zoom and reflow
Canadian requirements vary by jurisdiction and organization. In Ontario, public-sector organizations and businesses or non-profits with 50 or more employees must make public websites accessible under the AODA requirements described by the province. The Ontario website accessibility guidance references WCAG 2.0 Level AA, with stated exceptions.
Even when a specific rule does not apply, accessible design reduces friction and expands the number of people who can use the website.
7. Review privacy and data collection
Website redesigns often introduce new forms, analytics tools, chat widgets, booking systems, and advertising tags. Each addition can change how personal information is collected or shared.
Review:
- what information each form requests
- why the information is needed
- where submissions are stored
- which third parties receive data
- how consent is requested
- how long information is retained
- whether the privacy notice reflects actual practices
- whether administrative accounts and form data are properly protected
The Office of the Privacy Commissioner of Canada explains that organizations subject to PIPEDA must follow principles including accountability, consent, limiting collection, safeguards, openness, and individual access. Use its PIPEDA guidance for businesses as a starting point, and obtain appropriate legal advice for your situation.
8. Set performance requirements
Performance should be a project requirement, not a final optimisation task.
Agree on:
- image formats and size limits
- font families and weights
- third-party scripts
- caching and CDN requirements
- mobile performance targets
- testing on realistic devices and connections
Google’s current Core Web Vitals focus on loading, responsiveness, and visual stability. The recommended “good” thresholds are an LCP within 2.5 seconds, INP of 200 milliseconds or less, and CLS of 0.1 or less, assessed at the 75th percentile. These are useful experience targets, but they should be evaluated alongside conversion and usability data.
Avoid approving a design that depends on oversized video, numerous font files, or unnecessary animation before anyone has considered the performance cost.
9. Choose a maintainable WordPress system
A successful redesign must remain manageable after launch.
Ask how the new WordPress site will handle:
- global colours and typography
- reusable sections and components
- service and case-study templates
- responsive spacing
- forms and notifications
- image optimisation
- backups and security
- plugin updates
- staging and deployment
- staff editing permissions
Whether the project uses Bricks Builder, Elementor, or another system, repeated styles should be controlled globally. Editors should not need to adjust the same colour, button, or spacing value across dozens of pages.
Plan ongoing ownership too. A defined WordPress maintenance and website check-up service can cover updates, backups, monitoring, and routine checks after launch.
10. Evaluate the redesign partner beyond the portfolio
Visual work is important, but a portfolio alone does not show how an agency manages content, SEO, accessibility, testing, or handover.
Ask potential partners:
- How will you protect existing search traffic and URLs?
- How do you decide what content should be retained or consolidated?
- What is included in responsive and browser testing?
- How will the site remain easy to edit?
- How are accessibility and performance handled?
- Who owns the design files, website, and accounts?
- What happens after launch?
- How are scope changes documented?
The proposal should clearly state deliverables, responsibilities, revision limits, exclusions, payment milestones, and post-launch support. Review Nexxen Studio’s website project pricing guidance to understand how scope affects planning before requesting a tailored estimate.
11. Test the complete site before launch
Do not limit quality assurance to checking whether pages “look right.”
Test:
- navigation and internal links
- contact, quote, booking, and checkout forms
- confirmation messages and emails
- keyboard navigation and focus visibility
- mobile, tablet, and desktop layouts
- current versions of major browsers
- analytics and conversion events
- cookie and consent behaviour
- metadata, canonicals, robots directives, and schema
- redirects and 404 responses
- sitemap output
- page speed and Core Web Vitals
- backup and rollback procedures
Use real content and real devices where possible. Placeholder text and idealised browser sizes often hide issues that appear immediately after launch.
12. Monitor the site after launch
Launch day is the beginning of the verification period.
During the first days and weeks:
- crawl the live site again
- inspect redirected URLs
- monitor Search Console coverage and indexing
- review analytics for unexpected drops
- test forms and transactional emails
- check server and browser errors
- review real-user performance data
- gather feedback from customers and staff
Some search fluctuation can occur when URLs or page content change. Careful redirects, stable internal linking, accurate sitemaps, and ongoing monitoring reduce avoidable risk.
Frequently asked questions
How often should a small business redesign its website?
There is no fixed redesign interval. Redesign when the current site no longer supports the business, users struggle to complete important tasks, the system is difficult to maintain, or technical limitations prevent meaningful improvement. Regular maintenance and smaller iterative changes can extend the useful life of a good website.
How long does a small business website redesign take?
The timeline depends on the number of pages, content readiness, integrations, approvals, and technical complexity. A focused service website may take several weeks, while a content-heavy, multilingual, or e-commerce project can require substantially longer. A credible schedule should include discovery, content, design, development, testing, and launch preparation.
Will a website redesign hurt SEO?
It can if valuable content disappears, URLs change without redirects, internal links break, or indexing settings are wrong. A properly planned redesign can preserve important signals and create opportunities to improve content, structure, performance, and usability.
Should a redesign use a template or custom design?
The right choice depends on the business goals, budget, content, and required functionality. A well-implemented template can suit a simple project. A custom design is more appropriate when the business needs a distinctive customer journey, specialised content structure, stronger differentiation, or reusable components tailored to its operations.
Plan the redesign around business outcomes
The best small business website redesign projects begin with clear goals, evidence, and content priorities. Visual design then supports the strategy instead of replacing it.
If your Canadian business is preparing for a WordPress redesign, Nexxen Studio can audit the current site, identify risks and opportunities, and plan a maintainable conversion-focused rebuild. Request a website consultation to discuss the project.
