In this article
A redesign does not have to start with a new homepage sketch. Without knowing existing pages, outdated material and important links, the project can lose useful information. This guide explains a pre-design inventory. Its purpose is not to preserve everything unchanged, but to decide deliberately what should move, be updated or be consolidated. Treat launch as a shared content and technical process rather than assuming a new visual presentation proves the complete site transition has been handled.
Quick answer
List current URLs, page purposes, content status and owners. Separate material to retain, update or consolidate. Prepare an old-to-new map where addresses change. Create checks for forms, languages and important links. Approval of visual design is one milestone; technical transition and post-launch verification require their own responsibilities and evidence.
List pages beyond the main navigation
Include products, projects, articles, forms and language versions. Record which question each page answers. A hypothetical manufacturer may rely on product documents that are not prominent in the menu. Do not judge value from appearance alone. Consider actual use and available measurement information before deciding that an old-looking page can disappear without a replacement or updated destination.
Give each content item a decision and owner
Assign actions such as retain, revise or consolidate. Identify who verifies the facts and whether images can still be used. Resolve conflicting service explanations. List missing material with owners and dates rather than passing an invisible content gap into the design stage. A clear inventory lets the new structure reflect actual responsibilities instead of assuming every draft will somehow be finished before launch.
Map address changes deliberately
Google recommends mapping old addresses to suitable new destinations and checking redirects when site URLs change. Match the content rather than sending unrelated pages to one homepage. Hand the map to development and publication owners. Its existence is not proof of correct implementation; test the actual behaviour. This step connects editorial decisions about consolidation with the technical work needed to preserve useful paths for visitors.
Test layouts with realistic content
Use long titles, actual products and varied image proportions rather than only short sample text. Review language versions and mobile reading. A homepage approval does not establish that the whole site works. Try a service-to-enquiry path and a product-to-contact path. The exercise should reveal whether the new organisation helps someone complete a task, not simply whether the pages share a pleasing style.
Assign post-launch verification
Give forms, redirects, key links and measurement setup named check owners. Content and technical teams should use the same final list. Share the current website, inventory and priorities with BOCW when discussing a redesign. Establish a record for observed problems and corrections after publication. Close the transition when important behaviours have been checked, not merely when the new visual design becomes publicly visible.
Mapping three redesign content decisions
Consider three hypothetical decisions: retain a current service page, update an outdated pricing article and review two overlapping pages for consolidation. Assess content and available evidence, not filenames alone. Record address implications beside each decision. Where content moves, show its destination. After developers implement a redirect, the content owner verifies the target. Include forms and language links in sample journeys. The final table should connect old address, new destination, content status and verification result.
Key takeaways
- Include important pages outside the menu.
- Assign content decisions, owners and dates.
- Verify mappings and real post-launch behaviour separately.
- After launch, check important inventory URLs directly rather than assuming presentation pages all have working published equivalents.
Frequently asked questions
Must all URLs change during redesign?
No. New design does not require new addresses everywhere. Evaluate necessary changes through a technical transition plan.
Should old blog articles be deleted?
Not automatically. Assess purpose, currency, overlap and available evidence before deciding whether to retain or consolidate them.
Is homepage approval sufficient?
No. Check supporting pages, forms, language paths and technical links as well.
