diff --git a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md
index 45755f78a..da1221ccd 100644
--- a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md
+++ b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md
@@ -146,20 +146,6 @@ The following features are planned for future support in all {{serverless-full}}
 * Clone index API
 * Traffic filtering and VPCs
 
-The following {{es-serverless}} project-specific features are planned for future support:
-
-* [Behavioral Analytics](../../../solutions/search/site-or-app/behavioral-analytics.md)
-* [Search Applications](../../../solutions/search/search-applications.md)
-* Managed web crawler
-
-    You can use the [self-managed web crawler](https://github.com/elastic/crawler) in the meantime.
-
-* Managed Search connectors
-
-    You can use [self-managed Search connectors](asciidocalypse://docs/elasticsearch/docs/reference/ingestion-tools/search-connectors/self-managed-connectors.md) in the meantime.
-
-
-
 ### Unplanned features [elasticsearch-differences-serverless-feature-unavailable]
 
 The following features are not available in {{es-serverless}} and are not planned for future support:
@@ -167,3 +153,5 @@ The following features are not available in {{es-serverless}} and are not planne
 * [Custom plugins and bundles](/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md)
 * [{{es}} for Apache Hadoop](asciidocalypse://docs/elasticsearch-hadoop/docs/reference/ingestion-tools/elasticsearch-hadoop/elasticsearch-for-apache-hadoop.md)
 * [Scripted metric aggregations](asciidocalypse://docs/elasticsearch/docs/reference/data-analysis/aggregations/search-aggregations-metrics-scripted-metric-aggregation.md)
+* Managed web crawler: You can use the [self-managed web crawler](https://github.com/elastic/crawler) instead.
+* Managed Search connectors: You can use [self-managed Search connectors](asciidocalypse://docs/elasticsearch/docs/reference/ingestion-tools/search-connectors/self-managed-connectors.md) instead.
\ No newline at end of file
diff --git a/raw-migrated-files/docs-content/serverless/elasticsearch-differences.md b/raw-migrated-files/docs-content/serverless/elasticsearch-differences.md
index 0c980451e..20480732c 100644
--- a/raw-migrated-files/docs-content/serverless/elasticsearch-differences.md
+++ b/raw-migrated-files/docs-content/serverless/elasticsearch-differences.md
@@ -142,20 +142,6 @@ The following features are planned for future support in all {{serverless-full}}
 * Clone index API
 * Traffic filtering and VPCs
 
-The following {{es-serverless}} project-specific features are planned for future support:
-
-* [Behavioral Analytics](../../../solutions/search/site-or-app/behavioral-analytics.md)
-* [Search Applications](../../../solutions/search/search-applications.md)
-* Managed web crawler
-
-    You can use the [self-managed web crawler](https://github.com/elastic/crawler) in the meantime.
-
-* Managed Search connectors
-
-    You can use [self-managed Search connectors](asciidocalypse://docs/elasticsearch/docs/reference/ingestion-tools/search-connectors/self-managed-connectors.md) in the meantime.
-
-
-
 ### Unplanned features [elasticsearch-differences-serverless-feature-unavailable]
 
 The following features are not available in {{es-serverless}} and are not planned for future support:
@@ -163,3 +149,5 @@ The following features are not available in {{es-serverless}} and are not planne
 * [Custom plugins and bundles](/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md)
 * [{{es}} for Apache Hadoop](asciidocalypse://docs/elasticsearch-hadoop/docs/reference/ingestion-tools/elasticsearch-hadoop/elasticsearch-for-apache-hadoop.md)
 * [Scripted metric aggregations](asciidocalypse://docs/elasticsearch/docs/reference/data-analysis/aggregations/search-aggregations-metrics-scripted-metric-aggregation.md)
+* Managed web crawler: You can use the [self-managed web crawler](https://github.com/elastic/crawler) instead.
+* Managed Search connectors: You can use [self-managed Search connectors](asciidocalypse://docs/elasticsearch/docs/reference/ingestion-tools/search-connectors/self-managed-connectors.md) instead.
diff --git a/solutions/search/site-or-app.md b/solutions/search/site-or-app.md
index 243cce8e7..4f6140fdd 100644
--- a/solutions/search/site-or-app.md
+++ b/solutions/search/site-or-app.md
@@ -11,5 +11,4 @@ The following tools are available to help you add search to your site or app:
 
 - Clients: Use programming language clients to integrate {{es}} with your application.
 - [Search UI](site-or-app/search-ui.md): Use the Search UI library to build a user interface for your search application.
-- [Behavioral analytics](site-or-app/behavioral-analytics.md): Use Behavioral Analytics to track user behavior and improve search relevance.
 - [Search Applications](search-applications.md): Use Search Applications to simplify the process of building search experiences, by leveraging [search templates](search-templates.md).
\ No newline at end of file
diff --git a/solutions/search/site-or-app/behavioral-analytics-api.md b/solutions/search/site-or-app/behavioral-analytics-api.md
deleted file mode 100644
index b19b11cff..000000000
--- a/solutions/search/site-or-app/behavioral-analytics-api.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-navigation_title: "API overview"
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/behavioral-analytics-api.html
-applies_to:
-  stack:
----
-
-
-
-# API overview [behavioral-analytics-api]
-
-
-This page outlines all the APIs available for behavioral analytics and links to their documentation.
-
-
-## Behavioral Analytics REST APIs [behavioral-analytics-api-es-rest] 
-
-Behavioral Analytics relies on a number of {{es}} APIs to manage analytics collections. Refer to the [API documentation](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-analytics) for the details.
-
-
-## Behavioral Analytics Clients [behavioral-analytics-api-clients] 
-
-Behavioral Analytics integrates onto your website using one of our JavaScript clients:
-
-* **Browser tracker** - integrated into your website using a `<script>` tag.
-
-    * View the [`README` in GitHub](https://github.com/elastic/behavioral-analytics-tracker/tree/main/packages/browser-tracker).
-
-* **Javascript Tracker** - integrated into your website using a JavaScript module.
-
-    * View the [`README` in GitHub](https://github.com/elastic/behavioral-analytics-tracker/tree/main/packages/javascript-tracker).
-
-
-
-## Search UI integration [behavioral-analytics-api-search-ui] 
-
-To simplify the integration of Behavioral Analytics into your website, we provide a Search UI integration. This integration automatically sends Behavioral Analytics events to your collection as your customer interacts with your search experience.
-
-Refer to the [Search UI analytics plugin documentation](https://docs.elastic.co/search-ui/api/core/plugins/analytics-plugin).
-
-
-## Searchkit integration [behavioral-analytics-api-searchkit] 
-
-Behavioral Analytics also integrates with [Searchkit](https://www.searchkit.co), an open source library for building UIs on top of {{es}}.
-
diff --git a/solutions/search/site-or-app/behavioral-analytics-cors.md b/solutions/search/site-or-app/behavioral-analytics-cors.md
deleted file mode 100644
index f0549c92e..000000000
--- a/solutions/search/site-or-app/behavioral-analytics-cors.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-navigation_title: "Set up CORs"
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/behavioral-analytics-cors.html
-applies_to:
-  stack:
-  serverless:
----
-
-
-
-# Set up CORs [behavioral-analytics-cors]
-
-
-Behavioral Analytics sends events directly to the {{es}} API. This means that the browser makes requests to the {{es}} API directly. {{es}} supports [Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), but this feature is disabled by default. Therefore the browser will block these requests.
-
-There are two workarounds for this:
-
-* [Enable CORS on {{es}}](#behavioral-analytics-cors-enable-cors-elasticsearch)
-* [Proxy the request through a server that supports CORS](#behavioral-analytics-cors-proxy-request)
-
-
-## Enable CORS on {{es}} [behavioral-analytics-cors-enable-cors-elasticsearch] 
-
-This is the simplest option. Enable CORS on {{es}} by adding the following to your `elasticsearch.yml` file:
-
-```yaml
-http.cors.allow-origin: "*" # Only use unrestricted value for local development
-# Use a specific origin value in production, like `http.cors.allow-origin: "https://<my-website-domain.example>"`
-http.cors.enabled: true
-http.cors.allow-credentials: true
-http.cors.allow-methods: OPTIONS, POST
-http.cors.allow-headers: X-Requested-With, X-Auth-Token, Content-Type, Content-Length, Authorization, Access-Control-Allow-Headers, Accept
-```
-
-On Elastic Cloud, you can do this by [editing your {{es}} user settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md#ec-add-user-settings).
-
-1. From your deployment menu, go to the **Edit** page.
-2. In the **{{es}}** section, select **Manage user settings and extensions**.
-3. Update the user settings with the configuration above.
-4. Select **Save changes**.
-
-
-## Proxy the request through a server that supports CORS [behavioral-analytics-cors-proxy-request] 
-
-If you are unable to enable CORS on {{es}}, you can proxy the request through a server that supports CORS. This is more complicated, but is a viable option.
-
diff --git a/solutions/search/site-or-app/behavioral-analytics-event-reference.md b/solutions/search/site-or-app/behavioral-analytics-event-reference.md
deleted file mode 100644
index 1a0d66b9c..000000000
--- a/solutions/search/site-or-app/behavioral-analytics-event-reference.md
+++ /dev/null
@@ -1,415 +0,0 @@
----
-navigation_title: "Events reference"
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/behavioral-analytics-event-reference.html
-applies_to:
-  stack:
-  serverless:
----
-
-
-
-# Events reference [behavioral-analytics-event-reference]
-
-
-Behavioral Analytics logs events using the [Elastic Common Schema^](asciidocalypse://docs/ecs/docs/reference/ecs/index.md), including a custom field set for analytics events. Refer to [examples](#behavioral-analytics-event-reference-examples) of the full data objects that are logged.
-
-
-## Fields overview [behavioral-analytics-event-reference-fields] 
-
-* [Common event fields](#behavioral-analytics-event-reference-common-fields)
-* [Search event fields](#behavioral-analytics-event-reference-search-fields)
-* [Search click event fields](#behavioral-analytics-event-reference-search_click-fields)
-* [Pageview event fields](#behavioral-analytics-event-reference-pageview-fields)
-
-
-## Common event fields [behavioral-analytics-event-reference-common-fields] 
-
-`@timestamp`
-:   Timestamp of the event.
-
-`event.action`
-:   The type of event. Possible values are `search`, `search_click`, and `pageview`.
-
-`event.source`
-:   The source of the event. Possible values are `client` and `server`.
-
-`session.id`
-:   A unique identifier for the session.
-
-`user.id`
-:   A unique identifier for the user.
-
-`_id`
-:   The document ID.
-
-`_index`
-:   The index name.
-
-`_score`
-:   The score of the document.
-
-
-## Search event fields [behavioral-analytics-event-reference-search-fields] 
-
-`search.filters`
-:   The filters applied to the search query.
-
-`search.query`
-:   The search query.
-
-`search.results.items.document.id`
-:   The ID of the document in the search results.
-
-`search.results.items.document.index`
-:   The index of the document in the search results.
-
-`search.results.items.page.url.domain`
-:   The URL domain of the page in the search results.
-
-`search.results.items.page.url.original`
-:   The original URL of the page in the search results.
-
-`search.results.items.page.url.path`
-:   The URL path of the page in the search results.
-
-`search.results.items.page.url.scheme`
-:   The URL scheme of the page in the search results.
-
-`search.results.total_results`
-:   The total number of results returned by the search query.
-
-`search.search_application`
-:   The search application used to perform the search query.
-
-`search.sort.name`
-:   The name of the sort applied to the search query.
-
-
-## Search click event fields [behavioral-analytics-event-reference-search_click-fields] 
-
-`document.id`
-:   The ID of the document that was clicked.
-
-`document.index`
-:   The index containing the document that was clicked.
-
-`page.url.domain`
-:   The URL domain of the page that was clicked.
-
-`page.url.original`
-:   The original URL of the page that was clicked.
-
-`page.url.path`
-:   The URL path of the page that was clicked.
-
-`page.url.scheme`
-:   The URL scheme of the page that was clicked.
-
-`search.filters`
-:   The filters applied to the search query.
-
-`search.query`
-:   The search query.
-
-`search.results.items.document.id`
-:   The ID of the document in the search results.
-
-`search.results.items.document.index`
-:   The index of the document in the search results.
-
-`search.results.items.page.url.domain`
-:   The URL domain of the page in the search results.
-
-`search.results.items.page.url.original`
-:   The original URL of the page in the search results.
-
-`search.results.items.page.url.path`
-:   The URL path of the page in the search results.
-
-`search.results.items.page.url.scheme`
-:   The URL scheme of the page in the search results.
-
-`search.results.total_results`
-:   The total number of results returned by the search query.
-
-`search.search_application`
-:   The search application used to perform the search query.
-
-`search.sort.name`
-:   The name of the sort applied to the search query.
-
-`session.location.country_iso_code`
-:   The ISO code of the country where the search click occurred.
-
-`session.location.country_name`
-:   The name of the country where the search click occurred.
-
-
-## Pageview event fields [behavioral-analytics-event-reference-pageview-fields] 
-
-`document.id`
-:   The ID of the document that was viewed.
-
-`document.index`
-:   The index containing the document that was viewed.
-
-`page.referrer.domain`
-:   The URL domain of the page that referred to the viewed page.
-
-`page.referrer.original`
-:   The original URL of the page that referred to the viewed page.
-
-`page.referrer.path`
-:   The path of the page that referred to the viewed page.
-
-`page.referrer.scheme`
-:   The URL scheme of the page that referred to the viewed page.
-
-`page.title`
-:   The title of the viewed page.
-
-`page.url.domain`
-:   The URL domain of the viewed page.
-
-`page.url.original`
-:   The original URL of the viewed page.
-
-`page.url.path`
-:   The URL path of the viewed page.
-
-`page.url.scheme`
-:   The URL scheme of the viewed page.
-
-`session.location.country_iso_code`
-:   The ISO code of the country where the pageview occurred.
-
-`session.location.country_name`
-:   The name of the country where the pageview occurred.
-
-
-## Examples [behavioral-analytics-event-reference-examples] 
-
-::::{dropdown} Expand to see a full example of a search event data object:
-```js
-{
-  "@timestamp": [
-    "2023-05-16T12:52:29.003Z"
-  ],
-  "event.action": [
-    "search"
-  ],
-  "event.source": [
-    "client"
-  ],
-  "search.filters": [
-    {
-      "color": [
-        "silver"
-      ],
-      "brand": [
-        "Robel, Klocko and Ziemann",
-        "McClure, Marks and Mertz"
-      ]
-    }
-  ],
-  "search.query": [
-    "transformation"
-  ],
-  "search.results.items.document.id": [
-    "045a164b-229e-40b5-ba66-b2ebabd2a251"
-  ],
-  "search.results.items.document.index": [
-    "products"
-  ],
-  "search.results.items.page.url.domain": [
-    "fancy-overcoat.org"
-  ],
-  "search.results.items.page.url.original": [
-    "http://fancy-overcoat.org/happy/pancakes/deals"
-  ],
-  "search.results.items.page.url.path": [
-    "/happy/pancakes/deals"
-  ],
-  "search.results.items.page.url.scheme": [
-    "http"
-  ],
-  "search.results.total_results": [
-    67
-  ],
-  "search.search_application": [
-    "search-ui"
-  ],
-  "search.sort.name": [
-    "relevance"
-  ],
-  "session.id": [
-    "2bc31b08-d443-4b7a-81ea-65edf3dd82e7"
-  ],
-  "user.id": [
-    "42704a4b-692b-4654-bb67-a65eb0c72f15"
-  ],
-  "_id": "y3IBBogBWHKTU-4a543S",
-  "_index": ".ds-behavioral_behavioral-analytics-event-website-2023.05.10-000001",
-  "_score": null
-}
-```
-
-::::
-
-
-::::{dropdown} Expand to see a full example of a searchclick event data object:
-```js
-{
-  "@timestamp": [
-    "2023-05-16T12:22:23.468Z"
-  ],
-  "document.id": [
-    "38cca784-109a-4ea0-a4e8-60c3be667ffd"
-  ],
-  "document.index": [
-    "products"
-  ],
-  "event.action": [
-    "search_click"
-  ],
-  "event.source": [
-    "client"
-  ],
-  "page.url.domain": [
-    "unfurnished-appartments"
-  ],
-  "page.url.original": [
-    "https://unfurnished-appartments/new/europe"
-  ],
-  "page.url.path": [
-    "/new/europe"
-  ],
-  "page.url.scheme": [
-    "https"
-  ],
-  "search.filters": [
-    {
-      "brand": [
-        "McClure, Marks and Mertz",
-        "Ondricka - Rath"
-      ]
-    }
-  ],
-  "search.query": [
-    "ferryboat"
-  ],
-  "search.results.items.document.id": [
-    "0c76967b-4915-446e-9b2c-b1bfb9e39e1e"
-  ],
-  "search.results.items.document.index": [
-    "products"
-  ],
-  "search.results.items.page.url.domain": [
-    "dependent-lecture.info"
-  ],
-  "search.results.items.page.url.original": [
-    "http://dependent-lecture.info/documents/additional/latest"
-  ],
-  "search.results.items.page.url.path": [
-    "/documents/additional/latest"
-  ],
-  "search.results.items.page.url.scheme": [
-    "http"
-  ],
-  "search.results.total_results": [
-    54
-  ],
-  "search.search_application": [
-    "search-ui"
-  ],
-  "search.sort.name": [
-    "relevance"
-  ],
-  "session.id": [
-    "9411fb93-8707-49a4-baab-cec4d6aef753"
-  ],
-  "session.location.country_iso_code": [
-    "GP"
-  ],
-  "session.location.country_name": [
-    "Guadeloupe"
-  ],
-  "user.id": [
-    "911d0c19-e713-4413-8f4c-c6c612bc37c4"
-  ],
-  "_id": "m8cBBogBG4-Ak0Iy7LME",
-  "_index": ".ds-behavioral_behavioral-analytics-event-website-2023.05.10-000001",
-  "_score": null
-}
-```
-
-::::
-
-
-::::{dropdown} Expand to see a full example of a pageview event data object:
-```js
-{
-  "@timestamp": [
-    "2023-05-16T12:52:51.309Z"
-  ],
-  "document.id": [
-    "c98ppfc8-3a04-4a20-888a-f87292b31181"
-  ],
-  "document.index": [
-    "products"
-  ],
-  "event.action": [
-    "page_view"
-  ],
-  "event.source": [
-    "client"
-  ],
-  "page.referrer.domain": [
-    "happy-pancakes.name"
-  ],
-  "page.referrer.original": [
-    "https://happy-pancakes.name/magnam"
-  ],
-  "page.referrer.path": [
-    "/magnam"
-  ],
-  "page.referrer.scheme": [
-    "https"
-  ],
-  "page.title": [
-    "Super fast delivery"
-  ],
-  "page.url.domain": [
-    "happy-staircase.net"
-  ],
-  "page.url.original": [
-    "http://happy-staircase.net/quam"
-  ],
-  "page.url.path": [
-    "/quam"
-  ],
-  "page.url.scheme": [
-    "http"
-  ],
-  "session.id": [
-    "2bc31b08-d443-4b7a-81ea-65edf3dd82e7"
-  ],
-  "session.location.country_iso_code": [
-    "SN"
-  ],
-  "session.location.country_name": [
-    "Senegal"
-  ],
-  "user.id": [
-    "42704a4b-692b-4654-bb67-a65eb0c72f15"
-  ],
-  "_id": "zHIBBogBWHKTU-4a543S",
-  "_index": ".ds-behavioral_behavioral-analytics-event-website-2023.05.10-000001",
-  "_score": null
-}
-```
-
-::::
-
-
diff --git a/solutions/search/site-or-app/behavioral-analytics-event.md b/solutions/search/site-or-app/behavioral-analytics-event.md
deleted file mode 100644
index e1faf5583..000000000
--- a/solutions/search/site-or-app/behavioral-analytics-event.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-navigation_title: "View events"
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/behavioral-analytics-event.html
-applies_to:
-  stack:
----
-
-
-
-# View events [behavioral-analytics-event]
-
-
-::::{tip}
-Refer to [Events reference](behavioral-analytics-event-reference.md) for a complete list of the fields logged by events.
-
-::::
-
-
-Once you’ve started **tracking events** using the [Behavioral Analytics Tracker](https://github.com/elastic/behavioral-analytics-tracker/tree/main#readme), you can view them on a pre-built dashboard in {{kib}}.
-
-
-## View events in the Overview dashboard [behavioral-analytics-event-send-view-events-overview]
-
-The **Overview** dashboard provides a quick overview of the following:
-
-* Searches
-* No results
-* Clicks
-* Sessions
-
-This allows you to quickly check both absolute numbers and trends (tracked in percentage changes) about these events. Find this dashboard under **Search > Behavioral Analytics>** *your-collection* **> Overview**.
-
-The following screenshot shows an example **Overview** dashboard:
-
-:::{image} ../../../images/elasticsearch-reference-analytics-overview-dashboard.png
-:alt: Analytics Overview dashboard showing the number of searches
-:class: screenshot
-:::
-
-
-## View events in the Explorer dashboard [behavioral-analytics-event-send-view-events-dashboard]
-
-The **Explorer** dashboard provides a more detailed view of your events. Find this dashboard under **Search > Behavioral Analytics>** *your-collection* **> Explorer**.
-
-Here you can find and search over the following:
-
-* Search terms
-* Top clicked results
-* No results
-* Locations
-* Referrers
-
-You can also easily sort in ascending or descending order by clicking on the header arrows.
-
-The following screenshot shows the **Locations** tab of an **Explorer** dashboard, with a list of top locations in descending order:
-
-:::{image} ../../../images/elasticsearch-reference-analytics-explorer-dashboard.png
-:alt: Explorer dashboard showing the top locations in descending order
-:class: screenshot
-:::
-
-
-## Discover and Lens [behavioral-analytics-event-send-view-events-discover]
-
-For more detailed analysis, you can view events in the Kibana [Discover^](../../../explore-analyze/discover.md) app. The Behavioral Analytics UI will guide you here from the **Explorer** dashboard. You can dig into the details using Discover and then generate visualizations using [Lens^](../../../explore-analyze/visualize/lens.md).
-
-Discover works with [data views^](../../../explore-analyze/find-and-organize/data-views.md). You’ll find a data view automatically created for your collection, named `behavioral_analytics.events-<your-collection>`. This data view will be pre-selected in the data view dropdown menu. Use this menu to switch between data views for different collections.
-
-The following screenshot shows you where to find the data view dropdown menu in Discover:
-
-:::{image} ../../../images/elasticsearch-reference-discover-data-view-analytics.png
-:alt: Analytics Discover app showing the data view dropdown menu
-:class: screenshot
-:::
-
-Discover has a lot of options, but here’s a quick overview of how to get started:
-
-* Filter your data by searching for terms, such as `search`, `page_view`, and `search_click`. You’ll see a time series of hits that match your search.
-* Search for "event" in the field name search bar. For example:
-
-    * Select `event.action`. You’ll find a list of all the events you’ve sent and their frequency distribution.
-
-* Search for `search.query` to find all search queries.
-* Select **Visualize** to create a Lens visualization.
-
-The following screenshot shows a Lens visualization of an `event.action` distribution:
-
-:::{image} ../../../images/elasticsearch-reference-discover-lens-analytics.png
-:alt: Analytics Discover app showing a Lens visualization of an event action distribution
-:class: screenshot
-:::
-
-
-### Learn more [behavioral-analytics-event-send-view-events-learn-more]
-
-Read the [Discover documentation^](../../../explore-analyze/discover.md).
-
-Read the [Lens documentation^](../../../explore-analyze/visualize/lens.md).
-
diff --git a/solutions/search/site-or-app/behavioral-analytics-start.md b/solutions/search/site-or-app/behavioral-analytics-start.md
deleted file mode 100644
index 1c6fe6eb7..000000000
--- a/solutions/search/site-or-app/behavioral-analytics-start.md
+++ /dev/null
@@ -1,182 +0,0 @@
----
-navigation_title: "Get started"
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/behavioral-analytics-start.html
-applies_to:
-  stack:
----
-
-
-
-# Get started [behavioral-analytics-start]
-
-
-You can manage your analytics in the {{kib}} UI. Go to **Search > Behavioral Analytics** to get started.
-
-Using behavioral analytics is a three-step process:
-
-1. **Create a [collection](#behavioral-analytics-start-collections)**. A collection is a logical grouping of your analytics events.
-2. **Set up** a [UI integration](#behavioral-analytics-start-ui-integration).
-3. **Analyze** the data collected.
-
-
-## Collections [behavioral-analytics-start-collections] 
-
-::::{note} 
-This guide focuses on using the Behavioral Analytics UI in {{kib}} to create and manage collections. You can also use the [Behavioral Analytics APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-analytics) to create, list, and delete collections, as well as post events to a collection.
-
-::::
-
-
-A collection is a set of analytics events.
-
-The first step in setting up behavioral analytics is to create a collection. To do this in the {{kib}} UI:
-
-1. Go to **Search > Behavioral Analytics**.
-2. Select **Create collection**.
-3. Name your collection carefully, because you can’t change it later.
-4. Select **Create**.
-
-When you create a collection we automatically create a [data view^](../../../explore-analyze/find-and-organize/data-views.md) for the collection. This allows {{kib}} to access your analytics data stored in {{es}}.
-
-This means that once you integrate analytics into your application or website, you can immediately use [Discover^](../../../explore-analyze/discover.md) to view events, set filters, and create visualizations using [Lens^](../../../explore-analyze/visualize/lens.md).
-
-Once you’ve created a collection, you need to complete your UI integration.
-
-
-## UI integration [behavioral-analytics-start-ui-integration] 
-
-::::{note} 
-Detailed integration instructions are provided in the {{kib}} UI. Find these in the **Integrate** tab under **Search > Behavioral Analytics >** *<your-collection>*.
-
-::::
-
-
-Choose *one* of the following integration options:
-
-* [Option 1: Browser tracker](#behavioral-analytics-start-ui-integration-js-embed)
-* [Option 2: JavaScript tracker](#behavioral-analytics-start-ui-integration-js-client)
-
-Once embedded, users of the [Search UI](https://docs.elastic.co/search-ui/getting-started) JavaScript library can use the following integration for simplified event shipping:
-
-* [Search UI integration](#behavioral-analytics-start-ui-integration-search-ui)
-
-
-### Option 1: Browser tracker [behavioral-analytics-start-ui-integration-js-embed] 
-
-Add a JavaScript snippet to your website or application source files, using the [Browser tracker](https://github.com/elastic/behavioral-analytics-tracker/blob/main/packages/browser-tracker/README.md).
-
-This approach is best for web browsers. Node apps and Search UI users shouldn’t choose this option.
-
-Instructions for getting started are available in the {{kib}} UI.
-
-**Follow these steps**:
-
-1. Embed the behavioral analytics JavaScript snippet on every page of the website or application you’d like to track.
-
-    ```js
-    <script src="https://cdn.jsdelivr.net/npm/@elastic/behavioral-analytics-browser-tracker@2"></script>
-    ```
-
-2. Initialize the client to start tracking events. For example:
-
-    ```js
-    <script type="text/javascript">
-    window.elasticAnalytics.createTracker({
-      endpoint: "https://77561m8ivn1olhs5fczpls0xa85bueqt.us-west2.gcp.elastic-cloud.com:443",
-      collectionName: "my-collection",
-      apiKey: "########",
-      // Optional: sampling rate percentage: 0-1, 0 = no events, 1 = all events
-      // sampling: 1,
-    });
-    </script>
-    ```
-
-3. Track search events, like result clicks and searches, by using the `trackSearch` or `trackSearchClick` methods.
-
-
-### Option 2: JavaScript tracker [behavioral-analytics-start-ui-integration-js-client] 
-
-The JavaScript client is available as an [NPM package](https://www.npmjs.com/package/@elastic/behavioral-analytics-javascript-tracker). We recommend this approach if your application bundles JavaScript from NPM packages. This is a good option for Node apps (server-side apps). Analytics will be bundled with your app.
-
-This allows the browser to optimize the JavaScript download.
-
-Instructions for getting started are also available in the {{kib}} UI.
-
-**Follow these steps** to get started:
-
-1. **Download** the behavioral analytics JavaScript tracker client from NPM:
-
-    `npm install @elastic/behavioral-analytics-javascript-tracker`
-
-2. **Import** the client into your application:
-
-    ```js
-    import {
-      createTracker,
-      trackPageView,
-      trackSearch,
-      trackSearchClick
-    } from "@elastic/behavioral-analytics-javascript-tracker";
-    ```
-
-3. **Initialize** the client to start tracking events:
-
-    Use the `createTracker` method to initialize the tracker with your configuration. You can then use the tracker to send events to Behavioral Analytics.
-
-    Example initialization:
-
-    ```js
-    createTracker({
-      endpoint: "https://77561m8ivn1olhs5fczpls0xa85bueqt.us-west2.gcp.elastic-cloud.com:443",
-      collectionName: "my-collection",
-      apiKey: "<api-key>"
-    });
-    ```
-
-4. **Dispatch** Pageview and search behavior events.
-
-    Once you have called `createTracker`, you can use the tracker methods such as `trackPageView` to send events to Behavioral Analytics.
-
-
-Once integrated, you should be able to see page view events within the **Explorer** tab.
-
-::::{tip} 
-**Session-based sampling**
-
-You don’t always want all sessions to be sent to your Elastic cluster. You can introduce session-based sampling by adding a sampling parameter to the `createTracker` method.
-
-If sampling is set to 1 (default), all sessions will send events. If sampling is set to 0, no sessions will send events.
-
-Here’s an example:
-
-```js
-createTracker({
-  // ... tracker settings
-  sampling: 0.3, // 30% of sessions will send events to the server
-});
-```
-
-::::
-
-
-
-## Search UI integration [behavioral-analytics-start-ui-integration-search-ui] 
-
-[Search UI](https://docs.elastic.co/search-ui) is a JavaScript library for building search experiences. Use the [Search UI analytics plugin](https://www.npmjs.com/package/@elastic/search-ui-analytics-plugin) available on NPM to integrate behavioral analytics with Search UI.
-
-This integration enables you to dispatch events from Search UI to the behavioral analytics client. The advantage of this integration is that you don’t need to set up custom events. Events fired by Search UI are dispatched automatically.
-
-To use this integration, follow these steps:
-
-1. Embed Behavioral Analytics into your site using [Option 1: Browser tracker](#behavioral-analytics-start-ui-integration-js-embed) **or** the [Option 2: JavaScript tracker](#behavioral-analytics-start-ui-integration-js-client).
-2. Install the [`@elastic/search-ui-analytics-plugin`](https://www.npmjs.com/package/@elastic/search-ui-analytics-plugin) by importing it into your app.
-3. Add the plugin to your Search UI configuration.
-
-See the [Search UI analytics plugin documentation](https://docs.elastic.co/search-ui/api/core/plugins/analytics-plugin) for details.
-
-
-## Next steps [behavioral-analytics-start-next-steps] 
-
-* Refer to the [analytics API reference](behavioral-analytics-api.md).
-
diff --git a/solutions/search/site-or-app/behavioral-analytics.md b/solutions/search/site-or-app/behavioral-analytics.md
deleted file mode 100644
index a84d39ea4..000000000
--- a/solutions/search/site-or-app/behavioral-analytics.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-mapped_pages:
-  - https://www.elastic.co/guide/en/elasticsearch/reference/current/behavioral-analytics-overview.html
-applies_to:
-  stack:
----
-
-# Behavioral analytics [behavioral-analytics-overview]
-
-Behavioral Analytics is an analytics event collection platform. Use these tools to analyze your users' searching and clicking behavior. Leverage this information to improve the relevance of your search results and identify gaps in your content.
-
-[Get started](behavioral-analytics-start.md) by embedding one of our JavaScript clients on your website or application and instrumenting the user actions you want to track. For example, you can track when a user searches, when they click on a search result, or when a user visits a particular page on your website.
-
-Data and analytics are stored in {{es}} indices, for advanced analysis and visualization.
-
-Even if you don’t use Elastic for search, you can use these tools to collect analytics from your application/website.
-
-
-## Availability and prerequisites [behavioral-analytics-overview-prerequisites] 
-
-::::{note} 
-Behavioral Analytics is a **beta feature**. Beta features are subject to change and are not covered by the support SLA of general release (GA) features. Elastic plans to promote this feature to GA in a future release.
-
-::::
-
-
-::::{dropdown} Expand to learn about version history
-* Behavioral Analytics was introduced in Elastic **8.7.0** to the Enterprise Search service.
-* There was a breaking schema change in **8.8.0**. (See [Migrating from 8.7 to 8.8](https://www.elastic.co/guide/en/enterprise-search/current/analytics-migration.html) in the Search documentation if you’re upgrading from 8.7 to 8.8.)
-* The feature was moved to Elasticsearch in **8.10**, meaning the Enterprise Search service is no longer required as of 8.10.
-::::
-
-
-Analytics are available to all Elastic Cloud users.
-
-Analytics are also available to **self-managed** deployments that satisfy subscription requirements. View the requirements for this feature under the **Elastic Search** section of the [Elastic Stack subscriptions](https://www.elastic.co/subscriptions) page.
-
-Your Elastic deployment must include the {{es}} and {{kib}}services.
-
-
-## Documentation [behavioral-analytics-overview-docs] 
-
-The following documentation is available in the {{es}} docs:
-
-* [Get started](behavioral-analytics-start.md)
-* [API overview](behavioral-analytics-api.md)
-* [Set up CORs](behavioral-analytics-cors.md)
-* [View events](behavioral-analytics-event.md)
-* [Events reference](behavioral-analytics-event-reference.md)
-
-Additional documentation is available in the following places:
-
-* The [Behavioral Analytics Tracker Mono Repo](https://github.com/elastic/behavioral-analytics-tracker/tree/main#readme) contains the source code for the Behavioral Analytics Tracker, which can be embedded using either the JavaScript or Browser trackers:
-
-    * Read the [JavaScript tracker README](https://github.com/elastic/behavioral-analytics-tracker/blob/main/packages/javascript-tracker/README.md).
-    * Read the [Browser tracker README](https://github.com/elastic/behavioral-analytics-tracker/blob/main/packages/browser-tracker/README.md).
-
-* The Search UI documentation contains information about the [Search UI Analytics Plugin](https://docs.elastic.co/search-ui/api/core/plugins/analytics-plugin).
-* Behavioral Analytics uses a number of [APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-analytics) to manage analytics collections.
-
-::::{admonition} GDPR compliance
-:class: note
-
-Users may be concerned about the privacy implications of analytics data collection. Behavioral Analytics is fully GDPR compliant, because no personal data are collected.
-
-To integrate the behavioral analytics client, session data are stored in two tokens:
-
-* **User Token**. A unique identifier for the user. Stored under `EA_UID` cookie. Default time length is 24 hours from the first time the user visits the site.
-* **Session Token**. A unique identifier for the session. Stored under `EA_SID` cookie. Time length is 30 minutes from the last time the user visits the site.
-
-These tokens enable the client to identify a user across sessions. They do not collect sensitive information, such as IP addresses or location data, or any other personal data.
-
-::::
-
-
-
-
-
-
-
diff --git a/solutions/toc.yml b/solutions/toc.yml
index b377e5dba..6b921f5a4 100644
--- a/solutions/toc.yml
+++ b/solutions/toc.yml
@@ -660,13 +660,6 @@ toc:
         children:
           - file: search/site-or-app/clients.md
           - file: search/site-or-app/search-ui.md
-          - file: search/site-or-app/behavioral-analytics.md
-            children:
-              - file: search/site-or-app/behavioral-analytics-start.md
-              - file: search/site-or-app/behavioral-analytics-cors.md
-              - file: search/site-or-app/behavioral-analytics-event.md
-              - file: search/site-or-app/behavioral-analytics-event-reference.md
-              - file: search/site-or-app/behavioral-analytics-api.md
           - file: search/search-applications.md
             children:
               - file: search/search-applications/search-application-api.md