Website Redesign Checklist for Winnipeg Businesses

A website redesign is not only a visual project. It changes how visitors find information, how search engines understand the site, and how the business receives calls, quote requests, applications, or orders. A new design can look better while performing worse if useful content, URLs, local details, or tracking are lost during the move.

This checklist helps Winnipeg businesses prepare a redesign that protects what already works and improves the experience for real visitors.

1. Define the business outcome

Choose the primary actions the website should support. Examples include requesting a quote, calling, booking, applying, purchasing, downloading a document, or signing in to a customer portal.

Record a baseline before changing the site: current search queries, important landing pages, conversions, call or form volume, page speed, accessibility issues, and common support questions. The baseline makes the redesign measurable.

2. Inventory every current URL

Create a list of pages, posts, files, forms, campaign URLs, and subdomains. For each URL, decide whether to keep it, improve it, merge it, redirect it, or retire it.

Use a permanent redirect when an old page has a clear replacement. Do not redirect every removed page to the homepage; that creates a confusing experience and can hide broken content decisions. Pages that were accidental demos, spam, or completely unrelated may be better removed with a clear not-found or gone response.

3. Organize content around visitor questions

Navigation should reflect how customers think about the service, not the company’s internal structure. Each core service page should explain:

• Who the service is for.
• The problem or task it addresses.
• What is included and what information is needed to begin.
• The process, constraints, and next step.
• Related services or resources that help the visitor continue.

Replace theme-demo text, placeholder paragraphs, unsupported awards, and generic superlatives with specific information a customer can use. A shorter accurate page is more trustworthy than a long page filled with claims that cannot be verified.

4. Make local information consistent

For a Winnipeg business, use one consistent public business name, phone number, email address, street spelling, city, province, and postal code across the website and business profiles. Fix differences in the footer, contact page, map, structured data, and external listings.

If customers do not visit the address, configure the Google Business Profile as a service-area business and follow Google’s address-visibility rules. The public website and profile should accurately reflect how the business serves customers.

5. Separate design from development decisions

Design covers content hierarchy, navigation, layouts, components, interaction states, and responsive behaviour. Development turns those decisions into a working, maintainable system.

Before approving layouts, test them with real page titles, long and short content, error messages, forms, tables, and mobile screens. Placeholder content hides problems that appear when the site contains actual information.

6. Include accessibility from the start

Use semantic headings, keyboard-accessible navigation, visible focus states, labelled form fields, useful alternative text, sufficient colour contrast, and error messages that explain how to recover. The current Web Content Accessibility Guidelines (WCAG) 2.2 provide testable success criteria.

Accessibility checks belong in design review, component development, content entry, and final testing—not only in a scanner at the end.

7. Protect technical search foundations

Every indexable page should have a descriptive title, a useful main heading, a concise meta description, a self-referencing canonical URL, and crawlable internal links. The site should also provide a focused XML sitemap and a robots.txt file that does not block required public assets or admin AJAX.

Review structured data for the organization and local business, but do not add properties that are not visible, accurate, or supported. Follow the Google Search Essentials and avoid paid or automated link schemes.

8. Verify forms, analytics, and privacy

Test each public form with synthetic information and an approved test destination. Confirm validation, spam protection, consent language, success and error messages, recipient ownership, and how submissions are retained. Never use a real customer or project participant as a test recipient.

Check analytics events for the actions that matter: submitted forms, calls, downloads, purchases, or portal sign-ins. Update the privacy policy when tracking, cookies, or data collection changes.

9. Run a controlled launch checklist

• Back up the database, uploads, source, web-server configuration, and certificates.
• Verify redirects with both old and new URLs.
• Crawl the site for broken internal links, accidental noindex tags, duplicate titles, and missing canonicals.
• Test representative pages on desktop and mobile viewports.
• Check forms, login, search, maps, downloads, and integrations.
• Validate the XML sitemap, robots.txt, and structured-data JSON.
• Monitor server errors, application logs, indexing, and conversions after launch.

10. Improve the site after launch

A redesign is the beginning of a measurement cycle. Review search queries, local-profile activity, form quality, support questions, page engagement, and conversion paths. Update service pages and publish useful articles when customer questions reveal missing information.

NAM Software Solutions provides website design and website development in Winnipeg. To discuss a redesign, share the current site, goals, and important workflows.