Effective website redesign planning starts before anyone chooses colours, layouts, or a content management system. First decide whether the business needs a migration, a targeted refresh, or a full redesign. Then document the goals, content, URLs, technical requirements, account access, responsibilities, and testing needed to protect the value of the current site.

Starting with a visual concept alone can leave important pages behind, create unclear ownership, or introduce problems with forms, search visibility, mobile use, and analytics. The steps below help small and mid-sized businesses prepare a useful redesign brief and decide whether the project is ready to proceed.

Step 1: Decide whether you need a migration, refresh, or full redesign

The first decision is not which platform to use. It is whether the current website’s underlying structure still serves the business and its visitors.

A migration moves existing material to a new location or platform. A refresh updates selected elements while retaining much of the current structure. A redesign changes the broader visual system, information architecture, user journey, or functionality.

Stop point: If the team cannot describe the current problem in specific terms, pause before commissioning design work. “The website looks old” may indicate a visual issue, but it may also reflect unclear content, poor navigation, slow pages, outdated functionality, or an ownership problem.

Step 2: Define business goals and user tasks before discussing design

Replace vague objectives such as “make the site better” with a short list of business priorities and visitor tasks. A visitor may need to request a quote, find a service, download a document, book an appointment, contact a representative, or complete an online purchase.

Record the audiences that matter most, the actions they should complete, and how the business will determine whether the redesigned site supports those actions. Useful measures might include completed forms, qualified inquiries, product orders, document downloads, or successful support journeys. These are planning indicators, not guaranteed outcomes.

Design decisions should help people complete the task that brought them to the page. Canada’s content design guidance recommends identifying the user’s task first and using it to guide design decisions. A documented website design workflow can then connect goals and audience tasks to content planning, prototypes, development, testing, and launch.

Stop point: Do not approve a homepage concept until the team can explain which audience and business problem it supports. A polished homepage cannot compensate for an unclear service structure or incomplete customer journey.

Step 3: Audit the current website before changing it

Build one working inventory of what exists before deciding what to keep, rewrite, redirect, archive, or replace. The inventory should cover more than visible pages.

• Page URLs, titles, headings, metadata, and internal links.
• Images, videos, downloadable files, brand assets, and licensed materials.
• Forms, email notifications, calendars, search, customer accounts, and integrations.
• Ecommerce categories, products, filters, checkout steps, order notifications, and administrative workflows.
• Analytics, advertising tags, consent tools, backups, and reporting connections.
• Domains, DNS records, hosting accounts, administrator accounts, plugins, themes, and software licences.
• A named owner for each important page, asset, system, and approval.

For every URL, record whether it serves an important business or search function, whether the information remains accurate, and where it should go if the page is removed. This prevents a redesign from accidentally deleting useful content or breaking a customer process.

Stop point: Pause if nobody can access the domain, hosting, analytics, content management system, or key integrations. A redesign cannot be planned responsibly when the business does not know which accounts exist or who controls them.

Step 4: Plan content, navigation, and information architecture

Use the audit to create a proposed page map rather than copying the old navigation automatically. Organise pages around visitor tasks, recognisable service terms, and the information customers need before taking action.

Decide which content will be migrated as written, rewritten, consolidated, newly created, or removed. Assign an owner for each page and set an approval process. Content responsibilities should include drafting, subject-matter review, legal or regulatory review where relevant, image selection, and final sign-off.

Clear structure matters for usability and accessibility. British Columbia accessibility guidance recommends descriptive hierarchical headings, a clear and consistent structure, search where appropriate, a sitemap overview, keyboard navigation, assistive-technology access, and user testing.

Stop point: If content has no owner or approval date, do not treat the page map as final. Unapproved content is a common reason for late changes, incomplete pages, and delayed testing.

Step 5: Protect search intent during the redesign

A redesign does not automatically improve search performance. Protecting existing value requires deliberate mapping and review.

• Map each important old URL to a relevant new destination.
• Use redirects when a URL changes and confirm that the destination serves the same underlying intent.
• Review page titles, headings, metadata, internal links, and visible content.
• Preserve useful topic coverage unless there is a documented reason to consolidate or remove it.
• Check canonical settings, indexing controls, XML sitemaps, and analytics after launch.
• Review broken links, redirect chains, missing pages, and unexpected changes in crawlable content.

Do not redirect every old page to the homepage. A relevant service, product, location, or information page is usually a more useful destination when the original content has been replaced. Keep a record of removed URLs, reasons for removal, and replacement destinations.

Step 6: Specify responsive, accessible, performance, and technical requirements

Turn design preferences into requirements that can be demonstrated and tested. A responsive website should keep content readable, navigation understandable, forms usable, and important actions available across phones, tablets, and desktop screens.

Include requirements for text size and contrast, reflow at narrow widths, descriptive headings, keyboard operation, focus visibility, error messages, form labels, alternative text, and assistive-technology access. Avoid claiming formal compliance unless the project includes a defined assessment against the relevant standard.

Also document performance expectations, image handling, hosting needs, security requirements, analytics, email delivery, CRM connections, search, downloads, and ecommerce workflows. If the site sells online, specify product data, categories, customer accounts, payments, shipping, taxes, returns, inventory, notifications, and order administration as applicable.

Use these responsive design testing checks to review representative devices and complete journeys rather than judging only the homepage. Big Time IT Solutions describes responsive website design, ecommerce development, website optimisation, prototypes, and quality-assurance testing as stated capabilities, but exact deliverables still need confirmation in the project scope.

Step 7: Put scope, deliverables, and responsibilities in writing

A useful redesign brief should give every participant the same definition of “finished.” Include business goals, priority audiences, page inventory, proposed sitemap, content responsibilities, design direction, technical requirements, integrations, SEO preservation, accessibility expectations, milestones, approval points, testing responsibilities, launch support, maintenance, and exclusions.

State who supplies copy, images, product data, credentials, legal notices, and approvals. Also state who configures forms, analytics, redirects, hosting, backups, email notifications, and third-party integrations.

If the redesign supports printed materials, signage, or an in-person installation, coordinate digital brand decisions with the physical implementation plan. Related branded installation planning can involve practical site and approval considerations beyond screen design.

Stop point: If a proposal uses broad terms such as “SEO,” “responsive,” “ecommerce,” or “support” without listing actual tasks and exclusions, request clarification before signing.

Step 8: Confirm ownership, access, and provider fit before signing

Compare providers by scope, process, communication, technical fit, and ownership terms, not only by screenshots. Ask:

• Will the business receive administrator access to the content management system?
• Who controls the domain, DNS, hosting, analytics, advertising, and email accounts?
• When will design files, development files, content, and data be transferred?
• Are fonts, images, plugins, themes, and other assets licensed for continued use?
• Who owns the website and its data if the relationship ends?
• Who writes, migrates, reviews, and approves content?
• Which forms, integrations, redirects, tests, and launch checks are included?
• What maintenance, training, troubleshooting, backup, and post-launch support are available?

Big Time IT Solutions Inc is based in Surrey, BC, and states that it serves clients locally and across Canada, the US, and the UK. Its published process refers to project analysis, prototyping, delivery, and quality-assurance testing. Treat these as points for discussion, then confirm the precise scope, milestones, access terms, and handover requirements in writing.

Step 9: Test the complete website before approving launch

Test representative pages and complete journeys, not just attractive screens. Include phones, tablets, desktop widths, portrait and landscape orientations, and realistic connection conditions where they matter.

• Navigate menus, search, breadcrumbs, calls to action, and error pages.
• Complete forms with valid, invalid, missing, and unusually long entries.
• Use keyboard navigation and verify focus order and visible focus states.
• Check headings, labels, readable content, images, links, and downloadable files.
• Test redirects, internal links, metadata, analytics, tracking, and indexing controls.
• Test ecommerce product browsing, cart, checkout, confirmation, notifications, and administration where applicable.
• Confirm integrations, email delivery, backups, security settings, and rollback procedures.
• Obtain content-owner approval for every launch-critical page.

Assign one person authority to record defects and another authority to approve launch. The project should also have a documented response if a critical form, redirect, integration, or checkout process fails after release.

Launch-readiness checklist: proceed, narrow the scope, or pause

Proceed when goals, scope, content owners, account access, sitemap, technical requirements, redirects, testing, approvals, and post-launch responsibilities are documented.

Narrow the scope when the audit shows that the current structure works and the problem is limited to selected content, visual elements, performance improvements, or a controlled platform migration.

Pause when the business lacks domain or system access, nobody owns content decisions, critical integrations are undefined, important URLs have no destination, or launch approval has no clear authority.

Frequently asked questions

How do I know whether my website needs a refresh or a full redesign?

Choose a refresh when the structure and user journeys work but selected content, visuals, or functionality need improvement. Choose a redesign when navigation, accessibility, information architecture, performance, or core functionality require broader change.

What should be included in a website redesign brief?

Include goals, audiences, user tasks, page inventory, sitemap, content responsibilities, technical requirements, integrations, SEO safeguards, accessibility expectations, milestones, approvals, testing, ownership, launch support, maintenance, and exclusions.

How can I preserve SEO during a website redesign?

Inventory important URLs, map changed pages to relevant destinations, implement and test redirects, preserve useful content intent, review titles and headings, check internal links, and monitor indexing and analytics after launch. These steps reduce avoidable losses, but do not guarantee ranking improvements.

Who should own the domain, hosting account, and website files after a redesign?

Clarify ownership and administrator access in the contract before work begins. Confirm control of the domain, DNS, hosting, content management system, analytics, data, design files, development files, and licensed assets.

What should I test before launching a redesigned ecommerce website?

Test product discovery, categories, search, filters, product details, cart, checkout, payments, shipping, taxes, confirmation messages, order notifications, returns information, mobile layouts, error states, analytics, and administrative workflows.

Conclusion: start with the smallest scope that solves the real problem

Good website redesign planning is an evidence-based decision process. Audit the current site, define user tasks, choose migration, refresh, or redesign based on the actual problem, and document the content, access, SEO, accessibility, technical, and testing requirements before approving a visual concept.

If the project is ready, move forward with a brief that names owners, deliverables, approvals, and launch checks. If critical information or access is missing, pausing is safer than discovering those gaps after development has started.

Big Time IT Solutions Inc provides responsive website design, ecommerce development, website optimisation, prototyping, and quality-assurance-related services for businesses in Surrey and beyond. Request a discussion to confirm whether its stated capabilities and process fit your redesign requirements.