Character encoding not declared

Warning severity, in the Content tab

Why it matters

Without a charset in the header or a meta tag, browsers may misrender non-ASCII characters.

How to fix it

Declare charset=utf-8 in the Content-Type header and add <meta charset="utf-8">.

How Crawlune finds it

Crawlune flags Character encoding not declared automatically on every crawl and lists the affected URLs under the Content tab, where you can filter, inspect each page and export the list to CSV. The free version crawls up to 550 URLs with every check enabled.