A website redesign is more than a visual refresh. For a marketing manager, it is an opportunity to improve how the website supports brand positioning, organic search, lead generation, customer journeys, conversions, analytics and long-term digital growth. A redesign can involve changes to information architecture, page templates, content, navigation, technical infrastructure, design systems, performance and conversion paths.
Without a structured process, even a visually impressive redesign can create problems such as lost search visibility, broken URLs, tracking gaps, slower performance or weaker conversion rates. The most effective approach is to treat the website as a business and marketing asset rather than simply a design project.
This website redesign checklist provides a practical framework for planning, executing, testing and measuring the project from a marketing perspective.
1. Define the Business and Marketing Goals
Before discussing layouts, colour palettes, wireframes or content management systems, establish what the redesigned website needs to accomplish. Marketing managers should document the primary business objectives and connect them to measurable website outcomes. Common goals include increasing qualified leads, improving ecommerce revenue, generating more product enquiries, strengthening organic visibility, supporting a repositioned brand, improving user experience or reducing friction in the sales process.
Each objective should have corresponding metrics so the redesign can be evaluated after launch rather than judged primarily by appearance. For example, a lead-generation website might measure qualified enquiries, conversion rate, form completion rate and organic traffic, while an ecommerce website may focus on product engagement, add-to-cart rate, checkout completion and revenue per visitor.
A useful redesign brief should also define project success criteria and establish which requirements are essential for launch. This helps prevent scope from expanding without clear business justification. It is useful to separate must-have functionality from improvements that can be introduced after launch. Marketing, design, development and SEO teams should have a shared understanding of the priorities before production begins.
Website Redesign Goal Checklist
- Define the primary business objective.
- Identify the main marketing objectives.
- Establish measurable KPIs.
- Document current website performance.
- Identify the website's most valuable conversion actions.
- Define target audiences and important customer segments.
- Identify existing business or marketing problems.
- Establish realistic post-launch benchmarks.
- Separate essential requirements from desirable improvements.
- Define project success criteria.
A useful redesign brief should answer one central question: What should the new website do better than the current website? The answer should be measurable wherever possible.
2. Audit the Existing Website Before Making Changes
A redesign should begin with evidence rather than assumptions. Conduct a comprehensive audit of the existing website to understand what is working, what is underperforming and what must be protected during migration. Review website analytics, organic search performance, conversion data, top landing pages, traffic sources, user behaviour, existing content, backlinks, indexed URLs, technical errors, page speed and conversion paths.
Pay particular attention to pages that already generate significant organic traffic, leads, sales or backlinks because removing or changing them without a migration strategy can create unnecessary losses. The audit should also identify outdated content, duplicate pages, thin content, broken links, obsolete features, poor-performing templates and sections that no longer align with the company's positioning.
A more structured audit should include a content inventory and technical discovery alongside the standard SEO and analytics review. The content inventory records the important pages and their purpose, while technical discovery identifies integrations, templates, dependencies and functionality that the new website must preserve or replace. This information gives the redesign team a reliable baseline before decisions are made about what should be retained, consolidated, rewritten or removed.
| Area | What to Review |
| Analytics | Traffic, engagement, conversions, acquisition channels |
| SEO | Rankings, indexed pages, backlinks, organic landing pages |
| Content | Relevance, quality, duplication, outdated information |
| UX | Navigation, journeys, accessibility, mobile experience |
| Technical | Performance, errors, crawlability, security |
| Conversion | Forms, CTAs, checkout, enquiry paths |
| Brand | Messaging, visual consistency, positioning |
| Tracking | Analytics, events, pixels, conversion tracking |
| Content inventory | Page purpose, ownership, freshness and future action |
| Technical discovery | Templates, integrations, dependencies and functionality |
The purpose of the audit is not to preserve everything. It is to distinguish between assets that should be retained, improved, consolidated, redirected or removed.
3. Define the Target Audience and Customer Journey
A website redesign should reflect how customers actually research, evaluate, compare and purchase rather than how the organisation internally categorises its services. Marketing managers should identify the major audience groups and document the questions, objections, information needs and conversion actions associated with each group. Consider where users are entering the website, what information they need before making a decision and which pages should move them toward the next stage of the journey.
A visitor arriving from an informational search may require educational content before contacting sales, while a returning visitor may want pricing, product specifications, case studies or a direct enquiry route. Mapping these journeys helps determine navigation, content hierarchy, internal linking, calls to action and landing-page structure.
The process should also account for search intent mapping. A user arriving from a commercial query may need a different page experience from someone searching for general information. Aligning the page type, content depth and conversion path with the reason behind the visit can make the redesigned website more useful and easier to navigate.
Customer Journey Questions
For each important audience, document:
- What problem are they trying to solve?
- What search or referral brought them to the website?
- What information do they need first?
- What objections might prevent conversion?
- Which proof points build trust?
- Which pages should they visit next?
- What is the preferred conversion action?
- What happens after they submit a form, purchase or enquire?
This process prevents the redesign from becoming purely internally focused and ensures that page structure supports real user intent.
4. Review Website Architecture, Navigation and Templates
Information architecture is one of the most important elements of a redesign because it affects users, search engines, content organisation and internal linking. Review the existing navigation and determine whether important pages are easy to find and logically grouped. The redesigned architecture should reflect the relationship between core services, products, categories, supporting information and educational content. Avoid creating excessively deep navigation structures that require users to click through multiple levels before reaching important pages. At the same time, avoid reducing navigation so aggressively that valuable content becomes difficult to discover.
Create a sitemap before development begins. The sitemap should identify important existing URLs, proposed new URLs, pages being consolidated, pages being removed and replacement destinations for redirected URLs. This becomes particularly important when a redesign changes URL structures, content categories or page templates.
The project should also establish a template hierarchy. Instead of treating every page as a completely separate design, identify reusable structures for service pages, product pages, category pages, articles, landing pages and other recurring content types. A consistent design system can then define reusable components, spacing, typography, buttons, forms and interface patterns. This makes the new website easier to maintain and scale.
5. Protect SEO During the Redesign
SEO should be integrated into the redesign process from the beginning rather than added immediately before launch. Search visibility depends on many interconnected factors, including content relevance, crawlability, internal linking, URL structure, metadata, structured data, performance, mobile usability and external authority.
A new design can unintentionally remove content that previously generated organic traffic or introduce technical changes that affect crawling and indexing. Marketing managers should therefore work closely with SEO and development teams before approving structural changes.
Create a complete URL inventory and classify pages according to their organic value. Record current rankings, organic traffic, backlinks, indexed status and conversion performance for important pages. If URLs change, create a comprehensive URL-to-URL redirect map using permanent redirects from old URLs to the most relevant new destinations.
Avoid redirecting every removed page to the homepage because this can create poor user experiences and does not provide an appropriate replacement for specific content.
SEO Redesign Checklist
- Crawl the current website.
- Export important URLs.
- Identify high-value organic landing pages.
- Record important rankings and search queries.
- Review title tags and meta descriptions.
- Audit heading structures.
- Review internal links.
- Check canonical tags.
- Review XML sitemaps.
- Check robots.txt.
- Identify broken links.
- Map old URLs to new URLs.
- Prepare permanent redirects.
- Review structured data.
- Test indexability before launch.
- Monitor organic performance after launch.
- Complete a pre-launch SEO crawl.
SEO continuity should be treated as a core migration requirement, not an optional marketing task.
6. Create a Content Strategy for the New Website
A redesign often exposes content problems that were difficult to see on the old website. Some pages may contain outdated information, while others may lack enough detail to satisfy users or search intent. Marketing managers should establish which content will be retained, rewritten, consolidated, expanded or created from scratch.
The process should consider the entire content ecosystem, including service pages, product pages, category pages, landing pages, case studies, blog articles, guides, FAQs, resources and conversion-focused copy.
Content should have a defined purpose. Core commercial pages should communicate value, relevance, differentiators, evidence and next steps. Supporting content can answer informational queries, explain complex concepts, address objections and strengthen topical authority. Internal links should connect these related pages naturally so users and search engines can understand their relationships.
Content decisions should be based on evidence rather than volume. A page does not need to be rewritten simply because the website is being redesigned. Existing content that attracts valuable traffic, generates enquiries or supports customer decisions may be worth preserving and improving. Conversely, outdated or overlapping pages may be better consolidated into a stronger resource.
Content Quality Review
For each important page, assess:
- Search intent.
- Target audience.
- Primary purpose.
- Primary and related topics.
- Accuracy and freshness.
- Conversion opportunity.
- Internal linking opportunities.
- Supporting evidence or trust signals.
- Metadata.
- Content ownership and update requirements.
This approach creates a website that is useful beyond launch day and can continue to grow through a structured content strategy.
7. Plan Conversion Paths and Calls to Action
A redesigned website should make the next step clear without overwhelming visitors with competing calls to action. Review the conversion paths across key pages and determine whether users can easily understand what to do next.
Depending on the business model, primary conversions might include purchasing a product, requesting a quote, booking a consultation, completing a form, starting a trial, calling the business or contacting sales. Secondary conversions might include downloading a guide, subscribing to updates, viewing a case study or exploring a related service.
CTAs should correspond to user intent and page purpose. A high-intent service page may benefit from a direct enquiry CTA, while an educational article may need a softer transition toward a relevant service or resource. Forms should also be reviewed for unnecessary fields because excessive friction can reduce completion rates.
This is where conversion rate optimisation (CRO) can become part of the redesign strategy. Instead of asking only whether a CTA is visually prominent, review whether the page provides enough information, trust signals and context for the visitor to act. Conversion design should therefore be connected to content, UX and customer journey decisions.
8. Make Mobile Experience a Core Requirement
Mobile responsiveness should not be treated as a final development check. The mobile experience affects navigation, readability, forms, page speed, interactions and conversions, so it needs to be considered throughout design and development. Review how menus, tables, forms, buttons, images, cards, accordions and other interactive components behave on smaller screens. Text should remain readable without excessive zooming or horizontal scrolling, and important actions should remain easy to access.
Marketing managers should test representative pages rather than relying only on the homepage. Service pages, product pages, forms, checkout screens, blog articles, search results and landing pages can behave differently on mobile. Testing should cover multiple viewport sizes and, where practical, real devices.
9. Prioritise Website Performance
Performance is both a user-experience consideration and an important technical quality factor. Large images, unnecessary scripts, excessive third-party integrations, inefficient code, poorly configured caching and heavy page builders can contribute to slower experiences. A redesign provides an opportunity to remove technical overhead and establish performance standards before the new website goes live.
Review image formats and dimensions, browser caching, compression, JavaScript and CSS loading, font usage, third-party scripts, server response time and content delivery. Test important templates rather than only testing a single homepage. Where appropriate, review Core Web Vitals and other performance measurements alongside real-world page behaviour.
Performance should be evaluated on mobile connections as well because users may not access the website through fast desktop broadband. Set measurable performance expectations for important templates and monitor them after launch.
10. Preserve Analytics, Tracking and Marketing Integrations
One of the easiest redesign mistakes to overlook is losing marketing data. New templates, forms, buttons, checkout processes, consent systems or third-party integrations can break existing tracking even when the website appears to function normally. Before development begins, create an inventory of all analytics and marketing technologies currently connected to the website.
Review analytics platforms, conversion events, advertising pixels, tag management systems, CRM integrations, form integrations, email marketing tools, heatmaps, call tracking, ecommerce tracking and other measurement systems. Document what each integration measures and where it is implemented. The new website should reproduce required tracking deliberately rather than relying on copied code.
Before launch, define conversion event validation procedures so important actions can be tested individually. After deployment, manually test important conversion events and confirm that data is reaching the appropriate platforms. A successful redesign should preserve the ability to measure performance accurately.
11. Establish Accessibility and Usability Standards
Accessibility should be part of the design and development requirements rather than a post-launch correction. Review colour contrast, keyboard navigation, form labels, focus states, alternative text, heading hierarchy, link clarity, error messages and interactive components. Content should be understandable and navigable for people using different devices and assistive technologies.
Usability testing should also examine whether visitors can complete important tasks without confusion. Ask representative users to find a service, compare products, contact the business, locate pricing, submit an enquiry or complete a purchase. Their behaviour can reveal problems that internal stakeholders may overlook because they already understand the website and business terminology.
12. Create a Thorough Pre-Launch QA Checklist
Before launch, the redesigned website should go through a structured quality-assurance process. This should include functional, visual, technical, SEO, content, analytics, accessibility and performance testing. Testing should take place in a staging environment before production deployment, with representative page templates checked rather than relying only on the homepage.
Do not assume that successful development testing means the website is ready for the public. Different browsers, devices, templates, integrations and user paths can expose problems that are not visible during routine development.
Pre-Launch QA Checklist
Content
- Review spelling and grammar.
- Verify contact information.
- Confirm pricing and product information.
- Check images and captions.
- Verify legal and policy pages.
Functionality
- Test forms.
- Test navigation.
- Test search.
- Test filters and interactive elements.
- Test ecommerce and checkout where applicable.
- Test emails and notifications.
SEO
- Verify indexability settings.
- Check canonical tags.
- Test redirects.
- Review metadata.
- Check XML sitemap.
- Verify structured data.
- Check internal links.
- Complete the pre-launch crawl.
Technical
- Test mobile layouts.
- Test major browsers.
- Check page speed.
- Verify HTTPS.
- Check 404 handling.
- Confirm backups and recovery procedures.
Analytics
- Test pageview tracking.
- Test conversion events.
- Verify advertising pixels.
- Test ecommerce tracking where applicable.
- Confirm CRM and marketing integrations.
13. Prepare the Launch and Migration Plan
A website launch should be treated as a controlled migration rather than simply switching one design for another. Establish who owns each launch task, when it will happen, what needs to be tested and how rollback will work if a serious problem appears. Take a complete backup of the existing website and database where applicable, and confirm that the new environment is ready before changing DNS or production settings.
The launch checklist should include final crawl checks, redirect activation, indexability settings, analytics verification, sitemap submission, form testing, critical page testing and monitoring arrangements. Establish a rollback plan before deployment so the team understands how to respond if a major technical or business-critical problem occurs.
Marketing, SEO, development and business stakeholders should know who is responsible for responding to issues. A redesign involving a web design and development partner such as Glopbe should also have clear ownership for approvals, technical fixes, content changes and post-launch support.
14. Monitor Performance After Launch
The redesign is not finished when the website goes live. The first days and weeks after launch are particularly important because real users and search engines can reveal issues that pre-launch testing did not identify. Monitor organic traffic, rankings, indexed pages, crawl errors, conversions, form submissions, ecommerce activity, page performance and user behaviour. Compare results against the baseline collected before the redesign.
Not every fluctuation indicates a problem, and some SEO changes can take time to stabilise. However, significant drops in important landing pages, unexplained conversion declines, widespread crawl errors, broken redirects or missing tracking should be investigated quickly. Establish a regular review schedule for the first week, first month and subsequent months.
A baseline-versus-post-launch comparison is particularly useful because it provides context for evaluating changes. The goal is not simply to determine whether traffic went up or down, but to understand how the redesigned website is affecting visibility, user behaviour and business outcomes.
15. Build a Continuous Optimisation Process
The redesign should create a foundation for ongoing improvement rather than becoming a one-time project. Once the new website has collected sufficient data, marketing managers can identify opportunities for conversion optimisation, content expansion, technical improvements and user-experience refinement. Analyse which pages attract visitors, which pages generate conversions, where users abandon journeys and which content supports commercial outcomes.
A useful post-launch roadmap can prioritise improvements according to business impact, user impact, technical effort and available resources. This may include improving landing-page copy, testing CTAs, creating supporting content, refining navigation, improving internal links, enhancing forms or expanding structured data. Continuous optimisation also prevents the website from becoming outdated again after several years.
Website Redesign Checklist: Final Summary
A marketing-led website redesign should cover much more than visual design. The project should begin with business goals and an audit, continue through audience research, information architecture, content, SEO, UX, performance, analytics, accessibility and conversion planning, and finish with structured testing and post-launch monitoring. Every important existing asset should be evaluated before it is changed or removed. The new website should be designed around measurable objectives and real user needs rather than assumptions about what looks modern.
For marketing managers, the most important principle is continuity: preserve valuable search equity, content, tracking and conversion paths while improving the experience for users. A successful redesign connects business strategy, search intent, information architecture, content strategy, technical implementation and measurement rather than treating them as separate tasks. SEO and analytics should be protected throughout the migration, while performance and accessibility should be built into the project from the beginning. Most importantly, launch should be treated as the start of an optimisation cycle rather than the final stage of the redesign.
Frequently Asked Questions
1. What should be included in a website redesign checklist?
A comprehensive website redesign checklist should cover business goals, audience research, website auditing, information architecture, content, SEO, UX, mobile responsiveness, accessibility, performance, conversion paths, analytics, integrations, quality assurance, migration, launch and post-launch monitoring. It should also document existing URLs, important organic landing pages, conversion data and tracking requirements. This ensures that the redesign improves the website without accidentally removing valuable assets.
2. How do I prevent a website redesign from hurting SEO?
Start by auditing the existing website and identifying high-value pages, rankings, organic traffic, backlinks and indexed URLs. Preserve important URLs where practical and create relevant permanent redirects when URLs must change. Before launch, verify metadata, canonical tags, internal links, structured data, XML sitemaps, robots directives and indexability. After launch, monitor rankings, organic traffic, crawl errors, indexed pages and important landing pages to identify migration problems quickly.
3. How long does a typical website redesign take?
The timeline depends on the website's size, technical complexity, number of templates, content requirements, integrations, ecommerce functionality, approval process and migration requirements. A relatively simple marketing website can require substantially less time than a large ecommerce platform or content-heavy website. The planning stage should account for discovery, content, UX, design, development, testing, migration and post-launch monitoring rather than focusing only on development time.
4. Should content be rewritten during a website redesign?
Content should be reviewed systematically rather than automatically rewritten. Existing pages that generate valuable traffic, leads, backlinks or customer engagement may need to be retained and improved rather than replaced without evidence. Outdated, duplicated, thin or poorly aligned content can be consolidated or rewritten. New content should be created where important customer questions, search intent or commercial opportunities are not adequately covered.
5. What should marketing managers monitor after a website redesign?
Marketing managers should monitor organic traffic, important keyword rankings, indexed pages, conversion rates, leads or sales, form submissions, engagement metrics, landing-page performance, page speed, crawl errors, redirects and analytics tracking. Ecommerce businesses should also monitor product views, add-to-cart activity, checkout completion and revenue. Comparing these metrics against the pre-redesign baseline provides a more reliable assessment than judging the new website primarily by its appearance.
Cleanup order is easy to get wrong.
Get expert help from Globpe.
Your website should make it clear who you are, what you offer and what visitors should do next. Whether you are launching a new digital presence or improving an existing website, start with the goals, customers and opportunities that matter most to your business.