{"id":5617,"date":"2010-12-28T21:05:49","date_gmt":"2010-12-28T21:05:49","guid":{"rendered":"http:\/\/jurnsearch.wordpress.com\/?p=5617"},"modified":"2010-12-28T21:05:49","modified_gmt":"2010-12-28T21:05:49","slug":"found-an-additional-way-to-auto-check-jurn","status":"publish","type":"post","link":"https:\/\/jurn.link\/jurnsearch\/index.php\/2010\/12\/28\/found-an-additional-way-to-auto-check-jurn\/","title":{"rendered":"Found an additional way to auto-check JURN"},"content":{"rendered":"<p>I&#8217;m pleased to say that I&#8217;ve found a robust way to auto-check if Google is still &#8220;seeing&#8221; content at the article-level URLs indexed by JURN.  It&#8217;s a software based solution, and is basically &#8216;dark side&#8217; SEO software that I&#8217;ve turned to the good side.  It auto-prepends the <strong>site:<\/strong> modifier to each of the URLs contained in the JURN index, and then checks if those URLs are actually indexed by Google.  It then logs any wholly un-indexed URLs.  It just chugs away in the background and is <em>very<\/em> slow &mdash; so as not to trigger flood-control blocking measures.  But it&#8217;s certainly better than doing the checking by hand.<\/p>\n<p>If you have such a list you want to check, it&#8217;s probably best to remove or cut back any URLs containing multiple wildcards such as \/*\/*\/.  Google has also been known to choke on URLs containing question-marks (it can see them as evidence of someone trying a scripting exploit on Google), although I don&#8217;t see this happening during the checking.  But if you&#8217;re doing the checking in blocks of 200, it&#8217;s not difficult to correct those sort of URLs first.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;m pleased to say that I&#8217;ve found a robust way to auto-check if Google is still &#8220;seeing&#8221; content at the &hellip;<\/p>\n<p><a href=\"https:\/\/jurn.link\/jurnsearch\/index.php\/2010\/12\/28\/found-an-additional-way-to-auto-check-jurn\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,10,12],"tags":[],"class_list":["post-5617","post","type-post","status-publish","format-standard","hentry","category-jurn-tips-and-tricks","category-my-general-observations","category-new-titles-added-to-jurn"],"_links":{"self":[{"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/posts\/5617","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/comments?post=5617"}],"version-history":[{"count":0,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/posts\/5617\/revisions"}],"wp:attachment":[{"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/media?parent=5617"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/categories?post=5617"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jurn.link\/jurnsearch\/index.php\/wp-json\/wp\/v2\/tags?post=5617"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}