Title: Build index automatically
Last modified: June 24, 2020

---

# Build index automatically

 *  [patricia2019](https://wordpress.org/support/users/patricia2019/)
 * (@patricia2019)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/build-index-automatically/)
 * Hello,
 * We are adding content on this website constantly so we need the new content to
   be indexed but is not working until we build index manually. Is there a way to
   build the relvanssi index automatically?
 * Thanks
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fbuild-index-automatically%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  Plugin Author [Mikko Saari](https://wordpress.org/support/users/msaari/)
 * (@msaari)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/build-index-automatically/#post-13039902)
 * Relevanssi automatically indexes new posts whenever they are added. How are you
   adding the content? Are you importing the posts somehow? If you are, you need
   to modify the import process so that the posts are indexed when they are added.

Viewing 1 replies (of 1 total)

The topic ‘Build index automatically’ is closed to new replies.

 * ![](https://ps.w.org/relevanssi/assets/icon-256x256.png?rev=3529670)
 * [Relevanssi - A Better Search](https://wordpress.org/plugins/relevanssi/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/relevanssi/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/relevanssi/)
 * [Active Topics](https://wordpress.org/support/plugin/relevanssi/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/relevanssi/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/relevanssi/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Mikko Saari](https://wordpress.org/support/users/msaari/)
 * Last activity: [5 years, 11 months ago](https://wordpress.org/support/topic/build-index-automatically/#post-13039902)
 * Status: not resolved