Redesign guide 07
A website redesign checklist for reducing avoidable risk.
The short answer
Before changing the design, inventory every current URL and lead path plus the available high-value search queries, links, forms, integrations, and trusted content. Keep useful URLs when possible, map every changed URL to its closest replacement, test the new site before launch, and monitor both users and search afterward. These controls reduce avoidable losses, but migrations can still move search visibility and customer behavior.
How this guide was made. Parcha Lab synthesized firsthand service scope and the official sources listed below. AI assisted with drafting and structural checks.Human review byMikeon.
Name the problem before replacing the interface.
A dated look, weak mobile use, unclear positioning, missing service pages, slow editing, broken forms, and poor search performance are different problems. A visual refresh may solve only the first. Write the business reason for the redesign and the evidence that will show improvement.
Separate a redesign from a platform or domain move when possible. Google recommends changing one major thing at a time because combined moves make failures harder to diagnose. If the changes must happen together, the migration plan needs more testing and a clear rollback point.
- What user task is failing today?
- Which pages or channels currently create useful inquiries?
- What must be easier to publish or operate after launch?
- Which result will be measured at 7, 30, and 90 days?
Build the preservation inventory.
Export or record the current URL list, page titles, search performance, links from other sites, top landing pages, forms, downloads, scripts, structured data, analytics, and Business Profile links. Save screenshots for comparison, but do not treat screenshots as a backup of the content or system.
Mark each URL with one action: keep, improve in place, redirect to a close replacement, archive for records, or remove. The decision should follow the page's value and current accuracy, not whether it fits the new navigation.
- URLs and their current response codes
- Search impressions, clicks, and top queries by page
- External and internal links
- Forms, confirmation messages, notifications, and stored data
- Titles, descriptions, headings, canonicals, language links, and schema
- Account access, DNS, analytics, and deployment records
Preserve URLs or map them one to one.
Keeping a useful URL is usually simpler than changing it. When a URL must change, send it with a server-side permanent redirect to the closest equivalent page. Google specifically warns against sending many unrelated old URLs to the new homepage because that can confuse visitors and be treated as a soft 404.
Update internal links to their final destinations so visitors and crawlers do not travel through redirect chains. Keep the redirect map as an operational record and test every row after launch.
- Old URL
- New URL or removal reason
- Redirect status
- New canonical URL
- Internal links updated
- Live response verified
Test the finished system, not just the homepage.
Crawl the preview and test representative paths on real phone and desktop sizes. Compare the old and new inventories. Important content, metadata, structured data, and language relationships should remain complete on mobile. Submit forms and confirm the visitor message, business notification, and stored result where applicable.
Check keyboard use, focus, labels, contrast, alt text, reduced motion, error states, privacy links, and third-party failure states. A redesign can introduce accessibility and operational regressions even when every screenshot looks stronger.
Related: Use the mobile-friendly checklistUse the accessibility checklist
Launch with a watch list and a rollback point.
Record the last known good version, then monitor errors, form delivery, performance, indexing, and lead paths immediately after launch. Submit the updated sitemap and inspect important URLs in Search Console. Expect search results to take time to recrawl and process after meaningful changes.
Do not judge a redesign from one traffic day. Compare equivalent periods and annotate launch dates, campaigns, outages, and seasonal changes. Fix clear defects immediately; evaluate broader search and conversion movement with enough data to distinguish a trend from noise.
Questions
What buyers usually ask next.
Will a website redesign hurt search rankings?
It can if useful content disappears, URLs change without accurate redirects, mobile content becomes thinner, or technical signals break. A careful inventory, one-to-one URL map, prelaunch crawl, and post-launch monitoring reduce avoidable risk, but temporary movement can still occur while pages are reprocessed.
Should a redesign change all the page URLs?
No. Keep useful, descriptive URLs when possible. Change a URL only for a clear reason, then permanently redirect the old address to its closest relevant replacement and update internal links to the final address.
Should old website content be copied into the redesign?
Inventory it first. Keep accurate content that serves a user or search need, improve weak but valuable content, combine genuine duplicates, and remove material that is obsolete or unsupported. Preserve the intent and evidence, not every sentence.
How do I know whether a redesign worked?
Define the baseline before launch. Measure task completion, qualified inquiries, form reliability, mobile usability, performance, search visibility, and maintenance effort. Compare equivalent periods and account for campaigns and seasonality.
References
Official sources used for factual claims.
Advice and checklists are Parcha Lab's original synthesis. Changeable technical, platform, standards, and legal-context facts are grounded in the primary sources below.
- Google Search Central How to move a site with URL changes
- Google Search Central Mobile-first indexing best practices
- Google Search Central SEO Starter Guide