WordPress Auto Tag Plugin – TagPiG

tagpig-box-small-reflectionToday I’m excited to announce the launch of TagPiG 2.1 our WordPress Auto Tag plugin.

This is the first paid version of TagPiG we’ve released and as you’d expect there are a bunch of great new features:

  • Archive Tagging – Now you can have TagPiG auto tag you all your existing posts as well as new one
  • New Tag Sources – We’ve added the Open Calais API to the list of text extractors with the option to include social & topic tags
  • Preferred Tags – You can create you own list of word that should always be tagged if they appear in a post regardless of whether the TagPiG chooses them
  • Tag Now Button – If you’re not running your blog on auto you can now manually tag posts using a new button within the edit post screen

TagPiG really can help your blog get indexed deeper and faster by the search engines. Remember every new tag you create equals a new page on your blog. TagPiG can auto tag more than 50 tags per post!

You can try TagPiG out right now with our new seven day trial.

See exactly how Auto Tagging with TagPiG can help your blogs….

Tags: , , , , , , , ,

Facebook Comments:

Leave A Reply (3 comments So Far)


  1. Murof
    522 days ago

    I need a "tag plugins" that work automatically with custom text long. I only want use (minimum) 2 words.

    I know, there are many auto tag plugins, but I'm confused with all of them. They all appear 1 word tags. I dont like it.

    I need a tag plugins with minimum words to use as tag = 2 words.

    Does this plugin can help me?


  2. Rick Lomas
    437 days ago

    Your page http://blogpig.com/products/tagpig/ seems to be a bit broken today – it says:
    The page isn’t redirecting properly
    Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
    * This problem can sometimes be caused by disabling or refusing to accept cookies.

    I also tried it in Chrome and Safari too, they don’t work either.
    Rick


    • fiona
      436 days ago

      Thanks, Rick! We’ve fixed the page. It was down to user error (that user being – ahem – me).