A website redesign needs a project plan that covers content and approvals as carefully as design and development. Define the goal, page scope, deliverable owners, migration needs, test criteria, and launch decision before work begins.
Set scope before choosing dates
List pages, functions, integrations, content changes, and migration tasks. Identify what is excluded and how new requests will be handled. Define a business goal such as clearer service enquiries; “make it look better” is not enough to guide trade-offs.
Plan work in phases
- Discovery, analytics review, and information architecture.
- Content inventory, copy, imagery, and approvals.
- Design system and page templates.
- Build, integrations, redirects, and migration.
- QA for mobile, forms, links, metadata, and performance.
- Launch, monitoring, and issue response.
Make launch readiness visible
Use a checklist with owners and pass criteria. Test user journeys, forms, analytics, redirects, page titles, and key links. Confirm backups and who makes the go/no-go decision. Track feedback in one place to prevent conflicting revisions. For coordinated digital delivery, see project management services.
How long does a redesign take? It depends on scope, content readiness, integrations, and approvals. Include SEO migration and redirect checks in the project.
Set a business goal before redesigning pages
A website redesign should respond to a defined problem: visitors cannot understand the offer, the mobile experience is difficult, leads are not reaching the right person, or the content no longer reflects the business. Review analytics, customer questions, search queries, conversion paths, and technical issues before choosing a new look. Establish baseline measures so the team can evaluate whether the redesign improved the experience.
Plan content, design, development, migration, and quality assurance as connected workstreams. Confirm who owns copy and approvals, what pages are in scope, which URLs must remain or redirect, and what tracking or integrations need to survive. Search visibility can be harmed by missing redirects, changed page titles, broken links, and untested structured data. Include these checks before launch, not as cleanup afterward.
Website launch checks
- Approve sitemap, page goals, and content responsibilities.
- Review layouts on mobile, keyboard, and common browsers.
- Test forms, booking links, analytics, and confirmation messages.
- Map old URLs to new URLs and verify redirects.
- Monitor errors, search indexing, and conversion signals after release.
Keep a post-launch issue list with severity, owner, and target date. Not every improvement must block launch, but accessibility, security, broken core journeys, and major tracking problems should be resolved or explicitly managed.
Frequently asked: How long does a website redesign take?
It depends on scope, content readiness, integrations, and approval speed. A clear brief and timely decisions usually reduce delay more than adding more people to the project.
A worked example: scoping before dates
A consultant wants a new website "in a month". Before any date is agreed, the scope is written down. Goal: more discovery calls booked from the site. In scope: home, about, services, contact and one case study page, plus a booking link and a contact form. Not in scope: a blog, new photography, a new logo. Content: the consultant supplies approved copy for all five pages by the end of week one.
That last line is the one that decides the timeline. With content agreed up front, the phases are short and predictable: structure and copy, design, build, review, launch. Without it, the designer builds pages around placeholder text, the real copy arrives late and is twice as long, and the layout has to be redone. The project slips, and the cause is not design or development.
Mistakes that delay a redesign
- Treating content as a detail. Late or unapproved content is the most common reason website projects overrun. Give it an owner and a deadline of its own.
- Too many approvers. Name one person who gives final sign-off, and collect everyone else's feedback through them.
- Open-ended feedback. Agree the number of review rounds and how long each one has.
- Forgetting the old site. List the existing pages and links that must keep working, so visitors and search engines are not sent to dead pages after launch.
Where to start this week
Write one sentence stating what the new website must do for the business, then list the pages that serve that goal. Anything that does not serve it can wait for a later phase. Then run the build like any other project, with one owner and visible milestones, as described in project management for small business.
Want a second opinion on your operations?
Take the free Business Scale Readiness Assessment, or book a strategy call and I will tell you what I would fix first.