A redesign often focuses on what the new website needs. Existing content is therefore easily left until late in the process. Yet that is where earlier decisions, useful explanations and hidden dependencies reside. A page inventory reveals what is actually being moved. Start it before the new menu structure and schedule are fixed.
Make a list that goes beyond page titles
For each address, record the title, content type and main visitor question. Add a content owner and note when the information was last reviewed. Identify separately whether a page contains forms, downloads, external links or other features. Those often need more attention during a move than the text itself.
Do not judge quality solely by length or age. A short contact page may do exactly what is needed. A recent service page may still be vague. Assess whether the content is accurate, supports a clear task and sits in a logical place. Record missing evidence as an open issue instead of silently inventing it.
Choose a specific destination for each page
Use a small set of decisions: keep, rewrite, merge, archive or remove. When merging, identify the main page immediately. When removing a page, decide what visitors following an old link will see. That requires editorial judgement, rather than automatically redirecting every old address to the homepage.
In a fictional example, an installation company has separate pages for three old names for the same maintenance service. The inventory shows that they largely answer the same question. One current service page can become the main destination, with a short explanation of the familiar old name. The value lies in coherence, rather than moving as many pages as possible.
Use the inventory to plan the work
A list without owners quickly becomes a backlog. Divide the work between people who can assess the content and people who can edit it. They do not have to be the same person. Schedule the most demanding material first: technical explanations, complex services and pages requiring new photos or permission.
A website project becomes more predictable when you know how many pages need rewriting. Dependencies involving custom software also emerge early. Consider an application page that sends data to an existing system. A different design does not automatically mean the underlying processing can disappear.
Include the purpose of downloads in the inventory. A price list, manual and historical brochure call for different decisions. Note whether a document is shared independently and which page provides its context. This prevents a neatly completed text migration from leaving attachments without an owner, explanation or current destination.
Check beyond the visible menu
Go through older news posts, campaign pages, download links and links in emails too. Some important pages are absent from the main menu. Ask employees which addresses they regularly send to customers. Compare that list with the inventory and add missing routes.
Finish preparation with a joint review of the decisions. Show which content is moving, what is still missing and which old routes will get a new destination. Keep the inventory as a progress tracker during the build. Mark a page complete only when its content, design and links have been checked. The list then becomes a practical bridge between the existing website and the new version, rather than a one-off administrative exercise.