HTML encoded or decoded?

HI all, I have a simple question


The question is about encoding ort not the HTML content in my web
pages, in order to make them SE friendly.

I mean, I have an spanish version of my web site...then ...should I use
the HTML-encoded function to "encode" the special characters?..like
Guía de Turismo or can I use the decoded way "Guía de Turismo"

Can the SE (google, MSN, yahoo)..deal without problems with accents and
special characters (like: ñ)...in the body, Title, keywords...etc of
my HTML pages ???


Thanks for your help

Alberto

On Fri, 03 Mar 2006 13:59:25 +0100, Gordowey <albertoiriarte (AT) gmail (DOT) com>
wrote:

I mean, I have an spanish version of my web site...then ...should I use
the HTML-encoded function to "encode" the special characters?..like
Guía de Turismo or can I use the decoded way "GuÃ*a de Turismo"

Can the SE (google, MSN, yahoo)..deal without problems with accents and
special characters (like: ñ)...in the body, Title, keywords...etc of
my HTML pages ???

Use proper encoding (like UTF-8) and your pages will be spidered and
indexed correctly. No need for &#number; tricks.

Best,
Borek
--
http://www.chembuddy.com
http://www.bpp.com.pl

thanks all for your help!

"canadafred" <canadian_web (AT) hotmail (DOT) com> wrote:

I want the browser to get, for example :

é

My question is what character below is more SE friendly, which of the
three would be the best to use in the html content.

&#233
&eacute
é

Doesn't matter, they are equivalent (if you use the right character set).
The easiest for you is to use the latter. When a bot processes the HTML it
*should* decode the entities (é &eacute; ) to the right character and
all major search engines do this. (Note that the ; is required after the
entities).

--
John Experienced (web) developer: http://castleamber.com/

Perl RSS Builder: http://johnbokma.com/perl/rss-web-feed-builder.html

"John Bokma" <john (AT) castleamber (DOT) com> wrote

"canadafred" <canadian_web (AT) hotmail (DOT) com> wrote:

I want the browser to get, for example :

é

My question is what character below is more SE friendly, which of the
three would be the best to use in the html content.

&#233
&eacute
é

Doesn't matter, they are equivalent (if you use the right character set).
The easiest for you is to use the latter. When a bot processes the HTML it
*should* decode the entities (é &eacute; ) to the right character and
all major search engines do this. (Note that the ; is required after the
entities).

--
John Experienced (web) developer: http://castleamber.com/

Perl RSS Builder: http://johnbokma.com/perl/rss-web-feed-builder.html

Ok, thanks man. Got it.

--

Fred canadian_web (AT) hotmail (DOT) com
Ethical SEO Tips, Tools and Resources
www.rezultz-web-site-promotion.com

Search engines usually convert any "foreign" characters (variations of
the same letter) as the root letter. For example ñ will be transformed
to n. If your browser can render the characters, search engines will
use them too.

On Sat, 04 Mar 2006 04:45:01 +0100, canadafred <canadian_web (AT) hotmail (DOT) com>
wrote:

I'm glad we are discussing this. I'm working on some French web sites
and I
have a question. I understand to use of the : <meta
http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> tag in
this case.

I want the browser to get, for example :

é

My question is what character below is more SE friendly, which of the
three
would be the best to use in the html content.

&#233
&eacute
é

I would go for UTF-8 - no tricks needed, é displayed both in code and on
pages.

Best,
Borek
--
http://www.chembuddy.com
http://www.bpp.com.pl

sorry to disturb you again, but I still have some questions

I have set upt a simple page to test the character set,

http://www.madridinfosite.com/teste.aspx

When I browser this page, all is ok. But when I use a "Search Engine
Simulator" to see how the SE see my page...all the text is not properly
decoded

Please try my "test page" at:
http://www.1-hit.com/all-in-one/tool...ine-viewer.htm ,

What I am doing wrong? I have set up the <meta
http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
in my aspx page, I have also tried with the UFT-8 code...but nothing
changes?

Should I be worry about this SE simulating tools, or no?

any help would be apreciated...., thanks

Borek <m.borkowski (AT) delete (DOT) chembuddy.these.com.parts> wrote:

I would go for UTF-8 - no tricks needed,

Same for ISO-8859-1

é displayed both in code and
on pages.

Same for ISO-8859-1

--
John isa Perl programmer: http://johnbokma.com/perl/perlprogrammer.html

Fox G Bar: http://johnbokma.com/firefox/google-...stomizing.html

On Sat, 04 Mar 2006 17:18:31 +0100, John Bokma <john (AT) castleamber (DOT) com>
wrote:

I would go for UTF-8 - no tricks needed,

Same for ISO-8859-1

é displayed both in code and
on pages.

Same for ISO-8859-1

Yes. The reason I prefer UTF-8 is that with ISO you can't mix characters -
for example you are not able to quote both Polish and Spanish text in the
same document, or French and Czech. While in many cases that's not a
problem I prefer solution that is as easy as ISO - but not restricted.

Best,
Borek
--
http://www.chembuddy.com
http://www.bpp.com.pl