Skip to content

Website Redesign Planning Checklist: URLs, Content, SEO and Launch

3 min read Web Design & UX
Website Redesign Planning Checklist: URLs, Content, SEO and Launch

A successful website redesign begins before design choices are made. By identifying the information that is already useful, the pages people find through search, and the parts your team struggles to update, you can create a site that supports sales, recruitment, and communication—not simply a newer appearance.

Before deciding what to change, decide what deserves to stay

An existing website may hold useful entry points from search, URLs customers already use, and explanations that support sales conversations. Not everything should remain, but nothing valuable should disappear by accident.

  1. Clarify the purpose of the renewal
  2. Review important pages and URLs
  3. Gather copy, imagery, and case studies
  4. Check measurement and enquiry routes
  5. Plan who will update the site after launch

1. Define the purpose in business terms

“The site looks old” can start a conversation, but it is not a useful end point. Better aims might include improving the quality of enquiries, explaining a changing service, supporting recruitment, or communicating to an international audience. Clear aims make page and content priorities easier to decide.

2. Record valuable URLs, traffic, and content

Use analytics and Search Console to understand which pages are read, which search terms lead people in, and which URLs are referenced elsewhere. If an address changes, plan the old-to-new relationship and redirects. Rankings cannot be guaranteed, but this work helps avoid losing a useful route without understanding its value.

3. Plan content and editing around reality

You do not need to rewrite everything. Sales material, recurring questions, proposals, and existing case studies can reveal useful starting content. Decide what is missing and who will keep information current after launch; this should inform the CMS and the structure as much as the design does.

4. Record ownership and decision rights

Adding more participants does not automatically make review faster. For business purpose, factual accuracy, copy, design, technology, legal review and launch, distinguish the person doing the work, the reviewer and the final decision owner. On a bilingual site, the person judging natural language may not be the person authorised to approve a business claim.

Area Work and review Final decision
Business and audience Goals, priority customers and page jobs Business owner
Content Source material, copy, images, rights and facts Subject owner
Design and technology Experience, CMS, integrations, migration and testing Agreed project owner
Launch and operation Release decision, editing, measurement and enquiries Post-launch website owner

5. Share timing and investment as assumptions and priorities

Even when the amount and launch date are not fixed, share the essential pages, required functions, business events, source-material readiness and realistic review time. Separate fixed conditions from negotiable ones so phased release and scope options can be compared. A proposal should make clear whether copy, photography, translation, migration, external costs and post-launch work are included.

6. Define launch acceptance before the final review

If “complete” is first discussed at the end, important checks can be missed. Record the project-specific conditions for key pages, mobile behavior, forms and notifications, language switching, old-to-new URL handling, measurement, permissions, backups and operational handover. Distinguish release-blocking defects, post-launch improvements and out-of-scope work.

Next: turn the content inventory into a migration map

Once pages, URLs, forms, measurement and connected services have owners, define the old-to-new relationship and the checks needed around launch.

Continue to the website migration guide

RENEW WITH CARE

Could your existing website provide a stronger foundation for the next stage?

Clickmark can help from review and structure through production, migration, launch, and ongoing improvement.

Discuss a website redesign