A redesign can improve clarity, speed, conversion, and search visibility. It can also erase years of useful signals when teams change URLs, remove important content, or launch without measurement. SEO belongs in the redesign plan from the first sitemap—not at the end of development.
Before design, record what already works
Export the pages that receive organic traffic, earn links, or generate leads. Note their current URLs, search queries, conversions, and important inbound links. This becomes the baseline for deciding what to keep, combine, improve, or retire.
Talk to sales and customer-facing teams before rewriting the navigation. Search data shows how people phrase a need; conversations reveal the objections and proof the new site must address.
- Crawl and inventory the current site.
- Export Google Search Console landing-page and query data.
- Mark pages with backlinks, conversions, or strategic value.
- Save current titles, descriptions, headings, and copy for comparison.
Plan one permanent home for every important topic
Build a sitemap around customer decisions, not internal departments. Give each service a stable, descriptive URL. Combine overlapping pages when a stronger single page would answer the intent more completely.
When a URL must change, map it to the closest relevant new page with a permanent redirect. Do not send every retired URL to the homepage; that loses context for visitors and search engines.
Build search essentials into the templates
Every page template should support a unique title, meta description, canonical URL, social preview, one clear main heading, descriptive image alternatives, and structured data that matches visible content. Navigation and in-copy links should use ordinary crawlable anchors.
- Keep useful copy visible and readable on mobile.
- Compress large images and video without making them look soft.
- Generate a sitemap from the final public URL list.
- Prevent staging and private tools from being indexed.
Verify launch with evidence
Crawl the production site, test redirects, check canonical tags, inspect the robots file and sitemap, and confirm analytics and form submissions work. Then request indexing for the most important pages and monitor coverage, rankings, traffic, and leads against the saved baseline.
A temporary fluctuation after a significant migration can happen. Missing redirects, blank rendered content, accidental noindex tags, or broken internal links are not normal fluctuations; they are launch defects to fix quickly.
The useful takeaway
The safest redesign keeps proven equity, improves the information architecture, and launches with redirects and measurement already tested.
Want help putting this into practice?
See how iSight approaches website design + development, or share the business problem through our project intake.