Website Redesign Checklist: Strategy to Launch

A safe website redesign protects every valuable page before it changes. Export search and conversion evidence, map each old URL to a keep, merge, redirect, or retire decision, then verify the new site for at least 14 days after launch.

The visual system can change completely while the search job stays the same. If a useful URL disappears without an accurate replacement, the project has not refreshed the brand; it has removed a proven entry point.

Start with the current site, not a Figma file. The baseline tells the team which pages already earn attention, which journeys create enquiries or revenue, and which assets must survive the move.

1. Export Search Console evidence: Record top pages, queries, impressions, clicks, CTR, and the query-to-page relationship. Mark P0 pages that support leads, revenue, branded trust, or a critical service.
2. Export analytics evidence: Record landing pages, source and medium, form submissions, calls, purchases, and other key events. Keep the event names and parameters needed for a comparable post-launch view.
3. Inventory the site: Include every indexable URL, title, canonical, status code, internal links, backlinks, media, schema, form, owner, and business purpose.
4. Choose the content action: Keep, improve, merge, redirect, or retire. Do not copy weak pages simply because they already exist.
5. Freeze the launch scope: Name the approved URL map, redirect file, sitemap, analytics plan, rollback owner, and acceptance checks.

A page with modest traffic can still be P0 if it owns a high-value query or completes a conversion journey. Page value is not the same as page views.

The URL map is the migration contract. Every old indexable URL needs an explicit decision and a destination that serves the same user intent. Keep a strong URL when its job remains valid. Merge true duplicates into the strongest owner. Use a permanent redirect only when a relevant replacement exists. Retire a page with a real 404 or 410 when no equivalent exists.

This is a template, not a claim about KBR Global's current URLs. The acceptance column makes each decision testable rather than leaving it as a spreadsheet note.

Avoid redirect chains, loops, blanket redirects to the homepage, and canonical tags that disagree with redirects. Update internal links to point directly at final destinations, publish the new sitemap, and keep useful redirects in place for at least a year.

A redesign is not a ranking reset. Search continuity depends on crawlable destinations, accurate redirects, consistent canonical signals, useful rendered HTML, internal links, and content that continues to satisfy the same search intent.

• Rendered answers: Keep the direct answer and essential evidence in the HTML. Do not hide the useful content behind interaction that a crawler or impatient visitor may never reach.
• Page ownership: Assign one primary query family to one canonical page. Merge overlapping pages before migration so the new site does not launch with the same cannibalization.
• Internal links: Replace old targets in navigation, body copy, breadcrumbs, related content, and footers. Do not rely on a redirect for links you control.
• Schema parity: Restore only structured data that matches visible content and the new page type. Validate the output, but do not treat schema as a substitute for the page.
• Answer-engine readiness: Preserve concise answers, named entities, verifiable facts, source links, visible authorship, and a clear relationship between the question, evidence, and next step.
• Local pages: Keep service or location pages only when each has distinct intent, useful local evidence, accurate business details, and a real role in the journey. Do not clone city names across thin pages.

The same URL map applies whether the redesign stays on one stack or moves between Wix, Shopify, WordPress, Astro, or another system. The platform changes the failure modes, not the need for ownership.

• Wix: Preserve slugs where possible, export the redirect plan, test automatic and manual redirects, and verify pages that use Wix collections or multilingual paths.
• Shopify: Map legacy product, collection, policy, and blog paths to Shopify's URL structure. Test product availability, collection links, market subfolders, checkout journeys, and product structured data.
• WordPress: Freeze the permalink decision before import. Check rewrite rules, redirect plugins, canonical output, XML sitemap ownership, media URLs, and any SEO plugin that can duplicate schema or metadata.
• Headless or custom: Confirm that titles, canonical tags, structured data, links, and meaningful content exist in the delivered HTML. Verify preview and production environments use different crawl rules.

When two old pages serve the same intent, merge their useful evidence before launch. Copying both into a new design preserves the problem.

Launch is the start of verification. Test the highest-value journeys first, then repeat the checks as crawlers, users, caches, and reporting systems encounter the new site.

The 14-day window is a technical acceptance period, not a promise that search performance will settle within two weeks. Google notes that site-move visibility can fluctuate while old and new URLs are crawled and processed.

In Search Console, compare equivalent windows for P0 pages and their query families. Watch impressions, clicks, CTR, average position, the page Google assigns to each query, and the canonical Google selects. A sharp loss on old URLs without a corresponding rise on their mapped replacements points to a migration gap that needs investigation.

In GA4, verify the same events and key events across the same journeys, including form success rather than button clicks alone. DebugView and Realtime confirm collection immediately; standard reports need processing time. Segment by landing page and source or medium so a channel shift is not mistaken for a redesign failure.

For related decisions, read the custom versus template guide, the website timeline guide, and the website cost guide. If the migration needs one accountable team, review KBR Global web design services or send a short project brief.

• Site moves and migrations, Google Search Central
• Search Console performance report tasks, Google Search Console Help
• URL Inspection tool, Google Search Console Help
• Verify and troubleshoot Google Analytics, Google for Developers
• Web Content Accessibility Guidelines 2.2, W3C