- RikardsAsked on September 10, 2011 at 02:16 AM
I have test used your forms for a few months.
I used to be among the first 5 search results.
Suddenly jotform started to inject 100s to 1000s of "amp" into the embedded code.
This resulted in a keyword stuffing ban from google.
Ihave several times deleted the "stuffed" code and replaced it with a new "lean" form code.
Why does the code self incject "amp"?
How do I get rid of it and stop it from happening again?
- JotForm SupportliyamAnswered on September 10, 2011 at 03:12 AM
Can you share more details about the incident such as the form URL and some of the submission details? We would like to check your form.
We will wait for your response.
- RikardsAnswered on September 10, 2011 at 04:21 AM
I above ennough?
- JotForm SupportliyamAnswered on September 10, 2011 at 05:03 AM
Is the amp that you're referring to are those in the HTML code of your blog source code? I did not see any amp in your jotform submissions, that's why I asked. I believe this is actually & not just amp.
This happens when you are entering an actual code inside the WYSIWYG editor of your blog. As it changes all possible special HTML characters to HTML readable format, this includes all & signs to & code.
To resolve this, you should be editing your page in HTML source editor format (Normally using the icon [HTML]. See example image below).
Then enter the code that you wish to insert, including the link to your JotForm page. Once done inserting codes, you can get back to WYSIWYG editor format and then save your entry.
If you have other questions or concerns, please do let us know.
- JotForm SupportabajanAnswered on September 10, 2011 at 06:15 AM
This is all rather curious. When I looked at the source of your page, I saw the entities (which from what I can decipher translates to an empty paragraph, save for the break it encloses plus some extra ";amps" that make no sense to me) to which you were referring between the opening and closing tags of the iFrame. Knowing that neither they nor anything ought to be there, I logged in to your account and checked the iFrame code provided by the Embed Form Wizard for the form in question and there were no entities. So, I figured that perhaps their injection happens after the code is embedded. This was highly unlikely, as it was just a simple copy & paste procedure but I figured there was no harm in inserting the code into a page I use for testing embedded forms just to check what would happen. When I did that, as expected, the entities did not show up in the source. And when I viewed the page, the form was displayed okay.
So the question is, what is generating the said entities? They do not appear to be coming from our end. I'm wondering if it has to do with the fact that the doctype of your page is XHTML 1.0 Strict because iFrames are not legal in such pages. Is it feasible for you to use the solution provided on this page or perhaps just change the doctype to XHTML 1.0 Transitional? Also, could you describe in detail the procedure you follow to embed the code into the page? There may be something obvious that we're overlooking.
In the meantime, I'll try to find alternatives to the solution described at the link I gave.
- RikardsAnswered on September 11, 2011 at 12:06 AM
Wayne and Lyam,
Thank you very much for your answer and efforts in trying to replicate the problem.
The amps appears within the code for the jot-form (iframe, pasted in to the relevant pages on my site).
The amps multiply over time, so in one instance there were nearly 4000 amps.
I have just recopied the jot from code (opening and closing tags of the iFrame) and repasted into the relevant place on my site.
I already known and done what Lyam suggest in his second answer.
I copy the snippet provided by your site. I paste it in to the relevant place (in the html mode). Save.
They are ;amp, not &.
The amp are not there immediately after pasting but starts appearing over time.
The amp resides within the jot-form snippet on my pages.
The multiply over time (like a plague) within the jot-form snippet.
I would say the injections happens after the code is embedded and multiplies over time.
It seems as these pages got banned/killed because of keyword (keyword is amp) stuffing. This has a very serious impact of conversion rate. Now all search engine traffic is directed to my homepage before just about 30% had this as the primary landing page. The rest had a conversion page as the primary landing page.
Practically there are no conversions anymore.
So this is an exceptionally serious problem.
If I can't solve this very quickly I have to find an alternative to Jotform as the present problem totally kills conversion, and what good is a form if there is nobody there use it?
Is there any good alternatives?
I had not yet had a chance to try the solution Wayne suggests.
The doctype is given as:
I'm a novice, so what should I do?
- allanftdAnswered on September 11, 2011 at 04:13 AM
Have you made changes with your form? I inspected your website code and the "amp" words have decreased to those within the opening and closing <iframe> </iframe> tags.
Picking up from what Wayne has suggested, please remove any spaces or characters in between the the opening and closing <iframe> tags when you re-embed the form.
<iframe allowtransparency="true" src="//yang.interlogy.com:82/form/73553351213" frameborder="0" style="width:100%; height:781px; border:none;" scrolling="no"></iframe>
Also, it might help that you put comment tags in between the iframe tags, like this (highlighted):
<iframe allowtransparency="true" src="//yang.interlogy.com:82/form/73553351213" frameborder="0" style="width:100%; height:781px; border:none;" scrolling="no"><!-- --></iframe>
We hope these tips would help resolve the issue. Our apologies again for the inconvenience and thank you for your patience.
- omerAnswered on September 11, 2011 at 06:45 AM
My form was disabled... Don't know why, and to be honest, there should be a REASON shown when it is, and at least a notice in "my forms" with the reason.
Jotform Account Name : sakarya42 , neural11 neural99 neural54 , neural44 , sakarya44
all of them shut down in 5 minutes.. There was no problem with the first closed my account.All the accounts opened within 5 minutes, then shut down.If you want to back accounts. I'd like to correct this situation and
I would use this for the gaming forum I'm member (and server admin) from (www.fpsoverload.com). It would help us to let people upload demo's of cheaters so we can ban them... Don't see why it was suddenly disabled.
- JotForm SupportabajanAnswered on September 11, 2011 at 07:47 AM
Sorry to hear about your situation but as it is totally unrelated to the topic at hand, would you be so kind as to re-post your question in a new thread? (This forum does not currently have any way for staff to move posts to different threads.) Please post the question at http://www.jotform.com/answers/answer.php?
Thanks for understanding.
- JotForm SupportabajanAnswered on September 11, 2011 at 02:27 PM
Allan's suggestion about using comment tags has given me an idea. Since the entities and other amps are showing up between the opening and closing tags of the iFrame, try embedding one of these the self-closing equivalents of the said iFrame instead of the current opening and closing tag version and let us know if that helps (assuming Allan's fix hasn't already helped, of course).
Looking forward to hearing from you.
EDIT: On second thought, bad idea! There are issues associated with self-closing iFrames. For one thing, in Chrome they prevent anything after them from being shown. (Actually, that seems to be the case with all browsers.)
- RikardsAnswered on September 20, 2011 at 10:02 AM
Sorry busy schedule in other parts of my life.
I have now re-embedded the iframe according to Allan's instructions. We will wait and see if this stops the self multiplying amps.
Good news is Google Webmasters Tools don't list amp as a keyword anymore (last week I had keyword count for amp=8400, more then all other keywords together, this is what is called keyword saturation).
Thank you very much for all the help so far!
- JotForm SupportabajanAnswered on September 20, 2011 at 10:11 AM
Good to hear from you again. You can always keep us posted on if Allan's solution puts an end to those annoying multiplying amps!
P.S. I can definitely empathise with your having busy schedule in other parts of your life.
- RikardsAnswered on September 28, 2011 at 10:38 AM
I have now tried Allan's method over a period of time.
It doesn't help! Possibly it slowed down the self-distruct.
The form code still self-distructs by inserting amp and various other superflous material, which in the end will hurt Google ranks over time. It seems as the self distruct expontially increase over a long period of time.
Does this problem occur for anybody else?
- JotForm SupportliyamAnswered on September 30, 2011 at 01:45 PM
After visiting so many blogspot sites, I noticed that all of them inserts an & HTML ascii to all the pages that even URL paramters inside the code uses the HTML ascii. So I guess this is how it really works on blogspot.
If you have other questions or inquiries, please let us know.