Category: Website Design & Development

A small business website redesign checklist helps you improve an outdated site without overlooking the content, SEO, usability and technical details that already support your business. A website redesign often begins with a simple complaint: the site looks old. That may be true, but appearance is rarely the only problem worth solving.

The website may also be difficult to use on a phone, slow to load, unclear about what the business offers or ineffective at turning visitors into enquiries. Redesigning without understanding these problems can produce a more attractive website that performs no better than the old one. It can also remove useful content, break existing links and make pages that already rank in search results harder to find.

This checklist covers what to review before development begins, what to check while the new site is being built and what to monitor after it goes live. The objective is not simply to give your website a different appearance. It is to create a website that represents your business accurately, helps visitors find what they need and supports measurable goals.

Does Your Website Need a Refresh or a Full Redesign?

Before planning new pages or choosing colours, decide how much of the current website actually needs to change. A complete redesign is not always necessary.

A website refresh makes focused improvements while retaining most of the existing structure. It may involve updating colours, fonts, photographs, page copy or calls to action. You might also improve selected pages, simplify the navigation or correct mobile layout problems without rebuilding the entire website.

A full redesign goes further. It may introduce a new page structure, different navigation, redesigned templates, rewritten content or a new content management system. It is usually appropriate when the existing website’s structure or technology prevents meaningful improvement.

A refresh may be enough when

• The website structure still matches your services.
• Most pages remain accurate and useful.
• The site works properly on mobile devices.
• Your team can update the content without difficulty.
• Only the branding, copy or selected layouts feel outdated.
• Search traffic and enquiries remain reasonably stable.

A complete redesign may be required when

• Visitors struggle to understand what your business offers.
• The navigation has become confusing.
• Important services do not have dedicated pages.
• The website performs poorly on mobile devices.
• Pages load slowly because of an outdated or overloaded setup.
• Your brand, services or target audience have changed significantly.
• The website is difficult for your team to update.
• Contact forms and important features frequently fail.
• Organic traffic or enquiries have declined.
• The existing platform can no longer support the features you need.

Do not rebuild the website simply because a competitor launched a new one. Start with the problems affecting your own customers and business. A focused refresh can sometimes correct those problems faster and with less risk.

Define the Purpose of the Redesign

A redesign becomes difficult to manage when its goal is simply to “make the website better.” Everyone involved may have a different interpretation of what better means.

Choose one primary outcome before discussing layouts or visual styles. Your main goal may be to:

• Generate more qualified enquiries.
• Increase online purchases or bookings.
• Present your services more clearly.
• Improve mobile usability.
• Support a new brand position.
• Reach a different type of customer.
• Make the website easier to maintain.
• Improve organic search visibility.
• Replace an outdated website platform.

You can have supporting goals, but one primary objective helps guide decisions. If generating enquiries is the priority, the page structure, copy, trust signals and calls to action should all support that outcome. A design element that looks impressive but distracts visitors from contacting the business may not be a useful addition.

Turn broad goals into results you can evaluate. “Improve the contact page” is vague. “Increase completed contact forms while reducing irrelevant enquiries” gives you something more meaningful to measure.

It is also useful to define what is outside the project. Agreeing on the required pages, features, content and integrations early helps prevent delays and unexpected costs.

Before moving forward, write down:

• The main reason for the redesign.
• The audience the website needs to serve.
• The most important action visitors should take.
• The services or products that need greater visibility.
• The problems customers currently experience.
• The results that will indicate improvement.
• The pages and features included in the project.

This short document becomes a reference point when opinions differ later. Instead of asking whether someone personally likes a design, you can ask whether it supports the agreed goal.

Record Current Performance Before Making Changes

You cannot judge whether the redesign improved the website if you do not know how the existing site performs.

Record a practical baseline before changing pages, URLs or tracking settings. Focus on information that shows how visitors find the website and what they do after arriving. Review the previous six to twelve months where possible to reduce the effect of short-term or seasonal changes.

Record:

• Overall website traffic.
• Organic search traffic.
• Most-visited landing pages.
• Pages generating enquiries or sales.
• Current search queries and rankings.
• Contact-form submissions.
• Phone calls or bookings attributed to the website.
• Conversion rates for important pages.
• Mobile and desktop traffic.
• Page-loading performance.
• Indexed pages.
• Pages receiving external links.
• Common 404 errors.
• Current engagement patterns.

Google Analytics can help you understand how people use the website, while Google Search Console shows which pages and search queries bring visitors from Google. Your form, booking or ecommerce system may contain additional conversion information.

Pay particular attention to pages that already perform well. A service page may look outdated but still attract valuable search traffic and enquiries. Removing it, rewriting it without a clear reason or changing its URL carelessly can damage an asset the business has built over time.

Save copies of your current sitemap, important metadata and existing URLs. Take screenshots of essential pages if helpful. Performance data should guide the project, but it should not make every decision automatically. A low-traffic legal page may still be necessary, while a high-traffic article may attract visitors who never become customers.

By the end of this first stage, you should know whether the website needs a refresh or full redesign, what the project is expected to achieve and which parts of the existing site must be protected.

Audit Every Existing Page and Content Asset

Once you understand what the redesign should achieve, examine what already exists. Many projects run into trouble because the visible navigation is mistaken for the complete website.

A menu may contain only ten pages, while the website actually has hundreds of blog posts, campaign pages, old service pages, images and downloadable files. If these are discovered late, the project can require more time and content work than expected.

Create a content inventory using sources such as:

• Your XML sitemap.
• Google Search Console.
• Google Analytics.
• The WordPress page and post lists.
• Landing-page software.
• Ecommerce product collections.
• Server or website crawl reports.
• Files linked from emails or advertising campaigns.

Include blog posts, category archives, landing pages, downloadable PDFs, videos and images that receive traffic or have links pointing to them. A basic inventory can contain the current URL, page title, page type, purpose, organic traffic, conversions, external links, last update date, recommended action and proposed new URL.

Assign one action to each page:

• Keep: The page is accurate, useful and should remain mostly unchanged.
• Update: The subject remains valuable, but the content, design or information needs improvement.
• Combine: Two or more pages cover the same subject and would be more useful as one stronger page.
• Redirect: The page will no longer exist, but visitors should be sent to a closely related replacement.
• Remove: The content is outdated, unnecessary and has no suitable replacement.

Traffic should inform these decisions, but it should not make them automatically. Consider each page’s business value alongside its numbers. Pay special attention to old prices, former employees, discontinued services, closed locations and expired offers.

Review Competitors Without Copying Them

Competitor research can reveal what visitors expect from websites in your market. Select three to five businesses that compete for the same customers, not simply websites whose visual design you admire.

Review:

• How quickly the homepage explains what the business does.
• How services are organized.
• What appears in the main menu.
• Where calls to action are placed.
• Which questions are answered.
• How testimonials and case studies are presented.
• Whether prices or service processes are explained.
• How the website works on a phone.
• How easy it is to contact the business.
• What information appears to be missing.

Record both effective and frustrating elements. The purpose is not to reproduce another business’s layout, wording or brand. Use the research to identify what customers expect, which questions you can answer more clearly and how your website can provide something competitors do not.

Plan the New Website Structure

The website structure determines how pages are organized and how visitors move between them. It should be planned before individual pages are designed.

Begin with the pages most businesses need:

• About page.
• Main services page.
• Individual service pages.
• Case studies or portfolio.
• Blog or resource section.
• Contact page.
• Privacy policy and other required legal pages.

Additional pages depend on the business. A local service company may need separate location pages. A consultant may need industry-specific pages. An ecommerce business will require product, category, delivery and returns information.

Keep the main navigation focused. Adding every page to the menu does not make the website easier to use. Group related content under clear labels and place less important links in the footer or within relevant pages.

Plan at least one clear journey for each important audience, such as homepage to service page to case study to contact form, or blog article to related service to consultation request. Ask someone unfamiliar with the project to review the planned navigation.

The blog also needs a manageable category structure. Categories should represent subjects you expect to publish about regularly. Avoid creating a separate category for every article.

Create a Page-by-Page Content Plan

A sitemap shows which pages will exist. A content plan explains what each page must accomplish.

For every important page, record:

• The intended audience.
• The primary subject.
• The main customer question.
• The desired visitor action.
• Required sections.
• Existing content that can be reused.
• New content that must be written.
• Images or videos needed.
• Relevant testimonials or case studies.
• Internal links.
• The person responsible for review and approval.

This prevents designers from building sections around placeholder text that later proves too short or too long. Decide who will write, review and approve each page so content does not delay the project.

Map Every Old URL to Its New Destination

URL planning is one of the most important parts of a redesign, particularly when the existing website receives search traffic.

A URL is the address of a page, such as example.com/services/website-design. If the address changes, visitors and search engines using the old address need to be sent to the correct new page through a permanent redirect.

Keep existing URLs when they remain accurate and useful. Unnecessary URL changes create additional work and risk. When a change is necessary, send each old page to the most relevant replacement. Do not redirect every removed page to the homepage.

Google recommends preparing an old-to-new URL map, updating internal links and using permanent server-side redirects when addresses change. See: Move a site with URL changes.

Use the URL map to configure redirects, update internal links and canonical addresses, build the new sitemap, test old links after launch and identify pages that were omitted. Include important images, PDFs and other files as well as standard pages.

Prepare Content Before Development Begins

Website content is often treated as something that can be added after the design is finished. In practice, design and content depend on each other.

A page built around two short paragraphs will not work well if the final copy requires detailed service information, testimonials and FAQs. Prepare as much content as possible before the main development work begins so layouts can be built around real information.

Gather:

• Final service and product descriptions.
• Company background and history.
• Team biographies.
• Customer testimonials.
• Case studies and project examples.
• Certifications, memberships and awards.
• Service areas and business locations.
• Contact information and opening hours.
• Frequently asked questions.
• Pricing information, where appropriate.
• Calls to action.
• Privacy and other required legal information.
• Photographs, videos and brand graphics.

Review every item for outdated services, former employees or incorrect contact information. Organize approved content by page and decide who will write missing sections, check accuracy and provide final approval.

Build Every Page Around a Clear Purpose

Each page should have one primary job. The homepage introduces the business and directs visitors to suitable next steps. A service page explains one offering and encourages an enquiry. A case study demonstrates results. A contact page makes starting a conversation simple.

Before writing or designing a page, answer four questions:

1. Who is expected to visit this page?
2. What do they need to understand?
3. What concerns could prevent them from acting?
4. What should they do next?

A useful service page might explain the service, the problem it solves, what is included, how the process works, relevant experience, FAQs and a clear next step.

Place the most important information near the beginning. Use one clear main heading followed by descriptive subheadings. Short paragraphs, lists and highlighted details make content easier to scan, especially on mobile devices.

Calls to action should match the visitor’s likely level of interest. Avoid placing several competing actions beside each other; when every button is equally important, visitors may struggle to choose.

Design for Mobile Visitors from the Beginning

Mobile design is not the desktop version squeezed into a smaller screen. It requires decisions about what visitors need first and how they will interact using their fingers rather than a mouse.

Review the redesigned website on real mobile devices, not only inside the website editor. Check that:

• Text is readable without zooming.
• Buttons are large enough to tap comfortably.
• Links are not packed too closely together.
• The navigation opens and closes correctly.
• Phone numbers can be tapped to call.
• Forms are short and easy to complete.
• Images fit without horizontal scrolling.
• Tables remain readable.
• Pop-ups do not cover important content.
• Important calls to action appear at suitable points.
• Headings do not break awkwardly.
• The page remains usable in portrait and landscape views.

Think carefully about content order when side-by-side desktop sections stack vertically. Crop background images intentionally and remove decorative elements when they make content harder to read.

Google recommends responsive design because it allows the same URL and content to work across screen sizes and is easier to maintain. See: Mobile site and mobile first indexing

Do not assume that a responsive theme makes every page mobile-friendly. Content length, image dimensions, custom sections and third-party tools can still create problems.

Include Accessibility from the Start

An accessible website allows more people to understand and use its content, including visitors who rely on keyboards, screen readers or other assistive tools. Accessibility is easier to include during the redesign than to repair later.

Start with these checks:

• Use sufficient contrast between text and its background.
• Keep body text comfortably readable.
• Maintain a logical heading order.
• Add descriptive alt text to meaningful images.
• Label every form field clearly.
• Make links understandable outside the surrounding sentence.
• Ensure menus and forms can be used with a keyboard.
• Show which element currently has keyboard focus.
• Provide captions or transcripts for important video content.
• Do not rely only on colour to communicate meaning.
• Use buttons for actions and links for destinations.
• Write clear error messages for incomplete forms.

Alt text should describe the purpose of an image in context. Avoid generic links such as “click here” when more useful wording is possible. Forms should keep instructions visible and explain how to correct errors.

The W3C Web Accessibility Initiative provides practical guidance. Automated tests can identify some problems, but manual keyboard testing and task-based reviews remain valuable.

Control Images, Fonts and Extra Features

Modern designs can become unnecessarily heavy when every available visual effect is used. Large photographs, video backgrounds, animations, multiple font families and third-party tools all add work for the browser.

Use visuals with a clear purpose. Before uploading images:

• Resize them to the largest dimensions actually needed.
• Compress the files.
• Choose a suitable file format.
• Use descriptive filenames.
• Add appropriate alt text.
• Check how they crop on different screens.
• Avoid uploading several nearly identical copies.

Keep typography simple. One font for headings and another for body text is usually enough. Animations should support understanding rather than delay it.

Review plugins, embedded tools and tracking scripts with the same care. Keep those that provide a necessary business function and remove those that duplicate features or are no longer used.

Build the New Website on a Private Staging Version

A redesign should normally be developed away from the live website. This private copy is often called a staging website. It allows the team to build pages, test features and review content without disrupting the website customers currently use.

Before major work begins, create a complete backup containing website files, the database, images, downloads, theme and plugin settings, custom code, redirect rules and important server settings. Confirm that the backup can be restored.

The staging website should not appear in search results. Password protection is generally safer than relying on one setting inside the content management system. Keep a record of every restriction applied so accidental noindex settings or blocked robots rules are removed from the live site at launch.

Keep the existing website available during development. If the live site receives new posts, products or customer information, plan how those updates will be transferred.

Use staging for task-based reviews. Ask reviewers to find a service, submit the contact form, locate the phone number, read an article or complete a booking. These tasks reveal problems that general feedback may miss.

Transfer Existing SEO Elements Carefully

A redesigned page should not lose useful search information simply because its layout changed.

For each important page, review the existing:

• Page title.
• Meta description.
•  
• Main and supporting headings.
• Core content.
• Internal links.
• Image alt text.
• Canonical URL.
• Structured data.
• Indexing settings.

Preserve elements that already perform well, but do not copy every item automatically. Keep what remains useful and improve what is weak or outdated.

Every indexable page should have one clear primary topic. Update internal links to point directly to final new addresses rather than relying on redirects. Review links in the main content, menus, buttons, footers, blog posts, reusable sections and downloadable documents.

If URLs change, each new page should contain the correct canonical address. The XML sitemap should list only final indexable URLs and should not contain staging pages, redirects or broken addresses. Check structured data instead of assuming it transferred correctly.

Before launch, compare the old and new versions of high-value pages side by side. Confirm that important information has not been shortened, removed or hidden merely to create a cleaner design.

Complete a Page-by-Page Quality Check

Quality assurance should be a planned stage, not a quick review on launch day. Create a checklist and record the problem, device, browser, person responsible and status of the fix.

Check Content and Formatting

Review page titles, headings, spelling, paragraph spacing, lists, tables, images, captions, alt text, contact details, prices, button wording, downloads, dates and author information. Look for placeholder text, duplicate sections and unfinished buttons.

Test Navigation and Links

Click menu items, dropdowns, footer links, buttons, text links, logo links, breadcrumbs, social icons, email addresses and telephone numbers. Confirm that internal links do not point to staging addresses.

Test the custom 404 page by visiting an address that does not exist. It should explain what happened and provide a useful route back into the website.

Test Forms and Notifications

Submitting a form successfully on the page does not guarantee that the message reaches the business. Test every form from beginning to end:

• Complete all fields correctly.
• Leave required fields empty.
• Enter an invalid email address.
• Submit from a mobile device.
• Confirm the success message.
• Check the recipient inbox and spam folder.
• Verify any automatic reply.
• Confirm the submission is stored where expected.
• Test email or customer-management integrations.

Use a real external email address for testing. Check that forms collect only information the business genuinely needs.

Test Across Devices and Browsers

Review the website on a desktop, laptop, tablet and at least two mobile screen sizes. Use browsers relevant to the audience and test at widths between standard device presets.

Test Important Business Functions

Depending on the website, test product search, cart, checkout, discount codes, payment processing, shipping calculations, booking, registration, password reset, memberships, downloads, live chat, language selection and maps. Use test transactions and confirm that both customer and business notifications arrive.

Verify Analytics and Conversion Tracking

Check that contact-form submissions, phone clicks, email clicks, quote requests, purchases, bookings, downloads and newsletter sign-ups are recorded. Avoid duplicate tracking codes that can make reports unreliable.

Confirm Website Ownership and Account Access

A small business should retain control of the accounts that keep its website operating. Confirm who owns and can access:

• Domain registration.
• Website hosting.
• WordPress administration.
• Business email.
• Google Analytics and Search Console.
• Google Business Profile.
• Payment processor.
• Form and email services.
• Premium themes and plugins.
• Image and font licences.
• Backup storage.
• Security and performance services.

Where possible, accounts should use an email address controlled by the business rather than a developer’s personal address. Give each person only the access needed for their role and remove accounts that are no longer required.

Store account ownership, renewal dates, licence details, support contacts, backup locations and recovery methods securely. Enable additional login protection for the domain, hosting, website administration and payment accounts.

Complete the Final Launch Checklist

The launch should be treated as a controlled process rather than the moment someone presses a publish button. Choose a lower-traffic time and ensure the people responsible for development, content and enquiries are available.

Create one final backup of the live website immediately before replacing it. Before launch, confirm:

• All approved pages are present.
• Placeholder content has been removed.
• Contact information is correct.
• Forms send messages to the right recipients.
• Analytics and conversion tracking are active.
• The website uses a valid SSL certificate.
• Staging URLs do not appear in links or images.
• Temporary noindex settings have been removed.
• Search engines are not blocked from the live website.
• Canonical URLs use the live domain.
• The sitemap contains the final URLs.
• Permanent redirects are ready.
• Navigation and footer links work.
• Legal pages are accessible.
• Backups are running.
• The site works on mobile devices.
• Important pages load without an administrator login.

If URLs change, activate redirects as the new site goes live and test a sample immediately. Google recommends keeping permanent redirects for at least one year. After launch, clear relevant caches, review the website in a private browser window and complete a test enquiry, purchase or booking.

Monitor the Website After Launch

A successful launch does not mean the project is finished. Some problems appear only after real visitors and search engines begin using the new website.

During the First 24 Hours

Check the homepage, important service pages, mobile navigation, forms, checkout or booking functions, SSL, analytics, server errors, images, downloads, redirects and accidental staging links. Ask someone who was not involved in the build to complete a typical customer journey.

During the First Week

Review Search Console indexing reports, the sitemap, 404 errors, redirects, organic landing pages, submissions, phone and email clicks, website speed, mobile usability and customer feedback. Avoid drawing firm conclusions from only a few days of data.

During the First 30 to 90 Days

Compare the redesigned website with the original baseline. Review organic traffic, search impressions and clicks, important keyword positions, enquiries, sales, conversion rates, engagement, mobile performance, page speed and index coverage.

Some search fluctuations can occur while Google recrawls substantial changes. Investigate clear errors instead of reacting to every daily movement. Use business results alongside traffic numbers and keep a record of improvements made after launch.

Treat the Website as an Ongoing Business Asset

A redesigned website will gradually become outdated if no one is responsible for maintaining it. Assign ownership and a monthly or quarterly review schedule for:

• Software and security updates.
•  
• Form testing.
• Website access reviews.
• Service and price updates.
• Fresh content.
• Team information.
• Broken links.
• Image optimization.
• Analytics and conversion reviews.
• Mobile testing.
• Licence, hosting and domain renewals.
• Removal of unused users, themes and plugins.

Review high-value pages first, including the homepage, main services, contact page, popular articles and pages responsible for enquiries or sales. Do not wait for another full redesign; small improvements based on customer questions and performance data are easier to manage.

Final Small Business Website Redesign Checklist

Use this condensed small business website redesign checklist to confirm that the essential work has been completed.

Strategy and Planning

• Decide between a focused refresh and complete redesign.
• Define the primary business goal and audience.
• Record current traffic, rankings and conversions.
• Confirm the scope, budget and responsibilities.

Content and Structure

• Create an inventory of pages, posts and files.
• Mark content to keep, update, combine, redirect or remove.
• Review competitor websites.
• Plan the sitemap, navigation and customer journeys.
• Prepare a page-by-page content plan.
• Assign writing and approval responsibilities.
• Gather testimonials, images and brand assets.

URLs and SEO

• Record every important existing URL.
• Map old URLs to relevant new destinations.
• Preserve high-performing content.
• Review titles and meta descriptions.
• Transfer headings, internal links and image alt text.
• Update canonical URLs and structured data.
• Prepare permanent redirects and the XML sitemap.
• Remove accidental search-engine blocks.

Design and Development

• Create a complete backup.
• Build the new website on staging.
• Use approved content in the layouts.
• Check mobile navigation and content order.
• Review accessibility.
• Resize and compress images.
• Limit unnecessary plugins, scripts and animations.
• Confirm important integrations work.

Testing and Launch

• Proofread every important page.
• Test menus, buttons, links and forms.
• Confirm email notifications arrive.
• Test relevant browsers and devices.
• Complete test purchases or bookings.
• Verify analytics and conversion tracking.
• Confirm business ownership of important accounts.
• Create a final pre-launch backup.
• Test redirects and submit the sitemap.
• Check the website as a logged-out visitor.

Post-Launch

• Monitor errors during the first 24 hours.
• Review Search Console during the first week.
• Compare results with the original baseline.
• Check leads, sales and form submissions.
• Review mobile performance and redirect errors.
• Schedule ongoing website and content maintenance.

Frequently Asked Questions

How often should a small business redesign its website?

There is no fixed schedule that suits every business. Consider a redesign when the website no longer represents your services, performs poorly on mobile devices, is difficult to maintain or consistently fails to support enquiries and sales. Do not redesign solely because a certain number of years has passed.

What is the difference between a website refresh and a redesign?

A refresh improves selected visual or content elements while keeping most of the existing structure. A redesign may change the navigation, templates, content, technology and customer journeys. A refresh is often suitable when the website works but looks or feels outdated.

Can a website redesign hurt SEO?

Yes, particularly when useful content is removed, URLs change without redirects, internal links are broken or the live website accidentally blocks search engines. Careful auditing, URL mapping, SEO transfer and post-launch monitoring can reduce these risks.

How long does a small-business website redesign take?

The timeline depends on the number of pages, features, content readiness and speed of feedback. A small website using approved content may take several weeks, while a larger project involving ecommerce, new content or a platform change can take several months.

Should the current website stay live during the redesign?

In most cases, yes. The new version can be prepared on a private staging website while the existing site continues serving customers. Replace the live website only after the redesigned version has been reviewed and tested.

What should I prepare before hiring a website designer?

Prepare your redesign goals, website access, page inventory, brand assets, service information, examples you like, required features and approximate budget. Identify who will provide content and who has final approval.

Plan the Redesign Around What Your Business Needs

A successful redesign is not measured by how different the website looks. It is measured by whether customers can understand the business, find useful information and complete important actions more easily.

The strongest projects begin with an honest review of the existing website. They protect pages and content that already provide value, improve areas that create friction and test the complete customer journey before launch.

Following a structured small business website redesign checklist gives designers, developers, writers and business owners a shared process. It reduces missed details and helps the new website launch with clearer content, safer URL changes and more reliable tracking.

Need Help Redesigning Your Business Website?

NextWebOps can help organize your website structure, WordPress setup, content implementation, on-page SEO and final quality checks. The goal is a website that is easier for visitors to use and easier for your business to manage after launch.