Missing Charset Declaration
What This Means
No <meta charset="..."> element was found in the document's <head>, and no equivalent http-equiv="content-type" meta tag declaring a charset is present. The page has no explicit character encoding declaration.
Why It Matters for SEO
Without a charset declaration, browsers must guess the character encoding of the page using heuristic analysis of the byte patterns in the HTML. Most modern browsers default to UTF-8 when heuristics fail, which means many pages render correctly despite the missing declaration — but this is not guaranteed.
Pages with special characters (accented letters, currency symbols, quotation marks, non-Latin scripts) are most at risk from encoding misidentification. If a browser or crawler misidentifies the encoding, special characters render as garbled sequences (??, ’, etc.). The HTML specification requires the charset declaration, and its absence is a markup quality issue even when no visible rendering problem occurs.
What the Platform Checks
The platform scans the document <head> for a <meta charset="..."> element. It also checks for the older <meta http-equiv="content-type" content="text/html; charset=..."> format. Fires when neither form is found.
How to Fix It
Add <meta charset="UTF-8"> as the very first element inside <head>:
<head> <meta charset="UTF-8"> <title>Page Title</title> ...
UTF-8 is the recommended charset for all modern web content. The declaration must appear before the <title> element to ensure the title itself is correctly interpreted by the parser.
In most CMSs and frameworks, this is a template-level change — one fix to the base layout template applies across all pages.
Find every pagemissing a charset
The audit flags every page without a charset declaration — usually a single template fix resolves the issue across all pages.