Thread

Hi all,

A few quick questions about the form tag encoder extension.

* Does this extension improve form security (e.g. from injection attacks), or is it just intended to disguise form information from spammers who would otherwise be able to automate comment spam?

* Use of this extension introduces a lot of encoding into the source code for a page. Because of our page layout, this is appearing between the article title and the article body text. Are there any implications for SEO from this much non-verbal content so prominently before keyword-rich content in the source code sequence?

Many thanks, hope someone has some insight.

R

RobJ25,

What is the full title of this extension. Is this from a third party developer. I am not familiar with it

Or are you referring to the encode variable?

Does this extension improve form security (e.g. from injection attacks), or is it just intended to disguise form information from spammers who would otherwise be able to automate comment spam?

The latter, making it more difficult for spam harvesters to grab an email address from your site

Are there any implications for SEO from this much non-verbal content so prominently before keyword-rich content in the source code sequence?

No I don’t believe there is. I have never seen anybody have any issues regarding the encode output and SEO

Hi John,

Thanks so much for the quick reply. I’m referring to the Form Tag Encoder extension:
http://ellislab.com/blog/entry/the_spammer_menace/

Rob - did you notice the following:

NOTE:  Requires ExpressionEngine 1.5.2. UPDATE: The Form Tag Encoder extension has been removed due to problems with Internet Explorer.