Start with an inventory, not a blank canvas
Before changing layouts or choosing a new theme, I review what already exists. That includes important page URLs, navigation, title and heading patterns, indexed content, internal links, forms, images, downloads, and pages that may receive traffic or generate inquiries. The goal is to understand which parts of the current site deserve protection and which parts are creating friction.
A redesign inventory also exposes less obvious dependencies. An old service page may be linked from a Google Business Profile, a sales email, a brochure, or another website. A PDF may be the only place a prospect finds a key detail. A contact form, scheduling tool, analytics tag, or payment connection can also be easy to overlook when the focus is primarily visual.
From that review, I can separate essential pages from outdated or redundant material. I do not assume that every old page should stay forever, but I also do not delete content simply because it looks dated. Each removal, merge, or rewrite should have a clear reason and a replacement plan.
- List current URLs and important page types
- Flag pages, files, forms, and integrations that must survive
- Identify outdated content that needs revision rather than automatic deletion
Map old URLs to the right new destinations
URL changes are one of the most important technical parts of a redesign. If a page moves from an old address to a new one, we create a redirect map that records the original URL, its replacement, and the reason for the change. This gives the launch a deliberate structure instead of relying on a last-minute search for broken links.
A redirect should lead visitors to the closest useful replacement, not simply send every old page to the homepage. A service page should generally point to its updated service page; a retired article may need a related article or category; and a page with no meaningful replacement may need a carefully considered response. This preserves a better experience for people arriving through old links.
I also check internal links, navigation, canonical settings, XML sitemap references, and common variations such as trailing slashes or changed folder structures. Redirects are not a substitute for clean architecture, so I use them to manage necessary changes while keeping the new site understandable and maintainable.
- Create a source-to-destination redirect spreadsheet
- Use relevant replacement pages instead of blanket homepage redirects
- Update internal links so the new site does not depend on avoidable redirects
Preserve the content that earns attention
Visual redesigns often fail when useful content is treated as filler. Existing copy can answer customer questions, describe services, support local relevance, and help search engines understand what a page is about. I review content before rewriting it so important topics, service details, FAQs, and calls to action are not accidentally lost during the build.
Preservation does not mean keeping every sentence unchanged. Some copy may be thin, repetitive, inaccurate, or difficult to scan. I can reorganize it into clearer sections, improve headings, strengthen calls to action, and remove duplication while keeping the substance that makes the page useful. If several pages overlap, I decide whether to improve, combine, or retire them based on purpose rather than appearance.
Images and media need the same care. File names, alternative text, captions, downloads, and embedded videos can all support usability or carry practical information. I make sure the new design does not hide important details behind confusing interactions or replace meaningful content with decorative graphics alone.
- Compare old and new copy before launch
- Keep service details and customer questions visible
- Review images, downloads, alternative text, and embedded media
Build for people first, then verify the technical details
A redesign should make the next step obvious on a phone, tablet, and desktop. I pay attention to navigation depth, readable type, button placement, form friction, contrast, and whether important content remains easy to reach on smaller screens. A polished desktop layout is not enough if mobile visitors have to pinch, hunt, or fight a crowded menu.
Performance is part of that experience. I look for oversized images, unnecessary scripts, inefficient embeds, and layout changes that make a page feel unstable. Google’s Core Web Vitals—Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift—provide useful technical signals, but I pair them with real usability checks rather than treating a score as the whole project.
I also verify basic SEO and accessibility foundations during the build: sensible heading order, descriptive links, meaningful labels, keyboard access, crawlable navigation, page titles, and metadata. This work supports visitors with different needs while making the site easier to understand and maintain.
- Test key journeys on real phone and desktop layouts
- Review Core Web Vitals alongside actual page usability
- Check headings, labels, links, contrast, and keyboard behavior
Launch in controlled stages and check the live site
I prefer a launch process with a checklist rather than a single dramatic handoff. Before the switch, I confirm backups, hosting access, domain settings, forms, analytics, tracking, and the redirect file. I then test representative pages in the staging environment, including service pages, contact paths, menus, downloads, and any booking or ordering flow.
Immediately after launch, I check that the right version of the site is live, secure connections work, redirects resolve correctly, and important pages return the expected responses. I review the sitemap and robots settings, test forms from more than one device, and look for obvious console or crawl issues. These checks catch problems that can be invisible during a design review.
The first days after launch are for observation and cleanup. I review analytics and search-related signals available to you, watch for 404 errors, inspect important landing pages, and correct broken links or unexpected behavior. No redesign can promise a particular ranking outcome, but a careful migration reduces preventable disruption and gives the new site a sound starting point.
- Create a pre-launch and post-launch checklist
- Test redirects, forms, analytics, sitemap, and security after release
- Monitor errors and important user paths after the redesign