# Combine App and Workplace search

**URL:** <https://discuss.elastic.co/t/combine-app-and-workplace-search/254466>\
**Category:** Elastic Search\
**Created:** [November 5, 2020, 10:40pm UTC](https://discuss.elastic.co/t/combine-app-and-workplace-search/254466 "2020-11-05T22:40:29Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![icechunk\_k9](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/icechunk_k9/32/78506_2.png) [@icechunk\_k9](https://discuss.elastic.co/u/icechunk_k9)\
**Post date:** [November 5, 2020, 10:40pm UTC](https://discuss.elastic.co/t/combine-app-and-workplace-search/254466/1 "2020-11-05T22:40:29Z")

</div>

If we want to use workplace search with an application sources (Confluence) and then include content from our website (Wordpress) into a unified search. How can we do that? it seems like App search (Wordpress) and Workplace (Confluence) are two different applications.

---

<div class="post-metadata">

**Author:** ![ross.bell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ross.bell/32/77559_2.png) [@ross.bell](https://discuss.elastic.co/u/ross.bell)\
**Post date:** [November 6, 2020, 3:58pm UTC](https://discuss.elastic.co/t/combine-app-and-workplace-search/254466/2 "2020-11-06T15:58:35Z")

</div>

Hey icechunk\_k9,

App Search and Workplace Search are both part of _Enterprise_ Search at Elastic, but they're different experiences as you allude to. Just so I understand correctly: you want to use Workplace Search, and connect it to both Confluence and a Wordpress site you manage? There's no direct way to expose App Search data _within_ the Workplace Search experience. And Workplace Search does not currently have a Wordpress content source. I think you'd have to use Workplace Search's [Custom Sources](https://www.elastic.co/guide/en/workplace-search/current/workplace-search-custom-api-sources.html) to expose a Wordpress site's search results in the Workplace Search search experience. I'm not sure if using App Search would make any of this easier.

---

<div class="post-metadata">

**Author:** ![icechunk\_k9](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/icechunk_k9/32/78506_2.png) [@icechunk\_k9](https://discuss.elastic.co/u/icechunk_k9)\
**Post date:** [November 9, 2020, 1:40pm UTC](https://discuss.elastic.co/t/combine-app-and-workplace-search/254466/3 "2020-11-09T13:40:22Z")

</div>

Thanks Ross

Is there a plugin for Wordpress for App (or workplace) search? Seems that the plugin documented here works for Swiftype site search.

> **[Elastic Site Search: Wordpress Search Plugin](https://www.elastic.co/blog/elastic-site-search-wordpress-search-plugin)**
>
> Learn how you can replace the default Wordpress search experience with Elastic Site Search. It's a giant leap in just a few clicks.

And if that is correct, then the difference between Site search (swiftype) and app search is that swiftype has all the UI components, while app search (both document submission and search ui) has to be fully implemented with its API. Is that correct?

---

<div class="post-metadata">

**Author:** ![ross.bell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ross.bell/32/77559_2.png) [@ross.bell](https://discuss.elastic.co/u/ross.bell)\
**Post date:** [November 9, 2020, 2:50pm UTC](https://discuss.elastic.co/t/combine-app-and-workplace-search/254466/4 "2020-11-09T14:50:16Z")

</div>

I think the Wordpress plugin you're referring to solves for embedding App Search powered search within Wordpress, not the other way around as I think you're looking to do.

As for UI components, App Search has [Reference UI](https://www.elastic.co/guide/en/app-search/current/reference-ui-guide.html). And there's also a [Search UI](https://github.com/elastic/search-ui) React library.

---

<div class="post-metadata">

**Author:** ![icechunk\_k9](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/icechunk_k9/32/78506_2.png) [@icechunk\_k9](https://discuss.elastic.co/u/icechunk_k9)\
**Post date:** [November 9, 2020, 3:01pm UTC](https://discuss.elastic.co/t/combine-app-and-workplace-search/254466/5 "2020-11-09T15:01:12Z")

</div>

The plugin also submits content for indexing

---

<div class="post-metadata">

**Author:** ![ross.bell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ross.bell/32/77559_2.png) [@ross.bell](https://discuss.elastic.co/u/ross.bell)\
**Post date:** [November 9, 2020, 3:25pm UTC](https://discuss.elastic.co/t/combine-app-and-workplace-search/254466/6 "2020-11-09T15:25:46Z")

</div>

Ah, I see what you're saying. Right, that will get the data into App Search. However, App Search and Workplace Search are two different experiences and sets of data. I don't think getting Wordpress data into App Search will help at all with exposing Wordpress data in Workplace Search. You'll have to use the Custom Source api.

---

<div class="post-metadata">

**Author:** ![icechunk\_k9](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/icechunk_k9/32/78506_2.png) [@icechunk\_k9](https://discuss.elastic.co/u/icechunk_k9)\
**Post date:** [November 9, 2020, 10:02pm UTC](https://discuss.elastic.co/t/combine-app-and-workplace-search/254466/7 "2020-11-09T22:02:09Z")

</div>

Yes understood. I think the original use case was to index both confluence and Wordpress. So choices are

1. Use Workplace search and add a custom source for Wordpress
2. Use App search and just submit documents for both Wordpress and Confluence manually

The advantage of 2 seems to be the Reference UI and the advantage of 1 seems to be the built in connector for Confluence and the auto schema discovery. Did i get it right?

---

<div class="post-metadata">

**Author:** ![ross.bell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ross.bell/32/77559_2.png) [@ross.bell](https://discuss.elastic.co/u/ross.bell)\
**Post date:** [November 10, 2020, 3:03pm UTC](https://discuss.elastic.co/t/combine-app-and-workplace-search/254466/8 "2020-11-10T15:03:21Z")

</div>

Full disclosure, I'm on the Workplace Search team, but I would still advise option #1. If you want search for your organization's internal documents and data, that's what Workplace Search was purpose built for. And to be clear, it also comes with [a search interface](https://www.elastic.co/guide/en/workplace-search/current/searcher-manual-workplace-search.html). Yes, it means you'll have to handle piping Wordpress page data to Workplace Search, but the Confluence data will ingest out of the box in addition to many [other content sources](https://www.elastic.co/guide/en/workplace-search/current/workplace-search-content-sources.html) you might have.

If you go with option #2, you'll be building _a lot_ yourself.

---

<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:** [November 4, 2022, 8:17am UTC](https://discuss.elastic.co/t/combine-app-and-workplace-search/254466/9 "2022-11-04T08:17:04Z")

</div>


