Website Redesign Checklist

This website redesign checklist is the forty steps that separate a redesign that keeps its search rankings, inbound links and conversions from one that loses them. The steps are in order: benchmark and audit before anything is designed, build the redirect map before the build, test the redirects before launch, and keep watching for weeks afterward. Most ranking losses after a redesign come from the same few causes: URLs changed without redirects, content deleted or thinned, titles and headings lost, a staging site left open to search engines, and nobody watching the numbers after launch. Each of those has a step below.

Website redesign checklist: before you start

Everything here happens before a designer opens a file. It is the least glamorous part and the part most often skipped.

1. Write down why you are redesigning and what must be better afterward: more inquiries, faster pages, a site your team can edit, a new brand. If the goal is vague, the redesign will be judged on taste.
2. Decide fix versus redesign. Slow pages, weak calls to action and outdated styling can often be fixed in place. A redesign is justified when the structure, platform or design system is the problem.
3. Benchmark the current site. Export rankings, organic traffic by page, conversion rates, top landing pages, inbound links and Core Web Vitals. Without this you cannot tell what changed.
4. Inventory accounts and access: hosting, DNS, domain registrar, CMS, analytics, Search Console, CRM, forms, payment and email tools. Collect access now, not in launch week.
5. Name the decision maker and the reviewers, and agree a turnaround for approvals. Decision latency is the most common schedule killer, as our website development timeline guide explains.
6. Set the budget and scope in writing, including who writes content, how many templates are in scope and how change requests will be handled. The drivers are covered in our website development cost guide.

Content and SEO audit

The audit tells you what to keep. Skipping it is how valuable pages get deleted because nobody knew they ranked.

7. Crawl the whole site with a crawler to get every URL, including PDFs, images, tag pages and old campaign pages nobody remembers.
8. Join the crawl to analytics and Search Console data so each URL carries its traffic, impressions, clicks, ranking keywords and conversions.
9. Add inbound links per URL from a backlink tool. Pages with links from other sites must be kept or redirected one to one.
10. Mark every URL keep, improve, merge or retire. Merge weak pages on the same topic into one stronger page rather than deleting them; retire only pages with no traffic, no links and no purpose.
11. Record title tags, meta descriptions, H1s and schema for every page you are keeping, so they carry across or are improved on purpose rather than lost.
12. List the keywords each ranking page holds and make sure the new page outline still answers that search. A redesign that changes the topic of a page loses the ranking even if the URL stays.
13. Audit the content itself: outdated facts, broken links, duplicate pages, thin pages, missing alt text, and pages that need rewriting for the new structure.
14. Audit integrations and forms: which forms post where, which tracking tags fire, which embeds and scripts exist, and which can be dropped.

Redirect map

The redirect map is the single most important document in a redesign. Build it before the new site is built, not after.

15. Keep URLs wherever the page’s purpose is unchanged. A stable URL keeps its link equity and ranking history. Change URLs only where the structure improves materially.
16. Map every old URL to exactly one new URL in a spreadsheet: old path, new path, reason, status. Include images and PDFs that have inbound links.
17. Redirect to the closest equivalent page, never to the home page. Mass redirects to the home page are treated as soft 404s and lose the signals that pointed at specific pages.
18. Use permanent (301) redirects, avoid chains and loops, and update old redirects from previous redesigns so they point to the final destination in one hop.
19. Plan internal links and navigation for the new structure so the new site links to new URLs directly and does not rely on redirects internally.

Design and build

The design and build phase is where SEO is usually lost by accident: a template that drops the H1, a builder that loads slowly, a migration that strips alt text.

20. Design from the content and structure, not the other way round. Wireframe the key templates with real content so the design serves the pages that rank and convert.
21. Build the new site on a staging domain that is blocked from indexing with a noindex header and, where possible, password protection. A staging site that gets indexed competes with the live one.
22. Carry over or improve titles, meta descriptions, H1s and headings page by page from the audit sheet. One H1 per page, headings in order.
23. Migrate content with its metadata: publish dates, authors, categories, alt text, captions and schema markup. Spot-check migrated pages against the originals.
24. Keep the pages that rank substantially intact. Improve them deliberately; do not rewrite them from scratch in a new voice and expect the ranking to survive.
25. Build for performance from the first template: optimized images, minimal scripts, caching and a CDN, measured against Core Web Vitals on staging.
26. Build for accessibility: semantic HTML, keyboard navigation, color contrast, labeled forms and alt text, with WCAG 2.2 AA as the working target.
27. Reconnect every integration on staging: forms to the CRM, analytics and tag manager, consent management, booking, payments and chat, using test modes where they exist.

QA

Quality assurance is a phase with its own duration, not a day before launch.

28. Test the redirect map on staging by crawling the list of old URLs against the new site and confirming each returns a single 301 to the mapped destination.
29. Crawl the staging site for broken links, missing titles, duplicate titles, missing H1s and orphan pages, and fix them before launch rather than after.
30. Test every template across browsers and devices, including the oldest ones your analytics say your visitors use.
31. Run accessibility and performance audits on each template, and test the main journeys with a screen reader and a keyboard.
32. Submit every form and complete every transaction end to end, and confirm the data arrived where it should and the notifications fired.
33. Review the XML sitemap, robots.txt, canonical tags and schema on staging so they are correct the moment the site goes live.

Launch day

Launch in a quiet week, early in the day, with the people who can fix things available.

34. Switch DNS and TLS, remove the noindex and password from the new site, and confirm the live site returns the correct pages over HTTPS.
35. Switch the redirects on and spot-check them live, including the highest-traffic and most-linked old URLs from the audit.
36. Submit the new XML sitemap in Search Console, request indexing for key pages, and confirm analytics and tag manager are recording.
37. Crawl the live site and compare it to the staging crawl: same page count, no new errors, no stray noindex tags, no staging URLs in links.

After launch

The redesign is finished when the numbers are back at or above the benchmark, not when the site goes live. Search engines take weeks to recrawl and settle.

38. Watch Search Console daily for the first few weeks: crawl errors, 404s, coverage changes and manual actions. Redirect any 404 that has traffic or links.
39. Compare rankings, traffic and conversions to the benchmark weekly for the first quarter. Some fluctuation is normal; a sustained drop on specific pages points to a lost title, heading, content block or redirect.
40. Hand the site to a maintenance routine: updates, backups, monitoring, performance checks and a change process, with editor training and a written guide for the templates.

Where PS3G fits

PS3G runs this checklist as a service. Our website redesign services start with the benchmark and audit, build the redirect map before the design, rebuild on WordPress, .NET or a modern JavaScript stack, test the redirects before launch and watch the numbers through hypercare, for organizations of every size. When a redesign turns into a new site on a new platform, our website development process takes over from the structure stage. We work from Wilmington, Delaware with a delivery center in India, and we maintain our own public sites with the same routine, which is why the post-launch steps are in the proposal rather than left to chance.

Related reading

• Website Development Timeline: Phases, Durations and a Template
• Website Development Cost: What Drives It and How to Budget
• Website redesign services

Frequently asked questions

Does a website redesign affect SEO?

Yes, in either direction. Changed URLs without redirects, deleted or thinned content, lost titles and headings, slower templates and indexed staging sites cause losses. Keeping or redirecting every URL one to one, carrying content and metadata across, improving speed and accessibility, and monitoring after launch usually keep rankings and often improve them. Expect some fluctuation while search engines recrawl the new site.

Should I change my URLs during a redesign?

Only where the structure improves materially, such as grouping services under one clear path or removing dates from evergreen URLs. Every changed URL needs a permanent redirect to its exact new counterpart, and internal links should point to the new URLs directly. Where the page’s purpose is unchanged, keeping the URL preserves its links and history at no cost.

How long should I monitor rankings after a redesign?

Check Search Console daily for the first few weeks for crawl errors and 404s, then compare rankings, traffic and conversions to your benchmark weekly for about a quarter. Search engines need time to recrawl and reassess the site, so judge the result over that period rather than in the first week, and investigate sustained drops on specific pages rather than overall noise.

What is the most common website redesign mistake?

Launching without a complete redirect map. Old URLs then return 404s, inbound links point at nothing, and the rankings those pages held disappear. The second most common is leaving the staging site open to search engines, so a duplicate of the new site is indexed before launch. Both are avoided by doing the audit and redirect map before the build and testing them before launch.

Can we redesign in phases instead of all at once?

Yes, and for large sites it is often safer. Launch the new design on a section or a set of templates, keep the URLs, measure, then continue. Phased redesigns need a consistent design system so the site does not look like two sites, and the redirect and monitoring steps apply to each phase. The benchmark and audit still happen once, up front.