When a website is about to be redesigned, teams often focus on the new home page, visual direction, or new features. A more basic question needs an answer first: which pages exist today, what job does each one do, and which ones no longer do the right job? Without a clear answer, even a well-written piece of copy can live on the wrong page, a current service can go missing, or the same topic can weaken itself in three different places. A content inventory helps you see site pages not merely as a list, but as jobs within a visitor’s decision journey.
This work is not only for major redesigns. It is useful when adding a service, when organic visibility is not improving as expected, when sales keeps explaining the same thing, or when the team cannot agree on which page to update next. The aim is not to produce more pages. It is to identify why each existing page should exist and what the most meaningful next action is. Our corporate web design approach builds page structure around brand messaging, visitor needs, and the next action.
What a content inventory is, and what it is not
A content inventory is more than copying URLs, titles, and publication dates into a spreadsheet. It records the purpose of each page, the visitor question it should answer, its state of freshness, its need for proof, and the next action it deserves. That lets a team say more than “this page is old.” It can say, “this page meets the right intent, but it lacks an example, a clear explanation of pricing, or a useful route forward.”
It is not a content calendar either. A calendar describes future production. An inventory shows what exists now, how pieces connect, and whether a gap represents a real decision problem. The strongest inventories do not treat page count as the success metric. They ask what the visitor came to resolve after a search result and whether the page actually resolves it.
Write down the decisions the website needs to make easier
Before opening the spreadsheet, list the decisions the website should support in short sentences. Is a prospective client trying to understand which service fits? Do they need to see examples from the team? Do they need to clarify scope before asking for a proposal? Is an existing customer looking for contact or support information? The same URL can mean different things to different people. That is why a page should be recorded not only by its name, but by the decision moment it carries.
A service page, for instance, does not need to explain everything to everyone. Its job is to make the scope clear for the right client, rule out the wrong expectation early, and prepare a useful next conversation. A project page does more than display a polished result. It should show how an approach worked for a particular problem. This distinction later determines which content should be retained and which deserves a new treatment.
Classify pages by four useful jobs
For a practical start, give every URL one or two of four jobs: discovery, evaluation, trust, and action. Discovery pages name a question or need. Evaluation pages explain options, scope, or method. Trust pages offer team, project, process, example, and proof. Action pages make it easier to contact, request a proposal, or take the next step. When a page has no clear job, its problem is rarely just copy length.
This classification also explains why two pages on a similar subject should remain distinct. A journal article can help a reader ask “where should I start?” A service page explains scope and fit for working together. Keeping that distinction matters for search intent. Our SEO service reviews content visibility alongside technical structure, search intent, and site architecture.
Create a small inventory card for every page
An overly detailed template makes an inventory harder to finish. For a first pass, seven fields are enough for every URL: page name, URL, primary job, target visitor question, last verification date, missing proof or information, and recommended next action. Use clear actions such as retain, update, merge, redirect, and remove. “We will look at it later” is not a decision.
The target visitor question is the most valuable field on this card. When you write “I need to understand quickly which service relates to my need” rather than just “Services page,” an information-architecture problem becomes visible. If the heading, examples, links, and CTA do not serve that question, you can correct the content decision before changing the design.
Find gaps in the journey, not in the page count
Once the inventory is complete, the first instinct may be to open new page titles. Look for breaks in the journey first. Can a visitor reach a service page but find no example? Is there a project page, but is it difficult to understand the decisions behind the result? Does the contact page leave out the context needed for a useful first conversation? These questions reveal more meaningful content needs than a keyword list alone.
They also expose pages that are too similar. When two articles answer the same question with only small differences in wording, it may be better to strengthen one and link to it from the other. Visual assets belong in the inventory too. For images that no longer support the job of the page, use our corporate website photography brief guide to decide what needs to be commissioned or replaced.
Prioritise with risk, visibility, and business value
Not every gap has the same urgency. Score three simple questions: how much does a visitor lose when this page is wrong, dated, or incomplete? How much visibility or traffic potential does it carry? Which conversation, enquiry, or trust signal does it support for the business? A contact journey with a high score may deserve priority even when traffic is low. A high-traffic page that already does its job can remain on a monitoring list.
This approach keeps a redesign from turning into an endless effort to revise every line of copy. Select no more than five priorities in the first round. Give each one an owner, the input it needs, and a review date. When the task is to create a recurring operating rhythm, our 90-day corporate website maintenance plan is a useful companion for small, sustainable review cycles.
Keep the inventory alive after publication
It is easy to create an inventory once and leave it in a folder. Its real value comes from returning to it when a service, project, campaign, season, or technical change appears. When a page changes, record its verification date, the reason for the change, and the signal that should be watched. Six months later, the team can see what decision was made and why, rather than reopening the same debate.
Start by marking the first 20 URLs with these seven fields. You will quickly see which page should be protected, which explanation should be strengthened, and which connection needs to be made. Fark Studio reviews content inventories alongside website architecture, SEO, and the commercial journey. Send us your current site map and we can identify the most useful first review.
