7

Google is getting confused because while the page is ISO-8859-1, some content is loaded into the page in UTF-8. This causes Googlebot to have to re-encode the content page content as UTF-8 so that it can process it. Something is going wrong during that process and characters are getting mangled. For example, you use a JavaScript library for consenting to ...


2

So far i see, french diacritical signs are not a part of ISO-8859-1 (beside of apostrophe). The cache version of Google doesn't contain these characters. I see two workarounds: Encode the whole content as UTF-8 (would be the way i prefer) Encode diacritical signs as HTML entities. Example: séries becomes séries. This can be done in an editor like ...


2

Thus, instead of displaying >, the article displays >. This occurs (for me, at least) on Chrome, Firefox, and Safari (all latest versions with cache cleared). That is probably a software error where > was turned into > then that was turned into > by some kind of duplicate encoding. You can use "Control-U" to view the ...


1

There are five characters that should be escaped as entities in HTML documents, no matter which character set your website uses: < as &lt; > as &gt; & as &amp; " as &quot; ' as &#39; Other special characters always can be escaped with entities, but only need to be if you are using a character set that doesn't contain them....


Only top voted, non community-wiki answers of a minimum length are eligible