Should I do reciprocal linking on my site?

Reciprocal links are touch and go for a few reasons.

The reason that incoming links are good is that search engines think your site is worthwhile if humans are linking to it. In other words, if a webmaster reviews your content and links to it then your content must be good (thinks the search engine).

So people actively started to try and build links, to make search engines think that their content is good.

The only thing is that search engines hate it when you do things just to optimize your site for search engines. Optimize your site for users, while making it easy for search engines to see what it's about (this is where the bold, italics, page title and headings come in)

Search engines see reciprocal links as a distortion. The webmaster is not linking to you because your content is good, they're only linking to you because they're getting something in return (a link to their site, or even money). If you have a page of links that link to sites that are linking to you a search engine is going to realize that none of those links actually mean anything. They're going to think that you're trying SEO "tricks".

Google specifically warns against "excessive" reciprocal linking, but doesn't quantify this. So if you find a nice juicy site that insists on a reciprocal link then fine - give them a link from an article. Never create a page of reciprocal links to a whole bunch of worthless sites that are irrelevant, or have low page rank. Think how easy it would be for a search engine to spot this.

Google puts this a whole lot better than I can (in their Guidelines for Webmasters) when they say "make pages primarily for users, not for search engines. ... Don't participate in link schemes designed to increase your site's ranking or PageRank."

They expand on this when defining link schemes.

Two better alternatives to reciprocal linking are to use link bait and to submit your site to RSS aggregators. Don't go rushing off to build hundreds of reciprocal links to other sites. Rather spend your energy building your site into a great resource that people will want to visit (and link to).

By the way, to report a site that is using link spam you can use the Google tool: http://goo.gl/linkspam . If you can use this tool, then your competitors can use it on you too.

Comments

Using Fail2Ban to protect a Varnished site from scrapers

I'm using Varnish to cache a fairly busy property site. Varnish works like a bomb for normal users and has greatly improved our page load speed. For bots that are scraping the site, presumably to add the property listings to their own site, though the cache is next to useless since the bots are sequentially trawling through the whole site. I decided to use fail2ban to block IP's who hit the site too often. The first step in doing so was to enable a disk based access log for Varnish so that fail2ban will have something to work with. This means setting up varnishncsa. Add this to your /etc/rc.local file: varnishncsa -a -w /var/log/varnish/access.log -D -P /var/run/varnishncsa.pid This starts up varnishncsa in daemon mode and appends Varnish access attempts to /var/log/varnish/access.log Now edit or create /etc/logrotate.d/varnish and make an entry to rotate this access log: /var/log/varnish/*log { create 640 http log compress ...

Translating a bit of the idea behind domain driven design into code architecture

I've often participated in arguments discussions about whether thin models or thin controllers should be preferred. The wisdom of a thin controller is that if you need to test your controller in isolation then you need to stub the dependencies of your request and response. It also violates the single responsibility principal because the controller could have multiple reasons to change. Seemingly, the alternative is to settle on having fat models. This results in having domain logic right next to your persistence logic. If you ever want to change your persistence layer you're going to be in for a painful time. That's a bit of a cargo cult argument because honestly who does that, but it's also a violation of the single responsibility principal. One way to decouple your domain logic from both persistence and controller is to use the "repository pattern". Here we encapsulate domain logic into a data service. This layer deals exclusively with imple...

Grokking PHP monolog context into Elastic

An indexed and searchable centralized log is one of those tools that once you've had it you'll wonder how you managed without it. I've experienced a couple of advantages to using a central log - debugging, monitoring performance, and catching unknown problems. Debugging Debugging becomes easier because instead of poking around grepping text logs on servers you're able to use a GUI to contrast and compare values between different time ranges. A ticket will often include sparse information about the problem and observed error, but if you know more or less when a problem occurred then you can check the logs of all your systems at that time. Problem behaviour in your application can occur as a result of the services you depend on. A database fault will produce errors in your application, for example. If you log your database errors and your application errors in the same central platform then it's much more convenient to compare behaviour between...

Adventures in IT

Search This Blog