
Record what works before changing it.
List the important pages, contact paths, products, and search landing pages. Where you have access, export your Search Console query and page data and record existing analytics goals. Note the date and any other marketing changes that might affect the comparison. Include linked images, PDFs and downloads, not just page addresses. Record where each should remain available if its URL changes.
A homepage screenshot alone is not a baseline. Include the URLs, titles, main headings, internal links, and content that your customers already use.
Keep useful URLs, and map necessary changes.
A visual redesign does not automatically require new URLs. Preserve useful addresses when they still match the content. If a page really needs a new address, map the old URL to the relevant replacement and plan a permanent redirect.
Do not send every removed page to the homepage simply to avoid a 404. Decide which pages have a genuine replacement, and update internal links, canonicals, and the sitemap consistently.
An example URL map
Illustrative URL map, not a client migration. Follow each old address to its intended result.
-
Current URL
/servicesKeep200 / Same address/servicesKeep the page and its self-canonical. -
Current URL
/old-service-name301 / Move200 / Relevant final page/services/current-nameRedirect directly; avoid chains and loops. -
Retired URL
/retired-offerRemove404 or 410 / No replacementReturn a genuine not-found response, not an unrelated homepage redirect.
A design-only update can keep existing URLs. Moving a domain, changing a platform and changing the page design are different decisions.
Download the editable worksheet
URL map and launch-test log. XLSX, no signup.
Carry over the information customers need.
Check service descriptions, product information, important answers, titles, headings, and descriptive image text. A cleaner layout should not accidentally remove the content that made a page useful.
Use real work as evidence. The Canario Detailing case study shows package, vehicle, and add-on selection connected to an existing Wix booking setup. That journey needs different content from the product and collection browsing in the CARBON.DEPT storefront.
- Canario / booking
- Follow package, vehicle and add-on selection through to the Wix booking handoff. Check that the selected services and the displayed price remain consistent.
- CARBON.DEPT / shopping
- Follow vehicle-led browsing to a relevant product. Check dependent choices, unavailable combinations and the intended cart handoff.
These are examples of what to test, not measured SEO or sales results. Use agreed test arrangements rather than submitting a live booking or purchase.
Review the complete site on staging.
Review the new pages before changing the live domain. Keep private previews behind suitable access controls. Before launch, check that intended public pages will not inherit a preview-only noindex directive or crawler block.
Compare priority pages with the old version: titles, headings, canonicals, indexing instructions, important links and structured data. Verify the rendered content as well as the page source. Test phone layouts, loading, menu response and agreed inquiry or purchase paths, including receipt and failure states.
A robots.txt block is not an indexing-removal instruction. Google must be able to crawl a page to read noindex; use access controls when the preview itself must remain private.
Use a written launch checklist.
- Check the domain, HTTPS, redirects, and the final public URLs.
- Confirm titles, canonical tags, robots directives, and crawlable content.
- Test inquiry or purchase paths with appropriate test arrangements.
- Update internal links and publish the correct sitemap.
- Keep a known-good release and a rollback plan.
For changes that move URLs, Google's site-move guidance explains mapping, redirects, and monitoring. Not every design-only change is a site move.
Watch for problems after launch.
Compare search queries and landing pages over comparable date windows. Use the symptom to choose what to investigate first:
- Visits down, search clicks steady
- Verify analytics and consent changes before attributing the difference to lost rankings.
- One moved page down
- Open its old URL, check the final destination and compare the replacement content.
- Visits steady, inquiries down
- Check the form or booking handoff and actual receipt with approved test arrangements.
These are investigation paths, not automatic diagnoses. For Shopify stores, check conversion changes after a redesign separately.
Search visibility can fluctuate and cannot be guaranteed unchanged. The aim is to reduce avoidable mistakes, find problems early, and judge results against the recorded baseline. Scope the monitoring work explicitly rather than assuming it is included with every build.
Before you approve a proposal
Keep the scope, required costs, ownership arrangements, launch responsibilities, and post-launch work together in writing. For a product-led project, review our Shopify website design service. For a business website, start with the published packages and discuss any additional requirements.
