If you are struggling to get buy-in for such a change, investigate if the URLs in question are being escaped properly, and if users or search engine crawlers are having issues accessing them. We recommend that you don't use non-ASCII characters in URLs, so if possible move to a system that does not use them. This Hint is a 'Potential Issue', which means that it is unlikely to be affecting the site at the moment, but should be investigated as it could cause issues in the future. Why is this Hint marked 'Potential Issue'? Here are a range of examples that would trigger this Hint: This Hint will trigger for any internal URL which contains non-ASCII characters. when your monitor term is google, the monitoring system will find the following examples. This is dangerous as you cannot be certain how search engines or browsers will handle these characters, which could cause unwelcome results if there are issues with the encoding procedure (when the URL contains characters that have not been escaped, they need to be encoded by browsers and search engine crawlers). PhishEyes Monitor will surface non-ASCII characters (i.e. This means that the URL in question contains characters outside the ASCII set. This Hint is unlikely to be affecting the site at the moment, but should be investigated as it could cause issues in the future. In UTF-8, ASCII characters get 8-bit codes- in fact, an ASCII character has the same encoding in UTF-8 and in ASCII- but other characters get longer codes, adding on 8 more bits at a time. For example, removing non-ASCII characters from a string with. The most popular one is called UTF-8 (UTF means 'Unicode Transformation Format' and 8 is the number of bits it takes to encode a standard ASCII character). This Hint is of the lowest significance, and should only be addressed if there are not more serious issues which have not been handled. Removing non-ASCII characters results in a string that only contains ASCII characters.

What are non ascii characters