> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/discovery/content-inventory.md).

# Content Inventory

{% hint style="info" %}
AKA Content Inventory & Auditing
{% endhint %}

Content inventory and auditing is the process of systematically collecting and evaluating all the content on a website or digital platform. It involves creating a detailed list of every piece of content and assessing its quality, relevance, and effectiveness. 

This helps identify outdated, redundant, or low-performing content that may need improvement or removal. Content inventory and auditing enables organisations to gain a clear understanding of their content assets, make informed decisions about content strategy, improve user experience, and ensure that the content aligns with business goals and user needs.

#### Further Reading

{% embed url="<https://www.nngroup.com/articles/content-audits/>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=Ni5jAX6IGVw>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.designreference.xyz/ux-methods/discovery/content-inventory.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.