Small Business Website Redesign Checklist: Plan It Safely

A small business website redesign checklist should not begin with colours, templates or animation ideas. It should begin with a harder question: what must the website do better for the business, and what existing value must survive the project?

A redesign can clarify an offer, make proof easier to find, improve the enquiry path and replace a fragile technical foundation. It can also remove pages that already earn visibility, break links, weaken forms or hide the same commercial problem behind a cleaner interface.

This guide helps a small B2B company decide between focused improvements and a full redesign, then scope the work before approving a proposal. It does not promise automatic growth. Its purpose is to protect useful assets, make decisions testable and turn the website into a commercial system that can improve over time.

Illustrations in this article, including the featured image, are AI-generated.

Repair, improve or redesign: make this decision first

A full rebuild is not always the safest answer. If the website has a sound technical base, sensible URLs and a clear content structure, a focused improvement to messaging, priority pages or forms may create value faster and with less disruption.

A redesign becomes more credible when several issues overlap: the offer is no longer clear, navigation reflects internal departments rather than buyer needs, content is difficult to maintain, mobile use is uncomfortable, proof is scattered, the technology is fragile, or nobody can measure what happens after an enquiry.

Checklist 1: define the commercial job and baseline

Before designing anything, describe the future website’s job in one sentence. It might need to explain a technical offer before a sales call, produce better-qualified enquiries, reassure procurement teams, present premium project proof or help buyers choose the right service. Manufacturers and industrial suppliers will find sector-specific structure guidance in our manufacturing website design and SEO guide.

Then record the starting point. List pages that receive organic visits, visible Search Console queries, forms people use, enquiries that reach the sales team, pages viewed before contact and content that earns external links. Without a baseline, it is impossible to tell a genuine improvement from a stronger visual impression.

• Which commercial action should the website make easier?
• Which pages already support visibility, trust or sales conversations?
• Which actions must be measured: forms, calls, bookings, downloads or RFQs?
• Who owns messaging, proof, content and final approval?
• Which constraints are fixed: access, budget, languages, CRM, maintenance or compliance?

Checklist 2: inventory pages, content and access

A small company should not start again from zero without knowing what it owns. Export the URL list, titles, metadata, documents, images, forms, redirects, visible pages and important internal links. Add access to the domain, hosting, CMS, backups, Search Console, analytics and form systems.

Give every page a proposed action: keep, improve, merge, replace or retire. A merge or removal should never be automatic. Check the search intent, visits, incoming links and the closest useful destination first. If an address changes, include it in a complete old URL → new URL map.

Checklist 3: rebuild around buyer decisions

The new structure should follow the questions a buyer needs answered, not merely mirror the company organisation. A visitor should quickly understand what you do, who it is for, when it is relevant, what proof supports it and what step to take next.

Every important page needs a role. The homepage establishes the promise and routes visitors. Service pages explain the problem, method, scope and evidence. Project or case-study pages reduce risk. Articles answer questions buyers ask before they speak to sales. The form should collect enough context to help the team without turning the first contact into an application process.

AUTOM7 frames website creation and redesign as the construction of a commercial asset: clearer messaging, offer pages, proof, SEO structure, measurement and useful integrations. That approach prevents the project being reduced to a theme or a collection of screens.

Checklist 4: protect SEO throughout the redesign

Google recommends preparing and testing the new site, mapping old URLs to their new destinations, implementing server-side permanent redirects and monitoring traffic after a move.^[1] It also recommends changing one major element at a time where practical instead of combining a domain move, CMS change and new layout in one uncontrolled event.^[1]

• Keep useful URLs when there is no strong reason to change them.
• Create one permanent redirect to the closest relevant replacement for every changed URL.
• Avoid redirect chains and update internal links to their final destination.
• Carry across the titles, metadata, useful copy and internal links of valuable pages before improving them.
• Check canonicals, XML sitemaps and robots.txt, and rule out any accidental noindex directives.
• Keep Search Console and analytics operational before, during and after launch.

Temporary ranking fluctuations can occur while Google recrawls and reindexes changed URLs.^[1] That does not justify promising perfectly stable rankings. A realistic commitment is to prepare, test, monitor and correct issues quickly.

Checklist 5: test mobile, performance and the enquiry journey

A design is not approved until it works on real screens. Test at least one narrow phone, a current smartphone, a tablet and a desktop display. Review typography, buttons, tables, forms, navigation, images and error messages.

Google describes Core Web Vitals as real-world measures of loading, responsiveness and visual stability. Its “good” thresholds are LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, assessed at the 75th percentile of visits.^[2] These measures are useful, but they do not replace the commercial test: a fast website with a vague offer remains weak.

• Can a visitor understand the main message without scrolling?
• Is the primary call to action visible, specific and appropriate to the page?
• Does proof appear near the points where a buyer makes a decision?
• Does the form work and explain what happens next?
• Does the enquiry reach the right person with its source attached?

Checklist 6: require a proposal that describes the system

A redesign proposal should make scope testable. Ask who produces the content, who supplies images, which pages are included, how redirects will be prepared, which measurement tools will be configured, who owns the accounts, how backups will work and what support exists after launch.

Maintenance, SEO, ongoing content, CRM and automation may be included, optional or scheduled for a later phase. The important point is to make that status explicit. A feature described as “planned” without an owner, data source, acceptance test or date is not a deliverable.

Checklist 7: control launch and the next 90 days

Launch should be a sequence, not a celebratory upload: final backup, staging review, redirect activation, form tests, removal of indexing blocks, sitemap checks, inspection of priority URLs and comparison with the baseline.

During the first weeks, watch 404 errors, form delivery, strategic pages, indexing, queries, performance and enquiry quality. Compare signals at 30, 60 and 90 days without treating every daily movement as a strategic verdict. The review should separate launch defects, content gaps and changes that simply need more time.

If you are still deciding between targeted repair and a full rebuild, the AUTOM7 free mini-diagnostic provides a first reading of offer clarity, proof, the enquiry path, mobile experience and how well search systems can understand the website. It helps identify the first useful priorities before committing to a larger project.