> 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.&#x20;

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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
