A small-business website redesign should improve the customer journey without discarding search visibility, analytics history, working forms, or useful content. The safest process treats design, content, SEO, tracking, and launch operations as one project.
Define the business job of the website
List the primary audiences, services, service area, conversions, and objections the site must address. Decide which actions matter—calls, forms, appointments, purchases, downloads, or another measurable outcome. A visual mood board cannot replace this operating brief.
Inventory the current site before changing URLs
Crawl the current site and export every indexable URL, title, description, heading, canonical, status, internal link, and available performance data. Classify each page: keep, improve, consolidate, redirect, or retire. Record backlinks and organic landing pages before making decisions.
When URLs change, create a one-to-one redirect map. Google recommends permanent server-side redirects for permanent moves in its Search Central redirect guidance.
| Workstream | Before build | Launch check |
|---|---|---|
| Strategy | Audience, services, markets, journeys, conversions | Navigation and calls to action support priority journeys |
| Content | Inventory, intent map, gaps, proof, approvals | No placeholders, duplicates, invented claims, or missing pages |
| SEO | Rankings, GSC pages and queries, canonicals, links, redirects | Titles, headings, canonicals, robots, sitemap, and redirects verified |
| UX and accessibility | Device needs, forms, navigation, contrast, keyboard behavior | Critical paths tested on mobile and desktop |
| Measurement | Events, calls, forms, consent, CRM handoff | Real test events reach the correct systems |
| Operations | Hosting, backups, DNS, ownership, rollback | Monitoring and rollback contacts are ready |
Write content before polishing layouts
Real content exposes hierarchy and component needs. Service pages need enough room for scope, process, service boundaries, proof, location context, and next steps. Designing around placeholder copy often produces layouts that fail when actual content arrives.
Protect conversion and tracking systems
Inventory phone numbers, forms, email routing, CRM integrations, analytics tags, advertising pixels, consent tools, thank-you states, and spam controls. Test them without submitting false leads to operational teams. Confirm that source data and event names remain interpretable after launch.
Test the built site as a system
- Responsive layout at common and in-between widths
- Keyboard navigation, focus, labels, and color contrast
- Image dimensions, compression, and alt text
- Internal and external links
- Forms, validation, confirmations, and routing
- Page titles, descriptions, H1s, canonicals, and structured data
- Redirects, 404 behavior, sitemap, and robots rules
- Performance on representative mobile devices
Use a controlled launch
Take a backup, freeze content changes, lower DNS risk where applicable, deploy during a monitored window, and keep a rollback path. Immediately crawl the live site and test critical journeys. Then watch Search Console, analytics, forms, logs, and key rankings for issues that only appear after real crawlers and users arrive.
AQ Marketing offers small-business web design services. A redesign plan should preserve what already works while improving strategy, content, user experience, technical SEO, and launch readiness.
