# Deprecating the Search Banner theme component

**URL:** https://meta.discourse.org/t/deprecating-the-search-banner-theme-component/379322
**Category:** Announcements
**Tags:** search-banner
**Created:** [November 10, 2025, 3:44pm UTC](https://meta.discourse.org/t/deprecating-the-search-banner-theme-component/379322 "2025-11-10T15:44:53Z")
**Posts on this page:** 1
**Showing post:** 22

<div class="post-metadata">

### Author: ![lindsey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lindsey/32/318210_2.png) [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [January 20, 2026, 1:50pm UTC](https://meta.discourse.org/t/deprecating-the-search-banner-theme-component/379322/22 "2026-01-20T13:50:04Z")

</div>

Hi @Moin, sorry for the long delay in our response while we were looking into this.

The Search Banner component came with built-in translations for many languages (German, Spanish, French, Chinese, etc.) in its locale files. These weren’t stored as TranslationOverrides in the database - they were part of the component itself. The migration script from Search Banner → Welcome Banner only migrates translation overrides (custom site texts that admins have explicitly set), not the theme component’s built-in translations, which is what you were seeing here:

> [@Moin](#):
>
> ![image](https://global.discourse-cdn.com/meta/original/4X/a/b/8/ab85d5e81e387a0a10f85c981015a744732a9123.png)

I’m sorry for the oversight on our part and that this made migration less smooth!

---

_[View the full topic](https://meta.discourse.org/t/deprecating-the-search-banner-theme-component/379322)._
