Enter the text that you wish to encode or decode:
to get the link to the destination When the Web was born, only ASCII characters were used in links. However, with the advent of dynamically generated documents, PHP, and content management systems, the need to create unique URLs that could be handled by servers and browsers from text lines with non-ASCII characters or lines containing so-called reserved characters has emerged. URL Encoder and decoder were the answer.
Many modern content management systems and shop systems have sophisticated mechanisms to rewrite non-ASCII and reserved characters into characters that are permitted and unique in the URL. Other systems, on the other hand, rely on the use of a URL encoder internally, but to display a so-called speaking URL to human users. For the talking link to the right document, a decoder must translate the URL requested by the browser into a form that the web server can answer with the correct document. In order to avoid misunderstandings (and the URL leads to nowhere - ie to the 404 page), the rules which character is circumscribed must be unique. If the encoding is incorrect, the decoder will probably not understand the URL properly, and the web server will not return the correct document.
Spaces Usually, a space is the end of the URL string. But what if I want to automatically convert document titles that contain spaces to URLs? Fortunately, there is a detour: spaces are replaced by the string "% 20" after RFC3986.
Similarly, the so-called reserved characters, which have a particular function or meaning within a URL: The character # is usually a leap for reference to a particular location in a document; The question mark initiates a query part. If such characters do not have this function in a URL, they must be converted by an encoder in such a way that the browser does not misunderstand them as their reserved function and then request such a document in vain.
And last but not least, there are still non-ASCII characters, e.g. The German umlauts or the ß: also these can not be used directly (despite umlaut-Domains!) Not directly in a URL, but must be encoded.
Correct URL encoding also has an advantage for SEO: it makes it easier to use "speaking URLs", which are not only more appealing to (and easier to remember) for users, but also include the desired keyword and can thus send an additional rankingsignal. If the URL contains the keyword you're looking for, it will be bold in the search result ad in the URL. This results in a higher click rate compared to a URL without a keyword.
The URL decoder is the indispensable counterpart to encoding. In order for the machine to output the correct document, it must also understand the encoded URL - and the human visitor should be shown a clearly readable URL if possible. A reliable decoder is particularly important when non-ASCII characters occur regularly in automatically generated URLs - if it is not clear which encoding was used, a "%" in the decoded URL can become a "% F6". The seotoolsearch.com URL decoder helps you to determine whether a URL can be read out correctly from the encoding.