1. Record the current site before changing it
List the pages, their URLs, main headings, contact actions, and forms. Note which pages explain real services and which ones are outdated. If you have access to search and analytics data, record the pages that already attract relevant visitors and inquiries. A redesign can improve the site without discarding everything that works.
Save copies of approved text, photos, project details, and legal notices. Confirm who owns the domain, where DNS is managed, and who has access to hosting and form delivery. Missing credentials can delay a launch more than design work.
2. Write the customer questions beside each page
For every service page, ask what a visitor needs to know before contacting you. A roof-repair page might need a clear distinction between inspection, patch, and replacement work. An automotive page might need vehicle types, shop hours, and whether an online request is a confirmed appointment. The answer should come from the real business, not a generic template.
Remove duplicate pages only after deciding what information belongs on the replacement page. If a page has no distinct purpose, combine it with the stronger page and plan a redirect from the old URL.
3. Prepare real proof and practical details
Gather approved job photos and write a caption for each: what the customer needed, what your team did, and what the image shows. Verify reviews, credentials, warranties, service areas, hours, phone numbers, and team details. A redesign is a good time to remove claims that are outdated or cannot be supported.
If there are no approved photos yet, keep the page useful with accurate descriptions and a clear process. Do not turn concept art or stock photos into implied client projects.
4. Plan contact paths before the visual polish
Decide whether each visitor should call, request an estimate, book through an approved tool, or send an inquiry. Keep mobile actions visible and forms short. The confirmation message should describe what actually happened: a message was sent, an appointment request was received, or a booking was confirmed. These are different outcomes.
Test every path against a real receiving inbox. If delivery is not configured, keep the form disabled and say so rather than showing a false success message.
5. Protect URLs and search signals
Keep useful URLs when possible. For each changed URL, record the old and new address and implement a permanent redirect where appropriate. Update internal links, sitemap entries, canonical URLs, and navigation. Google’s site-move guidance describes why redirects and verification matter during URL changes; its canonical guide explains how to choose a preferred URL.
Avoid launching with canonicals pointing at a domain that does not resolve. Verify the primary host, HTTPS, and any www or staging addresses. A sitemap should list reachable canonical pages, not every URL the site has ever used.
6. Review the real launch
On a phone and desktop, check the homepage, every main service page, representative industry pages, contact page, form submission, navigation, and a nonexistent URL. Inspect status codes, titles, descriptions, headings, canonical tags, and sitemap links in the delivered HTML. Test redirects from old addresses and confirm that a missing page returns 404.
After launch, use search-engine webmaster tools and real inquiry data to find problems. A redesign is the beginning of measurement, not proof of immediate ranking or lead improvement. Use our website checklist for a repeatable review, or read about website care for post-launch responsibilities.