Source: https://nishanth-fern-test.docs-staging.pageloop.ai/os/content-aggregation-best-practices

# Content Aggregation Best Practices

Expand the accordions for more details:

**De-clutter your Content Repository**

Keep your Content Repository up-to-date. Add relevant content and remove obsolete information regularly. This helps end users find relevant content each time they search for something in Self Help.

**Make Self Help content more relevant to your end users**

Tailor Self Help for your end users to get relevant content every time they open the widget.

Here are a few ways you can do that:

- Integrate specific folders and spaces of your Content Repository with Whatfix.
- Integrate multiple Repositories with Whatfix to make Self Help, a one-stop help space.
- Associate a tag to your Repository. Whatfix adds the tag to the entire content fetched from the Repository and also to the content added later. For more information, see [Add Repository Content to Self Help](/os/add-repository-content-to-self-help).

**Set up regular syncs**

Sync frequency is the time interval between which the Whatfix crawler indexes or updates your content. By default, the crawler fetches content from your repository once every 7 days. However, if you update your content more frequently, consider increasing the sync frequency to ensure the latest information is always reflected in Self Help. For more information, see [Change the Sync Frequency of a Repository Integration](/os/change-the-sync-frequency-of-a-repository-integration).

**Test the search experience regularly**

Run regular tests by entering common queries in [Explorer](/os/search-in-explorer) to evaluate the relevance and accuracy of the search results. It helps you identify gaps or outdated content that needs attention.

**Perform Push-to-Production regularly**

After syncing your content repository, you must [perform a push to production](/os/push-whatfix-contents-and-widgets-to-production) for content changes to appear in Self Help. Have a regular schedule for performing a push to production so that the most updated content is always available to users.
