Besides, since the search query is more clear, the submit issue button can be shown after clicking the check existing issues link, forcing the user to check existing issues.
(You know better than me, at present, the button is triggered after waiting a couple of seconds )

Yes, this is a weak point in the current process ..

I can do this.

If you know of a better solution I would appreciate a PR on this. In that we can then discuss the pros and cons / so far I had no idea we improve it, but we are grateful for any suggestion that represents an improvement 👍

Second, we can use some tools to automatically extract the error&solution from github issue, this can avoid maintaining a check sheet.

Not sure what you have in mind ..

Just for the records and slightly out of topic:

• the Engines tab of https://searx.space/ is based on the /stats/errors API. For example : https://paulgo.io/stats/errors
• there is an embedded checker
  • it can run on schedule in the webapp. See settings.yml
  • run from the command line: make search.checker.bing.
  • some engine can have some specific tests: see settings.yml, wikidata engine and this section

Or, more Convienent, we can write a script that Auto-checks the problem and provide solution.

That's a good idea! We could have a dedicated page for solutions for the admin. Like we already have /stats

But each solution will point to a wiki page.

Or we could on the same page like https://darmarit.org/searx/stats?engine=duckduckgo, provide an easy link to a wiki page for a solution so that the admin can easily find the solution.

But each solution will point to a wiki page.

Do you mean a special section for all the solutions, where each of a solution has a single page in wiki?

As I said, each problem has a unique technical report (the same you saw on every issue), so we can index the bugs/solutions by their technical report or the hash of technical report.

we can also use the wiki documents search system.