Table of Contents (click to expand)
- Pre-redesign checklist
- 1. Crawl the current site
- 2. Identify top SEO pages
- 3. Map old URLs to new URLs
- 4. Protect forms and calls
- 5. Design for mobile first
- 6. Improve speed, do not just preserve it
- 7. Keep accessibility basics in scope
- 8. Rewrite service pages for buyers, not committees
- 9. Add real proof
- 10. Launch with a QA checklist
- Common redesign mistakes
- What this means in practice
- Migration safety checklist
- Launch-day QA
- Redesign priorities for local services
- Related Techpros guides
- Sources and further reading
- FAQs
A website redesign can improve leads, speed, trust, and SEO. It can also quietly destroy the pages that were already bringing in calls.
For a service business, the redesign goal is not “new look.” The goal is a stronger lead path without losing the local visibility, URLs, reviews, proof, and tracking that already work.
Use this checklist before you touch the design.
Quick answer: A service-business redesign should protect URLs, rankings, forms, calls, tracking, proof, speed, and mobile conversion before visual polish. A prettier broken funnel is still broken.
Pre-redesign checklist
| Step | Why it matters |
|---|---|
| Crawl the current site | Find all URLs before they disappear |
| Export top pages from analytics/Search Console | Protect pages that already get traffic |
| Map old URLs to new URLs | Prevent broken links and lost rankings |
| Inventory forms and phone tracking | Avoid launching a prettier lead leak |
| Save title tags and metadata | Preserve useful search signals |
| Review service and city pages | Keep or improve local SEO structure |
| Benchmark speed and mobile UX | Know whether the redesign improves anything |
| Collect reviews/proof/photos | Add trust, not just design polish |
1. Crawl the current site
Before redesigning, get a list of every live URL.
You need to know:
- homepage
- service pages
- city pages
- blog/resource pages
- old campaign pages
- thank-you pages
- PDFs or assets
- sitemap URLs
- redirected URLs
- 404s with backlinks or traffic
If you do not crawl first, you will miss something. That “something” is usually the page that had rankings.
2. Identify top SEO pages
Pull data from Search Console and analytics before launch.
Find pages with:
- organic clicks
- impressions
- form submissions
- phone clicks
- backlinks
- rankings for service terms
- local city/service combinations
Do not replace useful pages with thinner versions because the new layout looked cleaner in a mockup.
3. Map old URLs to new URLs
If URLs change, redirects are mandatory.
Google’s site move documentation recommends mapping old URLs to new URLs, setting redirects, and updating links when URLs change. Source: Google site move guidance.
A redirect map should include:
| Old URL | New URL | Notes |
|---|---|---|
| /services/ | /services/ | Keep if possible |
| /seo-services/ | /services/seo/ | One-to-one replacement |
| /contact-us/ | /contact/ | Preserve form path |
| /blog/old-post/ | /resources/relevant-guide/ | Redirect to closest useful page |
Do not redirect everything to the homepage. That is lazy and bad for users.
4. Protect forms and calls
A redesign that breaks forms is not a redesign. It is sabotage with a launch date.
Test:
- quote form fields
- required field validation
- spam protection
- thank-you page
- email notifications
- CRM and lead routing
- phone links
- call tracking
- source tracking
- mobile form usability
Do not wait for a customer to discover the form is broken.
5. Design for mobile first
Most local buyers compare service businesses on phones. The mobile version is not the afterthought. It is the main event.
Check:
- phone visible in header
- quote CTA visible above fold
- navigation is simple
- text is readable
- buttons are easy to tap
- forms are short
- no horizontal overflow
- photos do not crush load speed
6. Improve speed, do not just preserve it
Google’s Core Web Vitals thresholds for a good experience are LCP ≤ 2.5s, INP ≤ 200ms, and CLS ≤ 0.1 at the 75th percentile. Source: web.dev Core Web Vitals.
During a redesign, watch for:
- huge uncompressed images
- heavy JavaScript
- layout shift from late-loading assets
- third-party script pileups
- bloated page builders
- video backgrounds that add no value
7. Keep accessibility basics in scope
The DOJ says businesses open to the public should make websites accessible to people with disabilities under the ADA. Source: ADA web accessibility guidance.
Minimum checks:
- readable contrast
- keyboard navigation
- form labels
- helpful error states
- alt text where appropriate
- headings in logical order
- buttons and links that make sense
Accessibility is not just legal risk. It is also basic usability.
8. Rewrite service pages for buyers, not committees
Service pages should not say “we offer quality solutions tailored to your needs.” Every competitor says that. It means nothing.
A useful service page explains:
- what the service includes
- signs the buyer needs it
- common problems
- price or budget factors when possible
- process
- service area
- proof
- FAQs
- next step
9. Add real proof
Use:
- testimonials
- reviews
- project photos
- before/after images
- case notes
- certifications
- warranties
- service vehicles/team photos
- local market context
Trust is not built by saying “trusted.” It is built by showing reasons to trust.
10. Launch with a QA checklist
Before launch:
- build passes
- all main pages return 200
- redirects work
- forms submit correctly
- phone links work
- tracking fires
- sitemap is live
- robots.txt is correct
- canonical tags are correct
- mobile menu works
- no console errors on key pages
- no horizontal overflow
- schema validates enough to be clean
After launch:
- check Search Console coverage
- inspect top URLs
- test forms again
- monitor 404s
- watch rankings and traffic
- verify ads landing pages if campaigns are live
Common redesign mistakes
- launching without a redirect map
- deleting useful service pages
- replacing detailed pages with thin copy
- forgetting thank-you pages
- breaking call tracking
- hiding the phone number on mobile
- using stock photos everywhere
- ignoring site speed
- skipping accessibility basics
- not checking Search Console after launch
What this means in practice
A service-business redesign checklist should protect old URLs, rankings, forms, calls, tracking, reviews, proof, page speed, mobile CTAs, and conversion paths before visual polish. The redesign is not successful if the new site looks better but loses leads or breaks measurement.
A redesign has two jobs:
- Improve trust and conversion.
- Preserve or improve the visibility that already exists.
If either job is ignored, the launch is risky.
Migration safety checklist
| Item | Why it matters | Done? |
|---|---|---|
| Crawl existing site | Finds every URL that may need protection | ☐ |
| Identify traffic/backlink pages | Keeps valuable pages from disappearing | ☐ |
| Map redirects | Prevents broken links and lost equity | ☐ |
| Preserve service intent | Avoids deleting ranking/service relevance | ☐ |
| Verify forms | Prevents silent lead loss | ☐ |
| Verify phone/call tracking | Keeps call attribution intact | ☐ |
| Submit sitemap | Helps Google discover the new structure | ☐ |
| Check Search Console | Catches indexing and coverage issues | ☐ |
| Validate schema | Keeps structured data accurate | ☐ |
| QA mobile widths | Prevents hidden overflow and broken CTAs | ☐ |
Launch-day QA
Before launch, test:
- homepage, services, contact, quote, proof pages
- every main CTA
- mobile menu
- tap-to-call links
- form safe failures and success path
- thank-you page/noindex behavior where relevant
- sitemap and robots content types
- old URL redirects
- analytics and conversion tags
- Core Web Vitals basics
- social preview image
- schema JSON-LD parsing
Do not trust “the build passed” as launch approval. A site can build perfectly and still have a dead form. Ask me how fun that is. Actually, don’t.
Redesign priorities for local services
| Page type | What to improve |
|---|---|
| Homepage | Clear service/category, service area, proof, primary CTA |
| Service pages | Process, pricing factors, FAQs, reviews/photos, local intent |
| Contact/quote | Short form, phone, service details, tracking metadata |
| About | Real ownership, local trust, why the company exists |
| Portfolio/results | Specific proof, before/after, project notes |
| Resources | Buyer education that supports services and internal links |
Related Techpros guides
- If conversion is the problem, read Why Your Service Business Website Is Not Converting.
- If SEO preservation is the worry, use the Local SEO Checklist for Utah Service Businesses.
- If you are comparing vendors, read Best Web Design Companies in Utah.
- If tracking needs cleanup, read Call Tracking and Lead Attribution Guide.
Sources and further reading
- Google site move guidance
- Google Search Central SEO Starter Guide
- Google structured data introduction
- web.dev Core Web Vitals
FAQs
Will a redesign hurt SEO?
It can. It should not if URLs, content, redirects, internal links, metadata, and technical SEO are handled carefully.
Should we keep old blog posts?
Keep or redirect posts with traffic, backlinks, or useful relevance. Delete or consolidate weak posts that do nothing.
What is the most important redesign step?
Protect the pages and conversion paths that already work. Then improve the weak spots.
Should tracking be set up before or after launch?
Before. Launching without tracking is how teams argue from vibes instead of evidence.