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.
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.
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 Model Public Adjusters preview presents service types, a process, and an inquiry path. Those are different needs from the product and collection browsing in the CARBON.DEPT storefront.
Review the complete site on staging.
Review the new pages before changing the live domain. Keep staging out of search results through suitable access or indexing controls, then verify that production will not inherit an accidental noindex directive or crawler block.
Test desktop and phone layouts, menu navigation, links, forms or booking paths, and the key shopping journey where applicable. Check that essential text and media load, not just that a page returns a successful status.
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.
Check important pages, redirect behavior, indexing reports, missing-page errors, and your inquiry or purchase events. Compare search queries and landing pages over a meaningful period, not just one day's traffic.
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.
