Melody Scott
asked on
Obfuscated mail to link showing as error on site map
Hi, on the header of my pages I have obfuscated text for my mailto link.
But then when I do a link check or a site map, I get an error. What can I do to avoid that?
<url>
<loc>https://www.magickitchen.com/menu/seniors-gifts/mailto&;</loc>
<lastmod>1970-01-01T21:09: 44+00:00</ lastmod>
<changefreq>weekly</change freq>
<priority>0.43</priority>
</url>
the code on the page is: <!-- googleoff: all-->
<a href='mailto:I%4EF O@% 2;DAG& #73;CK I%54&# 37;43H% 2;5 8;%2E%4 ;3O%4D '>IN&# 70;O@M AGI 7;KITC HEN 6;COM< /a>
<!-- googleon: all-->
But then when I do a link check or a site map, I get an error. What can I do to avoid that?
<url>
<loc>https://www.magickitchen.com/menu/seniors-gifts/mailto&;</loc>
<lastmod>1970-01-01T21:09:
<changefreq>weekly</change
<priority>0.43</priority>
</url>
the code on the page is: <!-- googleoff: all-->
<a href='mailto:I%4EF
<!-- googleon: all-->
I get an error
Show us the error message, please.
Have you tried to add a simple colon ':' after the mailto instead? like :
<a href='mailto:I%4EFO@%4DAGICKI%54%43H%45N%2E%43O%4D'>INFO@MAGICKITCHEN.COM</a>
ASKER
Zakaria Acharki This was the error.
<url>
<loc>https://www.magickitchen.com/menu/seniors-gifts/mailto&;</loc>
<lastmod>1970-01-01T21:09: 44+00:00</ lastmod>
<changefreq>weekly</change freq>
<priority>0.43</priority>
</url>
<url>
<loc>https://www.magickitchen.com/menu/seniors-gifts/mailto&;</loc>
<lastmod>1970-01-01T21:09:
<changefreq>weekly</change
<priority>0.43</priority>
</url>
Do you mean you're not getting the full link?
ASKER
Hi, all, I am trying this instead, then running the sitemap generator to see if it issues any errors. http://joemaller.com/js-mailer.shtml
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks! Zakaria, sorry I didn't get back to you. That was showing as a broken link, on both the sitemap generator and my link checker. Just running a link check now, and the new javascript seems to be ok.
ASKER
Thanks, the solution was to use different code, and lenamtl got the closest.
Glad we could help, happy coding.
Open in new window
Do note that it takes more than this to fool a modern bot. In the past some bots would not convert HTML entities, but now they do; defenses such as CAPTCHA became available and now bots are hungry for any valid email address. A better approach is a "email me" page protected by a CAPTCHA.