Skip to main content

Product suppliers can also provide backlinks

Search engines reward websites that are well linked. Search engines operate under the assumption that if many other websites link to yours then that reflects a measure of trust and value in your site content. This means that building up these links to your website is an important task for any website owner.

Finding relevant sites to approach for a backlink can be a difficult prospect.

Reciprocal linking


Many reciprocal link exchanges end up being an exercise in spam management as completely inappropriate sites approach you for a link. Reciprocal linking is actually a risky affair. Google specifically warns against creating pages for reciprocal linking in its Webmaster guidelines. It's pretty obvious why reciprocal linking is discourage - it is an articifical distortion of a person's desire to link to your content. They're not linking to you because you have valuable content, they're linking to you in exchange for a favour.

One way links


Clearly one way links are much more desireable, but where can you find people willing to do this?

One place to look is to approach all of your business suppliers. You've probably built up a relationship with them and having them link to your website will just be a reflection of this relationship. Remember that if your website is relavent to their users they should be willing to link one-way to you.

One way that people suggest as a way to get a backlink is to provide a testimonial in which your link appears. Your supplier can then place the testimonial on their site and provide a link to you.

Who are your suppliers? It may take a little digging to identify all of your suppliers but the potential reward of relevant backlinks should be enough to motivate you to picking up the phone.

If you'd like to find out more about SEO please feel free to contact me.
Labels:

Comments

  1. albina N muro1 September 2013 at 14:24

    Search engines reward websites that are well linked. Search engines operate under the assumption that if many other websites link to yours then that reflects a measure of trust and value in your site content. buy blog comment links

    ReplyDelete

Post a Comment

Popular posts from this blog

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 ...
Post a Comment
Read more

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...
Post a Comment
Read more

Separating business logic from persistence layer in Laravel

There are several reasons to separate business logic from your persistence layer.  Perhaps the biggest advantage is that the parts of your application which are unique are not coupled to how data are persisted.  This makes the code easier to port and maintain. I'm going to use Doctrine to replace the Eloquent ORM in Laravel.  A thorough comparison of the patterns is available  here . By using Doctrine I am also hoping to mitigate the risk of a major version upgrade on the underlying framework.  It can be expected for the ORM to change between major versions of a framework and upgrading to a new release can be quite costly. Another advantage to this approach is to limit the access that objects have to the database.  Unless a developer is aware of the business rules in place on an Eloquent model there is a chance they will mistakenly ignore them by calling the ActiveRecord save method directly. I'm not implementing the repository pattern in all its ...
Post a Comment
Read more