Easy Guide to TYPO3 Indexed Search (Setup, Configuration & Optimization)

Search is one of the most underestimated components of a TYPO3 website, yet it directly impacts usability, engagement, and conversion.

In this guide, you’ll get a clear overview of TYPO3 search solutions and a step-by-step walkthrough to install and configure EXT:indexed_search, including crawler setup for automated indexing.

This guide will help you:

• Understand available TYPO3 search options
• Decide when indexed_search is the right choice
• Set up and configure it correctly
• Avoid common issues and performance limitations

Note: This guide covers TYPO3 v9 and v10 setups. The core concepts remain the same for newer TYPO3 versions, though minor configuration differences may apply.

TYPO3 offers multiple ways to implement search functionality, from its built-in core extension to advanced third-party solutions. The right approach depends on your website size, performance requirements, and the level of search features you need.

In general, TYPO3 search solutions can be grouped into two categories:

• Core solution:
  EXT:indexed_search, suitable for small to medium-sized websites with basic search requirements.
• Advanced extensions and external engines:
  Solutions like Solr, ke_search, or Elasticsearch-based extensions designed for larger websites that require better performance, scalability, and advanced features such as faceted search.

Below is a comparison of commonly used TYPO3 search solutions:

In the following section, we’ll look at these extensions in more detail and help you choose the right TYPO3 search solution for your project.

Before diving into TYPO3 indexed_search setup, here’s a practical overview of the most commonly used TYPO3 search extensions, including where they work best and their limitations.

#1 EXT:indexed_search (TYPO3 Core)

Best for:
Small to medium-sized TYPO3 websites with basic search needs

Key strengths:

• Built into TYPO3 core
• No additional setup required
• Supports basic full-text search and file indexing

Limitations:

• Limited scalability for large websites
• No faceted search
• Performance can drop with large datasets

#2 EXT:solr (Apache Solr for TYPO3)

Best for:
Medium to large-scale websites with advanced search requirements

Key strengths:

• High performance and fast results
• Faceted search, synonyms, relevance tuning
• Scalable for enterprise-level projects

Limitations:

• Requires external Solr server setup
• Higher maintenance and configuration effort

#3 EXT:ke_search

Best for:
Small to medium websites needing more flexibility than indexed_search

Key strengths:

• Easy to install and configure
• Supports faceted search
• Flexible indexing from database records

Limitations:

• Not as powerful as Solr for large-scale projects
• Performance depends on database size

#4 EXT:mksearch

Best for:
Projects requiring flexible backend integration (Solr, Lucene, Elasticsearch)

Key strengths:

• Supports multiple search engines
• Highly customizable and extendable

Limitations:

• More complex setup
• Less commonly used, smaller community support

#5 EXT:search_core

Best for:
Developers needing custom search implementations with external engines

Key strengths:

• Supports Elasticsearch, Algolia, Solr
• Flexible API for custom integrations

Limitations:

• Limited support for newer TYPO3 versions
• Requires development effort

#6 EXT:pr_googlecse

Best for:
Quick implementation of search using Google Custom Search

Key strengths:

• Easy to set up
• No indexing required within TYPO3
• Leverages Google’s search capabilities

Limitations:

• Limited control over results
• External dependency
• Not ideal for privacy-sensitive or enterprise projects

#7 Other TYPO3 Search Extensions

TYPO3 also offers additional search extensions through the TYPO3 Extension Repository (TER), as well as the option to build custom solutions based on specific project requirements.

Best for:
Custom or niche use cases

Limitations:

• Varying levels of support and maintenance
• May require additional development and testing

In the next section, we’ll help you decide which TYPO3 search solution fits your project based on your website size, complexity, and performance needs.

Choosing the right TYPO3 search solution depends mainly on your website size, content complexity, and performance requirements. Instead of comparing features alone, it’s more practical to decide based on real use cases.

Quick Decision Guide

When to Choose EXT:indexed_search

Choose indexed_search if:

• You have a small to medium-sized TYPO3 website
• You need a simple, built-in solution
• You want minimal setup and maintenance

Avoid it if:

• Your website is large or content-heavy
• You need advanced features like faceting or relevance tuning
• Search performance is critical

When to Choose ke_search

Choose ke_search if:

• You need more flexibility than indexed_search
• You want faceted search without external servers
• Your project is medium-sized

Avoid it if:

• You are running a large-scale or enterprise website

When to Choose Solr (EXT:solr)

Choose Solr if:

• You are working on a large TYPO3 project
• You need fast, scalable search performance
• You require advanced features (facets, synonyms, ranking control)

Avoid it if:

• You want a quick, low-maintenance setup
• You don’t have resources for server configuration

Important Limitation to Consider

According to TYPO3 documentation, indexed_search has not been fully benchmarked for large-scale usage. Existing benchmarks cover up to approximately 2000 pages and ~400,000 indexed records. Beyond this, performance and scalability may require optimization or alternative solutions like Solr.

Practical Takeaway

• Use indexed_search for simplicity
• Use ke_search for flexibility without heavy infrastructure
• Use Solr for performance and scalability

In the next section, we’ll focus on how to install and configure TYPO3 indexed_search step by step.

While EXT:indexed_search is a convenient built-in solution, it has clear limitations that should be considered before implementation, especially for larger or performance-critical TYPO3 projects.

Performance Constraints

Indexed Search relies on database-based indexing and querying. As the number of indexed pages grows, search queries can become slower, particularly under high traffic or complex search requests. In larger setups, response times may increase significantly.

Scalability Limitations

This solution is not designed for large-scale websites. According to TYPO3 documentation, benchmarks have been tested only up to around 2000 pages and ~400,000 indexed records. Beyond this range, performance may degrade, and additional optimization efforts are required.

Limited Advanced Features

Compared to solutions like Solr or Elasticsearch, indexed_search lacks:

• Faceted search (filters)
• Advanced relevance tuning
• Synonym handling
• Real-time indexing capabilities

Indexing Method Dependency

By default, pages are indexed when they are accessed in the frontend. This can lead to incomplete indexing unless a crawler or scheduler is properly configured.

When Not to Use Indexed Search

Avoid using indexed_search if:

• Your website has 2000+ pages or large datasets
• You require fast, enterprise-level search performance
• You need advanced search features (facets, filters, ranking control)
• Your project demands scalable or future-proof architecture

In such cases, consider using Solr or other external search solutions for better performance and flexibility.

Step 3: Activate the extension

Tip: If installed via Composer, it is usually activated by default. Reactivating ensures database schema updates are applied correctly.

Step 5: How Indexing is Triggered

By default, TYPO3 Indexed Search indexes pages when they are visited in the frontend.

• Pages must be accessed at least once to be indexed
• New or hidden pages will not appear in search automatically
• For full-site indexing, a crawler or scheduler is recommended

Step 6: Exclude Header/Footer from Indexing (Optional)

To restrict indexing only to relevant content, define search markers:

Step 7: Customize Search Templates (Optional)

Override default templates by defining custom paths:

Step 1: Go to Web → List → Root Page
Step 2: Create a new “Indexing Configuration” record
Step 3: Configure it based on your content structure

Step 9: Advanced TypoScript Configuration

Fine-tune search behavior using:

Before configuring the extension, it’s important to understand what indexed_search offers.

Key Features

• Content-based relevance ranking
  Search results are prioritized based on:
  • Page title
  • Meta keywords
  • Meta description
  • Page body content
• File indexing support
  Can index external files such as:
  • HTML, TXT
  • PDF (via pdftotext)
  • DOC (via catdoc)
• Flexible search types
  Supports:
  • Exact match
  • Partial match
  • Phonetic (metaphone) search
• Word frequency-based ranking
  Results are ranked based on how often search terms appear in content.
• Case-insensitive search
  Ensures consistent results regardless of capitalization.
• Sentence-level scanning
  Allows matching within content even if not explicitly indexed as structured data.

In the next section, we’ll configure TYPO3 indexed_search step by step to ensure proper indexing and accurate search results.

If TYPO3 indexed_search is not returning results or behaving incorrectly, the issue is usually related to indexing, configuration, or cache settings. Use this checklist to quickly identify and fix the problem.

1. No Search Results Showing

Possible causes:

• Pages are not indexed yet
• Cache is disabled
• Indexing is not enabled

Fix:

Also ensure:

• The page is marked as “Include in Search”
• The page has been visited at least once

2. Pages Not Getting Indexed

Possible causes:

• Pages have not been accessed in frontend
• Indexing is disabled
• Crawler is not configured

Fix:

• Open pages manually in frontend to trigger indexing
• Or use a crawler/scheduler to index the entire site

3. Search Returns Incomplete Results

Possible causes:

• Only partial content indexed
• External files not configured
• Markers limiting indexed content

Fix:

Also check:

• TYPO3 SEARCH markers are not excluding important content
• File indexing tools (PDF, DOC) are properly configured

4. Slow Search Performance

Possible causes:

• Large number of indexed pages
• Full-word search enabled
• Database-heavy queries

Fix:

Additional actions:

• Limit indexed content scope
• Use crawler instead of frontend indexing
• Consider Solr for large websites

5. Duplicate Search Results

Possible causes:

• Multiple indexed versions of same page
• URL variations (parameters, cHash)

Fix:

6. Search Works, But Results Are Irrelevant

Possible causes:

• Poor content structure
• Missing meta data
• Weak keyword signals

Fix:

• Improve page titles and meta descriptions
• Use clear headings and structured content
• Ensure relevant keywords are present in content

7. Backend Indexing Data Not Visible

Possible causes:

• Missing access permissions
• Incorrect module usage

Fix:

• Check Web → Indexing module
• Ensure backend user has proper access

8. Search Not Working for Restricted Pages

Possible causes:

• Access restrictions blocking indexing

Fix:

Quick Debug Checklist

• Cache enabled
• Indexing enabled
• Pages visited or crawler configured
• Pages included in search
• No access restrictions blocking indexing
• TypoScript correctly applied

If issues persist on larger websites, it may indicate limitations of indexed_search. In such cases, consider switching to a more scalable solution like Solr.

To understand how TYPO3 indexed_search works, it’s important to look at two core processes: indexing and searching.

1. Indexing: How TYPO3 Stores Content

Indexing is the process of collecting and storing content from your TYPO3 website into a searchable database.

• When a page is accessed in the frontend, TYPO3 automatically scans its content
• It extracts words from:
  • Page title
  • Meta tags
  • Body content (or defined sections using markers)
• Each word is analyzed, counted, and stored along with its position and frequency

This data is then saved in TYPO3 database tables, creating a structured index that can be searched efficiently.

Important:
By default, indexing happens on page visit. If a page is never opened, it will not be indexed unless a crawler is used.

2. Searching: How Results Are Retrieved

When a user performs a search:

• TYPO3 checks the indexed word database
• It finds matching entries for the search query
• It retrieves all pages associated with those words
• Results are ranked based on:
  • Frequency of the keyword
  • Location of the keyword (title > meta > body)
  • Relevance scoring

The system then displays results in order of relevance.

3. Ranking Logic (How Results Are Prioritized)

TYPO3 indexed_search uses a basic relevance model:

• Higher weight is given to keywords in:
  • Page titles
  • Meta descriptions
• Lower weight for body content
• Word frequency increases ranking
• Exact matches are prioritized over partial matches

This ensures that more relevant pages appear higher in search results.

4. Indexing Workflow

The typical workflow looks like this:

1. A page is visited in the frontend
2. TYPO3 extracts and processes content
3. Words are stored in the index database
4. A user performs a search
5. TYPO3 queries the index
6. Results are ranked and displayed

5. Manual vs Automated Indexing

There are two ways indexing happens:

• Frontend-based indexing (default)
  Pages are indexed when users or admins visit them
• Crawler-based indexing (recommended for larger sites)
  A crawler systematically visits all pages and builds the index automatically

6. Key Limitations in the Workflow

• Indexing depends on page access unless automated
• Large datasets increase database load
• No advanced ranking logic compared to Solr/Elasticsearch

Practical Insight

TYPO3 indexed_search is effective for smaller websites where simple keyword-based search is sufficient. For larger or more complex projects, the limitations in indexing and ranking become more noticeable, making advanced search solutions more suitable.

Page Properties → disable “Include in Search”

• Multiple pages (TypoScript):

You can integrate TYPO3 indexed_search into your frontend using the following approaches:

1. Native Plugin (EXT:indexed_search)

• Default TYPO3 plugin
• Provides search form + results page
• Supports basic and advanced search

2. EXT:macina_searchbox

• Adds a lightweight search box
• Passes queries to indexed_search
• Easy Fluid-based customization

3. EXT:indexed_search_autocomplete

• Adds autocomplete functionality
• Enhances user experience
• Works on top of indexed_search

For larger websites, manual indexing (via page visits) is not sufficient. TYPO3 Crawler automates indexing across the entire site.

Installation

CLI:

Cron Job:

Results per Page

Prevent Duplicate Results

Disable indexing on page visits:

• Admin Tools → Settings → indexed_search
• Uncheck: Index pages in frontend

• Use full-word search for faster results:

• Limit indexed content scope
• Use crawler instead of frontend indexing
• Avoid indexing unnecessary pages (e.g., search results page)

For large websites, consider switching to Solr for better performance.

• Small corporate websites (≤500 pages)
• Documentation or content-driven sites
• Projects needing quick setup with minimal maintenance

Not suitable for:

• Large enterprise portals
• E-commerce with complex filtering
• High-performance search requirements

TYPO3 indexed_search is a reliable solution for small to medium websites that need a simple, built-in search feature.

• Use it for quick implementation and low maintenance
• Avoid it for large-scale or performance-critical projects

If your project grows in size or complexity, upgrading to Solr or another advanced search solution will provide better scalability and control.