Docs
← Back to site

Connecting Elasticsearch / Elastic Cloud

2 min readUpdated November 21, 2026

Elasticsearch is a full-text search engine with powerful relevance tuning. WP Super Docs works with self-hosted Elasticsearch, Elastic Cloud, and Elasticsearch-compatible services like OpenSearch or Bonsai. Like Algolia, connecting it takes over docs search entirely, ahead of SearchWP, Relevanssi, and Ivory Search.

Where to set it up#

Go to WP Super Docs → Settings → Integrations and click the Elasticsearch / Elastic Cloud card to expand it.

The Elasticsearch / Elastic Cloud card with endpoint URL, API key and index name.

Getting your credentials#

For Elastic Cloud: in Kibana, go to Stack Management → Security → API Keys → Create API key.

You’ll need:

  • Endpoint URL: your cluster’s URL, including the port if needed, with no trailing slash (for example https://my-cluster.es.io:9200).
  • API key: the Base64-encoded key Elastic gives you. Stored encoded, not in plain text, though still treat it as sensitive.
  • Index name: defaults to wpsd_docs if left blank. Unlike Algolia, you don’t need to create this index yourself first, it’s created automatically the first time a doc is indexed.

Saving vs. activating#

Same two-step pattern as Algolia:

  • Save: stores your credentials without switching search over. The badge shows “Configured.”
  • Save & use Elasticsearch: stores your credentials and switches docs search to Elasticsearch immediately. The badge shows “In use.”

Once active, a Stop using Elasticsearch button appears to revert back to whichever engine would otherwise be in charge.

Testing the connection#

Click Test connection to confirm your endpoint and API key work before switching search over to rely on it.

Indexing your docs#

Going forward, every publish, update, or delete keeps your Elasticsearch index in sync automatically, each doc is indexed individually as it changes, using the WordPress post ID as the document ID.

For your existing docs, click Re-index all docs (shown once Elasticsearch is active) to index everything already published. Unlike Algolia’s single batch request, Elasticsearch indexing sends one request per doc, so this can take noticeably longer on a large docs site. Stay on the page until it completes.

Internal-only docs and docs in a Draft version are never sent to Elasticsearch, since it can’t check who’s logged in. If a doc becomes internal after it was indexed, it’s removed from the index the next time it’s saved, or when you re-index.

Was this helpful?

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only