Craft Scout provides a simple solution for adding full-text search to your entries. Scout will automatically keep your search indexes in sync with your entries.
Clone or download
Latest commit 6b8f81f Dec 6, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
resources/img Init Dec 11, 2017
src Apply fixes from StyleCI Dec 6, 2018
.craftplugin Init Dec 11, 2017
.gitignore Init Dec 11, 2017 1.1.0 Dec 3, 2018 Init Dec 11, 2017 1.1.0 Dec 3, 2018
composer.json 1.1.0 Dec 3, 2018
composer.lock Added splitElementIndex option based on long document suggestions fro… Apr 12, 2018


Latest Version Quality Score StyleCI Total Downloads

Scout plugin for Craft CMS 3

Craft Scout provides a simple solution for adding full-text search to your entries. Scout will automatically keep your search indexes in sync with your entries.

Support Open Source. Buy beer.

This plugin is licensed under a MIT license, which means that it's completely free open source software, and you can use it for whatever and however you wish. If you're using it and want to support the development, buy me a beer over at Beerpay!



This plugin requires Craft CMS 3.0.0-RC1 or later.


To install the plugin, follow these instructions.

  1. Open your terminal and go to your Craft project:

     cd /path/to/project
  2. Then tell Composer to load the plugin:

     composer require rias/craft-scout
  3. In the Control Panel, go to Settings → Plugins and click the “Install” button for Scout.


To define your indices, create a new scout.php file within your config folder. This file should return an array with 3 keys, an application_id, your admin_api_key (which are both found in your Algolia account) and a mappings key, which defines your site's mappings.

Within the mappings array, each index is represented by a configuration array.


return [
    "sync" => true,
    "connect_timeout" => 1,
    "application_id" => "algolia",
    "admin_api_key" => "algolia",
    "mappings" => [
            'indexName' => 'blog',
            'indexSettings' => [
                'settings' => [
                    'attributesForFaceting' => ['blogCategory'],
                'forwardToReplicas' => 'true',
            'elementType' => \craft\elements\Entry::class,
            'criteria' => [
                'section' => 'blog'
            'transformer' => function (craft\base\Element $element) {
                return $element->toArray();

The Sync option

This config variable determines if Scout should keep your entries in sync automatically. Setting this to false disables all of Scout's event listeners.

Connect timeout

This config variable determines the connect timeout in seconds to Algolia servers. You should only change this if you have a slow server. Standard is 1 second.

Mapping configuration settings


The index name in Algolia, if you don't already have an index created, Scout will create one for you.


Allows you to have your index settings in config. They need to be manually updated when changed with ./craft scout/settings.update.

Below are the default settings Algolia provides

'indexSettings' => [
    'forwardToReplicas' => 'true',
    'settings' => [
        'minWordSizefor1Typo' => 4
        'minWordSizefor2Typos' => 8
        'hitsPerPage' => 20
        'maxValuesPerFacet' => 100
        'version' => 2
        'attributesToIndex' => null
        'numericAttributesToIndex' => null
        'attributesToRetrieve' => null
        'unretrievableAttributes' => null
        'optionalWords' => null
        'attributesForFaceting' => []
        'attributesToSnippet' => null
        'attributesToHighlight' => null
        'paginationLimitedTo' => 1000
        'attributeForDistinct' => null
        'exactOnSingleWordQuery' => 'attribute'
        'ranking' => [
            0 => 'typo'
            1 => 'geo'
            2 => 'words'
            3 => 'filters'
            4 => 'proximity'
            5 => 'attribute'
            6 => 'exact'
            7 => 'custom'
        'customRanking' => null
        'separatorsToIndex' => ''
        'removeWordsIfNoResults' => 'none'
        'queryType' => 'prefixLast'
        'highlightPreTag' => '<em>'
        'highlightPostTag' => '</em>'
        'snippetEllipsisText' => ''
        'alternativesAsExact' => [
            0 => 'ignorePlurals'
            1 => 'singleWordSynonym'


The element type that this index contains, most of the time this will be craft\elements\Entry::class

Craft's default element type classes are:

  • craft\elements\Asset
  • craft\elements\Category
  • craft\elements\Entry
  • craft\elements\GlobalSet
  • craft\elements\MatrixBlock
  • craft\elements\Tag
  • craft\elements\User
'elementType' => craft\elements\Entry::class,


An array of parameters that should be set on the Element Query that limits which entries go inside the index. These criteria are also used when importing through the console command.

'criteria' => [
    'section' => 'blog',


The transformer that should be used to define the data that should be sent to Algolia for each element. If you don’t set this, the default transformer will be used, which includes all of the element’s direct attribute values, but no custom field values.

// Can be set to a function
'transformer' => function(craft\elements\Entry $entry) {
    return [
        'title' => $entry->title,
        'id' => $entry->id,
        'url' => $entry->url,

// Or a string/array that defines a Transformer class configuration
'transformer' => 'MyTransformerClassName',

// Or a Transformer class instance
'transformer' => new MyTransformerClassName(),

Your custom transformer class would look something like this:


use craft\elements\Entry;
use League\Fractal\TransformerAbstract;

class MyTransformerClassName extends TransformerAbstract
    public function transform(Entry $entry)
        return [
            // ...


For long documents it is advised to divide the element into multiple rows to keep each row within row data size. This can be done using splitElementIndex. Array items are array indexes returned from the transformer.

'splitElementIndex' => [

Important - distinctId (available after indexing) must be set up as an attribute for faceting for deletion of objects to work when using splitElementIndex.

Console commands

Scout provides two easy console commands for managing your indices.


To import one or all indices you can run the following console command

./craft scout/index/import <indexName?>

The indexName argument is not required, all your mappings will be imported when you omit it.


Clearing an index is as easy as running a command in your console.

./craft scout/index/flush <indexName?>

As with the import command, indexName is not required, when flushing Scout will ask you to confirm that you really want to clear all the data in your index.


Does a flush/clear first and then imports the index again.

./craft scout/index/refresh <indexName?>


  • Craft Algolia by aaronwaldon as a base to start from
  • @larsboldt for the Split Element Index option

Brought to you by Rias