{"id":323,"date":"2004-02-03T18:26:37-05:00","date_gmt":"2004-02-04T02:26:37+00:00","guid":{"rendered":"http:\/\/peterjanes.ca\/wordpress\/?p=323"},"modified":"2004-02-03T18:26:37-05:00","modified_gmt":"2004-02-04T02:26:37+00:00","slug":"sinker-swim","status":"publish","type":"post","link":"https:\/\/peterjanes.ca\/blog\/2004\/02\/03\/sinker-swim\/","title":{"rendered":"Sinker swim"},"content":{"rendered":"

Shortly after hitting a high result of hit #10<\/a> for sirens<\/cite>, the Sirens website<\/a> plummeted: first to hit #155, then to #376, and now out of the first 800 results. I’m at a loss to explain this: all of the pages on the site<\/a> are still in the index (including some I specifically told Googlebot not<\/em> to spider, but that’s another story) but Google refuses to show them in its search results. Could it be that the first rule of Google rankings is: you do not talk about Google rankings<\/q>? A little research says no, but that leaves me with no cause for the broken search and nothing I can do about it.<\/p>\n\n

This isn’t the only search I’ve seen behave similarly, but it’s the one closest to my heart. Fortunately, I’ve come across a tool that uses Google’s own algorithms to show that it’s an error on their side. Search Sinker<\/cite><\/a> returns Google searches to all their former Googly goodness. It seems that repeating words in a search string emphasizes them, so Sinker<\/cite> fills up the string with a term you deem most important: instead of sirens<\/samp><\/a>, it will look for sirens sirens sirens sirens sirens sirens sirens sirens sirens sirens<\/samp><\/a>. Using this technique, sirens3.com<\/a> appears in a (rightful?) place of hit #12… not bad considering the last thirty pages updated on the site haven’t even been crawled. It doesn’t solve the problem that the general public will never find the Sirens’ site, but at least now I know it’s not because of anything I’ve done.<\/p>\n\n

The so-called brandyupdate<\/cite> has put the Sirens back in a more reasonable place, at (appropriately for the date) #14.<\/ins><\/p><\/div>

<\/div>","protected":false},"excerpt":{"rendered":"Shortly after hitting a high result of hit #10 for sirens, the Sirens website plummeted: first to hit #155, then to #376, and now out of the first 800 results. I’m at a loss to explain this: all of the pages on the site are still in the index (including some I specifically told Googlebot…","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"mf2_syndication":[],"venue_id":0},"categories":[3],"tags":[],"kind":false,"_links":{"self":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/posts\/323"}],"collection":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/comments?post=323"}],"version-history":[{"count":0,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/posts\/323\/revisions"}],"wp:attachment":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/media?parent=323"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/categories?post=323"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/tags?post=323"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}