Docs SEO
Character encoding
Checks that your homepage declares its character encoding, so browsers show accents and symbols correctly.
What it checks
It passes when the HTML has a <meta charset> tag or an older http-equiv tag with charset=, or when the Content-Type response header includes charset=.
- PassAn encoding is declared in the HTML or the header.
- WarningNo encoding declared.
Why it matters
Without a declared encoding, the browser has to guess. A wrong guess turns accented letters, currency signs and curly quotes into strings of odd symbols.
How to fix it
Declare UTF-8. Put the meta charset tag first inside the head, before the title, or set the charset in the Content-Type header from your server.
Platform notes
Almost every CMS and framework does this. A missing charset usually means hand-written or old HTML.
Nginx can add it with the charset utf-8 directive. Apache can with AddDefaultCharset UTF-8.
Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.
Free, about 30 seconds, with every other check included.