Skip to main content
Last Reviewed: April 03, 2023

Pantheon Search (formerly Pantheon Solr)

Detailed information on using Pantheon Search with your Pantheon Drupal or WordPress site.

Pantheon Search (formerly Pantheon Solr) is a system for indexing and searching site content. Pantheon provides Solr-based search as a service for most plans including Sandbox, on all environments. No permission or action is required from Pantheon to use Pantheon Search.

Currently, Pantheon provides Apache Solr v3.6 and v8.0 as a service for all plans except the Basic plan.

Important Note

Pantheon Search derives from Solr and can perform full-text content searching in a single language.

If your search needs include geospatial search, emojis, or multilingual search, consider OpenSolr or another alternative search.

Pantheon Search supports Search API Solr 8.x-1.x, which is currently unsupported by Solr. Search API Solr 8.x-1.x should continue to work as long as the Search API Pantheon module is also being used, following the installation directions below.

All plans except for a Basic plan can use Pantheon Search. Pantheon Search is available to Sandbox site plans for developmental purposes, but Pantheon Search will not be available going live on a Basic plan.

PlansPantheon Search Support

Using Pantheon Search with WordPress or Drupal

For installation instructions and additional details, refer to Enabling Solr for WordPress or Enabling Solr with Drupal.

Known Limitations of Pantheon's Search Service

  • Solr can only be enabled by Admin users or Users in Charge.

  • Anything that takes more than 5 seconds to send to the Solr server to be indexed will timeout, which will block indexing. For example, Drupal nodes with large document attached. In these cases, the developer must work with the content or code to exempt the nodes and/or files from being indexed. Check Index and Batch sizes for possible scenarios or more time-outs.

  • If you have a very large number of facets, the URLs generated by CURL may exceed length limits (may be fixed in search_api).

  • Partial search, stopwords.txt, synonyms.txt, elevate.xml, etc. are features not supported in Solr version 3 at Pantheon.

  • Drupal 7: When a Solr query is over 4000 characters and the method is changed from GET to POST, queries may fail. Known workarounds are to patch the module and set apachesolr_search_post_threshold to a higher limit or to keep queries shorter.

  • The search terms in and or are ignored, regardless of casing.

  • Re-indexing may be required following any platform issue or event (server outage, service degradation). Check the status page for current and past platform events.

  • The Solr index is not included in Pantheon's Multizone Failover, and would need to be recreated in the event of failover.

  • Pantheon’s Solr offering is limited to a single core index. Although it is possible to host multiple indexes in a single core, Pantheon may not be able to provide support for troubleshooting issues related to multiple indexes in a single core.

Alternatives to Pantheon's Search Service

While Pantheon provides a stable, reliable, and basic Solr service, your individual site needs may require something more robust and customizable. In those cases, a dedicated hosted Solr service may be a better solution for your needs. Given that Solr can tolerate higher latency (one query per request vs hundreds of database queries), Solr servers do not need to be in the same data center to provide fast and responsive results.

Some customers have reported success using external Solr service providers for their Solr indexing:

Apache Solr Vocabulary


Allows certain parts of indexed items to influence the importance of search results. The higher the bias, the greater the influence; the range is 0.1 to 21.0.


A core is a separate configuration and index using a single Solr instance. A core is created when the schema is posted. For more information, see


A document is similar to a database row, containing the contents of what is to be searched and whatever fields are associated with it, like title.


Search facets allow search results to be filtered; examples include seeing a list of potential filters and the count of matches for each filter on the left, like Amazon product searches.


Structure containing extracted keywords from a document for rapid search and retrieval, similar to a database table.


Calculated relevance of matches influenced by bias, represented as a float.


Contains details about the fields that documents can contain, and how those fields are handled when adding documents to the index or querying those fields. Must be posted using the pantheon_apachesolr module before indexing and searching will work. For more information, see

Considerations for Solr Search on Pantheon

Check Index and Batch Sizes

Are you only indexing only 50 items at a time and wondering why hundreds of new content nodes generated in the last hour aren't being indexed? Numbers are important here. If you need to increase the number of items being indexed with each Solr indexing run, feel free to do so. However, don't get ridiculous here: setting 1000 items to be indexed per run could cause a page timeout. If a specific request times out, that could be because it's trying to POST too much data at once; try reducing the number of items being indexed per batch and see if that allows the items to be indexed.

Apache Spatial Search on Pantheon

Pantheon's Solr configuration does not support geospatial indexing and searching and there are currently no plans to add it. As an alternative, there are several external Solr service providers that do support spatial searching. Pantheon doesn’t do any blocking/filtering, so you’re welcome to use an externally hosted Solr index – and in a case where you’re looking for a more complex configuration, that might be optimal.

Specify Query Parsers to Allow Fields

Pantheon's Solr configuration uses the DisMax query mode by default. This parser is great for user-entered text because it's forgiving and similar to Google's parser, but it does not recognize field:value syntax.

The solution is to specify the parser in the request. Both the Lucene and eDisMax parsers support the required field:value syntax. You can add them to a query by adding &defType=lucene or &defType=edismax to the end. For example:


For details on supported query parsers, see Query Syntax and Parsing and Common Query Parameters.

Supported Search Components

The following Apache Solr search components are supported:

  • SpellCheckComponent
  • TermVectorComponent
  • TermsComponent

More Resources