In T352847#9396836, @Gehel wrote:

This seems overfitting for a very specific use case, it is highly likely that we will make the experience worth for more people. I'm declining this ticket. If there is a higher level use case that makes sense we can try to dig into it.

Note that in this particular example, the autocomplete does not raise the disambiguation page to the top 10, but the full text search places it as the 3rd result.

There is no full text search in the mobile app.

@Seddon / @JTannerWMF : it seems to me that the solution here might be to have better integration with full text search in the mobile app. Is this something that make sense? Or should this ticket be declined?

At first I wanted to speak out against making this a thing, but I think for the cases where the search request matches the standard page name of the disambiguation page (should be configurable), it makes a lot of sense to show it as a second result. So if you enter Tent and Tent (disambiguation) is a thing, it should be displayed more prominently even if it has low page views.

Currently the search system disadvantages disambiguation pages significantly since they don’t get visited as much as the articles (and never could be). For the disambiguation pages located at the ‘main’ title (Smith, not Smith (disambiguation)) this doesn’t present a problem at all since they get shown first, but many disambiguation pages can use the qualifier in the page name due to the more known main term but still be very useful to readers.