Not that a lot of sites get "digged", but this is a practice that was all the rage among Russian pornographerabout 5 years ago. They would frame blogs with great search rank like, ahh ... hmmmm ... culturektichen, in order to steal their "google juice".
Why oh why is Digg jumping on that bandwagon now? From Just Say No to Digg's DiggBar:
But let's explore the idea that Digg is just lying.
Think about it for a moment. You invest countless hours promoting your content. You get lucky enough to make the homepage of Digg, or you hit the Retweet motherload on Twitter. A certain percentage of all those people who see your content are going to copy & paste the link they land on into a blog post. (Thereby generating a link for your site).
Before the DiggBar, (and with legit shortening services) all those links would point to your url. Now, a large percentage of them are going to be links pointing to a page on Digg. Now if you are Yahoo, CNN, or the BBC, that isn't really going to matter much. You don't have to spend time thinking about building link equity, because you already have it. However, if you are a newer site struggling to build trusted link equity in the current black hole environment we live in, the mass adoption of the DiggBar is a serious issue.
I will be advising all clients to add some frame busting code to their sites so the DiggBar won't work for the simple reason that regarless which scenario is accurate, they are both equally wrong.
I've always made it a point to frame busting code on my site to make it impossible for other people to frame my site into theirs and steal my content wholesale --and I do the same for all the sites I develop.
And how do you do it?
Add the following script right before <HEAD> in all your blog templates:
<script type="text/javascript">
if(top.location != location) {
top.location.href = document.location.href;
}
</script>
UPDATE: John Gruber over at Daring Fireball has a way to block framing with PHP scripting:
Most pages on DF are served through PHP, so I added a short bit of PHP near the top that looks like this:
<?php
if (preg_match('#http://digg.com/\w{1,8}/?$#',
$_SERVER['HTTP_REFERER']) ) {
echo "<p>Special message for Digg users here.</p>";
exit;
}
?>The first line uses a regular expression to check if the HTTP referrer looks like a DiggBar URL, which, for my purposes, I’ve defined as “digg.com/” followed by exactly 1-8 letters or numbers and an optional trailing slash. It doesn’t attempt to block all referring URLs from Digg, just those that look like DiggBar pages. If the pattern matches, it prints a special message for Digg users and calls PHP’s standard exit function, which stops the rest of the page from being transmitted.
Some sites use JavaScript to completely block framing; I don’t want to do that, and, given DF’s configuration, it was easier for me to use PHP to target Digg specifically.
Am torn now because with my sites, I've had the Russian pornographer problem for years, so I have to disallow ALL framing. Will experiment with both techniques and report later.
Post new comment