A website redesign checklist helps agencies and clients clarify goals, sitemap, content, assets, technical access, SEO risks, timeline, responsibilities and approval flow before design or development begins. Most website redesign problems do not happen because the design team cannot design. They happen because the project starts without enough clarity about what should stay, what should change, what should be removed, who owns the content, what technical access is needed and how the new website will support the business.
A professional website redesign should not begin with colours, fonts or homepage references. It should begin with business purpose, page structure, content flow, search visibility, user journeys, technical requirements and final approval rules. This checklist explains what clients should prepare, what agencies should ask, and how both sides can avoid delays, scope confusion and SEO damage during a redesign.
Key Insights
- A website redesign should start with discovery, not visual design.
- The sitemap must be agreed before page design and development begin.
- Existing pages, PDFs, images, services, team information and downloadable assets should be reviewed before content is moved.
- Clients should clearly state what must stay, what must change and what must be removed.
- Agencies need domain, hosting, CMS, analytics and content access early in the project.
- SEO risks should be checked before URLs, menus or old pages are changed.
- A redesign is successful when the new website is clearer, easier to use, easier to manage and better aligned with business goals.
What Is Website Redesign Discovery?
Website redesign is the planning stage before a website is redesigned, rebuilt or relaunched. It helps the agency and client agree on the website’s purpose, structure, content, functionality, technical access, timeline and approval process.
Discovery answers the questions that design alone cannot solve:
- What is wrong with the current website?
- What should the new website achieve?
- Which pages should stay?
- Which pages should be removed?
- Which content needs to be rewritten?
- Which files, PDFs, images or documents are required?
- Who will provide the content?
- Who will approve the design?
- Which URLs need redirects?
- What platform will the website use?
- What access does the agency need?
- How will the website be launched?
A redesign without discovery usually becomes a guessing project. A redesign with proper discovery becomes a controlled project.
Why Website Redesign Projects Fail Without Proper Discovery
Website redesign projects often fail because the team starts too late on the important questions.
A client may approve a visual direction, then later realise the service pages are incomplete. A developer may start building before the sitemap is final. A project manager may ask for WordPress access after the deadline is already close. A designer may create a layout without knowing that every product, vessel, treatment, doctor, location or service needs a downloadable document or booking flow.
These issues are avoidable.
The most common redesign problems include:
- unclear sitemap
- missing content
- old pages forgotten
- PDFs and downloadable files not prepared
- poor image quality
- no final brand assets
- unclear technical access
- no redirect plan
- design comments scattered across WhatsApp or email
- no single approval owner
- unrealistic timeline
- confusion between template and custom website scope
- SEO pages removed without review
- content copied from the old website without checking accuracy
Discovery prevents these problems by forcing the right questions before execution begins.
Start With the Business Reason for the Redesign
A redesign should have a business reason. “The website looks old” is not enough.
Before planning pages or design, the client and agency should define the reason for the redesign.
Common reasons include:
- the business has changed
- the brand has changed
- the company has entered a new market
- the website does not explain services clearly
- the website does not generate leads
- the website is difficult to update
- the old design no longer feels professional
- the website is slow or technically outdated
- the old content is inaccurate
- the website does not support SEO
- the company needs better trust signals
- the business needs booking, inquiry, eCommerce or document-download features
The reason matters because it shapes the structure.
A redesign for brand trust is different from a redesign for lead generation. A redesign for SEO is different from a redesign for investor credibility. A redesign for a new country or business entity is different from a simple visual refresh.
Define the Main Website Goals
A redesign should usually have one primary goal and several supporting goals.
The primary goal may be:
- generate inquiries
- explain services better
- improve brand credibility
- support SEO growth
- help customers book appointments
- improve product sales
- provide technical information
- support recruitment
- support investor or partner confidence
- reduce admin questions
- support a new market launch
Supporting goals may include:
- faster website speed
- easier CMS editing
- better mobile experience
- clearer navigation
- updated imagery
- stronger case studies
- more professional content
- stronger internal linking
- better conversion tracking
- better search indexing
Agencies should ask the client to rank goals by importance. If every goal is treated as equal, the website structure becomes unfocused.
Audit the Existing Website Before Planning the New One
A redesign should not ignore the old website. Even if the old design looks outdated, it may contain useful SEO value, important content, backlinks, customer information or business history.
Before changing anything, review:
- current sitemap
- service pages
- product pages
- blog posts
- case studies
- contact pages
- location pages
- downloadable files
- PDFs
- image library
- menu structure
- footer links
- ranking pages
- indexed pages
- pages with backlinks
- pages with traffic
- pages that convert
- pages that are outdated
- pages that should be removed
Do not remove pages only because they look old. First check whether they still bring traffic, leads, links or trust.
Decide What Should Stay, Change or Be Removed
One of the most useful redesign exercises is a simple content decision list.
Every existing page or section should be marked as:
- keep
- rewrite
- merge
- remove
- redirect
- replace
- update later
This avoids vague content migration.
For example, an old “About Us” page may stay but need updated positioning. A service page may stay but need clearer headings. A certification section may need removal if it is no longer relevant. A company profile section may need rewriting if the business is now serving a new market. A gallery may need replacement if images are outdated or repetitive.
A redesign is not only about adding new pages. Sometimes the most important decision is what to remove.
Build the Sitemap Before Designing Pages
A sitemap is the structure of the website. It shows which pages exist and how they connect.
Before design starts, the agency and client should agree on the sitemap.
A simple business website may include:
- Home
- About
- Services
- Industries
- Projects
- Case Studies
- Blog
- Resources
- Contact
A more technical or B2B website may need:
- Company Profile
- Our Work
- Fleet or Equipment
- Specifications
- Certifications
- Downloadable PDFs
- Regional Entity Pages
- Team
- Careers
- News
- Contact
An eCommerce website may need:
- Categories
- Product Pages
- Collections
- Gift Sets
- Shipping
- Returns
- Rewards
- FAQs
- Contact
A healthcare website may need:
- Doctors
- Departments
- Treatments
- Appointments
- Emergency Contact
- Patient Information
- Insurance
- Reviews
- Contact
The sitemap should reflect how users make decisions, not only how the company is internally organised.
Map the User Journey
A website redesign should consider how different visitors move through the website.
Ask:
- Who will visit the website?
- What do they need first?
- What questions will they have?
- What proof do they need?
- What action should they take?
- What page should they visit next?
- What content helps them decide?
A first-time visitor may need a clear explanation of services. A returning prospect may need technical specifications. A procurement manager may need downloadable PDFs. A patient may need doctor information. A restaurant customer may need a menu and reservation button. A property buyer may need location, project details and inquiry forms.
The website should not force every user through the same path.
Clarify the Homepage Role
The homepage should not try to say everything.
Its job is to guide users to the right next step.
A strong redesigned homepage usually includes:
- clear positioning statement
- key service or product categories
- proof of credibility
- primary CTA
- secondary CTA
- important business highlights
- selected projects or case studies
- trust signals
- internal links to important pages
- contact or inquiry path
The homepage should answer three questions quickly:
- What does this business do?
- Who is it for?
- What should I do next?
If the homepage feels like a brochure, it may not convert. If it feels like a cluttered news feed, users may not understand the business.
Clarify Service, Product or Solution Pages
Every important service, product or solution should have enough information to stand alone.
A weak page says what the company offers.
A strong page explains:
- who the service is for
- what problem it solves
- what is included
- how the process works
- what proof exists
- what results or outcomes matter
- what questions buyers usually ask
- what the next step is
For SEO and AI search visibility, each important service page should answer clear questions instead of only using marketing claims.
Plan Downloadable Files and PDFs Early
Many businesses need downloadable files on their websites.
These may include:
- company profiles
- product specifications
- vessel specifications
- brochures
- service sheets
- menus
- treatment guides
- property brochures
- catalogues
- price lists
- safety documents
- technical sheets
- warranty documents
If PDFs are part of the website experience, they should be planned early.
Ask:
- Which PDFs are needed?
- Which pages should include them?
- Should each item have its own download?
- Are the PDFs final?
- Are the file names clear?
- Should PDFs be searchable?
- Should users fill a form before downloading?
- Are the PDFs branded properly?
- Are the files mobile-friendly?
- Do PDFs need updating later?
Do not treat PDF downloads as an afterthought. For many B2B and technical websites, they are a core part of the user journey.
Collect Brand Assets Before Design Starts
Design depends on brand assets.
Before redesign work begins, collect:
- logo files
- editable logo source files
- brand guidelines
- colour codes
- typography rules
- icons
- brand patterns
- image library
- video assets
- product photos
- team photos
- project photos
- company profile
- presentation decks
- brochures
- social media links
The agency should not rely only on low-resolution logos from the old website. If the client has AI, EPS, SVG or high-resolution files, those should be provided at the start.
Poor assets lead to poor design quality, even if the designer is skilled.
Confirm Content Ownership
Content delays are one of the biggest reasons redesign projects slow down.
Before the project starts, confirm who is responsible for:
- homepage copy
- service page copy
- about page copy
- team bios
- product descriptions
- case studies
- FAQs
- legal pages
- downloadable files
- image selection
- blog migration
- SEO metadata
- translations
- final proofreading
Some clients expect the agency to write everything. Some agencies expect the client to provide everything. This must be clarified before quoting and scheduling.
If the agency is writing content, the scope should say whether this includes research, copywriting, SEO writing, proofreading, editing, translation and upload.
Review Existing SEO Before Changing URLs
Website redesigns can hurt SEO if old pages are removed or URLs are changed without a plan.
Before redesigning URLs, check:
- current indexed pages
- current ranking pages
- pages with backlinks
- pages with organic traffic
- pages generating leads
- old blog posts with traffic
- location pages
- service pages
- product pages
- PDFs ranking in search
- old URLs that need redirects
The goal is not to keep every old page. The goal is to understand what value exists before making changes.
Create a Redirect Plan
If URLs change, redirects are needed.
A redirect plan maps old URLs to new URLs so users and search engines land on the most relevant replacement page.
For each old URL, decide:
- keep the same URL
- redirect to a new equivalent page
- redirect to a broader related page
- merge with another page
- remove with no replacement only if truly unnecessary
Avoid redirecting every old page to the homepage. That creates a poor user experience and weakens topical relevance.
A good redirect plan protects existing search visibility and reduces broken links.
Check Technical Access Early
Agencies should not wait until launch week to ask for access.
Depending on the project, the agency may need:
- domain registrar access
- hosting access
- cPanel or server access
- WordPress admin access
- Shopify admin access
- DNS zone access
- Google Analytics access
- Google Search Console access
- Google Tag Manager access
- Google Business Profile access
- email provider access
- CRM access
- booking system access
- payment gateway access
- old website backup access
If the client has an IT team, the agency should know who to contact and what to request.
Access delays can stop a redesign even when design and content are ready.
Decide Between Template and Custom Website Scope
A common source of conflict is the difference between a template-based website and a custom-designed website.
A template website usually means:
- faster timeline
- lower cost
- limited layout flexibility
- predefined sections
- fewer custom design decisions
- suitable for simple websites
A custom website usually means:
- longer timeline
- higher cost
- custom UI direction
- more design review
- more revisions
- more strategic layout planning
- better fit for complex businesses
Clients should understand this before signing.
If the client expects a custom experience at template pricing, the project will likely face tension. If the agency promises a custom website without enough discovery, the timeline may become unrealistic.
Set a Realistic Timeline
A redesign timeline depends on scope, not wishful thinking.
Timeline factors include:
- number of pages
- custom vs template design
- content readiness
- number of stakeholders
- technical complexity
- SEO migration
- image preparation
- downloadable assets
- CMS setup
- integrations
- approval speed
- revision rounds
- launch coordination
A one-week redesign may be possible for a very simple website with complete content and a template approach. A custom website with content migration, PDFs, SEO review, technical setup and stakeholder approvals usually needs more time.
Agencies should explain what can be done quickly and what requires proper planning.
Decide the Review and Approval Process
Redesign projects slow down when feedback comes from too many places.
Before design starts, decide:
- who gives feedback
- who has final approval
- where feedback should be added
- how many revision rounds are included
- how conflicting comments will be resolved
- how late changes will be handled
- when design is considered approved
- when development begins
Feedback should be collected in one place whenever possible. Comments spread across WhatsApp, email, documents and calls create confusion.
A clear approval process protects both the client and the agency.
Use Design References Correctly
Clients often share reference websites. These are useful, but they should not be copied blindly.
When a client shares a reference website, the agency should ask:
- What do you like about it?
- Is it the layout?
- Is it the colour style?
- Is it the navigation?
- Is it the spacing?
- Is it the content flow?
- Is it the animation?
- Is it the industry positioning?
- Is it the feeling of trust?
- Is it the simplicity?
A reference website is a clue, not a command.
The new website should be shaped by the client’s business, users, content and goals. It should not become a copy of another brand.
Plan Website Navigation
Navigation should help users find what they need quickly.
Before redesigning the menu, decide:
- which pages deserve top-level navigation
- which pages belong under dropdowns
- which pages should be in the footer
- which pages should be linked contextually
- which pages support SEO but do not need main menu placement
- which pages are only for campaigns or internal use
Navigation should not mirror company departments if users do not search that way.
For example, users may look for “services,” “pricing,” “case studies,” “specifications,” “doctors,” “booking,” “locations,” “projects” or “support.” The menu should match how visitors think.
Plan CTAs Before Design
Calls-to-action should be planned before designing pages.
Common CTAs include:
- Contact Us
- Get a Quote
- Book an Appointment
- Request a Consultation
- Download Brochure
- View Specifications
- View Portfolio
- Call Now
- WhatsApp Us
- Submit Inquiry
- Schedule Demo
- Start Project
Different pages may need different CTAs.
A technical product page may need “Download Specification.” A service page may need “Request a Quote.” A clinic page may need “Book an Appointment.” A restaurant page may need “Reserve a Table.” A property page may need “Register Interest.”
Good CTA planning improves conversion and makes the design more purposeful.
Plan Mobile Experience First
Most users will review the website on mobile at some point, even in B2B industries.
Before approving design, check:
- mobile menu
- button size
- contact links
- phone tap-to-call
- WhatsApp links
- form usability
- image cropping
- PDF download experience
- sticky CTA
- page speed
- text readability
- spacing
- horizontal scrolling
- embedded maps
- sliders
- tables
A website that looks professional on desktop but breaks on mobile is not ready.
Plan Website Management After Launch
A redesign should not only ask, “How will the website look?”
It should also ask, “Who will manage it later?”
Clarify:
- who can edit pages
- who can add blogs
- who can update team members
- who can change PDFs
- who can update images
- who can manage forms
- who can manage plugins
- who handles backups
- who handles security
- who handles maintenance
- who handles SEO updates
If the client wants to manage the website internally, the CMS should be easy enough for them to use. If the agency will manage it, maintenance scope should be clear.
Website Redesign Checklist
Use this checklist before starting a redesign.
Business and Strategy
- Why is the website being redesigned?
- What business goal should the new website support?
- Who are the main users?
- What should users do on the website?
- What problems exist with the current website?
- What must improve after launch?
- What services, products or markets have changed?
- What proof or trust signals should be added?
Sitemap and Structure
- What pages exist now?
- What pages should stay?
- What pages should be removed?
- What pages should be merged?
- What new pages are needed?
- What should appear in the main menu?
- What should appear in the footer?
- What pages need internal links?
- What pages are important for SEO?
Content
- Who will write the content?
- Which content can be reused?
- Which content must be rewritten?
- Which content is outdated?
- Are service descriptions final?
- Are product descriptions final?
- Are team bios ready?
- Are case studies ready?
- Are FAQs ready?
- Are legal pages ready?
- Are translations needed?
Assets
- Is the logo available in editable format?
- Are brand guidelines available?
- Are images ready?
- Are videos ready?
- Are PDFs ready?
- Are brochures ready?
- Are product or service documents ready?
- Are team photos ready?
- Are project photos ready?
- Are social links confirmed?
SEO
- Which pages currently rank?
- Which pages get traffic?
- Which pages have backlinks?
- Which URLs will change?
- Is a redirect map required?
- Are SEO titles needed?
- Are meta descriptions needed?
- Is an XML sitemap needed?
- Are old pages being removed safely?
- Are internal links planned?
- Is schema needed?
Technical Access
- Who owns the domain?
- Who controls hosting?
- Who has CMS access?
- Who has DNS access?
- Who has Google Analytics access?
- Who has Search Console access?
- Who has email system access?
- Is the old website backed up?
- Is staging required?
- Is the launch environment ready?
Design and Development
- Is the website template-based or custom?
- Are reference websites provided?
- What does the client like about the references?
- How many design concepts are included?
- How many revision rounds are included?
- Who approves design?
- When does development start?
- Are special features required?
- Are forms, downloads, booking or eCommerce needed?
Launch and Handoff
- What is the target launch date?
- Who approves launch?
- Is there a launch checklist?
- Are redirects ready?
- Is DNS access ready?
- Is SSL ready?
- Are forms tested?
- Are emails tested?
- Is analytics installed?
- Is Search Console verified?
- Is training needed?
- Is maintenance included?
Common Website Redesign Mistakes
Starting With Design Before Structure
A beautiful website can still fail if the sitemap is unclear.
Structure should come before visuals. The agency should know what pages are needed and what each page should achieve before creating design layouts.
Reusing Old Content Without Reviewing It
Old content may be outdated, inaccurate or poorly written.
Before moving content, check whether it still matches the business, services, market, pricing, team and brand positioning.
Removing SEO Pages Without Checking Traffic
Some old pages may still bring visitors or leads.
Before deleting pages, check whether they rank, attract traffic, earn backlinks or support internal linking.
Asking for Access Too Late
Access problems delay projects.
Domain, hosting, CMS, DNS, analytics and Search Console access should be requested during discovery, not at launch.
Treating PDFs as Last-Minute Files
PDFs, brochures and specifications may be central to the user journey.
Plan them early and decide where they belong.
Not Defining Final Approval
If five people give separate feedback, the project can become messy.
One person or one committee should be responsible for final approval.
Confusing Custom Design With Template Design
Clients and agencies should agree on what “custom” means.
If scope is unclear, design expectations and pricing expectations will conflict.
Forgetting the Post-Launch Plan
A redesigned website still needs maintenance, updates, backups, security checks, SEO monitoring and content improvements.
Launch is not the end of the website’s life. It is the start of the next stage.
Questions This Article Answers
What should be included in a website redesign checklist?
A website redesign checklist should include business goals, sitemap, existing content, new content, assets, SEO risks, technical access, design expectations, timeline, approval process, launch requirements and post-launch maintenance. It helps agencies and clients agree on the full scope before design and development begin.
Why is discovery important before redesigning a website?
Discovery is important because it prevents unclear scope, missing content, access delays, poor sitemap decisions, SEO loss and approval confusion. It helps the agency understand the business problem behind the redesign instead of only changing the visual design.
Should a website redesign keep the same URLs?
A website redesign should keep important URLs when possible, especially pages that already rank, receive traffic or have backlinks. If URLs must change, old URLs should be mapped to the most relevant new pages using redirects to protect user experience and search visibility.
What should clients prepare before a website redesign?
Clients should prepare brand assets, logo files, website access, domain and hosting details, content, images, PDFs, service information, team details, approval contacts, design references and business goals. The more prepared the client is, the smoother the redesign process becomes.
What access does an agency need for a website redesign?
An agency may need CMS access, WordPress access, Shopify access, domain registrar access, hosting access, DNS access, Google Analytics access, Search Console access, file backups and access to any booking, CRM, payment or email systems connected to the website.
How long does a website redesign take?
A simple template-based redesign may take a few weeks if content and access are ready. A custom redesign with sitemap planning, content writing, SEO migration, PDFs, integrations and multiple approvals usually takes longer. The timeline depends on scope, complexity and client response time.
Can a redesign hurt SEO?
Yes, a redesign can hurt SEO if important pages are removed, URLs are changed without redirects, metadata is lost, internal links break, content is reduced, pages are blocked from indexing or the new website loads slowly. SEO should be part of the redesign plan from the beginning.
Should clients provide reference websites?
Yes, reference websites can help the agency understand design preferences, but the client should explain what they like about each reference. The agency should use references to understand direction, not to copy another website.
What is the difference between a template redesign and a custom redesign?
A template redesign uses predefined layouts and is usually faster and more cost-effective. A custom redesign involves tailored layouts, more strategic design decisions and more flexibility. Custom redesigns are better for complex businesses, stronger branding, unique content flow and advanced functionality.
What happens after a redesigned website goes live?
After launch, the website should be monitored for broken links, form issues, email delivery, redirects, indexing, analytics, speed, mobile usability and user feedback. The client and agency should also agree on maintenance, backups, security, updates and ongoing SEO improvements.
Final Website Redesign Checklist
Before starting a redesign, confirm these items:
- business reason for redesign
- primary website goal
- target audience
- key user journeys
- existing sitemap
- new sitemap
- pages to keep
- pages to remove
- pages to merge
- pages to rewrite
- SEO pages to protect
- redirect requirements
- content responsibilities
- final brand assets
- required PDFs and downloads
- required images and videos
- technical access
- domain and hosting details
- CMS access
- design references
- custom or template scope
- approval owner
- revision process
- project timeline
- launch plan
- maintenance plan
A redesign without this clarity is risky. A redesign with this clarity becomes a structured project.
How Rozzario Can Help
A website redesign should improve more than appearance. It should make the website clearer, easier to use, easier to manage, stronger for SEO and more aligned with the business.
Rozzario helps businesses plan and deliver website redesign projects with the right discovery process before design begins. That includes sitemap planning, content structure, website copy, WordPress development, SEO migration, technical setup, domain and hosting support, launch checks and post-launch maintenance.
If your current website looks outdated, no longer reflects your business, or does not support your sales and marketing goals, Rozzario can help you redesign it with a proper strategy behind the structure, content and launch process.
