Small Business Website Redesign Checklist: What to Fix Before Rebuilding
Test your contact forms, mobile experience, service pages, and existing search traffic before approving a website rebuild. Use the findings to request a clear scope.
A small business website redesign should solve a specific problem: customers cannot understand your services, complete an inquiry, or reach the right person. Before approving a rebuild, check whether a smaller set of repairs would solve that problem.
Use this checklist to assemble a practical brief for a web designer. You will end with three lists: what already works, what needs fixing, and what a replacement site must do. That gives you a way to judge the proposal and the finished work.
1. Choose the customer action you want to improve
Write one sentence: "We want more inquiries for [service] from customers in [area]." Be specific enough that you could recognize a suitable inquiry when it arrives.
For a hypothetical painting company, "more leads" is vague. "Requests for exterior painting estimates within our service area" identifies the job, geography, and next step. Its website can then explain that service and offer an estimate request with the right details.
Record your starting point using the information you actually have:
- Which pages receive visits from Google?
- How many website inquiries reached you during the period you are reviewing?
- How many were for services and locations you accept?
- Which inquiries became estimates, appointments, or paid work?
Search Console provides search impressions and clicks, including breakdowns by page and query. It does not tell you whether a customer hired you; keep that outcome in your inquiry records. Google's Search Console guide explains the available search reports.
2. Test the entire contact journey
Open a service page on your phone and act like a prospective customer. Find the contact option, complete the form using clearly labeled test details, and check the destination inbox. Tell your team that the test is coming so nobody mistakes it for a genuine request.
Record whether:
- The call button opens the correct number.
- The form asks for enough information to follow up.
- Required fields and errors are understandable.
- A successful submission reaches the right inbox.
- A failed submission leaves a usable alternative, such as a phone number.
- Someone is responsible for replying to the inquiry.
A form's success message proves that the page displayed a message. Confirm delivery separately. If this journey fails, include the repair in the immediate scope, even if you later commission a redesign.
Also check what happens after delivery. A working website cannot resolve an unattended inbox or an outdated voicemail greeting.
3. Review the mobile experience with a real task
Ask someone unfamiliar with the business to use the site on their phone. Give them a task such as finding whether you offer a particular service and requesting a quote. Watch where they hesitate.
Look for small text, buttons covered by banners, horizontal scrolling, large images that delay useful content, and important information buried beneath decorative sections. Keep a screenshot and a short description of each problem.
Preserve visual elements that help explain your work. A useful project gallery may deserve better image sizing and clearer captions. It does not automatically need replacing because the rest of the site is changing.
4. Inventory the pages worth keeping
Make a list of existing page addresses before anyone deletes or renames them. Add each page's purpose, available search traffic, relevant inquiries, and intended destination on the updated site.
Your list might mark a service page "keep address, improve content" and an outdated page "combine with the current service guide." This makes the migration work visible in the proposal.
When addresses change, Google recommends mapping old URLs to appropriate new destinations and using permanent redirects. Sending unrelated old pages to the homepage can confuse visitors and be treated as a soft 404. Ask for redirects to be tested before and after launch. Google's site-move guidance covers this process.
A change of visual design does not inherently require a new domain or new addresses for every page. Ask what each proposed URL change accomplishes.
5. Check whether your service information answers buying questions
Read the pages for the work you actually want to sell. A prospective customer should be able to understand:
- What the service includes and any important exclusions.
- Who the service is for and where you provide it.
- What information you need to prepare an estimate or arrange an appointment.
- What happens after the customer contacts you.
- What relevant work or other evidence they can review.
Use photographs and examples you have permission to publish. Label demonstration work clearly. Keep claims about results tied to evidence you can explain.
Ask for clear, descriptive page titles too. Google uses several sources to produce search-result titles and recommends titles that accurately describe each page. The SEO Starter Guide explains the basics.
6. Check the route from your Google listing
If your business has an eligible Google Business Profile, open its public website link and confirm that it reaches the correct business and page. Review the phone number, hours, and business details at the same time.
Google says complete and accurate profile information can help a business appear for relevant local searches. A new website does not replace that work. Google's local-ranking guidance explains the role of business information and local ranking factors.
For a grounded example, the Sunsilk Tailor case study describes a website build and correction of a listing that had sent visitors to another business. A qualified fitting inquiry arrived through the new form; a completed booking or sale was not verified.
7. Decide between repairs and a rebuild
Use the problems you found to compare the scope:
| What you found | Work to discuss |
|---|---|
| Clear service pages, but a broken contact form | Form repair, delivery checks, and tracking |
| Useful site with confusing navigation or weak mobile layouts | Focused layout and navigation improvements |
| Missing information for the services you want to sell | Service-page content and a clearer inquiry path |
| Platform prevents needed changes or creates recurring maintenance problems | A rebuild with a migration and handover plan |
| A new visual direction is important to your business | Design changes with an agreed list of elements to preserve |
These are decision prompts, not a diagnosis of your site. Have the designer explain which existing components can be reused and why a rebuild, if proposed, addresses the problems you documented.
Your brief before requesting a quote
Bring the page inventory, mobile screenshots, contact-test results, and your preferred customer action. Add the features you want to preserve and the person who will approve copy and design.
Ask for a written list of deliverables, responsibilities, additional costs, and launch checks. Our guide to comparing small business web design proposals can help you compare the responses.
SleftAI reviews existing websites, Google listings, and inquiry processes before recommending a scope. Request a Website Review with your website, location, and the service you want more inquiries for. If the project fits, Grant will prepare a scope, timeline, and quote.