No character set declared
WarningMedium priority
Parsed pages of this site that do not say which character set their text is in: no charset in the Content-Type header, no <meta charset> in the first 1,024 bytes, and no byte-order mark.
Why it matters
A browser then has to guess, and guesses differ: Safari reads such a page as Windows-1252, so a UTF-8 page's accents, currency signs and punctuation come out garbled — “café” as “café” — for visitors and for any crawler that renders the page.
How to fix it
Send Content-Type: text/html; charset=utf-8 from the server, and put <meta charset="utf-8"> first in the page's <head>, before anything else that holds text.
Skitter runs this check on every crawl, and lists each page it finds with the evidence: the header, the tag or the link that gave it away.