LEADLEAK BY BRIVIXO
A redesign can make a business easier to understand and use, but changing URLs, content and navigation without a plan can disrupt search discovery. Use this checklist before, during and after a redesign to preserve useful pages, make the new site easier to crawl and verify that customer journeys still work.
Run the free Growth Snapshot →Create a list of existing URLs, page titles, meta descriptions, canonical tags, important headings and pages that receive enquiries or organic visits. Export landing-page and query data from Google Search Console and analytics before work begins. Note which pages have external links or are referenced by customers. This baseline helps distinguish normal fluctuations from avoidable migration problems.
Keep an existing URL when the page still serves the same purpose and there is no strong reason to change it. If a URL must change, map the old address to the closest equivalent new page. Avoid sending every removed page to the homepage: visitors and search engines should arrive at a destination that satisfies the original intent. Do not create several redirects in a chain when one direct redirect will do.
Do not remove a page simply because its design is old. Review the questions it answers, the service it explains and the evidence it contains. Improve weak sections, remove outdated claims and retain details that customers still need. If several pages overlap, consolidate them carefully and redirect retired URLs to the most relevant surviving page. Keep one clear primary purpose for each important page.
Write a distinct title and description for each important page based on what the page actually offers. Use a clear H1 and logical subheadings. Avoid copying the same metadata across every route or stuffing location and service keywords into a list. Make sure the new page content answers the searcher's question more completely than the previous version.
Confirm that each indexable page has the intended canonical URL, that production pages are not carrying a staging noindex rule, and that robots.txt does not block important assets or content. Generate a sitemap containing the preferred, canonical URLs that should appear in search. Exclude redirects, error pages, duplicate variants and private or transactional routes that are not intended for search.
Update navigation, footer links, contextual links, breadcrumbs and calls to action so they point directly to the final URLs. Check links inside older articles and service pages; these are easy to miss during a redesign. Use descriptive anchor text that tells visitors what they will find. A sitemap helps discovery, but useful internal links help people and crawlers understand how the pages relate.
Check representative pages on mobile and desktop. Verify that forms submit, phone and email links work, booking flows complete and confirmation messages appear. Test redirects, 404 handling, structured data, image alternative text, page titles, canonical tags and analytics events. Use a crawl or automated test to identify broken internal links and pages that accidentally return the wrong status code.
Publish the new site only after the critical customer journeys and technical checks pass. Confirm that the production domain, HTTPS certificate, canonical host and environment configuration are correct. Do not submit a preview hostname as the canonical site. Keep a copy of the URL mapping and a rollback plan available in case a serious issue appears after release.
Open Google Search Console and inspect the homepage plus representative new and changed URLs. Submit the updated sitemap once it is live. Request indexing for a small number of priority pages when appropriate, then monitor Page indexing, crawl statistics and URL Inspection. Use Bing Webmaster Tools as an additional discovery and diagnostic source. A sitemap submission is a discovery hint, not a guarantee that every URL will be indexed.
Watch for unexpected 404s, redirect loops, canonical mismatches, noindex directives, traffic drops on important landing pages and broken enquiry tracking. Compare performance with the pre-launch baseline over a suitable period and account for seasonality and normal reporting delays. Fix technical regressions first; then use query and landing-page data to decide which content needs further improvement.
Before declaring the redesign complete, confirm that priority old URLs have an appropriate destination, new pages are indexable, the sitemap contains the intended URLs, internal links work, analytics records page visits and enquiries, and a real person can complete the main customer journey on a phone. Keep a dated record of the checks and unresolved issues.
No. A redesign can improve usability and page clarity, but it can also damage search visibility if useful content, URLs, redirects or indexing settings are mishandled.
Usually not. Keep URLs that still fit the page purpose. Change only when there is a clear reason, and map every changed URL to its closest relevant replacement.
There is no fixed timetable. Crawling and reporting depend on the site and Google's systems. Monitor URL Inspection and Page indexing rather than assuming a sitemap submission means every page has been processed.
Save the current URL list, Search Console performance and indexing data, analytics landing-page and conversion data, metadata and any known high-value external links.