Collect addresses from several existing sources
Use the main navigation, the content list in the publishing system and any existing sitemap as starting points. They may show different selections. An older page may remain reachable despite having no visible menu entry. An automated list may also contain technical addresses that are not independent content pages.
Initially record address, title and a short purpose for each page. “Information” is too broad as a purpose. “Explains preparation for an on-site appointment” helps later when deciding whether a page can be replaced or merged. Record language versions as connected entries when the site provides them.
Add ownership and dependencies
Assign each important content page a responsible person or role. They need not operate the publishing system themselves, but should be able to assess the information. A phone number can display correctly while directing people to the wrong team. “The page loads” is therefore insufficient for a content inventory.
Note linked downloads, forms and external services. A service page may attach an old PDF checklist that is easily missed during a text revision. Also record where visitors reach the page from: menus, other pages, printed materials or known external references. You need not find every unknown link on the internet, but should account for routes your organization has published.
Add a review status such as open, content checked or change proposed. Use a small set of clear values. If everyone invents their own status labels, the table becomes difficult to interpret. A date should refer to a review actually performed rather than being copied automatically into every row.
Separate the jobs within an overloaded page
An inventory may reveal that one page contains opening hours, service details, a past event date and a lengthy instruction. First mark these jobs separately without immediately creating new pages. Establish which information people need together and which material merely happened to end up in the same document. The relationship from the visitor’s perspective matters more than the existing page length.
Record dependencies that are easy to miss during reorganisation. Several texts may reference one download, while a form is embedded on only one inner page. Make those relationships visible in the inventory. When content moves, its entry points can then be updated deliberately instead of rediscovered only after somebody reports a broken journey.
Prioritize actual consequences. A page showing the wrong contact address needs attention sooner than a slightly wordy article. Separate factual corrections that can be made now from larger structural decisions. Discussion of a new navigation should not hold up a small correction that could already prevent a misdirected inquiry today. Give these two kinds of work different owners or deadlines where appropriate.
Turn the list into decisions
Compare pages serving similar purposes. Two pages are not duplicates merely because both mention the same service. One may provide an overview while another explains preparation. What matters is whether they answer different visitor questions or contain contradictory versions of the same information.
Mark a proposed action with a short reason: update, retain, merge or refer for a decision. A page should not be removed simply because it is rarely mentioned internally. Check its task and known references before planning a replacement destination or error response.
Keep the scope explicit
On a small site, every content page may be reviewed individually. With a larger collection, begin with important entry pages and frequently used journeys, while recording areas still untouched. A sample review must not later be described as a complete inventory.
Keep the table with the project and update it with changes actually implemented. An inventory accurate only before rebuilding loses value for the next handover. A final column can therefore contain the confirmed outcome: new address, unchanged page or unresolved content decision. This preserves the distinction between what was checked and what was merely planned.
