# Best practices for internal corporate site search

**URL:** <https://discuss.elastic.co/t/best-practices-for-internal-corporate-site-search/325532>\
**Category:** Elasticsearch\
**Created:** [February 15, 2023, 4:18am UTC](https://discuss.elastic.co/t/best-practices-for-internal-corporate-site-search/325532 "2023-02-15T04:18:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Buntu\_Dev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/buntu_dev/32/117258_2.png) [@Buntu\_Dev](https://discuss.elastic.co/u/Buntu_Dev)\
**Post date:** [February 15, 2023, 4:18am UTC](https://discuss.elastic.co/t/best-practices-for-internal-corporate-site-search/325532/1 "2023-02-15T04:18:22Z")

</div>

I'm looking for best practices to tag the existing webpages which consist internal web apps and employee resources (internal forms, static content, policy documents) to help index into ES and make them available for site search.

Any pointers to any documentation around this would be helpful.

TIA!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 15, 2023, 9:44pm UTC](https://discuss.elastic.co/t/best-practices-for-internal-corporate-site-search/325532/2 "2023-02-15T21:44:48Z")

</div>

I don't believe there's best practises as such that we have published. Maybe someone else can give you some ideas though.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 15, 2023, 9:44pm UTC](https://discuss.elastic.co/t/best-practices-for-internal-corporate-site-search/325532/3 "2023-03-15T21:44:54Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.