Today, while looking at Google Webmaster Tools, I came across some 404 pages on Tweak And Trick. Being curious, I proceeded to see which pages Google reports as "Not Found" and I came across a strange URL; one which I have never seen associated with a Blogger blog. The URL which Google reported as not being found was as follows:-
- https://www.tweakandtrick.com/ related-content.g?q=
Note: This post was originally published in March 2011.
Update 2: Blogger has disallowed the related-content.g?q= page through robots.txt. It will no longer be anything worth worrying about.
When I checked on to see which pages linked to this page, I was surprised to see that almost all of the pages on this blog had links pointing to this page. As I did not remember placing such a link, I checked the source code of my blog. Strangely, I discovered a new bit of JavaScript added to it. The script which was added is as follows:-
Anyone looking at the names of the variables would understand that this code is for generating contextually related posts for blogger. So, this indicates that after launching mobile supported themes, Blogger development team is finally off to add another new and often demanded feature in Blogger, and gladly it is one that will help bloggers reduce bounce rate and display more appropriate related posts.<script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener("load", function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } function showRelatedContent() { var el = document.getElementById('related-frame'); if (el.style.visibility = 'visible') { return; } el.style.visibility = 'visible'; el.src = 'related-content.g?q=' /* insert URL here */; showRelatedContent.prevOnClick = document.onclick; // Hide related-content dropdown when clicking anywhere but on it. document.onclick = function() { var el = document.getElementById('related-frame'); if (el.style.visbility != 'hidden') { el.style.visibility = 'hidden'; } document.onclick = showRelatedContent.prevOnClick; }; } </script>
Investigating further, I have come to know that each blog hosted on Blogger has received this new bit of code implying that this feature would be made public any time soon.
Meanwhile, you can use the related posts widget I have employed here on this blog.
Steps:-
1. Just, copy and paste this CSS in your blog's template before </head>.
Note: If the code above gives errors while pasting in your Blogger template, then you will need to parse it for making it suitable for XML templates using any of the HTML to XML parser available online.
<b:if cond="data:blog.pageType == "item"">
<style type="text/css">
#related-posts{float:center;text-transform:none;height:100%;min-height:100%;padding-top:5px;padding-left:5px}
#related-posts .widget{padding-left:6px;margin-bottom:10px}
#related-posts ul{list-style-type:none;margin:0 0 0px 0;padding:0px;text-decoration:bold;font-size:12px;text-color:#000}
#related-posts ul li{background:transparent url(https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhI5c_U4WSzm5-ADvgwInRfmAOLq4-MTa20tXXjg0n9gajLhQ401KrEjg6UyftBMYO6QME1orQFmtG0fZmORkInCxZAqw5NLBt25JzaefeCt9oywLaUy9ux6x6WJ_RCGg11EXga0Ii6hNo/s200/greentickbullet.png)
no-repeat;display:block;list-style-type:none;margin-bottom:13px;padding-left:30px;padding-top:0px}
#related-posts .widget h2, #related-posts h2{font-size: 12px;font-weight: bold;margin-bottom:0.75em;margin-top: 0em;padding-top: 0em;}
</style>
<script type="text/javascript">
var relatedpoststitle="You might also like:";
</script>
<script type="text/javascript">var relatedTitles=new Array();var relatedTitlesNum=0;var relatedUrls=new Array();function related_results_labels(json){for(var i=0;i<json.feed.entry.length;i++){var entry=json.feed.entry[i];relatedTitles[relatedTitlesNum]=entry.title.$t;for(var k=0;k<entry.link.length;k++){if(entry.link[k].rel=='alternate'){relatedUrls[relatedTitlesNum]=entry.link[k].href;relatedTitlesNum++;break;}}}}function removeRelatedDuplicates(){var tmp=new Array(0);var tmp2=new Array(0);for(var i=0;i<relatedUrls.length;i++){if(!contains(tmp,relatedUrls[i])){tmp.length+=1;tmp[tmp.length-1]=relatedUrls[i];tmp2.length+=1;tmp2[tmp2.length-1]=relatedTitles[i];}}relatedTitles=tmp2;relatedUrls=tmp;}function contains(a,e){for(var j=0;j<a.length;j++)if(a[j]==e)return true;return false;}function printRelatedLabels(currenturl){for(var i=0;i<relatedUrls.length;i++){if(relatedUrls[i]==currenturl){relatedUrls.splice(i,1)relatedTitles.splice(i,1)}}var r=Math.floor((relatedTitles.length-1)*Math.random());var i=0;if(relatedTitles.length>1)document.write('<b>'+relatedpoststitle+'</b>');document.write('<ul>');while(i<relatedTitles.length&&i<20&&i<maxresults){document.write('<li><a href="'+relatedUrls[r]+'">'+relatedTitles[r]+'</a></li>');if(r<relatedTitles.length-1){r++;}else{r=0;}i++;}document.write('</ul>');relatedUrls.splice(0,relatedUrls.length);relatedTitles.splice(0,relatedTitles.length);}</script> </b:if>
2. Copy and paste the code below under <data:post.body/>. If there are more than one occurences of <data:post.body/> in your template and you are not aware of which one displays post body on individual posts, then you will need trial and error to find the right one.
<b:if cond='data:blog.pageType == "item"'>
<div id='related-posts'>
<b:loop values='data:post.labels' var='label'>
<b:if cond='data:label.isLast != "true"'>
</b:if>
<b:if cond='data:blog.pageType == "item"'>
<script expr:src='"/feeds/posts/default/-/" + data:label.name + "?alt=json-in-script&callback=related_results_labels&max-results=6"' type='text/javascript'/></b:if></b:loop>
<script type='text/javascript'>
var maxresults=5;
removeRelatedDuplicates(); printRelatedLabels("<data:post.url/>");
</script>
</div>
</b:if>
3. Save the template and apply the changes.
Reader Comments
I've been using the "Link Within" widget and have not detected any error... until this morning.
My latest run with Web Analytics now shows the "related-content.g?q=" error, in addition to a recently discovered "rpc_relay.html" error.
Is this something we can leave untouched until Google releases a similar widget like "Link Within"? :)
Hi teecup,
"rpc_relay.html" is not a new error. It is something I am quite familiar with and know that it is not much of an issue as it is nothing but an empty page. However, "related-content.g?q=" is quite a problem as it means that each page on our blogs links to non-existent 404 pages.
This is something we have to leave untouched as there is no way for blogs hosted on blogger to remove the scripts which Google inserts on its own. Lets just wait for an official confirmation and hope this error does not affect our rankings much.
Great! Thanks for the update. I appreciate it.
May I ask... How do I resolve an rpc_relay.html error? I'm not using Blogger's in-house related content feature but Linkwithin's.
Just like other problems on blogger, there is no way in which we can resolve this error. This is something that must be resolved by the Blogger Development Team. As a Blogger user, all you can do is simply ignore it. :)
I notice that problem also on mywebmaster account .
First i notice restricted by robot.txt (27) which are all my labels and ifootballvideo.blogspot.com/related-content.g?q= ( Detail (404) not found)under that are all my posts.It seems that everything on my blog is having problem and i also get lots of strange traffic from Mountain View.
Does anyone find some idea for resolving this,or whats going on ?
Cheers
The strange traffic you get is a common form of LOG spam which most bloggers, including me, face. I would advise you to use Google Analytics as it is less prune to this form of spamming.
The labels error you get is also normal and occurs only because Blogspot has blocked all its labels through robots.txt using:-
User-agent: *
Disallow: /search
This is also one of those unresolvable issues I hope Blogger did not have.
Regards
I have this kind of problem recently and it gets my nerve out of it considering that it affects my Analytic graph, that I am not receiving any visits at all. It also affects my Alexa ranking.
Thanks for the tutorial, despite being not a techy person I was able to manage it and I am crossing my fingers that it will have an effect.
BTW, how long would it take for the change to take effect? That I will be able to see some activity in my Analytics.
Hi there, I am afraid you are misunderstanding. The related posts widget I have given is just an option to show related posts until Blogger releases the official Related Posts and Media Search.
Also, the "related-content.g?q=" error has nothing to do with showing related posts in your blog using LinkWithin or any other provider (which many webmasters at Blogger Help Group misunderstood it to be).
Moreover, as you can see in the link I provided in the Update, it is official that Related Posts and Media Search is going to be released soon implying that the error is only temporary and will be resolved.
There is a blogger help forum thread starting about this here: http://www.google.com/support/forum/p/blogger/thread?tid=50d362505d17a88d&hl=en
I'm having the same problem. I think it's in the blogger template code.
Hi Nicole, your thread is not the only one out there. I have seen hundreds of similar threads on Blogger Help forums all begging for a reply to this 404 not found error.
You are not the only one having this problem, every blog that is hosted on the Blogger platform is experiencing the related-content.g?q= error. It is not in the template code. It is a server side script which gets inserted on its own when blog is loaded. Moreover, as far as I can tell, only Googlebot has been able to process this JavaScript as no other search engine displays this error for me.
Hi, Based on your update. Should we do anything about these crawl errors? Should we sit tight and let Google fix this?
Does your update mean that these errors do no have anything to do with a new "show related post" widget?
Thanks for your kind help!!
Hi Tess,
This problem has a solution. I have written about it here :-
http://tweakandtrick.blogspot.com/2011/04/related-posts-media-search-related.html
Regards
So, does that mean everything is going to be OK now that my robots.txt is:-
User-agent: *
Disallow: /search
Disallow: /related-content.g
Disallow: /related_content_helper.html
Apparently, it does.