Website Redesign Content Inventory: Keep, Merge or Remove
Create a list of current URLs using the CMS, XML sitemap, analytics and crawl information where available. Record each page title, topic, organic traffic, enquiries, backlinks and owner. A redesign that starts from only the main navigation often overlooks useful articles and service pages.
A redesign should not erase pages that already answer customer questions or attract relevant visitors. Build a URL-level content inventory before changing navigation, templates or page addresses.
Export the real website before drawing new screens
Create a list of current URLs using the CMS, XML sitemap, analytics and crawl information where available. Record each page title, topic, organic traffic, enquiries, backlinks and owner. A redesign that starts from only the main navigation often overlooks useful articles and service pages.
Classify pages using evidence
Keep pages that serve a clear customer need and remain accurate. Improve pages that have potential but lack detail. Merge overlapping pages when a single stronger page answers the same intent. Remove obsolete pages only after considering their traffic, inbound links and replacement destination. For more detail on this related topic, see Website Migration Redirect Mapping Checklist.
A practical URL mapping example
Suppose /old-services/web-design/ becomes /website-design/. Record the old URL, new URL, content owner and redirect requirement in one row. If three old pages merge into a new service guide, each old URL should redirect to the closest relevant destination rather than automatically sending everything to the homepage.
Preserve conversion paths and measurement
Document existing forms, phone links, thank-you pages, analytics events and advertising landing pages. A visually successful redesign can still lose leads if these workflows break. Test forms and tracking on staging before launch. For more detail on this related topic, see How to Plan a Business Website Sitemap Before Development.

Audit the first weeks after launch
Check server responses, redirects, canonical URLs, XML sitemaps, indexing reports and high-value landing pages. Compare performance against a sensible pre-launch baseline, recognising that short-term fluctuations do not prove the redesign succeeded or failed.
How to apply this guide to your next project
Use a short acceptance checklist centred on a visitor reaching an important old URL through its retained page or intended redirect. Assign an owner to approve the information and another to confirm that the visitor action works after implementation.
Use a Content Inventory to Protect Valuable Pages
A redesign inventory records current URLs, useful content and performance signals. It helps identify which pages to retain, improve, consolidate or redirect without losing important information.
For each retired URL, document its best relevant destination and test the redirect after launch. Avoid redirecting every removed page to the homepage, especially when a closer replacement exists.
Review business-critical content with its owner
Confirm service claims, prices, credentials, forms and contact details with the responsible team. A page that looks polished but carries outdated information can create poor enquiries.
WebDesignKart can help implement the plan for a website redesign. Share existing URLs, traffic evidence, content ownership and keep, update or redirect decisions so the quotation can distinguish content work, development and launch checks.
Frequently Asked Questions
What should a redesign content inventory contain?
Record each current URL, its purpose, useful content, available performance evidence and proposed destination. Assign an owner to approve the content and verify important redirects before launch.
Can you explain a practical URL mapping example?
Suppose /old-services/web-design/ becomes /website-design/. Record the old URL, new URL, content owner and redirect requirement in one row. If three old pages merge into a new service guide, each old URL should redirect to the closest relevant destination rather than automatically sending everything to the homepage.
How do you preserve conversion paths and measurement?
Document existing forms, phone links, thank-you pages, analytics events and advertising landing pages. A visually successful redesign can still lose leads if these workflows break. Test forms and tracking on staging before launch.
How do you audit the first weeks after launch?
Check server responses, redirects, canonical URLs, XML sitemaps, indexing reports and high-value landing pages. Compare performance against a sensible pre-launch baseline, recognising that short-term fluctuations do not prove the redesign succeeded or failed.
What will the project proposal cover?
The proposal will define the pages and functionality needed for a visitor reaching an important old URL through its retained page or intended redirect, identify content responsibilities and separate any integration work from the standard website scope.
