Is blog commenting Good for SEO

Table of Contents

Blog commenting has been around for quite some time now, but it’s a tactic that is still heavily debated within

SEO circles today.

No one can seem to agree on whether or not blog commenting should be used as an SEO tactic in order to build links.

Some argue that since spammy and low-quality comments are so easy to leave, blog commenting is nothing more than link spam.

One thing that everyone can agree on is that most of the time blog comments are not really necessary for a website to rank, but if done right they can help boost your search traffic and exposure immensely.

When it comes down to whether or not you should be using blog commenting as an SEO tactic, there are many factors that will ultimately decide what is best for your website.

If you care about the integrity of your website and want to build long-lasting links that have a positive impact on your SERPs, it would be in your best interest to stay away from spammy blog commenting altogether.

However, if you are willing to put in the time and effort to blog comment responsibly then you can see quite a substantial boost in your website’s overall performance.

What to keep in mind while blog commenting?

  1. Get high-quality links from well-respected websites
  2. Dive into a new topic and learn before commenting
  3. Engage with people who are blogging about that subject you love
  4. Research before commenting to show your audience you’re serious

Have you seen Matt’s official response to “blog commenting links”?

Luckily for us, Matt Cutts has come out with an official video response to this question in his weekly hangout series. Watch the video below to find out what he says about links built through comments.

Conclusion

If you want to get a link, it’s important that your comment is from a high-quality domain. This way the webmaster will be more inclined to accept and publish your post in their blog or website. Comment below for any questions!

Picture of Hassan Khan

Hassan Khan

Posted:
Share: