Comment to UNA 13.1
-
-
It's already set in UNA with the following metatag:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
moreover UNA sending encoding in HTTP headers, as suggested by Google documentation.
so I think this tool is broken since charset is provided using 2 ways, where one is exactly as recommended by their docs.
-
Thank you. Apparently yes, this is an error on their side, since I checked on different devices and the encoding is present everywhere.
-