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.

Comments

  1. 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

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 glory in this demo.  

Fixing puppet "Exiting; no certificate found and waitforcert is disabled" error

While debugging and setting up Puppet I am still running the agent and master from CLI in --no-daemonize mode.  I kept getting an error on my agent - ""Exiting; no certificate found and waitforcert is disabled". The fix was quite simple and a little embarrassing.  Firstly I forgot to run my puppet master with root privileges which meant that it was unable to write incoming certificate requests to disk.  That's the embarrassing part and after I looked at my shell prompt and noticed this issue fixing it was quite simple. Firstly I got the puppet ssl path by running the command   puppet agent --configprint ssldir Then I removed that directory so that my agent no longer had any certificates or requests. On my master side I cleaned the old certificate by running  puppet cert clean --all  (this would remove all my agent certificates but for now I have just the one so its quicker than tagging it). I started my agent up with the command  puppet agent --test   whi

Redirecting non-www urls to www and http to https in Nginx web server

Image: Pixabay Although I'm currently playing with Elixir and its HTTP servers like Cowboy at the moment Nginx is still my go-to server for production PHP. If you haven't already swapped your web-server from Apache then you really should consider installing Nginx on a test server and running some stress tests on it.  I wrote about stress testing in my book on scaling PHP . Redirecting non-www traffic to www in nginx is best accomplished by using the "return" verb.  You could use a rewrite but the Nginx manual suggests that a return is better in the section on " Taxing Rewrites ". Server blocks are cheap in Nginx and I find it's simplest to have two redirects for the person who arrives on the non-secure non-canonical form of my link.  I wouldn't expect many people to reach this link because obviously every link that I create will be properly formatted so being redirected twice will only affect a small minority of people. Anyway, here's