Background

Since we're using auto-generated numerical page titles now, the results through Special:Search can look confusing with only the page title being shown as the link. The entity's title should be shown as well, and as the more prominent part of the link, just as is seen on Wikidata.

Wikidata's ShowSearchHitHandler.php looks like basically what we want. We can even have it follow the language fallback chain. Currently we work around this by using {{#translation:}} in the MediaWiki-extensions-InputBox we currently have embedded in the wikitext at Community Wishlist/Wishes, which limits its results.

Other problems:

• No-JS messages show up in search results (example). We can configure CirrusSearch to index what we want, namely only the title, description and other free-form fields. See related task: T406419

Efforts for improving the search results for entities is tracked separately at T410548: Improve search results for Community Wishlist entities.

Acceptance criteria

• Show the entity page's display title in place of the actual page title

Derived Requirement

Ensure that Community Wishlist entities (wishes and focus areas) display improved, user-friendly information in search results on Special:Search. Instead of showing only auto-generated numerical page titles (e.g., *W10*, *FA3*), the entity’s display title should appear prominently as the main search result heading—similar to how Wikidata handles entity search results.

Additionally, search indexing and rendering should:

• Follow the language fallback chain for multilingual titles.
• Exclude No-JS or system messages from search results.
• Include only relevant content fields such as the title, description, and other free-form fields.

Test Steps

Test Case 1: Verify display title appears in search results

1. Navigate to Special:Search on Meta beta.
2. Search for an existing wish (e.g., type part of the wish’s display title).
3. Observe the search results.
4. ✅❓❌⬜ AC1: Confirm that the entity’s display title (e.g., *Allow section translation for all users*) appears prominently instead of the numeric page title (e.g., *W10*).

Test Case 2: Verify display title handling for focus areas

1. On Special:Search, search for a focus area (e.g., *Improving Editing Tools*).
2. Observe the search result link and snippet.
3. ✅❓❌⬜ AC2: Confirm that the focus area’s display title appears as the main result heading and not the auto-generated title (e.g., *FA3*).

Test Case 3: Verify exclusion of No-JS messages and irrelevant content

1. Perform a search with a keyword likely to return system-related pages (e.g., “Community Wishlist”).
2. Review the search results for any No-JS messages or system text.
3. ✅❓❌⬜ AC3: Confirm that No-JS messages or internal system strings do not appear in search results, and only relevant fields (title, description, free-form text) are indexed.

Test Case 4: Verify multilingual and language fallback behavior

1. Switch the wiki interface to a language that uses translation fallback (e.g., English → Hebrew).
2. Search for a translated wish or focus area.
3. ✅❓❌⬜ AC4: Confirm that the search result correctly displays the translated display title or falls back to the next available language in the fallback chain.

QA Results - Meta Beta