Generate OpenSearch XML description files for adding custom search to browser search bars.
An OpenSearch description file gives compatible browsers and search clients a machine-readable recipe for sending queries to one particular search service. Given a provider name, description, and search URL template, this generator formats those values as an OpenSearch XML document. Its output is a provider description, not a search page or a site search implementation. The detail most often missed is the literal `{searchTerms}` placeholder: the template must put it where the user's query belongs instead of containing a sample keyword or an empty query parameter.
The central value is the template attribute of an OpenSearch `Url` element. In `https://example.com/search?q={searchTerms}`, a client substitutes the user's encoded query for `{searchTerms}` when invoking the provider. Fixed query parameters can remain in the URL. The generated document describes that request pattern, but cannot determine whether the endpoint, parameter name, or declared response type is correct.
OpenSearch metadata belongs under the `OpenSearchDescription` root in the `http://a9.com/-/spec/opensearch/1.1/` namespace. The description contains human-readable provider fields and a `Url` declaration for search results. Because the template is stored in an XML attribute, a literal ampersand separating query parameters must be serialized as `&`; after XML decoding, the URL still contains `&`.
Start with a working results URL, but replace the sample search phrase with `{searchTerms}`. For example, turn `https://example.com/find?q=blue` into `https://example.com/find?q={searchTerms}`. If the search phrase appears in the path rather than a query parameter, replace that path segment instead. Leave required fixed parameters in place.
No. The generated document must be served from a reachable URL and made available to the intended client. A website can advertise it with an HTML `link` element using `rel="search"`, the description URL as `href`, and `application/opensearchdescription+xml` as the type. Whether users can discover or install it still depends on their browser.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.