Declare character encoding explicitly

10 min Impact: low Effort: low ✓ Scan-verified — no manual checkbox

The character encoding declaration tells the browser how to interpret the bytes of your page as actual characters — without a correct declaration (or with a mismatched one), special characters, accented letters, or symbols can render as garbled text (mojibake) instead of what you actually wrote.

Without an explicit charset declaration, browsers have to guess how to interpret your text — occasionally guessing wrong and rendering special characters as garbled text.

How to fix it

1

Add the charset meta tag

<meta charset="UTF-8"> should be the very first thing in your <head>, before any other meta tags.
2

Confirm your files are actually saved as UTF-8

The declaration needs to match reality — a UTF-8 declaration on a file actually saved in a different encoding still produces garbled output.
3

Check pages with special characters render correctly

Test a page containing accented characters, curly quotes, or symbols to confirm correct rendering.

Common mistakes

This needs to be one of the very first bytes of the document — placing it too late in the head after other content has already been parsed can cause the browser to have already made encoding assumptions.

How you'll know it's done

Every page declares UTF-8 as the very first item in the head, and special characters render correctly.

H.I.V.E. checks this automatically

Fix it, then re-scan — the check confirms itself. No manual checkbox, the scan is the truth.

Run this check in H.I.V.E. →

Declare character encoding explicitly

How to fix it

Common mistakes

How you'll know it's done

Related checks

H.I.V.E. checks this automatically