Scolta for WordPress

Built and maintained by Tag1 Consulting — technology leadership since 2007.

WordPress 6.x plugin — WP-CLI commands, Settings API page, [scolta_search] shortcode, and AI-powered search built on Pagefind.

Status

Scolta 1.0 — the plugin API documented here is stable. Breaking changes follow semantic versioning: no removal or signature change without a major version bump and a deprecation cycle. File bugs at the repo issue tracker.

What Is Scolta?

Scolta is a scoring, ranking, and AI layer built on Pagefind. Pagefind is the search engine: it builds a static inverted index at publish time, runs a browser-side WASM search engine, produces word-position data, and generates highlighted excerpts. Scolta takes Pagefind's result set and re-ranks it with configurable boosts — title match weight, content match weight, recency decay curves, and phrase-proximity multipliers. No search server required. Queries resolve in the visitor's browser against a pre-built static index.

This plugin is the WordPress adapter. It provides WP-CLI commands for building and maintaining the index, a Settings API admin page, a [scolta_search] shortcode, content change tracking, and REST API endpoints for the AI features. The actual scoring, indexing logic, memory management, and AI communication live in scolta-php, which this plugin depends on via Composer. Scoring runs client-side via the scolta.js browser asset and the pre-built WASM module shipped with scolta-php.

The LLM tier — query expansion, result summarization, follow-up questions — is optional. When enabled, it sends the query text and selected result excerpts to a configured LLM provider (Anthropic, OpenAI, or a self-hosted Ollama endpoint). The base search tier shares nothing with any third party.

Running Example

The examples in this README and the other Scolta repos use a recipe catalog as the concrete data set. Recipes are a good showcase because recipe vocabulary has genuine cross-dialect mismatches:

A search for aubergine parmesan should surface Eggplant Parmigiana.
A search for chinese noodle soup should surface Lanzhou Beef Noodles, Wonton Soup, and Dan Dan Noodles.
A search for gluten free pasta should surface Zucchini Spaghetti with Pesto and Rice Noodle Stir-Fry.
A search for quick dinner under 30 min should surface Pad Kra Pao, Dan Dan Noodles, and Steak Frites.

Here is how to model and index the recipe catalog in WordPress:

1. Register a recipe custom post type with custom fields: _recipe_cuisine, _recipe_diet, _recipe_cook_time.

// In your theme's functions.php or a plugin
register_post_type('recipe', [
    'label'       => 'Recipes',
    'public'      => true,
    'has_archive' => true,
    'supports'    => ['title', 'editor', 'custom-fields'],
]);

2. Add the scolta_content_item filter to include the regional synonyms in the indexed content:

add_filter('scolta_content_item', function ($item, $post) {
    if ($post->post_type !== 'recipe') {
        return $item;
    }
    $cuisine = get_post_meta($post->ID, '_recipe_cuisine', true);
    $diet    = get_post_meta($post->ID, '_recipe_diet', true);

    return new \Tag1\Scolta\Export\ContentItem(
        id:       $item->id,
        title:    $item->title,
        bodyHtml: $item->bodyHtml
                . '<p>Cuisine: ' . esc_html($cuisine) . '</p>'
                . '<p>Diet: ' . esc_html($diet) . '</p>',
        url:      $item->url,
        date:     $item->date,
        siteName: $item->siteName,
    );
}, 10, 2);

3. Enable the recipe post type in Settings > Scolta > Content > Post types to index.

4. Build the index:

wp scolta build

5. Add [scolta_search] to any page. Visit the page and search for aubergine parmesan. Scolta surfaces Eggplant Parmigiana because Pagefind's stemmer matches both "aubergine" and "eggplant" in the indexed content, and Scolta's title boost lifts the most relevant result.

The recipe fixture HTML files live in scolta-php at tests/fixtures/recipes/ if you want a pre-built data set without a WordPress database.

Quick Install

# 1. Install the plugin (upload via wp-admin or copy to wp-content/plugins/scolta/)

# 2. Activate in wp-admin > Plugins

# 3. Build the search index
wp scolta build

# 4. Add [scolta_search] to any page

# 5. Set your API key to unlock AI features

Add to wp-config.php:

define('SCOLTA_API_KEY', 'sk-ant-...');

With an API key configured, search queries are automatically expanded with related terms, results include an AI summary, and visitors can ask follow-up questions.

Verify It Works

wp scolta check-setup

This verifies PHP version, index directories, indexer selection, AI provider configuration, and binary availability. Fix any items marked as failed before proceeding.

wp scolta status

The REST health endpoint also reports current state: GET /wp-json/scolta/v1/health. Anonymous requests return only the overall status value (enough for uptime monitoring); the full diagnostic payload — AI provider, index detail, integrity breakdown — requires an authenticated request from a user with manage_options.

What Scolta Is Built For

Scolta is designed for content search on WordPress sites: posts, pages, custom post types, and other content indexed at publish time. WordPress powers over 40% of the web — marketing sites, editorial platforms, membership communities, documentation portals, and enterprise intranets — and Scolta is tuned for these content-publishing use cases.

The static-index architecture means no Elasticsearch or Solr server to manage. Scolta works on managed WordPress hosting (WP Engine, Kinsta, Flywheel, Pantheon) where running a dedicated search server is not possible. For dynamic sites that publish frequently, Scolta's auto-rebuild feature queues a re-index whenever content is saved — so the search index stays current without manual intervention.

Scolta replaces hosted search SaaS (Algolia, Coveo, SearchStax) and Elasticsearch-backed plugins (ElasticPress, SearchWP) for WordPress sites where the search use case is content relevance, recency, and vocabulary matching. WooCommerce sites already have Action Scheduler installed — enabling Scolta's auto-rebuild requires no additional dependencies.

Memory and Scale

The default memory profile is conservative, which targets a peak RSS under 96 MB and works on shared hosting with a 128 MB PHP memory_limit. Scolta never silently upgrades to a larger profile.

The Settings > Scolta > Memory Budget field accepts a profile name or an exact byte value:

conservative   # peak ≤ 96 MB  — default, safe for shared hosting (50 posts/chunk)
balanced       # peak ≤ 384 MB — recommended for VMs              (200 posts/chunk)
aggressive     # peak ≤ 1 GB   — high-memory servers              (500 posts/chunk)
256M           # custom byte value — routes to the nearest profile's tuning

The Settings > Scolta > Chunk Size field sets pages-per-chunk independently of the memory budget. Leave it blank to use the profile default. Lower values reduce peak RAM; higher values reduce merge overhead on large corpora.

Both settings apply to every PHP-indexer build path — wp scolta build, the admin Rebuild Now button, and Action Scheduler background rebuilds all stream content through the same budget-aware pipeline.

Both settings can be overridden per-run:

wp scolta build --memory-budget=balanced
wp scolta build --memory-budget=256M --chunk-size=100
wp scolta build --indexer=php --chunk-size=30  # low-RAM override

Tested ceiling at the conservative profile: 50,000 pages. Higher counts likely work; not certified yet.

AI Features and Privacy

Scolta's AI tier is optional. When enabled:

The LLM receives: the query text, and the titles and excerpts of the top N results (default: 10, configurable via ai_summary_top_n).
The LLM does not receive: the full index contents, full page text, user session data, or visitor identity.
Which provider receives the query data depends on your ai_provider setting: anthropic, openai, or a self-hosted endpoint via ai_base_url.

The base search tier — Pagefind index lookup and Scolta WASM scoring — runs entirely in the visitor's browser with no server-side involvement beyond serving static index files.

Configuration

AI Provider

Configure at Settings > Scolta > AI Provider, or via wp-config.php constants.

Setting	Option key	Default	Description
Provider	`ai_provider`	`anthropic`	`anthropic` or `openai`
API key	env/constant only	—	`SCOLTA_API_KEY` env var or `define('SCOLTA_API_KEY', '...')` in wp-config.php
Model	`ai_model`	`claude-sonnet-4-5-20250929`	LLM model identifier
Base URL	`ai_base_url`	provider default	Custom endpoint for proxies or Azure OpenAI
Query expansion	`ai_expand_query`	`true`	Toggle AI query expansion on/off
Summarization	`ai_summarize`	`true`	Toggle AI result summarization on/off
Summary top N	`ai_summary_top_n`	`10`	How many top results to send to AI for summarization
Summary max chars	`ai_summary_max_chars`	`4000`	Max content characters sent to AI per request
Max follow-ups	`max_follow_ups`	`3`	Follow-up questions allowed per session
AI languages	`ai_languages`	`['en']`	Languages the AI responds in (matches user query language)

These are stored in the scolta_settings WordPress option. Use Settings > Scolta to edit them, or update programmatically:

$settings = get_option('scolta_settings', []);
$settings['ai_model'] = 'claude-opus-4-6';
$settings['ai_languages'] = ['en', 'fr', 'de'];
update_option('scolta_settings', $settings);

Tuning search breadth

Getting fewer results than you expect on a recipe, product, or catalog site? Go to Settings > Scolta > Site Type and choose the Recipe & Content Catalog preset, then save and rebuild your index (wp scolta build).

Scolta defaults to a conservative search breadth so generic words ("easy", "quick", "best") don't flood your results. On a recipe or catalog site, the useful domain words you actually want to match — ingredients, techniques, product attributes — are common enough that the default can hide them. The Recipe & Content Catalog preset widens the breadth (and tunes a handful of other ranking settings) so those searches return the fuller set of matches you'd expect.

Pick the Site Type that matches your site and Scolta sets sensible defaults for you:

Your site	Preset
Recipes, product or content catalogs	Recipe & Content Catalog
Docs, knowledge bases, encyclopedias, references	Documentation & Reference
Online stores	E-commerce & Product Store
Blogs and editorial sites	Blog & Editorial
News sites	Start from Scratch, then tune recency

You rarely need to touch individual numbers — the preset is the recommended path, and any value you change by hand in the Scoring section still overrides the preset. The one advanced knob worth knowing is Search Breadth (expand_subword_max_frequency): higher returns more results but can pull in loosely-related matches; lower keeps results tight. The Recipe & Content Catalog preset already raises it from 0.05 to 0.10.

For the evidence behind each preset — the scoring sweeps and the per-parameter data — see scolta-php's docs/TUNING.md.

Search Scoring

Configure at Settings > Scolta > Scoring.

Setting	Option key	Description
Title match boost	`title_match_boost`	Boost when query terms appear in the title
Title all-terms multiplier	`title_all_terms_multiplier`	Extra multiplier when ALL terms match the title
Content match boost	`content_match_boost`	Boost for query term matches in body/excerpt
Expand primary weight	`expand_primary_weight`	Weight for original query results vs AI-expanded results (higher = original query dominates; raise to 0.7+ if you want literal keyword matches to win)
Recency strategy	`recency_strategy`	Decay function: `exponential`, `linear`, `step`, `none`, or `custom`
Recency boost max	`recency_boost_max`	Maximum positive boost for very recent content
Recency half-life days	`recency_half_life_days`	Days until recency boost halves
Recency penalty after days	`recency_penalty_after_days`	Age before content gets a penalty (~5 years)
Recency max penalty	`recency_max_penalty`	Maximum negative penalty for very old content
Language	`language`	ISO 639-1 code for stop word filtering
Custom stop words	`custom_stop_words`	Extra stop words beyond the language's built-in list
Expansion combine mode	`expansion_combine_mode`	How a multi-term query expansion combines its per-sub-query results into the AI-summary candidate set: `relevance_union` (historical behavior) or `round_robin` (deal the top few from each sub-query so the summary sees breadth across sub-topics). Preset-defaulted — the Recipe & Content Catalog, Blog & Editorial, and E-commerce presets default it to `round_robin`; the others use `relevance_union` — and any value you set by hand overrides the preset. The visible result list stays relevance-sorted either way.

Defaults and the full reference: scolta-php docs/CONFIG_REFERENCE.md.

News site (recency matters a lot):

$settings = get_option('scolta_settings', []);
$settings['recency_boost_max']           = 0.8;
$settings['recency_half_life_days']      = 30;
$settings['recency_penalty_after_days']  = 365;
$settings['recency_max_penalty']         = 0.5;
update_option('scolta_settings', $settings);

Documentation site (recency doesn't matter, titles matter a lot):

$settings = get_option('scolta_settings', []);
$settings['recency_strategy']           = 'none';
$settings['title_match_boost']          = 2.0;
$settings['title_all_terms_multiplier'] = 2.5;
update_option('scolta_settings', $settings);

Recipe catalog (no recency, title precision matters):

$settings = get_option('scolta_settings', []);
$settings['recency_strategy']           = 'none';
$settings['title_match_boost']          = 1.5;
$settings['title_all_terms_multiplier'] = 2.0;
update_option('scolta_settings', $settings);

Display

Configure at Settings > Scolta > Display.

Setting	Option key	Description
Excerpt length	`excerpt_length`	Characters shown in result excerpts
Results per page	`results_per_page`	Results shown per page
Max Pagefind results	`max_pagefind_results`	Total results fetched from index before scoring

Defaults and the full reference: scolta-php docs/CONFIG_REFERENCE.md.

Site Identity

Configure at Settings > Scolta > Content.

Setting	Option key	Default	Description
Site name	`site_name`	blog name	Included in AI prompts so the AI knows what site it's searching
Site description	`site_description`	`website`	Brief description for AI context

Custom Prompts

Override the built-in AI prompts at Settings > Scolta > Custom Prompts, or use the scolta_prompt filter:

add_filter('scolta_prompt', function (string $prompt, string $promptName, array $context): string {
    if ($promptName === 'summarize') {
        $prompt .= "\n\nFocus on cuisine type and dietary information.";
    }
    return $prompt;
}, 10, 3);

$promptName is one of expand_query, summarize, or follow_up.

Debugging

"Pagefind binary not found"

On managed hosting (WP Engine, Kinsta, Flywheel, Pantheon), exec() is disabled and the binary cannot run. The plugin falls back to the PHP indexer automatically — the search experience is identical. To confirm:

wp scolta check-setup
wp scolta status

If you want the binary on a host that supports it:

wp scolta download-pagefind

The PHP indexer supports 14 languages via Snowball stemming. The Pagefind binary supports 33+ languages and is 5–10× faster for large sites, but requires Node.js ≥ 18 or a direct binary download.

"AI features not working"

Verify API key: wp scolta check-setup
Clear stale cache: wp scolta clear-cache
Confirm the model name is current at Settings > Scolta > AI Provider

"AI summary says 'I don't have enough context'"

The defaults (10 results, 4000 chars) are already tuned for curation. If still insufficient, increase further:

$settings = get_option('scolta_settings', []);
$settings['ai_summary_top_n']     = 15;
$settings['ai_summary_max_chars'] = 6000;
update_option('scolta_settings', $settings);

"AI responses are in the wrong language"

Set ai_languages to match your site's language(s):

$settings = get_option('scolta_settings', []);
$settings['ai_languages'] = ['de'];  // or ['en', 'fr', 'de'] for multilingual
update_option('scolta_settings', $settings);

"Expanded queries return irrelevant results"

Raise expand_primary_weight (default: 0.5) to make original query terms dominate more, or disable expansion:

$settings = get_option('scolta_settings', []);
$settings['expand_primary_weight'] = 0.8;  // closer to 1.0 = original query dominates
// or: $settings['ai_expand_query'] = false;
update_option('scolta_settings', $settings);

"No search results"

Check index status: wp scolta status
Run a full rebuild: wp scolta build
Confirm the Pagefind output directory is web-accessible (Settings > Scolta > Pagefind)
Flush rewrite rules: wp rewrite flush

"Build is slow"

Use wp scolta diagnose to identify which phase dominates:

wp scolta diagnose             # sample 500 posts (fast)
wp scolta diagnose --count=2000  # larger sample for better projection accuracy

Output example:

=== Scolta PHP Indexer Diagnostics ===

Site: 44,107 published posts  (gather_count in 0.012s)
Sample: 500 posts  (--count=500)

Phase 1/3  gather  [WP_Query + apply_filters("the_content") + get_permalink]
  500 posts  18.40s  36.8 ms/post
  ! High ms/post — apply_filters("the_content") is likely slow.
    Common causes: Yoast SEO, Gutenberg do_blocks(), WooCommerce, Elementor.

Phase 2/3  HtmlCleaner  [strip HTML tags, check minimum content length]
  500 posts  1.70s  3.4 ms/post  (487 passed, 3% too short)

Phase 3/3  indexer  [tokenize, stem, chunk, merge, write — conservative budget]
  487 posts  0.89s  1.8 ms/post

=== Projected for full corpus (44,107 posts) ===

  gather:      27m 0s    86% of total
  HtmlCleaner: 2m 30s     8% of total
  indexer:     1m 19s     4% of total
  ----------------------------
  estimated total: 30m 49s

Recommendation: gather phase dominates (86% of build time).
  apply_filters("the_content") runs every active plugin filter on each post.
  Use the scolta_content_item filter to substitute $post->post_content
  (raw storage, no plugin processing) or do_blocks($post->post_content)
  (renders blocks only, skips SEO/analytics hooks).

If gather dominates (>50%): apply_filters('the_content', ...) is the bottleneck. Use the scolta_content_item filter to replace the body HTML with raw $post->post_content or do_blocks($post->post_content):

add_filter('scolta_content_item', function ($item, $post) {
    // Use do_blocks() instead of apply_filters('the_content'):
    // renders Gutenberg blocks but skips Yoast, WooCommerce, etc.
    return new \Tag1\Scolta\Export\ContentItem(
        id:       $item->id,
        title:    $item->title,
        bodyHtml: do_blocks($post->post_content),
        url:      $item->url,
        date:     $item->date,
        siteName: $item->siteName,
    );
}, 10, 2);

If indexer dominates (>50%): Increase the chunk size to reduce merge overhead. Either use a larger profile (--memory-budget=balanced, which sets 200 posts/chunk) or set the chunk size directly (--chunk-size=200) while keeping your current memory profile.

For per-phase wall-clock breakdowns during a live build, run with --debug:

wp scolta build --indexer=php --debug 2>&1 | grep '\[scolta\]'

Each [scolta] line now includes +Xs elapsed since build start, making it easy to see which chunk or merge step is slow.

"Build hangs or times out"

The plugin uses proc_open() with a 5-minute timeout for Pagefind binary builds. PHP indexer builds run in chunks via Action Scheduler to avoid PHP timeouts. If builds stall:

wp scolta status        # check for a stale build lock
wp scolta build --force # clear lock and force rebuild

"Fatal error on Settings page after upgrade"

Run wp scolta check-setup from CLI to check for configuration issues. If the admin page is unreachable, deactivate and reactivate the plugin to re-run the activation migration.

WP-CLI Commands

wp scolta build                          # Full build: mark all content, export HTML, run indexer
wp scolta build --incremental            # Only process tracked changes
wp scolta build --skip-pagefind          # Export HTML without rebuilding index
wp scolta build --indexer=php            # Force PHP indexer regardless of setting
wp scolta build --force                  # Skip fingerprint check, force full rebuild
wp scolta build --memory-budget=balanced # Use balanced memory profile
wp scolta build --resume                 # Resume an interrupted PHP build
wp scolta export                         # Export content to HTML only
wp scolta export --incremental           # Only export tracked changes
wp scolta rebuild-index                  # Rebuild index from existing HTML files
wp scolta diagnose                       # Profile gather / HtmlCleaner / indexer phases
wp scolta diagnose --count=2000          # Larger sample for more accurate projection
wp scolta status                         # Show tracker, content, index, and AI status
wp scolta cleanup                        # Remove stale double-nested pagefind directories
wp scolta clear-cache                    # Clear Scolta AI response caches
wp scolta download-pagefind              # Download the Pagefind binary for your platform
wp scolta check-setup                    # Verify PHP, indexer, and configuration

REST API Endpoints

Method	Path	Description
POST	`/wp-json/scolta/v1/expand-query`	Expand a search query into related terms
POST	`/wp-json/scolta/v1/summarize`	Summarize search results
POST	`/wp-json/scolta/v1/followup`	Continue a search conversation
GET	`/wp-json/scolta/v1/health`	Health check — anonymous: overall `status` only; full detail requires `manage_options`
GET	`/wp-json/scolta/v1/build-progress`	Current build status (admin only)
POST	`/wp-json/scolta/v1/rebuild-now`	Trigger immediate background rebuild (admin only)

Endpoints are public by default. Use the scolta_search_permission filter to restrict access.

Extend Indexed Content

By default, Scolta indexes all published posts and pages. Add custom post types at Settings > Scolta > Content > Post types to index.

Use the scolta_content_item filter to append custom fields before a post is indexed:

add_filter('scolta_content_item', function ($item, $post) {
    $extra = get_field('product_specs', $post->ID);
    if ($extra) {
        $item = new \Tag1\Scolta\Export\ContentItem(
            id:       $item->id,
            title:    $item->title,
            bodyHtml: $item->bodyHtml . '<p>' . esc_html($extra) . '</p>',
            url:      $item->url,
            date:     $item->date,
            siteName: $item->siteName,
        );
    }
    return $item;
}, 10, 2);

Optional Upgrades

Upgrade to the Pagefind binary indexer

The plugin auto-selects the PHP indexer on managed hosts. On hosts that support binaries, the Pagefind binary is 5–10× faster. The search experience is identical either way — both produce a Pagefind-compatible index.

wp scolta download-pagefind
# or:
npm install -g pagefind

Change Settings > Scolta > Indexer to "Auto" or "Binary" and rebuild.

Keeping the Index Fresh

When auto_rebuild is enabled in Settings > Scolta, the plugin listens for content changes (post saves and deletes) and automatically schedules a debounced rebuild after a configurable delay (default: 5 minutes). This requires Action Scheduler.

Three paths are available, in order of reliability:

Path A: Action Scheduler (recommended)

Install Action Scheduler to get automatic background index builds when content changes. WooCommerce sites already have it — just enable auto_rebuild in Settings > Scolta.

Path B: System cron

For hosts with SSH access. This is the most reliable option after Action Scheduler because it runs on the system clock and doesn't depend on WordPress page loads.

*/15 * * * * cd /var/www/html && wp scolta build --incremental 2>&1 | logger -t scolta

Adjust the path and interval to taste. --incremental only processes tracked changes, so runs are fast when nothing has changed.

Path C: WP-Cron via WP Crontrol

For users without SSH access who can't install Action Scheduler. Install WP Crontrol, then add this to your theme's functions.php or a custom plugin:

add_action( 'scolta_scheduled_rebuild', function () {
    if ( class_exists( 'Scolta_Rebuild_Scheduler' ) ) {
        Scolta_Rebuild_Scheduler::start_rebuild();
    }
} );

In Tools > Cron Events, add a new cron event: hook name scolta_scheduled_rebuild, recurrence "Every 15 minutes" (or "Twice hourly").

Caveat: WP-Cron events are triggered by page loads, not by the system clock. On low-traffic sites the rebuild may not run on schedule. If the site gets consistent traffic this works fine; otherwise Path B is more reliable.

Requirements

WordPress 6.0+
PHP 8.1+

The Pagefind binary is optional — the PHP indexer works without it.

Testing

Unit tests (no WordPress required):

cd packages/scolta-wp
./vendor/bin/phpunit

Integration tests (requires DDEV):

cd test-wordpress-7
ddev wp eval-file tests/integration-test.php

Architecture

scolta-wp (this plugin)            scolta-php              scolta-core (browser WASM)
  WP-CLI commands ───────────> ContentExporter ──────> cleanHtml()
  Scolta_Rest_Api ───────────> AiClient                buildPagefindHtml()
  Scolta_Admin ──────────────> ScoltaConfig
  Scolta_Shortcode ──────────> DefaultPrompts            (runs in browser)
  Scolta_Cache_Driver ───────> CacheDriverInterface     scoreResults()
  Scolta_Rebuild_Scheduler ──> PhpIndexer               mergeResults()
  Scolta_Auto_Rebuild ───────> PagefindBinary

This plugin handles WordPress-specific concerns: WP-CLI commands, Settings API, shortcodes, REST endpoints, post hooks for change tracking, Action Scheduler integration, and asset enqueueing. It depends on scolta-php and never on scolta-core directly. Scoring runs client-side via WebAssembly loaded by scolta.js.

scolta.php                              Plugin entry point, activation hooks
includes/
  class-scolta-tracker.php              Content change tracking table
  class-scolta-content-gatherer.php     Gathers WP posts as ContentItems
  class-scolta-ai-service.php           AI service wrapper
  class-scolta-rest-api.php             REST endpoint registration
  class-scolta-shortcode.php            [scolta_search] shortcode
  class-scolta-rebuild-scheduler.php    Action Scheduler integration
  class-scolta-auto-rebuild.php         Auto-rebuild on content change
  class-scolta-cache-driver.php         WordPress transients cache adapter
admin/
  class-scolta-admin.php                Settings page (Settings API)
cli/
  class-scolta-cli.php                  WP-CLI commands
vendor/
  tag1/scolta-php/                      Shared PHP library + assets

About Tag1 Consulting

Scolta is designed, built, and maintained by Tag1 Consulting. Tag1 has been delivering technology leadership since 2007 and is one of the leading open-source consulting firms in the world.

Tag1 offers AI strategy, architecture, and implementation consulting — from evaluating whether AI search is right for your organization, to production deployment and ongoing tuning. If you need help integrating Scolta, customizing scoring for your content model, or connecting it to your AI provider of choice, get in touch.

Credits

Scolta is built on Pagefind by CloudCannon. Without Pagefind, Scolta has no search to score — the index format, WASM search engine, word-position data, and excerpt generation are all Pagefind's. Scolta's contribution is the layer that sits on top: configurable scoring, multi-adapter ranking parity, AI features, and platform glue.

License

GPL-2.0-or-later

Related Packages

scolta-core — Rust/WASM scoring, ranking, and AI layer that runs in the browser.
scolta-php — PHP library that indexes content into Pagefind-compatible indexes, plus the shared orchestration and AI client.
scolta-drupal — Drupal 10/11 Search API backend with Drush commands, admin settings form, and a search block.
scolta-laravel — Laravel 11/12/13 package with Artisan commands, a Searchable trait for Eloquent models, and a Blade search component.

Name		Name	Last commit message	Last commit date
Latest commit History 391 Commits
.github		.github
admin		admin
assets		assets
cli		cli
includes		includes
scripts		scripts
tests		tests
.distignore		.distignore
.editorconfig		.editorconfig
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
BUILDING.md		BUILDING.md
CHANGELOG.md		CHANGELOG.md
CLAUDE.md		CLAUDE.md
LICENSE		LICENSE
README.md		README.md
composer.json		composer.json
composer.lock		composer.lock
phpcs.xml.dist		phpcs.xml.dist
phpstan-baseline.neon		phpstan-baseline.neon
phpstan.neon.dist		phpstan.neon.dist
phpunit.xml		phpunit.xml
readme.txt		readme.txt
scolta.php		scolta.php
uninstall.php		uninstall.php

Uh oh!

Folders and files

Latest commit

History

Repository files navigation

Scolta for WordPress

Status

What Is Scolta?

Running Example

Quick Install

Verify It Works

What Scolta Is Built For

Memory and Scale

AI Features and Privacy

Configuration

AI Provider

Tuning search breadth

Search Scoring

Display

Site Identity

Custom Prompts

Debugging

"Pagefind binary not found"

"AI features not working"

"AI summary says 'I don't have enough context'"

"AI responses are in the wrong language"

"Expanded queries return irrelevant results"

"No search results"

"Build is slow"

"Build hangs or times out"

"Fatal error on Settings page after upgrade"

WP-CLI Commands

REST API Endpoints

Extend Indexed Content

Optional Upgrades

Upgrade to the Pagefind binary indexer

Keeping the Index Fresh

Path A: Action Scheduler (recommended)

Path B: System cron

Path C: WP-Cron via WP Crontrol

Requirements

Testing

Architecture

About Tag1 Consulting

Credits

License

Related Packages

About

Topics

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases 25

Packages 0

Uh oh!

Uh oh!

Contributors

Uh oh!

Languages

Packages