Charset encoding problems

This report lists all pages that contain incorrect or inconsistent charset encoding specifications. This is the case, for example, if the charset encoding specified in the HTTP header is different from the one specified in the meta tags of the HTML page.

Why you should ensure correct and consistent charset encoding information:

Charset encoding tells web browsers, search engines, and other clients which character set is used on a webpage. This ensures that letters, numbers, and other characters can be interpreted and displayed correctly.

If the charset encoding declared does not match the charset that's actually used, or if there's conflicting charset information, browsers may not be able to display the content of the page correctly, and search engines may also have difficulties analyzing it.

What the notes in the 'Problem' column mean:

• Encoding is not specified: The page does not specify a charset encoding.
• Wrong HTTP Equiv: A charset specification was found on the page, but it contains errors.
• Specified character encodings do not match: The charset information in the HTTP header and the meta tags of the page do not match.

The 'Encoding' column will give you more details about the charset specifications found on the page.

How to fix the problems found:

Check the charset details on the affected pages and add any missing specifications or make sure that there's no conflicting information.

Ideally, the charset encoding should already be specified in the HTTP header, so browsers can immediately display the page with the correct encoding, rather than having to analyze the HTML code to determine the encoding.

For example:

Instead of just specifying "text/html" in the HTTP header:

Content-Type: text/html

you should set the following header with charset details:

Content-Type: text/html; charset=utf-8