How to add search engines to your browser

Adding search engines to your browser

Search engines can generally be added to browsers in similar ways through their settings page.
Programmatic availability generally does not exist. If it does, and it is not shown below, please share the information with us.
For per browser differences, see below.

Home-page is used on this page as an example URL for searching. If you wish to try out the Home Page search query path, please copy the following:
This search opens up in the Home Page Web App, allowing the ability to search from many different search engines:


Chrome doesn’t seem to offer a way to “add” a default search engine. It only offers a choice of a few presets and a way to search using keywords shown below:

1. Go to search engine settings: Chrome “Search Engines” Settings (Context Menu ⇒ “Settings” ⇒ “Search engine” ⇒ “Manage search engines and site search”).
2. Click “Add” under “Site search”.
3. “Add search engine”:

Search engine: The name of the search engine.
Keyword: Keyword to initiate search against this search engine.
URL with %s in place of query: For example: ""

Click “Add”.

Chrome also includes “Inactive shortcuts” which are automatically added when browsing websites.
See “Auto Detection” for further information.


1. Open the following link to enter the search settings page: Search.
2. You will be taken to the Firefox Browser ADD-ONS page.
3. Install the recommended(※ Recommended at time of writing. Please make sure it is still appropriate before installing and using.) custom search plugin: Add custom search engine.
4. Go to Add-ons and select options of the added extension.
5. Fill in the fields to add your custom search engine. Even any similar extensions should have common fields similar to OpenSearch.
6. In address bar, click … and “Add Search Engine”.
7. Go to about:preferences#search, select the added search engine, and add a keyword(Usually prefixed with “@”).

Alternatively, bookmark , set a keyword to search, and then search via “[keyword] search terms …”.


※ The below does not apply to old versions of Edge before implementing Chromium.

  1. Go to “Settings” in context menu or “edge://settings“.
  2. Go to “Privacy, search, and services” in the left sidebar or “edge://settings/privacy“.
  3. Go to the bottom of the page and click “Address bar and search” under “Services” or go to “edge://settings/search“.
  4. Go to “Manage search engines”.
  5. Click “Add” and fill in the information. The fields are similar to those in Chrome and many other browsers.
  6. The newly added search engine should be shown in the list. If it is not shown, it may be necessary to restart the browser. Click the “…” and select “Make default”.
  7. It is also possible to select the search engine from the previous page (edge://settings/search) under “Search engine used in the address bar”.


Use the following: IE Search Provider Builder Tool.

Chrome Android:

  1. Go to “Settings” from chrome://settings OR in the hamburger menu.
  2. Go to “Search engine”.
  3. Select your desired search engine.

At least in the environment I tested, it seems that only a few search engines are available, and that there are no ways to add any more.

If there is a way to add a custom search engine OR this changes in the future, please let us know.

Firefox Android:

  1. Go to “Settings” from the hamburger menu.
  2. Go to “Search”.
  3. Go to “Add search engine”.
  4. Select one of the preset search engines, OR add a custom search engine using the format displayed on the page.

Brave Android:

  1. Go to “Settings”.
  2. Go to “Search engines” under “General”.
  3. Go to “Standard tab” (OR Private Tab if you wish to customize the private tab).
  4. Select one of the preset search engines.

At least in the environment I tested, it seems that only a few search engines are available, and that there are no ways to add any more.

If there is a way to add a custom search engine OR this changes in the future, please let us know.

Kiwi android:

  1. Go to “Settings”.
  2. Go to “Search engine” under “Basics”.
  3. Select one of the preset search engines.

At least in the environment I tested, it seems that only a few search engines are available, and that there are no ways to add any more.

However, there does seem to be a lot more than other search engine limited browsers.

If there is a way to add a custom search engine OR this changes in the future, please let us know.


Mac, iOS, and other Apple related services are generally not supported by . If you know of any links that would help for this article, please continue sharing with us, and we will consider adding them.

Auto Detection:

Auto-detection of search engines can be done using the following ways:
Using an input of type “search”. For example: <input type="search" name="q">. Just in case, make sure to wrap in a valid form tag.
Using Open Search. This can by first creating a valid opensearch.xml file and then linking to it within the loaded HTML file.


  • Many browsers are limited in what search engines can be selected.
  • Firefox seems to be very good. It offers customization on both desktop and mobile (Android) browsers.
  • Chrome disappointingly offers very little customizability for a major browser.
  • Edge seems to be very good on PC. I had problems loading the Android version of Edge after installing it, and it seems this a common problem, so I have not included information here.
  • Brave has good customizability in the desktop version, but seems to be lacking in the Android version.

Please consider trying out the Home Page start page web service by adding it as a search engine in one of the methods described in this article.

The current state of Internet Explorer 2022

The current state of Internet Explorer

From time to time, another big service drops support for IE. However, due to this becoming more and more common, these stories do not stand out much, and the current state of IE, including usage statistics, and the issues with it, get forgotten in time.
This article looks to provide important information on the current state of IE for users, managers, and developers.

The decline

Internet Explorer has been on the decline for many years now, starting with better alternatives such as Firefox and then Google Chrome, and more later due to being phased out in favour of the newer Microsoft Edge browser.
It had been unclear, for a long time, whether developers should support even the latest version of IE, IE 11.
However, that seemed to change when Microsoft announced that they will no longer develop for IE after 2015, and then big players in the online world started publicly stating that they would no longer support IE 11.
Even though many services did continue to support IE in some way, libraries, frameworks, and services using more dynamic features from JavaScript were keen to drop IE quickly.
This explains the general current state of IE (at least for IE11) as generally supported by larger services for static content, while more dynamic content using newer features of browsers generally losing some features or being completely unusable.
With the growing lack of support for IE, the decline of IE was steady, but IE never completely went away.

Why did users continue to use IE for so long?

Development ceased for IE, support ended for many popular services, important new features for browsers were not implemented, and development for IE while making modern websites became more and more difficult. So why does it, even now (2022), still have a small but significant percentage of users?

IE is no longer the default web browser in modern versions of Windows. However, it was the default web browser until Windows 8.1.
Windows 8.1 included mainstream support until January 2018 and has extended support until January 10, 2023:
This means support is still available for a Windows operating system using IE as a default browser.
This is enough to provide a significant percentage of IE users, as long as a high percentage do not change their default browser.
The corporate world has been using IE for a long time, even when outdated.
The reason this is not such a big deal is that the systems made for corporate systems often relied heavily on proprietary VB (Visual Basic) code.
Because these systems were often made many years ago, the latest JavaScript features have not been a big advantage.
The cost of moving away from IE is a lot more, though. These old systems are strictly dependent on VB language, old Microsoft APIs, IE-specific JavaScript features and plugins such as ActiveObject, and IE quirks such as CSS layouts.
With few benefits and many costs, many large corporations have put off moving away from IE, and the number of employees using these systems can be thousands per company due to having often been implemented in very large corporations.
Edge has support for an IE mode. However, not only does this not have many differences from using IE instead, even if it is used, it is unclear how different statistics distinguish between Edge in IE mode, and IE, if at all.

Current and historical usage statistics

The current stats of IE are so low that they are often not included or bundled with Edge.

For example, in the “Web Browser Market Share” includes Internet Explorer with Edge, but in the “Top 10 Web Browsers” only Edge seems to be shown for Microsoft browsers. The others are generally Chrome and Safari.

Looking at the longest and latest and earliest ranges for NET MARKETSHARE:
4.08% for 2020-03 – 2022-02:
13.41% for 2016-05 – 2018-04:
In between those dates, show a steady decline.

Can I Use shows approximately a 0.7% usage rate for all IE versions combined:

stat counter shows a decline to 0.47% in February 2022.

As can be seen above, the recorded stats range widely, but they all show a steady decline.
It is likely that higher stats come from inaccuracies, desktop-focused datasets, countries using older technology, etc.

Support by Windows and important services

If you are interested in the current support status for Windows and important services such as Google, Twitter, YouTube, etc., then please check the following article:

IE support by Windows and important services

Why users should not expect support for IE

If you have read the sections above, you will have already seen just how little support IE has at this point.
However, from a manager’s perspective, a 1% increase in users may actually seem like a good opportunity to increase revenue by around 1%.
The problem with this logic is that the cost of maintaining support for IE is so high, and the returns will only decrease over time.
Even if you already support IE, this maintenance cost is still often too high to justify the additional revenue.
From the perspective of developers, having to maintain knowledge and code so different to what is currently used can be very time-consuming and so undesirable that it could risk developers choosing to leave instead,
and rightly so because if a developer is tasked with the coding on a dying language, they will be unprepared for future tasks and jobs using newer technology, resulting in a likely lower income.
There are some easy (if the code and build process is well maintained) actions developers can take, such as adding polyfills which may fix some issues, but full support for a dying browser is almost always not recommended.

How should developers handle IE?

Spending too much time and effort on IE support is often not worth the effort, but reporting why something is not working, and where to go, can be an effective way of handling unsupported environments.
1. As a last point of defence, adding sufficient information and non-breaking styles in non-JavaScript environments will keep a professional look and give users using unsupported environments a way to have access to your service and any necessary information.
2. Detect unsupported environments and add a banner for these environments instructing what browsers are supported and what to do. Even better, instead of detecting unsupported environments which are going to require JS, show a support banner by default and hide it when an allowed browser version is detected. Preventing showing while loading may require some techniques, and even using CSS quirks to hide on specific browser versions may be a solution.
3. Add polyfills. Check a library such as Babel.
4. Add conditional usage. For example, using and if conditional to detect for a class on the window object. This may be a bit time-consuming for more advanced sites, so as an alternative, try-catch blocks could be used.

How to drop IE support gracefully:


Google Search ends support for IE11:
A Business Case for Dropping Internet Explorer:
Information on the why, who, and how of the death of ie11. Also has a countdown to the end of service(less than 2 months at the time of writing):
Internet Explorer support for Japanese services (In Japanese):

IE support by Windows and important services in 2022

IE support by Windows and important services

This post describes the current (2022 May) support status of IE (Internet Explorer) for Windows, and other important services.

“The Internet Explorer (IE) 11 desktop application will end support for Windows 10 semi-annual channel starting June 15, 2022.”
Regarding Microsoft Edge with IE mode: “IE mode enables backward compatibility and will be supported through at least 2029”

Edge is installed by default from Windows 10, and IE is not even available in Windows 11.
Older versions of Windows can install Edge, and this differs on whether installing the newer Chromium builds or the older non-Chromium Edge builds.
Further information can be found here:

It looks like, as of some time at the end of 2020, IE has stopped working for many popular websites.
I can only assume that requires that Edge is installed so that would mean this wouldn’t be an issue on older versions of Windows (Windows 8 and less if Edge is not installed.), but I do not have an older version of Windows to check with.
“Microsoft will forcibly open some websites in Edge instead of Internet Explorer”:
The article shares a list of websites that require Edge:
I am not sure if this is the latest list or if it gets updated, so please look into it further if required.
Trying to load which is on the list, in IE11 on Windows 10 automatically loaded in Edge for me, so the above seems to be accurate.
Due to the above, it is actually very difficult to test for IE11 support because if you have Edge installed, most sites will redirect to Edge.

Looking at western sites from Alexa( and other ranking services, and ignoring any likely duplicates, I checked the following popular websites for IE support where clear info is provided:
From a post on Twitter on 2nd October 2021, it can be assumed that support for IE11 ended around the same time as the post for Google Search.
“YouTube no longer supports Internet Explorer.”:
“Starting in March, YouTube will cease their support of Microsoft’s Internet Explorer web browser.” posted on Feb 27, 2020, so I assume this means YouTube ended support during March 2020:
Twitter does not support IE, and it looks like unsupported user agents are blocked:
Yahoo seems to have been unsupported for a while, with many reporting an unsupported message: “You’re seeing Basic Mail because you’re using an unsupported Internet browser. Upgrade your browser for the full Yahoo experience.”
This does not mean it does not work at all.
A Japanese blog entry states that IE11 is not recommended for “Yahoo! JAPAN” starting from 7th September 2021:
Internet Explorer support ended by Amazon:
E-commerce sites such as Amazon choosing to miss out on potential sales by removing support for IE shows just how dead IE is.
GitHub does not support IE:
From this Tweet, it can be seen that GitHub stopped supporting Internet Explorer in July 2018:
Although IE does not seem to be a supported browser:
It does appear for the Silverlight plug-in here:
At the time of writing this article, support seems to exist for IE11 to IE7 for Silverlight 5.