When to use a website redesign template
A website redesign touches strategy, content, design, development and search, and it usually involves the client’s team as much as the agency’s. Redesigns most often go wrong in two places: content that arrives late and delays launch, and launches that lose search traffic because old URLs were not redirected. This template treats both as first-class tasks.
Use it when replacing or significantly redesigning an existing website. For a brand-new site with no traffic to protect, you can skip the search tasks in discovery and launch.
How the template is structured
- Discovery. Agree goals, audit the current site and record current search traffic before anything changes.
- Structure & content. Plan the sitemap, create wireframes and give every page a content owner and a due date.
- Design. Design key page templates, run review rounds and prepare a design system developers can build from.
- Build. Develop templates, load content and set up forms, analytics and tracking.
- QA & launch. Test on devices and browsers, map redirects from every old URL and launch with a checklist.
- Post-launch. Monitor traffic and errors, fix issues, train the client’s editors and review results against the original goals.
How to use it in Worklenz
- Create a project for the redesign and link the client.
- Add the phases and tasks above, then add one task per page in the content step so every page has an owner.
- Use labels such as Content needed and Waiting on client to see what is blocking launch.
- Plan dates on a timeline. Worklenz’s Gantt view is read-only on the Pro plan and fully editable on Business.
- Track time by phase on the Pro plan and above.
Making web projects visible and billable
Website projects are usually sold at a fixed price, and the risk sits in content delays and extra design rounds. Time tracking shows where hours go phase by phase. On the Business plan, project finance compares the budget with the cost of logged time, and the client portal gives clients one place to submit content and requests.
Example: redesigning a services firm website
An agency is redesigning a 40-page site for an engineering consultancy. Discovery shows that six service pages bring most of the search traffic and leads, so the sitemap keeps their URLs. Wireframes and designs are approved in four weeks, but content is the risk, so each of the client’s partners owns the copy for their service pages, with due dates in the project.
Developers build the templates while content arrives. Before launch, the team maps redirects for twelve retired URLs and tests forms on mobile. After launch, the agency watches search traffic and fixes two broken links in the first week. At the 60-day review, contact form submissions are up compared with the old site.
Who should be involved
An agency project manager owns the plan and the client relationship. A strategist or SEO specialist owns discovery and redirects, a designer owns design, and a developer owns the build. On the client side, name one decision maker and one content owner per section of the site. Content owners are the role most often forgotten, and they decide whether the launch date holds.
Common website redesign mistakes
The first mistake is designing before the sitemap and content are planned, so pages are designed around placeholder text that never matches the real copy. The second is launching without a redirect map, which loses search traffic that took years to build. The third is treating launch as the end of the project, when the first weeks after launch are when broken forms, missing pages and tracking gaps appear. This template gives each of those risks a task and an owner.
Tips for a smoother redesign
- Record search traffic before you start. It is the only way to know what to protect.
- Assign content owners on day one. Content delays are the most common reason launches slip.
- Redirect every changed URL. Missing redirects are the most common cause of traffic loss after a redesign.
- Plan a post-launch review. Goals set in discovery should be checked after launch.
Related: the user experience (UX) design template and the e-commerce development template.






