On this page
A content inventory template helps you see which pages need attention before another publishing cycle adds to the archive. It turns scattered URLs, outdated product references, and unassigned articles into a list someone can review and maintain.
The downloadable sheet below uses a fictional planter store. It includes example page roles and proposed review tasks, with dates and performance observations left for your own evidence. The goal is a usable maintenance queue, not a spreadsheet that becomes another abandoned asset.
Download the content inventory template
Open the CSV in your spreadsheet tool, duplicate the sheet, and replace the three sample rows with real pages. Keep a copy of your first snapshot before editing the site. The template contains no measured traffic results or keyword opportunities; it is an inventory structure with illustrative entries.
URL,Page title,Page type,Reader task,Owner,Published date,Last reviewed,Product destinations,Evidence source,Performance window,Next action,Priority,Status /blogs/guides/planter-drainage,Planter drainage guide,Article,Understand drainage,Editor,,,Review current product links,Manufacturer specifications,,Verify stale links,High,Needs review /collections/indoor-planters,Indoor planters,Collection,Browse suitable products,Merchandising,,,Current collection,Product catalog,,Check category description,Medium,Needs review /blogs/guides/ceramic-vs-plastic,Ceramic vs plastic planters,Comparison,Compare materials,Editor,,,Relevant material collections,Verified product labels,,Review overlap with existing guide,Medium,Needs review
| Field group | What to record | Why it matters |
|---|---|---|
| Identity | Current URL, title, and page type | Know which live page the row describes |
| Purpose and responsibility | Reader task and editorial owner | Explain why the page exists and who reviews it |
| Accuracy | Evidence source and product destinations | Locate facts and recommendations that need checking |
| Maintenance | Dates, observation window, action, priority, status | Turn the review into accountable work |
Choose a scope the team can finish reviewing
Start with a defined collection of pages: the advice blog, one product category and its supporting articles, or another manageable section. Write down what you excluded. A partial inventory is useful when its boundaries are clear; it becomes misleading when the team assumes it represents the whole site.
Collect the current URLs from the publishing system, your sitemap, and a site crawl when available. Compare those lists instead of assuming any one export is complete. A page can exist in the CMS without being published, and an old link can describe a destination that no longer serves the original content.
- Use one row for each current page you intend to maintain.
- Record draft or unpublished status explicitly if those pages are in scope.
- Keep old-to-new URL mappings in a separate migration note when addresses change.
- Do not silently discard a URL just because its title resembles another page.
Describe the reader’s task before judging the page
A title is an identity field, not a complete explanation of purpose. ‘Indoor planters’ could be a collection, a buying guide, or a care article. Add a short reader task such as ‘browse available indoor planters’ or ‘understand how to check drainage before ordering.’ That sentence helps distinguish pages that share product words but serve different needs.
For the fictional store, the collection helps a shopper browse current products, while the drainage guide explains what to check. Those pages can support each other. Two guides offering the same explanation deserve a closer review, but the inventory should record the overlap before recommending a merge.
Use the keyword mapping template when assigning future search targets. The inventory describes what exists; the keyword map explains which page should answer a researched query. Linking those documents avoids planning a new article that duplicates an existing answer.
Add evidence and comparable observations
Open the live page before filling its accuracy fields. Record the current source for important product claims, the destinations of recommendations, and the last verified review date. A timestamp from the CMS tells you when a record changed; it does not prove someone checked every fact in the article.
If you add search metrics, record the report, dates, and filters with the numbers. Search Console’s Performance report can group observations by page and query. Compare like-for-like scopes and distinguish an article with declining history from a new page with little data.
Turn each finding into a specific next action
| Finding in the example store | Useful action | Completion evidence |
|---|---|---|
| A recommendation reaches a discontinued planter | Verify a suitable replacement or remove the recommendation | The sentence and live destination agree |
| Two material guides appear to answer the same question | Compare their reader tasks and observed queries | A documented keep, differentiate, or consolidate decision |
| A collection has no assigned maintainer | Assign a merchandising owner | An owner and next review are recorded |
Prioritize by the importance of the problem and the page’s role, rather than a traffic column alone. A misleading product claim may need attention even on a quiet article. Keep the action narrow enough that a reviewer can tell when it is finished.
Where performance has faded, use the content decay process to investigate before rewriting. Where pages overlap, run a keyword cannibalization check. These are follow-up investigations, not labels to apply automatically to every inventory row.
Update the inventory when the page changes
After an edit, confirm the live result and update the current URL, review date, action status, and evidence. Keep historical observations in dated notes or snapshots so the sheet does not erase the context needed for later comparisons. Name a person responsible for maintaining the inventory itself.
For a new article, add its record during the publication check. For a renamed Shopify article, attach the old-to-new mapping described in the URL structure guide. Maintenance becomes easier when it is part of publishing rather than a large cleanup months later.
Common questions
How is a content inventory different from a content audit?
The inventory records what exists and the facts you have collected about each page. An audit evaluates those facts and recommends actions. Keeping those roles distinct makes it easier to see whether a conclusion is supported.
Should the sheet include products and collections?
Include them when they are part of your stated scope, especially if articles depend on those destinations. Mark the page type so a shopping collection is not judged as though it were a tutorial.
Should I remove every low-traffic article?
No. Check its reader purpose, accuracy, support value, and evidence before deciding. Low observed search traffic alone does not establish that a page is redundant or harmful.
Sources & further reading
Platform details checked against these primary sources. Store examples in this guide are illustrative.
Research. Write. Review. Publish.



