search-engine-bots

remove pages from google dynamic url - robots.txt

落爺英雄遲暮 提交于 2019-12-24 18:06:12
问题 I have a few links on google that are domain.com/results.php?name=a&address=b The results page/parameters has now been renamed and I need to remove the existing links on google etc. I tried User-agent: * Disallow: /results.php in robots.txt and then on google webmaster added the url to be removed: domain.com/results.php it says it was removed successfully, however when I look at google an type domain.com - the existing urls with parameters are all still there. What am I doing wrong? There are

Are search-bots or spam-bots able to emulate/trigger JavaScript events?

喜欢而已 提交于 2019-12-22 17:58:44
问题 Are search-bot or spam-bots able to emulate/trigger JavaScript events while they read out the page? 回答1: No, because search bots fetch a static HTML stream. They aren't running any of the initialization events like init() or myObj.init() , which is in your JavaScript code. They don't load any external libraries like jQuery, nor execute the $(document).ready code nor any of the standard .click() listeners. So unless a search bot author has a specific reason to intentionally build their search

Allow search bots to crawl your sites without session IDs

断了今生、忘了曾经 提交于 2019-12-05 22:17:21
问题 Google's Webmaster guidelines state Allow search bots to crawl your sites without session IDs or arguments that track their path through the site. These techniques are useful for tracking individual user behavior, but the access pattern of bots is entirely different. Using these techniques may result in incomplete indexing of your site, as bots may not be able to eliminate URLs that look different but actually point to the same page. My ASP.NET 1.1 site uses custom authentication

Allow search bots to crawl your sites without session IDs

好久不见. 提交于 2019-12-04 04:10:55
Google's Webmaster guidelines state Allow search bots to crawl your sites without session IDs or arguments that track their path through the site. These techniques are useful for tracking individual user behavior, but the access pattern of bots is entirely different. Using these techniques may result in incomplete indexing of your site, as bots may not be able to eliminate URLs that look different but actually point to the same page. My ASP.NET 1.1 site uses custom authentication/authorization and relies pretty heavily on session guids (similar to this approach ). I'm worried that allowing non