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

Solving Doctrine - A new entity was found through the relationship

There are so many different problems that people have with the Doctrine error message: exception 'Doctrine\ORM\ORMInvalidArgumentException' with message 'A new entity was found through the relationship 'App\Lib\Domain\Datalayer\UnicodeLookups#lookupStatus' that was not configured to cascade persist operations for entity: Searching through the various online sources was a bit of a nightmare.  The best documentation I found was at  http://www.krueckeberg.org/  where there were a number of clearly explained examples of various associations. More useful information about association ownership was in the Doctrine manual , but I found a more succinct explanation in the answer to this question on StackOverflow . Now I understood better about associations and ownership and was able to identify exactly what sort I was using and the syntax that was required. I was implementing a uni-directional many to one relationship, which is supposedly one of the most simpl...
Post a Comment
Read more

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