A website redesign is not just a visual change. It can affect page URLs, search visibility, analytics, contact forms, redirects and the way customers navigate the site. The safest approach is to document what exists, decide what should change, test the new site before launch and monitor the important pages afterwards.
The main principle is simple: keep what is already working, improve what is not, and do not remove a useful page or URL without a deliberate replacement plan.
TL;DR
- Crawl the existing website and record its important URLs, traffic and leads before design work begins.
- Map old URLs to relevant new destinations and test permanent redirects where URLs change.
- Check titles, metadata, canonical URLs, sitemap, robots directives, content and internal links.
- Test forms, analytics, mobile layouts, accessibility and error pages before launch.
- Monitor indexing, traffic and enquiries after the release.
Before design and development
1. Record the current baseline
Crawl the site and export URLs, status codes, page titles and headings. In Search Console and analytics, identify pages that attract organic clicks, useful visits and enquiries. Record important backlinks where available. This inventory helps you avoid accidentally deleting a page that already contributes value.
2. Decide what should stay, change or go
Classify each important page as keep, improve, merge or remove. When two pages cover the same topic, decide which one best serves the visitor and how relevant information should be consolidated. Do not remove content solely because it is old; check whether it still answers a useful question or attracts relevant traffic.
3. Plan the URL map
Keep existing URLs when there is no strong reason to change them. If a URL must change, map it to the closest relevant new page. A redirect should not send every old URL to the homepage, because that can confuse users and discard the context of the original page. Review Google's canonical URL guidance when dealing with duplicates and preferred URLs.
During the build
4. Keep staging private and non-indexable
Use appropriate access controls for a staging site. Prevent it from being indexed, but make sure the production version does not accidentally inherit a staging noindex directive or crawl block. Check the final rendered HTML and HTTP status, especially on JavaScript-heavy pages.
5. Preserve and improve useful content
Carry over important service details, headings, descriptive titles, internal links and image alternative text where relevant. If the new design changes the copy, make sure the page still answers the original audience's question and does not lose useful detail. Review mobile layouts and keyboard access alongside visual design.
6. Set up technical essentials
Confirm canonical URLs, sitemap generation, robots directives, analytics tags, verification methods and any structured data. Structured data should match the page content and be tested; it does not guarantee a rich result. Make sure the 404 page returns an appropriate not-found response instead of pretending every unknown URL is a valid page.
7. Test business-critical actions
Submit every key form, test click-to-call links, check email notifications and verify thank-you states. Confirm that appointment booking, checkout or WhatsApp routes work if they are part of the customer journey. A polished redesign that loses leads because a form no longer delivers email is a failed launch.
Pro Tip: Test the site as an unfamiliar customer, not only as the developer who knows where every button is. Use a real phone, a private browser session and a test email address.
Launch-day checks
Before publishing, confirm the correct domain and HTTPS certificate, remove staging restrictions, verify redirects, test navigation and forms, and generate the production sitemap. Check canonical tags and make sure important content renders without requiring an interaction that prevents it from being seen. Submit the sitemap in Search Console if needed and inspect priority URLs after launch.
Do not expect search engines to reflect every change immediately. Keep the old URL map and rollback plan available, and monitor server errors closely during the first days after release.
Monitoring after launch
Compare organic clicks and impressions with the pre-launch baseline over sensible periods. Check for sudden drops in indexed pages, 404 responses, redirect chains, incorrect canonical selection and missing analytics events. Investigate individual URLs before assuming every fluctuation was caused by the redesign; seasonality and normal search variation can also affect performance.
Document the release date and major changes. If a problem occurs, trace it to a specific redirect, metadata change, template error or analytics issue rather than making many new changes at once.
How The Super Shoppe can help
The Super Shoppe builds custom business websites designed around clear messaging and responsive use. If you are planning a redesign, explore our website service and decide early which existing pages, links and measurement systems must be preserved. A practical launch plan should cover the customer journey as well as the visual design.
Sources
- Google Search Central: Canonical URLs
- Google Search Central: Build and submit a sitemap
- Google Search Central: JavaScript SEO basics
- Google Search Central: Structured data policies